Replication domain collection
To view the configured replication domains used by the HTTP session manager, dynamic cache service, and stateful session bean failover components, go to....
Console | Environment | Replication domains
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 appservers use multi-broker replication domains which are collections of replicators. You should migrate any multi-broker replication domains to be data replication domains.
- Name
- Name of the replication domain. Must be unique within the cell.
- Domain type
Multi-broker domain Created with a version of WAS prior to v6.1. 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. You cannot create a multi-broker domain or replicator entries in the console after the deployment manager is upgraded to WAS v6.1.
Data replication domain Created with WAS v6.1. If the deployment manager has been upgraded to WAS v6.1 you can create data replication domains only.
You can specify a number of replicas instead of statically partitioning the replication settings.
Specify a data replication domain for each consumer of the domain, for example, two separate domains for dynamic cache and session manager.
Sub-topics
Data replication domain settings
Related tasks
Migrate servers from multi-broker replication domains to data replication domains