Connect to existing database domains

We can 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.

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

• We can only share WebSphere Portal v8.0 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. To connect or transfer a single database domain, you should 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. Ensure that the database client software is installed on instance2 using the same settings as instance1 and that we 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_dbdomain.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...
   cd WP_PROFILE/ConfigEngine
   ConfigEngine connect-database -DTransferDomainList=domain1,domain2,domain3 -DWasPassword=foo

5. Restart instance2.

Parent: Configuring