Installing and configuring the Infrastructure Management server for application high-availability

The following table helps you through the steps that you need to perform to enable high-availability for Infrastructure Management.


Step#DetailsReference
1

Review the requirements to configure Infrastructure Management for high availability.

Considerations for a high-availability deployment of Infrastructure Management
2

Install or upgrade Infrastructure Management on the primary server.

Fresh install:

(Windows)
Installing the Infrastructure Management Server on Microsoft Windows with Oracle

(Linux) Installing the Infrastructure Management Server on Linux with Oracle

Upgrade:

(Windows) Upgrading the Infrastructure Management server on Microsoft Windows

(Linux) Upgrading the Infrastructure Management server on Linux

3

Install Infrastructure Management on the secondary server.

Note: (Recommended) During the installation, specify a temporary Oracle instance.

(Alternatively) If you want to avoid usage of temporary oracle instance, you can create one. For more information, see Running the run_oracle_db_scripts.sql script in an Oracle environment.

(Windows)
Installing the Infrastructure Management Server on Microsoft Windows with Oracle

(Linux) Installing the Infrastructure Management Server on Linux with Oracle
4

Stop the Infrastructure Management process on both servers.

From the pw command prompt, run the following command:
pw sys stop
5

On the primary server:

    1. Run the following command from the pw command prompt:
      pw ha enable

      The command generates the HA configuration file ha-generated.conf in the installedDirectory\pw\pronto\tmp directory.
    2. Copy the ha-generated.conf file to the secondary server.

pw ha enable command

6

On the secondary server, run the following command from the pw command prompt:

pw ha enable standby file = <path of the ha-generated.conf file>

pw ha enable standby command

7

On the primary server, copy the following folder from the installedDirectory\TrueSight\pw\server\var folder to the same location on the secondary server:
pncell_<host name>#1


8

On the secondary server:

    1. Rename the folder that you copied from the primary server to:
      pncell_<host name>#2
    2. Copy the installedDirectory\TrueSight\pw\pronto\tmp\addremoteagent file to the primary server.

9

On the primary server, run the addremoteagent file.


10

(Optional - If you want to configure remote cells)

    1. On the primary server, add each remote cell entry to the installedDirectory/server/etc/mcell.dir file in the following format:
      cell <cell name> <encryption key>

      <cell host>:<cell port>
    2. On the primary server, run the iadmin command from the installedDirectory\pw\server\bin directory to register the remote cell:
      iadmin -ac name=<cell name>:key=<encryption key>:primaryHost=<cell host name>:primaryPort=<cell port>:environment=Production:usergroups=*
    3. Perform the preceding steps on the secondary server.

    4. On the primary server, run the mcontrol command from the installedDirectory\pw\server\bin directory to reload the cell configuration:
      mcontrol -n <pncell name> reload dir


11

Configure the Presentation Server:

Fresh install - Add the Infrastructure Management component to the Presentation Server. In the Host Name/IP Address field, enter the host name configured in the load balancer.

Upgrade install - Update the host name of the Infrastructure Management server in the Host Name/IP Address field with the host name configured in the load balancer.

Registering the component products with the Presentation Server
12

Configure the integrations with other BMC products.

Integrating components with TrueSight Infrastructure Management when configured for high availability


Related topics

Considerations for a high-availability deployment of Infrastructure Management

Infrastructure Management Server high-availability architecture

Was this page helpful? Yes No Submitting... Thank you

Comments