+

Search Tips   |   Advanced Search


Connect to existing database domains

View the steps to share a database domain between two separate WebSphere Portal instances (instance1 and instance2), where instance2 is connected to a instance1 database domain.

A WebSphere Portal instance can be either a single server or WebSphere Portal cluster.Notes:

The wkplc.properties, wkplc_comp.properties, and wkplc_dbtype.properties are published in the WebSphere Portal wiki.

The wiki articles include examples, valid values, and descriptions to help you determine what value to provide for a given property.

The documentation team and other IBM teams will update the properties to provide more examples and clarity as needed.

For the most up-to-date information about properties, such as examples, valid values, and more, see the following wiki articles:

Both WebSphere Portal instances must be installed and operational.

  1. Verify that both WebSphere Portal instances are operational.

  2. Ensure that the database client software is installed on instance2 using the same settings as instance1 and that you can connect to the remote database.

  3. The instance2 datasources must be made to point to the database used by instance1.

    The wkplc_dbtype.properties and wkplc_comp.properties files must be updated to specify what remote database will be used. This information should match the database information used for the instance1 installation.

    Do not use the same datasource names for the domains used in the previous version of the product. Use a different datasource so that the connect-database command will drop the old datasource and create the new one with the new connection information.

  4. Reconfigure instance2 to use one or more remote database domains of instance1 by running the following command from the directory profile_root/ConfigEngine :

      Windows: ConfigEngine.bat connect-database -DTransferDomainList=domain1,domain2,domain3 -DWasPassword=password

      UNIX: ./ConfigEngine.sh connect-database -DTransferDomainList=domain1,domain2,domain3 -DWasPassword=password

    • i5/OS From the UserData directory:

      • ConfigEngine.sh -profileName profile_root connect-database -DTransferDomainList=domain1,domain2,domain3 -DWasPassword=password

      where profile_root is the name of the WAS profile where WebSphere Portal is installed; for example, wp_profile. password is the WAS password.

  5. Restart instance2


Parent topic:

Configure WebSphere Portal


Related concepts


Configuration task properties
Configure WebSphere Portal with the configuration wizard
Configure portal behavior
Configure IBM Tivoli License Compliance Manager


Related tasks


Changing the portal URI
Manage the user registry
Configure Web Content Management
Set up a remote spell checker
Enable Document Conversion Services
Add features to an administration installation
Activate SSL and FIPS


Related information


Additional security features