Use this information to configure failover in your primary
and backup Network Manager installations.
Guidelines are also provided to optionally configure failover of the
integrating products and components. You must use the documentation
for these products and components as the first point of reference.
Before you begin
Before you begin to configure failover, determine whether
you want to implement a complete failover solution for all the components,
or failover for Network Manager and
a subset of components. Also decide on the number of computers and
the deployment options.
About this task
As a prerequisite to configuring failover:
Procedure
- You must have installed and configured IBM Tivoli Netcool/OMNIbus.
If you intend to run a primary and backup ObjectServer in failover
mode, you require two ObjectServer installations.
Tip: If you are using IBM Tivoli Netcool/OMNIbus V7.3
or later, with the supplied failover configuration files, be sure
to adhere to the naming conventions for your ObjectServers and ObjectServer
Gateways.
- You must have installed a topology database.
For NCIM topology database high availability, you require two topology
databases.
Note: In previous
Network Manager releases,
users could include an NCIM topology database failover configuration
by using NCIM replication (also referred to as NCIM topology database
replication). The NCIM replication feature has been replaced by the
high availability feature that is provided by the supported database:
- If you have a Db2® database,
you can use the High Availability Disaster Recovery (HADR) feature
to set up failover for NCIM.
- If you have an Oracle database, you can use the Real Application
Clusters (RAC) feature to set up failover for NCIM.
-
You must have installed and configured the Web GUI and the
Network Manager Web applications
within the Dashboard Application Services Hub server
framework.
- You must have installed the Network Manager core
processes on the designated primary and backup servers, under two
separate domains.