Specifying the underlying domains

An administrator uses the IC Domain Configuration objects to specify the underlying
,
IP Availability Manager
, and
Adapter Platform
domains in a
deployment. Doing so provides the sources of topology and events for the
Global Manager
and associates each underlying domain with the proper DXA file.
The expectation is that a user will either accept the default
named VoIP-AM or make a copy of the default to create a new
having a different name, say EAST-VoIP-AM.
This section provides procedures for the following two configuration scenarios:
  • Configuration scenario 1: A
    deployment containing a
    named VoIP-AM, an
    IP Availability Manager
    named INCHARGE-AM, and an
    Adapter Platform
    named INCHARGE-OI.
  • Configuration scenario 2: A
    deployment containing a
    named EAST-VoIP-AM, two
    IP Availability Manager
    s named EAST-AM1 and EAST-AM2, and an
    Adapter Platform
    named EAST-OI.
    To specify the underlying domains in a more complex
    deployment, consult the
    .
    Depending upon the
    version,
    Business Impact Manager
    may or may not appear listed as an underlying domain. For version 8.0, INCHARGE-MBIM is listed as an underlying domain which you can enable. For version 7.2,
    Business Impact Manager
    is not listed but is automatically enabled as part of the
    Global Manager
    . The following scenarios assume that 7.2
    Business Impact Manager
    is deployed.