Replication domain collection
Configure a list of replication domains used by the following components: Session Manager for session failover, EJB for stateful session bean failover, SIP for failover, and dynacache for cache replication. All components that need to share information must be in the same replication domain. Data replication domains replace multi-broker replication domains that were available for replication in prior releases. Migrated application servers use multi-broker replication domains which are collections of replicators. We should migrate any multi-broker replication domains to be data replication domains.
From the admin console, click...
Environment > Replication domains
Name for the replication domain. The name of the replication domain must be unique within the cell.
Following are the two types of replication domains:
Domain type Information Multi-broker domain Replication domain created with a previous version of WebSphere Application Server. This type of replication domain consists of replicator entries. Support of this type of domain remains for backward compatibility, but is deprecated. Multi-broker and data replication domains do not communicate with each other, so migrate any multi-broker replication domains to the new data replication domains. We cannot create a multi-broker domain or replicator entries in the administrative console after the deployment manager is upgraded to the current version of WAS. Data replication domain Replication domain created with the latest version of WAS. If the deployment manager has been upgraded to the latest version of WAS, we can create data replication domains only. With the data replication domain, we can specify a number of replicas instead of statically partitioning your replication settings. Specify a data replication domain for each consumer of the domain, for example, two separate domains for dynamic cache and session manager. Migrate servers from multi-broker replication domains to data replication domains Data replication domain settings