Locating the Global Managers in the network

In choosing locations for the platforms that support the Global Managers, there may be restrictions on locations that are not related to network and application efficiency. Locating the Global Managers may be based on the following considerations:

• Geographical requirements: An organization may require that all Managers be based in a single Network Operations Center (NOC). Other organizations might have the Global Manager in the NOC and underlying Domain Managers located in regional data centers.

• Corporate organizational requirements: For example, organizations that have a distributed business management might require that components be located to match the organization’s structure.

  Communication between applications is influenced by network speed and latency. Avoid configurations that require a Global Manager to receive information from other applications across WAN links with high latency. Instead, consider placing Global Managers on both ends of high-latency WAN links. The hierarchical Global Manager configurations can be used to eliminate high-latency link issues for these situations:

• Domain Managers that connect to a Global Manager over a high-latency link: Use the basic hierarchical, hierarchical aggregation, or hierarchical mesh configuration to place a Global Manager on the same side of the high-latency link as the Domain Managers.

• A group of clients that connect to a Global Manager over a high-latency link: Use the basic hierarchical, hierarchical presentation, or hierarchical mesh configuration to place a Global Manager on the same side of the high-latency link as the group of clients.

  After you determine the configuration and locations of the Global Managers, add system names and Global Manager names to your solution architecture diagram. Define IP addresses and dedicated port numbers when needed. Establish a host naming convention and a Global Manager naming convention before you settle on any names.