Configuring multi-cell performance management: Peer-Cell Topology
Configure and manage multi-cell performance in your environment to avoid overprovisioning resources, such as CPU and memory utilization.
About this task
The Peer-Cell Topology works well if you have two or more disjoint data centers, one cell per data center, and you want failover capability between them. In this topology, the on demand routers (ODRs) remain in the cells; however, the two cells are not joined via core-group bridges. In front of your two cells, you have one or more load-balancers, plugins, or sprayers which are able to both preserve session affinity (as applicable), as well as equitably distribute traffic.
A peer-cell topology applies to server virtualized environments, such as AIX® LPARs/WPARs, Linux on System z®, VMware, and Solaris Zones, as well as non-virtualized environments in which multiple cells do not share the physical hardware. In a peer-cell topology, all cells can perform work, such as contain ODRs and application servers, and make autonomic decisions to start or stop application servers.
- Your cells are peers (e.g. duplicates of one another)
- You want to join two or more disjoint data centers
- The cells you want to join do not share hardware
- The cells you want to join all need to contain ODRs
The following procedure describes a sample scenario in which multi-cell performance management is configured in a peer-cell topology environment so that work requests can be routed from an ODR to dynamic cluster members across cells. The ODR is installed and running on CellA, which is the center cell. The two-point cells, CellB and CellC, contain the dynamic clusters and applications.

- Run $WAS_HOME/bin/crossCellCGBCfg clear remote DMGR remote DMGR soap port on the local DMGR node.
- Stop all the processes in each cell. Make sure all processes are stopped before bringing the processes up again. This ensures that any data of the remote cell is cleared up in the on demand configuration (ODC). The profile profiles/profile name/config/cells/cell name/multicelloverlaybridgesettings.xml should not be present.
- To make sure the ODC does not contain data of the remote cell you can Run $WAS_HOME/bin/wsadmin.sh -lang jython -f ve_manageODC.py getTargetTree LocalDmgrNodeName dmgr > target.xml