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

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

DRU0 comprises two machines,
SYS0 and SYS2. HADB node active 0 is on the machine SYS0. HADB node spare
2 is on the machine SYS2.

DRU1 comprises two machines,
SYS1 and SYS3. HADB node active 1 is on the machine SYS1. HADB node spare
3 is on the machine SYS3.

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

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:

Machine SYS0 hosts instance A

Machine SYS1 hosts instance B

Machine SYS2 hosts instance C

Machine SYS3 hosts instance D

Machine SYS4 hosts instance E

Machine SYS5 hosts instance F

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