Connecting to existing database domains
This section describes how to share a database domain between two
separate WebSphere Portal Express instances (instance1 and instance2),
where instance2 is connected to a instance1 database
domain.
A WebSphere Portal Express instance can
be either a single server or WebSphere Portal Express cluster.Notes:
- Release data cannot be shared between separate WebSphere Portal Express instances.
- Note: You can only share WebSphere Portal Express Version
6.1 data.
Both WebSphere Portal Express instances
must be installed and operational.
- Verify that both WebSphere Portal Express instances
are operational.
- 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.
- 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.
- Reconfigure instance2 to
use one or more remote database domains of instance1 by
running the following command from the Windows directory portal_server_root/config Linux directory portal_server_root/config i5/OS directory portal_server_root_user/config:
- Windows: WPSconfig.bat
connect-database -DActDbDomainList=domain1,domain2,domain3
- Linux: ./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 Express is installed; for
example, wp_profile
- Restart instance2
Parent topic: Configuring WebSphere Portal
|
|
|