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 an instance1 database domain. A WebSphere Portal instance can be either a single server or WebSphere Portal cluster.

• Release data cannot be shared between separate WebSphere Portal instances. Also, if WCM is installed, the JCR domain cannot be shared.

• We can share only the WebSphere Portal v8.5 data.

• The entire set of database properties specified in the file...
  WP_PROFILE/ConfigEngine/properties/wkplc_dbomain.properties

  ...must be valid for the current configuration of all database domains. If we plan to connect or transfer a single database domain, modify only the database properties for that domain before running the connect-database or database-transfer tasks.

Both WebSphere Portal instances must be installed and operational.

1. Verify that both WebSphere Portal instances are operational.

2. Verify the database client software is installed on instance2 with the same settings as instance1 and we can connect to the remote database.

3. The instance2 data sources must be made to point to the database used by instance1. The wkplc_dbtype.properties and wkplc_dbdomain.properties files must be updated to specify what remote database is used. This information must match the database information used for the instance1 installation.

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

4. Reconfigure instance2 to use one or more remote database domains of instance1
   WP_PROFILE/ConfigEngine:
   ./ConfigEngine.sh connect-database -DTransferDomainList=domain1,domain2,domain3 -DWasPassword=foo

5. Restart instance2.

Parent Database Management Systems