Configure and manage multi-cell performance in your environment to avoid overprovisioning resources, such as CPU and memory utilization.
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.
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.