Database sharing between multiple clusters



Search Tips   |   Advanced Search


There are multiple database domains that are used in a typical WebSphere Portal environment, such as the release domain, customization domain, and community domain. In most cases, the relevance of data within these domains is WebSphere Portal specific.

In other words, different database domains are used for different configurations, because the application mix and user community is likely different. In many cases, you may want to support multiple identically configured WebSphere Portal installations in the same cell, where many of the database domains might be shared, for ease of maintenance or failover.

In the case that two independently configured clusters exist within the same cell, each cluster should have its own set of database domains.

In the case that two clusters configured identically exist within the same cell, all database instances should be shared except the release and JCR database domain. This ensures that all user-specific and community data is shared between clusters, while each cluster’s static configuration can be independently updated.

Special Database Considerations when Sharing Domains

Based on your configuration case, determine which database domains you want to share with other clusters which reside in the same cell (multiple cluster environment).

JCR domains and release domains cannot be shared between different Web Content Management clusters or servers. Each distinct cluster or server in your WCM system must use a separate JCR or release domain.

For example:

Development Server Authoring Cluster Staging Server Delivery Cluster
JCR Domain 1 JCR Domain 2 JCR Domain 3 JCR Domain 4
Release Domain 1 Release Domain 2 Release Domain 3 Release Domain 4

Assign the data source names for the domains based on which databases should be shared between the clusters and which should be unique per cluster. A single data source cannot be used for multiple domains if the domains are a mixture of shared and non-shared.

Maintain the same number of data sources with identical names in the case where enterprise applications are to be shared across all clusters in the same cell, so that data source bindings in the applications can be resolved on every cluster in which they run.

When installing the primary node of the next cluster (Cluster B), the node can be configured to use the shared database domains by setting the appropriate property values in the file.

Parent topic:

Plan for multiple clusters