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

Where you are in the Installation process

You need to perform the following tasks to install and configure TrueSight Infrastructure Managementin an application high-availability environment.

Step A: Install TrueSight Infrastructure Management on the primary computer

Application high-availability is supported only with the Oracle database. Install theTrueSight Infrastructure Managementserver on the primary computer. If you have a supported earlier version of theTrueSight Infrastructure Managementserver, upgrade it to the latest version. See Upgrading the Infrastructure Management Server.  

Do the following: 

1. Log in to the host computer on which you want to install the Infrastructure Management Server, and delete all the files from the temporary directory: 

   • (Windows) %temp%
   • (Linux) /tmp

   Note

   If you are reinstalling the Infrastructure Management Server due to a failure, you must delete all the existing installation directories and files.

2. Extract the downloaded zip files (the installer) to a temporary location outside the following location to avoid any file sharing conflicts:

   • (Windows) C:\Program Files
   • (Linux) /opt

3. (Linux) Apply executable rights to all the installation files by running the following command: 

   chmod -R 755 installationDirectoryFolderName 

   installationDirectoryFolderName is the name of the folder that contains all the installation files.

   For example, chmod -R 755 Disk1

4. (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately.
   export DISPLAY=<IP address of the host computer>:0.0
   
   

   Note

   Ensure that the following system requirements are met. If your target computer does not meet these requirements, you cannot proceed with the installation. However, in a test environment, you can skip the system requirements validation and run the installer by using the -J MINIMAL=true argument.

   • Total RAM (in MB): 32,000
   • Available RAM (in MB): 25,000
   • Total swap space / page file (in MB): 8,000
   • Available swap space / page file (in MB): 8,000

   By default, the TrueSight Infrastructure Management Server uses 256-bit encryption. However, AES 256-bit encryption is not allowed in some countries due to import regulations. You can change the default encryption key size when you invoke the installer.

5. Navigate to the Disk1 directory of the extracted folder, use one of the following options to run the installer.

   BMC recommends that you run the installer by using install.cmd and not setup.exe.

   You must right-click on install.cmd and select Run as administrator.

   Environment type	Command
   Production environment with the default encryption setting	(Windows) install.cmd (Linux)./install.sh
   Production environment with user-specified encryption setting	(Windows)install.cmd –J BMC_TS_KEY_SZ=<128/256> (Linux)./install.sh –J BMC_TS_KEY_SZ=<128/256>
   Test environment with the default encryption setting	(Windows)install.cmd -J MINIMAL=true (Linux)./install.sh -J MINIMAL=true
   Test environment with with user-specified encryption setting	(Windows)install.cmd –J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true (Linux)./install.sh –J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true

6. Review the welcome page, and click Next.
7. Read the license agreement, agree to the terms, and click Next. 

8. (Windows) Start the Windows Firewall service from services.msc and run the following commands:

   • • (Microsoft Windows 2008 R2) netsh advfirewall set allprofiles state on
     • (Microsoft Windows 2012 R2) netsh advfirewall set allprofiles state on
     • (Microsoft Windows 2012) netsh firewall set opmode mode = ENABLE

   Note

   If you turn on the firewall when Remote Desktop Protocol (RDP) is running, the RDP session may get disconnected if it is blocked by the firewall.

9. (Windows) On the Configuring Firewall Rules page, perform one of the following tasks, and click Next.

   • Select Automatically configure the Windows Firewall rules.
   • The Windows Firewall inbound rules are configured. 
   • Select I will manually configure Windows Firewall Rules now before proceeding further and configure inbound rules for the pw processes that are listed on the page.
     If you prefer to use a third party firewall application that is installed on your computer, you must manually create the firewall inbound rules. For more information about creating firewall inbound rules, refer to the documentation of the third party firewall application.

10. The default installation directory is:

    • (Windows) C:\Program Files\BMC Software\TrueSight

    • (Linux) /opt/bmc/TrueSight

    Notes
    • (Windows) Do not install TrueSight Infrastructure Management Server in the root directory (for example C: or D: ), on a shared drive, or in the Documents and Settings folder.
    • (Windows) While installing TrueSight Infrastructure Management Server on a 64-bit Windows computer, ensure that you do not install it in the Program Files (x86) directory path.
    • (Linux) Do not install TrueSight Infrastructure Management Server in the root directory.
    • (Linux) The directory in which the TrueSight Infrastructure Management Server is installed and all its parent directories must have 755 permissions (read, write, and execute permissions to owner, groups, and others) and must be owned by root as well as the other group. Without these permissions and ownership, you will not be able to log in to the TrueSight Infrastructure Management Server.
    • (Linux, as a non-root user) To avoid problems related to user permissions, ensure that you log in to a new session as a non-root user (without using the su command).
    • For Chinese, Korean, and Japanese installations, ensure that the system default locale is a UTF-8 locale. This enables the Input Method feature in the administration console.

11. The installer detects the FQDN of the host computer and populates the FQDN field automatically. Ensure that the FQDN is accessible by the other TrueSight components in your environment.
    If you modify the FQDN:

    • Do not manually type any IP address in the FQDN field. 

    • Do not leave this field empty

    Confirm this, and click Next. 
    

12. Select the configuration tasks that you want to perform, and click Next.

    
    

    
    

13. Do not select any of the options under System Configuration Tasks and Integrations Configuration Tasks.
    

    However, you can change the default Administrator email settings.

    Field	Description
    Sender E-mail ID	Email address that you specify as the sender of notification messages. The format must be hostName@company.com The administrator receiving the email message will be able to identify the host that has disk space problems or other issues that send notifications. The default value is blank.
    Administrator E-Mail ID	Fully qualified e-mail address of the administrator of the TrueSight Infrastructure Management Server. The format must be user@company.com. The default value is blank.
    Name or IP Address of SMTP Server	Name or IP address of the SMTP server. The default value is blank.

14. Ensure that you select the Configure to use an Oracle database option.
    
15. Specify the Oracle database details, and click Next. 
    

    1. Specify whether to connect to a standalone Oracle database instance or to an Oracle Real Application Cluster (RAC) setup.

       • For a Standalone Oracle database provide the following details:
         • Host name or IP address of the computer that is running the standalone Oracle database instance.
         • Oracle listener port on the computer. The default port is 1521.
         • Oracle database SID
       • For an Oracle Real Application Cluster (RAC) setup provide the following details:
         • Service name of the Oracle server
         • Host name of the computer that is running the Oracle RAC setup
           When you provide the RAC SCAN host name, the pw dbconfig list displays the node count as 1, and node 1 is the SCAN host.
         • Port number through which the RAC communicates.
    2. Specify whether to use an existing user or create a new user.

       • Type the user name. Do not use the terms "sys" or "system." The default user name is proact.

       • Type the password of the database instance, and confirm it. 

         The system creates a report user to access views in Oracle. The report user name is derived by suffixing "ru" to the Infrastructure Management user and the password is same as the user name. For example, if the Infrastructure Management user name is proact, then the report user name is proactru and the password is proactru. 

    3. If you are creating a new user for the Oracle database: 

       1. Provide the user name and password of the Oracle Report User, and click Next. 

       2. Provide the following details, and click Next:

       • • User name and password of the Oracle database. The user must have SYSDBA privileges.

         • Type of Infrastructure Management deployment. The size of the tablespace is determined by the type of deployment. The supported values are Small, Medium, and Large.

         • Names of the main and temporary tablespaces to be created.

         • Data file names with the absolute path for the main and temporary tablespaces.

16. Review the installation details, and click Install.

    Note

    If the DNS configurations are not correct, a warning message is displayed. You can either correct the DNS configuration and restart the installation, or provide the IP address instead of the host name when you are prompted to enter the host name.

    The installation may take upto 30 minutes.

    After the installation is complete, the Installation Summary page is displayed.

17. Select View Logs to open the installation logs.

18. (Linux) Verify that the following environment variables are set.

    • $BPPM_SERVER_HOME

    • $BMC_PROACTIVENET_HOME

19. Run the following command to verify the Infrastructure Management installation:

    (Windows) # pw system status
    (Linux)# pw system status

    A list of pw server processes is displayed.
    
    

     (Windows) Sample list

    ------------------------
Servers/Daemon Processes
------------------------
services 4820
httpd 6152
jserver 10660
pronet_agent 4680
pronet_cntl 3968
tunnelproxy 7792
rate 3976
dbsrv 6560
mcell 4952
pserver 4217

     (Linux) Sample list

    ------------------------
Servers/Daemon Processes
------------------------
pronet_agent 21256
services 21046
httpd 10069 21446 24238 28619 30746
jserver 21940
mcell 20930
pronet_cntl 21381
tunnelproxy 21660
rate 21540
oracle Running on <host name>:<port number>

    If errors occur, restart the BMC TrueSight Infrastructure Management Server by running the following command:

    (Windows)# pw system start
    (Linux) # pw system start

20. Apply the Infrastructure Management license.
    

    Note

    • Applying or updating the license restarts the JServer process and forces all active user sessions on the Infrastructure Management Server to log off.
    • You must have root privileges to apply the license.

    When you purchased the product, you would have received the following license files in a .zip file from your BMC Software representative:

    • proactivenet.lic
    • proactivenet.sign
     To apply the license on Microsoft Windows systems

    1. Copy the .zip file to a temporary directory on the Infrastructure Management Server (Example: C:\Program Files\BMC Software\licenses\TSIM).
    2. Unzip the file.
    3. Copy only the proactivenet.lic and proactivenet.sign files to the C:\Program Files\BMC Software\pw\licenses directory.
    4. To load the license data, run the command: pw lic update.
    5. Type y to restart JServer.

    If the license update is successful, an empty command prompt is displayed.

     To apply the license on Linux systems

    1. In binary mode, copy the .zip file to a temporary directory on the Infrastructure Management Server (Example: /opt/bmc/licenses/TSIM).
    2. Unzip the file.
    3. Copy only the proactivenet.lic and proactivenet.sign files to the /usr/pw/licenses directory.
    4. To load the license data, run the command: pw license update.
    5. Type y to restart JServer.

    If the license update is successful, an empty command prompt is displayed.

    Do not move or delete the license file

    - After loading the license, moving or changing the license files can cause a number of errors.

    - When the Infrastructure Management is installed, a hidden .pbk file is created. It is recommended to save a back copy of this .pbk file. If the licence directory is removed and then re-created, the .pbk no longer exists. So the .pbk file must be re-added for Infrastructure Management licensing to function properly. This file can be captured from a backup of the installation (if a backup exists) or from another computer where Infrastructure Management is installed.

21. (Linux) If you installed Infrastructure Management Server as a non-root user, do the following:

    Configure the TrueSight Infrastructure Management process to automatically start each time the TrueSight Infrastructure Management server is restarted. To do this, register the process as a service by running the script described in the following procedure. Running this script also results in copying the Integration Service security files required by the PATROL Agent to connect with the Integration Service.

    1. Locate the script at <Infrastructure-Management-Installation-Directory>/pw/scripts.
    2. Run the script in the following format:
       create_startup_script.sh [<Non-root-User-Name>]
       where, <Non-root-User-Name> refers to the non-root user name with which the process must be registered as a service. 
       Providing the non-root user name is optional. If you do not provide the non-root user name, by default, the script uses the non-root user name used for installing TrueSight Infrastructure Management to register the service.

Step B: Install TrueSight Infrastructure Management on the secondary computer

Do the following: 

1. Log in to the host computer on which you want to install the Infrastructure Management Server, and delete all the files from the temporary directory: 

   • (Windows) %temp%
   • (Linux) /tmp

   Note

   If you are reinstalling the Infrastructure Management Server due to a failure, you must delete all the existing installation directories and files.

2. Extract the downloaded zip files (the installer) to a temporary location outside the following location to avoid any file sharing conflicts:

   • (Windows) C:\Program Files
   • (Linux) /opt

3. (Linux) Apply executable rights to all the installation files by running the following command: 

   chmod -R 755 installationDirectoryFolderName 

   installationDirectoryFolderName is the name of the folder that contains all the installation files.

   For example, chmod -R 755 Disk1

4. (Linux) Set the DISPLAY environment variable to ensure that the wizard-based installer launches the screens appropriately.
   export DISPLAY=<IP address of the host computer>:0.0
   
   

   Note

   Ensure that the following system requirements are met. If your target computer does not meet these requirements, you cannot proceed with the installation. However, in a test environment, you can skip the system requirements validation and run the installer by using the -J MINIMAL=true argument.

   • Total RAM (in MB): 32,000
   • Available RAM (in MB): 25,000
   • Total swap space / page file (in MB): 8,000
   • Available swap space / page file (in MB): 8,000

   By default, the TrueSight Infrastructure Management Server uses 256-bit encryption. However, AES 256-bit encryption is not allowed in some countries due to import regulations. You can change the default encryption key size when you invoke the installer.

5. Navigate to the Disk1 directory of the extracted folder, use one of the following options to run the installer.

   BMC recommends that you run the installer by using install.cmd and not setup.exe.

   You must right-click on install.cmd and select Run as administrator.

   Environment type	Command
   Production environment with the default encryption setting	(Windows) install.cmd (Linux)./install.sh
   Production environment with user-specified encryption setting	(Windows)install.cmd –J BMC_TS_KEY_SZ=<128/256> (Linux)./install.sh –J BMC_TS_KEY_SZ=<128/256>
   Test environment with the default encryption setting	(Windows)install.cmd -J MINIMAL=true (Linux)./install.sh -J MINIMAL=true
   Test environment with with user-specified encryption setting	(Windows)install.cmd –J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true (Linux)./install.sh –J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true

6. Review the welcome page, and click Next.
7. Read the license agreement, agree to the terms, and click Next. 

8. (Windows) Start the Windows Firewall service from services.msc and run the following commands:

   • • (Microsoft Windows 2008 R2) netsh advfirewall set allprofiles state on
     • (Microsoft Windows 2012 R2) netsh advfirewall set allprofiles state on
     • (Microsoft Windows 2012) netsh firewall set opmode mode = ENABLE

   Note

   If you turn on the firewall when Remote Desktop Protocol (RDP) is running, the RDP session may get disconnected if it is blocked by the firewall.

9. (Windows) On the Configuring Firewall Rules page, perform one of the following tasks, and click Next.

   • Select Automatically configure the Windows Firewall rules.
   • The Windows Firewall inbound rules are configured. 
   • Select I will manually configure Windows Firewall Rules now before proceeding further and configure inbound rules for the pw processes that are listed on the page.
     If you prefer to use a third party firewall application that is installed on your computer, you must manually create the firewall inbound rules. For more information about creating firewall inbound rules, refer to the documentation of the third party firewall application.

10. The default installation directory is:

    • (Windows) C:\Program Files\BMC Software\TrueSight

    • (Linux) /opt/bmc/TrueSight

    Notes
    • (Windows) Do not install TrueSight Infrastructure Management Server in the root directory (for example C: or D: ), on a shared drive, or in the Documents and Settings folder.
    • (Windows) While installing TrueSight Infrastructure Management Server on a 64-bit Windows computer, ensure that you do not install it in the Program Files (x86) directory path.
    • (Linux) Do not install TrueSight Infrastructure Management Server in the root directory.
    • (Linux) The directory in which the TrueSight Infrastructure Management Server is installed and all its parent directories must have 755 permissions (read, write, and execute permissions to owner, groups, and others) and must be owned by root as well as the other group. Without these permissions and ownership, you will not be able to log in to the TrueSight Infrastructure Management Server.
    • (Linux, as a non-root user) To avoid problems related to user permissions, ensure that you log in to a new session as a non-root user (without using the su command).
    • For Chinese, Korean, and Japanese installations, ensure that the system default locale is a UTF-8 locale. This enables the Input Method feature in the administration console.

11. The installer detects the FQDN of the host computer and populates the FQDN field automatically. Ensure that the FQDN is accessible by the other TrueSight components in your environment.
    If you modify the FQDN:

    • Do not manually type any IP address in the FQDN field. 

    • Do not leave this field empty

    Confirm this, and click Next. 
    

12. Select the configuration tasks that you want to perform, and click Next.

    
    

    By default, Administrator e-mail from BMC TrueSight Infrastructure Management is selected. You can deselect it.

    Ensure that you select the Configure to use an Oracle database option. 

13. (Optional) Based on your selection, the applicable configuration pages are displayed. Type the appropriate details, and click Next.

    1.  Configure TrueSight Infrastructure Server for Disaster Recovery Mode

       Type a valid host name alias to configure disaster recovery, and click Next. The default host name alias is pronet.

    2.  Configure TrueSight Infrastructure Server default Cell

       
       

       Field	Description
       Cell details
       Instance Name	Name of the cell instance. The default is pncell_hostname.
       Port	Port number in the range of 1024 to 65535. The default port for the cell is 1828.
       Encryption Key	Encryption key for the cell. The default is mc. No special characters are allowed.

    3.  Change TrueSight Infrastructure Server default ports

       Port name	Description
       Apache Port	Used by the operator console and web services. The default port number is 80. (Linux) If you are installing as a non-root user, use a port number that must be between 1025 and 65535.
       Apache SSL Port	Used by the operator console for secure channel access. The default port number is 443. (Linux) If you are installing as a non-root user, use a port number that must be between 1025 and 65535.
       AgentController Port	Used by the Agent Controller. The default port number is 12123.
       BMC Impact Admin Server Port	Used by BMC Impact Admin Server clients to communicate with BMC Impact Admin Server. The default port number is 3084.
       Remote Method Invocation Port	Used by the operator console. The default port is 1099.
       Service Desk Integration Port	Used by the Integration for Service Desk Integration service if BMC Atrium CMDB integration is enabled. The default port number is 3115.
       Tomcat Port	Used by the Tomcat process
       JBoss JMS Port	Used by the JBoss process
       Cache Server Port	Used by the Cache Manager process

    4.  Administrator e-mail from TrueSight Infrastructure Management — Change defaults

       These details are required to receive e-mail notifications from the TrueSight Infrastructure Management Server.

       Field	Description
       Sender E-mail ID	Email address that you specify as the sender of notification messages. The format must be hostName@company.com The administrator receiving the email message will be able to identify the host that has disk space problems or other issues that send notifications. The default value is blank.
       Administrator E-Mail ID	Fully qualified e-mail address of the administrator of the TrueSight Infrastructure Management Server. The format must be user@company.com. The default value is blank.
       Name or IP Address of SMTP Server	Name or IP address of the SMTP server. The default value is blank.

    5.  Atrium CMDB — Enable and Configure

       
       

       Note

       Configuring the TrueSight Infrastructure Management Server for integration with BMC Atrium CMDB is recommended, but not mandatory, during installation. If you do not configure the TrueSight Infrastructure Management Server for CMDB integration during installation, you can manually configure this integration any time after the installation is complete.

       Before configuring BMC Atrium CMDB, ensure that BMC CMDB Extensions and modules are installed on the computer where the BMC Atrium CMDB is installed. If necessary, you can stop this installation, install the extensions, and then restart the TrueSight Infrastructure Management Server installation.

       
       

       Field	Description
       CMDB Host	Host name of the AR Server. When integrating with the AR Server group, host name of the Load Balancer or Integration Server.
       CMDB Port	BMC Atrium CMDB or AR System Server port number. The default is 0. If the AR System is configured with a Portmapper, enter port 0.
       CMDB User	User name required to log on to the AR System Server. The default is Demo. This user requires the AR Server Administration rights.
       CMDB Password	Password required to log on to the AR System server
       UDDI Host	Host name of the UDDI registry for BMC Atrium CMDB
       UDDI Port	Port number of the UDDI registry for CMDB. The default is 8080.
       UDDI User	UDDI registry user name. The default is admin.
       UDDI Password	Password for the specified UDDI user name. The default is admin.

       Note

       The UDDI parameters are optional and are used only to cross-launch to other BMC products, such as Atrium AE and BMC Atrium Service Context.

       If you integrate with BMC Atrium CMDB in the AR Server Group, you must manually configure the pserver.conf file. Edit the ARSGroupMembers in the pserver.conf file and set to all AR Servers of the group that have reconciliation function enabled. See also Configuring the Publishing Server to integrate with an AR Server group .

    6.  Cloud Vista — Enable and Configure

       Based on your TrueSight Infrastructure Management environment, select any one of the following:

       • Select Single Server Environment Installation option to install the TrueSight Infrastructure Management Server as a standalone server.

       • Select any of the following options under Multiple Server Environment Installation.

         • Select BMC TrueSight Operations Management Central Server option to install this instance as a central server.

         • Enter the following Server Router details for BMC TrueSight Operations Management Child Server:

       Field	Description
       Host Name/IP Address	FQDN name and IP address of the Central Server Router.
       Protocol	Protocol with which to communicate to the Central Server Router. It can be either HTTP or HTTPS.
       Port	Port number with which to communicate to the Central Server Router. The default port number are 80 for HTTP and 443 for HTTPS.

    7.  DSIM — Enable and Configure

       Based on your TrueSight Infrastructure Management environment, select any one of the following:

       • Select Single Server Environment Installation option to install the TrueSight Infrastructure Management Server as a standalone server.

       • Select any of the following options under Multiple Server Environment Installation.

         • Select BMC TrueSight Operations Management Central Server option to install this instance as a central server.

         • Enter the following Server Router details for BMC TrueSight Operations Management Child Server:

       Field	Description
       Host Name/IP Address	FQDN name and IP address of the Central Server Router.
       Protocol	Protocol with which to communicate to the Central Server Router. It can be either HTTP or HTTPS.
       HTTP Port	Port number with which to communicate to the Central Server Router. The default port number are 80 for HTTP and 443 for HTTPS.

14. If you are using a single Oracle instance and already created the users as specified at Complete the preinstall tasks for application high-availability mode, enter details of the primary server Oracle instance with the proact and reporting user username and passwords specified for the secondary server.  
    

    1. Specify whether to connect to a standalone Oracle database instance or to an Oracle Real Application Cluster (RAC) setup.

       • For a Standalone Oracle database provide the following details:
         • Host name or IP address of the computer that is running the standalone Oracle database instance.
         • Oracle listener port on the computer. The default port is 1521.
         • Oracle database SID
       • For an Oracle Real Application Cluster (RAC) setup provide the following details:
         • Service name of the Oracle server
         • Host name of the computer that is running the Oracle RAC setup
           When you provide the RAC SCAN host name, the pw dbconfig list displays the node count as 1, and node 1 is the SCAN host.
         • Port number through which the RAC communicates.
    2. Specify a different (temporary) username and password for both proact and reporting user compared to the primary server.

       • Type the user name. Do not use the terms "sys" or "system." The default user name is proact.

       • Type the password of the database instance, and confirm it. 

         The system creates a report user to access views in Oracle. The report user name is derived by suffixing "ru" to the Infrastructure Management user and the password is same as the user name. For example, if the Infrastructure Management user name is proact, then the report user name is proactru and the password is proactru. 

    3. If you are creating a new user for the Oracle database: 

       1. Provide the user name and password of the Oracle Report User, and click Next. 

       2. Provide the following details, and click Next:

       • • User name and password of the Oracle database. The user must have SYSDBA privileges.

         • Type of Infrastructure Management deployment. The size of the tablespace is determined by the type of deployment. The supported values are Small, Medium, and Large.

         • Names of the main and temporary tablespaces to be created.

         • Data file names with the absolute path for the main and temporary tablespaces.

15. Review the installation details, and click Install.

    Note

    If the DNS configurations are not correct, a warning message is displayed. You can either correct the DNS configuration and restart the installation, or provide the IP address instead of the host name when you are prompted to enter the host name.

    The installation may take upto 30 minutes.

    After the installation is complete, the Installation Summary page is displayed.

16. Select View Logs to open the installation logs.

17. (Linux) Verify that the following environment variables are set.

    • $BPPM_SERVER_HOME

    • $BMC_PROACTIVENET_HOME

18. Run the following command to verify the Infrastructure Management installation:

    (Windows) # pw system status
    (Linux)# pw system status

    A list of pw server processes is displayed.
    
    

     (Windows) Sample list

    ------------------------
Servers/Daemon Processes
------------------------
services 4820
httpd 6152
jserver 10660
pronet_agent 4680
pronet_cntl 3968
tunnelproxy 7792
rate 3976
dbsrv 6560
mcell 4952
pserver 4217

     (Linux) Sample list

    ------------------------
Servers/Daemon Processes
------------------------
pronet_agent 21256
services 21046
httpd 10069 21446 24238 28619 30746
jserver 21940
mcell 20930
pronet_cntl 21381
tunnelproxy 21660
rate 21540
oracle Running on <host name>:<port number>

    If errors occur, restart the BMC TrueSight Infrastructure Management Server by running the following command:

    (Windows)# pw system start
    (Linux) # pw system start

19. Apply the Infrastructure Management license.
    

    Note

    • Applying or updating the license restarts the JServer process and forces all active user sessions on the Infrastructure Management Server to log off.
    • You must have root privileges to apply the license.

    When you purchased the product, you would have received the following license files in a .zip file from your BMC Software representative:

    • proactivenet.lic
    • proactivenet.sign
     To apply the license on Microsoft Windows systems

    1. Copy the .zip file to a temporary directory on the Infrastructure Management Server (Example: C:\Program Files\BMC Software\licenses\TSIM).
    2. Unzip the file.
    3. Copy only the proactivenet.lic and proactivenet.sign files to the C:\Program Files\BMC Software\pw\licenses directory.
    4. To load the license data, run the command: pw lic update.
    5. Type y to restart JServer.

    If the license update is successful, an empty command prompt is displayed.

     To apply the license on Linux systems

    1. In binary mode, copy the .zip file to a temporary directory on the Infrastructure Management Server (Example: /opt/bmc/licenses/TSIM).
    2. Unzip the file.
    3. Copy only the proactivenet.lic and proactivenet.sign files to the /usr/pw/licenses directory.
    4. To load the license data, run the command: pw license update.
    5. Type y to restart JServer.

    If the license update is successful, an empty command prompt is displayed.

    Do not move or delete the license file

    - After loading the license, moving or changing the license files can cause a number of errors.

    - When the Infrastructure Management is installed, a hidden .pbk file is created. It is recommended to save a back copy of this .pbk file. If the licence directory is removed and then re-created, the .pbk no longer exists. So the .pbk file must be re-added for Infrastructure Management licensing to function properly. This file can be captured from a backup of the installation (if a backup exists) or from another computer where Infrastructure Management is installed.

20. (Linux) If you installed Infrastructure Management Server as a non-root user, do the following:

    Configure the TrueSight Infrastructure Management process to automatically start each time the TrueSight Infrastructure Management server is restarted. To do this, register the process as a service by running the script described in the following procedure. Running this script also results in copying the Integration Service security files required by the PATROL Agent to connect with the Integration Service.

    1. Locate the script at <Infrastructure-Management-Installation-Directory>/pw/scripts.
    2. Run the script in the following format:
       create_startup_script.sh [<Non-root-User-Name>]
       where, <Non-root-User-Name> refers to the non-root user name with which the process must be registered as a service. 
       Providing the non-root user name is optional. If you do not provide the non-root user name, by default, the script uses the non-root user name used for installing TrueSight Infrastructure Management to register the service.

Step C: Configure application high-availability

1. Stop the Infrastructure Management process on both servers.
   From the pw command prompt, run the following command:
   pw sys stop
   

2. On the primary server:

   1. Run the following command from the pw command prompt:
pw ha enable
For details about the command, see  pw ha enable command
      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.

3. 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>

   For details about the command, see  pw ha enable standby command
4. Copy the installedDirectory\TrueSight\pw\pronto\tmp\addremoteagent file to the primary server.
5. Copy the installedDirectory\TrueSight\pw\server\var\pncell_<host name>#1 folder from the primary server to the same location on the secondary server.

6. On the secondary server, rename the folder that you copied from the primary server to:
   pncell_<host name>#2

7. Restart the primary server and then restart the secondary server.
   From the pw command prompt, run the following command:
   pw sys start
   
8. Run the following command from the primary and secondary server to verify the high availability status:
   pw ha status
9. Run the following command from the primary and secondary server to verify that both nodes are pointing to the same database instance:
   pw dbconfig test
10. On the primary server, run the addremoteagent file.

11. (Optional - 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>
       For example, cell aaa-test-bmc1 mc aaa-test-bmc1:1828
    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

12. To ensure that publishing works seamlessly, set the Publishing Server name of the secondary server to a different one than the primary server. For more information, see  Publishing server optional configurations
13. Register TrueSight Infrastructure Managementwith the Presentation Server.
    

    1. In the TrueSight console, go to Administration > Components, select the action menu next to Components, and select Add Component.

    2. Select Infrastructure Management Server as the component type.

    3. Enter the Host Name configured in the load balancer in FQDN format.

14. (Optional) Delete the Oracle database schema (or Oracle instance, if you created a separate instance) of the secondary node, since it is no longer required after application high-availability is configured.

Troubleshooting installation issues

Next step in the Installation process