Portal, V6.1

---

 

Connecting to existing database domains

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.Notes:

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

• You can only share WebSphere Portal V6.1 data.

• The entire set of database properties specified in the file WP_PROFILE/ConfigEngine/properties/wkplc.properties must be valid for the current configuration of all database domains. If you plan 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 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 WebSphere Portal. 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 WP_PROFILE/ConfigEngine :

   • Windows:

     ConfigEngine.bat connect-database -DTransferDomainList=domain1,domain2,domain3

   • UNIX:

     ./ConfigEngine.sh connect-database -DTransferDomainList=domain1,domain2,domain3

   • i5/OS From the UserData directory:

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

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

5. Restart instance2

 

Parent topic

Configure WebSphere Portal

 

Related concepts

Configuration task properties
Planning for IBM Tivoli License Compliance Manager
Configure portal behavior

 

Related tasks

Configure security
Configure search in a cluster
Set a remote spellchecker
Adding features to an administration installation

 

Related reference

Prerequisites for Document Conversion Services

---