This section describes how 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.
Connect to existing database domains
Notes:
- Release, LikeMinds, and Feedback data cannot be shared between separate WebSphere Portal instances.
We can only share WebSphere Portal Version 6.0 data.
Both WebSphere Portal instances must be installed and operational.
- Verify that both WebSphere Portal instances are operational.
- 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.
- The instance2 datasources must be made to point to the database used by instance1. The wpconfig_dbtype.properties and wpconfig_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. Refer to Configuring for WebSphere Portal for more information.
- Reconfigure instance2 to use one or more remote database domains of instance1 by running the following command from the Windows and UNIX directory portal_server_root/config, or thei5/OS directory portal_server_root/config:
- Windows: WPSconfig.bat connect-database -DActDbDomainList=domain1,domain2,domain3
UNIX:
./WPSconfig.sh connect-database -DActDbDomainList=domain1,domain2,domain3
- i5/OS : From the UserData directory:
- WPSconfig.sh -profileName profile_root connect-database -DActDbDomainList=domain1,domain2,domain3
where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile
- Restart instance2
Related Information
Parent topic:
Configure databases
Related tasks
Share database domains between clusters