Sun GlassFish Enterprise Server 2.1 Deployment Planning Guide

Co-located Topology

In the co-located topology, the Enterprise Server instance and the HADB nodes are on the same machine (hence the name co-located). This topology requires fewer machines than the separate tier topology. The co-located topology uses CPUs more efficiently—an Enterprise Server instance and an HADB node share one machine and the processing is distributed evenly among them.

This topology requires a minimum of two machines. To improve throughput, add more machines in pairs.

Note –

The co-located topology is a good for large, symmetric multiprocessing (SMP) machines, since you can take full advantage of the processing power of these machines.

Example Configuration

The following figure illustrates an example configuration of the co-located topology.

Figure 3–1 Example Co-located Topology

Example Co-located Topology

Machine SYS0 hosts Enterprise Server instance A, machine SYS1 hosts Enterprise Server instance B, machine SYS2 hosts Enterprise Server instance C, and machine SYS3 hosts Enterprise Server instance D.

These four instances form a cluster that persists information to the two DRUs:

Variation of Co-located Topology

For better scalability and throughput, increase the number of Enterprise Server instances and HADB nodes by adding more machines. For example, you could add two machines, each with one Enterprise Server instance and one HADB node. Make sure to add the HADB nodes in pairs, assigning one node for each DRU. Variation of Co-located Topology illustrates this configuration.

Figure 3–2 Variation of Co-located Topology

Variation of Co-located Topology

In this variation, the machines SYS4 and SYS5 have been added to the co-located topology described in Example Configuration.

Enterprise Server instances are hosted as follows:

These instances form a cluster that persists information to the two DRUs: