Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows
Sharing database domains between clusters
To help provide redundancy and failover support in production environments composed of multiple clusters, you can share database domains between those clusters.
IBM® WebSphere® Portal Express data is organized into different database domains, with different availability requirements depending on how the production environment is set up. When multiple lines of production are involved and each line of production is implemented as a cluster of servers, sharing database domains ensures that the data is automatically synchronized across the lines of production.
These instructions describe how to share database domains when setting up an environment with multiple clusters.
- Set up the first cluster (referred to as Cluster A in these instructions).
When installing the first cluster, follow the instructions in Setting up a cluster.
- Determine which database domains you want to share with any other clusters in the environment.
- Install the primary node of the next cluster (Cluster B), and configure the node to use the shared database domains.
The steps for installing an additional cluster are the same as the steps for installing the first cluster, with one important exception. Instead of performing a complete database transfer after installing WebSphere Portal Express on the node...
- Perform a partial database transfer of the database domains that you are not sharing.
For example, if you are sharing only the Customization and Community domains, you would transfer the remaining domains to the database you are using for Cluster B, as described in Transferring individual domains.
- Reconfigure the shared database domains on the node to connect to the shared database domains you are using for Cluster A.
For example, to connect to the Customization and Community domains for Cluster A, you would connect to those domains from Cluster B, as described in Connecting to existing database domains.
- Perform a partial database transfer of the database domains that you are not sharing.
- Continue setting up the primary node as described in the cluster instructions.
- Install the secondary node of Cluster B, and configure the node to use the shared database domains.
When installing the secondary node, instead of connecting the node to the entire database used by the primary node...
- For those database domains that you are not sharing between clusters, reconfigure the domains to connect to the database domains you are using for Cluster B.
As in the example for the primary node, if you are sharing only the Customization and Community domains, reconfigure the remaining domains on the secondary node to use the domains of the primary node for Cluster B, as described in Connecting to existing database domains.
- Reconfigure the shared database domains on the node to connect to the shared database domains you are using for Cluster A.
For example, to connect to the Customization and Community domains for Cluster A, you would connect to those domains from Cluster B, as described in Connecting to existing database domains.
- For those database domains that you are not sharing between clusters, reconfigure the domains to connect to the database domains you are using for Cluster B.
- Continue setting up the secondary node as described in the cluster instructions.
Parent topic:
Clustering and WebSphere Portal ExpressRelated concepts
Planning considerations Transferring individual domains
Related tasks
Connecting to existing database domains