Installing the Infrastructure Management server in the disaster recovery mode

Where you are in the Installation process

Infrastructure Management Server can be installed with Oracle or SAP SQL Anywhere as the database. Infrastructure Management is integrated with SAP SQL Anywhere, which is configured by default. If you want to install it with Oracle, you can configure the Oracle database during installation. 

You need to perform the following tasks to install the Infrastructure Management server in the disaster recovery mode:

Step A: To install the Infrastructure Management server on the primary host 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 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

    Note

    • (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 Configure TrueSight Infrastructure Server for Disaster Recovery mode from the System Configuration Tasks, and click Next.
    
    
    By default, Administrator e-mail from BMC TrueSight Infrastructure Management is selected. You can deselect it.
    By default, SAP SQL Anywhere, which is integrated with TrueSight Infrastructure Management, is configured. If you want, you can choose to configure the Oracle database instead.
    
    

13. 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.
       Apache SSL Port	Used by the operator console for secure channel access. The default port number is 443.
       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. Do not select the DSIM - Enable and Configure option.

14. (Oracle database only) If you are configuring an Oracle database, specify these details, and click Next. 

     Configure the Oracle database

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

       1. • For a Stanalone 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
              If you are installing multiple TrueSight Infrastructure Management Servers and configuring them to connect to the same Oracle database, ensure that value of the database SID is the same for all the servers.
          • For an Oracle Real Application Cluster (RAC) setup provide the following details:
            • Service name of the Oracle server
              If you are installing multiple TrueSight Infrastructure Management Servers and configuring them to connect to the same Oracle database, ensure that the service name is the same for all the servers.
            • 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.

       1. • 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. 

          Note

          Ensure that you enter a unique user for each TrueSight Infrastructure Management Server instance that you install.

       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

    
    

    BMCTrueSight.service (Applicable only to version 11.3.04 and later on Linux)

    You can use the systemd service BMCTrueSight.service located in the /etc/systemd/system directory to start and stop the Infrastructure Management server on Linux. For more information, see Starting and stopping the TrueSight Operations Management components.

    
    

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. Register Infrastructure Management Server with the Presentation Server.

     To register Infrastructure Management 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 a valid Host Name in FQDN format.

       Notes

       • Ensure that you specify a common alias name for both the primary and secondary servers.
       • If the "Invalid Host Name or IP Address" message appears, re-enter a valid FQDN hostname. The name cannot start or end with a dash ( - ), contain any spaces, or exceed 63 characters.

       • Adding an IP address of the TrueSight Infrastructure Management Server is no longer supported. With an IP address, the cross-launch to the TrueSight Infrastructure Management from the TrueSight console fails. Therefore, you must edit the hostnames of all the Infrastructure Management Servers that were added in the past after you upgrade the TrueSight Presentation Server.

    4. Select the protocol.

    5. Accept the default port number (443), or enter a new value.

    6. Select any of the listed tenants.
       The list includes each tenant defined in the Remedy Single Sign-On system.

    7. Enter a value between 1 and 10 for the Component Initialization Timeout (minutes) period.
       This is the time period for which the TrueSight Presentation Server tries to initialize a connection to the component. If the connection is not completed within the time period, the connection fails.

       Tip

       If the Infrastructure Management server contains a large number of groups, set the Component Initialization Timeout (minutes) period to 5 minutes.

    8. Clear the Propagate Events box to stop propagation of events from the Infrastructure Management server to the TrueSight Presentation Server.

       Note

       To enable propagation of events at a later time, delete the Infrastructure Management server and re-add it with the Propagate Events box checked.

    9. Click Save.

       Note

       In an Infrastructure Management Server high-availability deployment, ensure that the configured cluster name and host names of the primary and secondary Infrastructure Management servers are resolved with the proper FQDN host name and reachable from the computer that hosts the TrueSight Presentation Server.

    Note

    Complete the following configurations to ensure automatic failover when any of the Infrastructure Management servers goes down. If these configurations are not completed, you need to manually restart the Presentation Server each time one of the Infrastructure Management servers goes down (indicated by the Initializing status on the Administration > Components page).

    • Configure the primary and secondary server to use the same alias name on the DNS server.
    • Configure DNS replication for both the primary and secondary servers.
    • While registering Infrastructure Management with the Presentation Server, ensure that you specify the same alias name as the host name for both the primary and secondary servers.
    • Ensure that the alias name contains only alphanumeric text and does not contain any special characters like hyphen( - ) and underscore( _ ).
      For example: alias name could be pronet, pronet2, or pronettsim.

21. Use the following format to define the Infrastructure Management Server URL, and launch the application in a browser.

    • (Windows) http(s)://<TSIMFQDN>
    • (Linux) http(s)://<TSIMFQDN>
22. Type the default Admin credentials (User name: admin, Password: admin12345), and click Log In.
    The Infrastructure Management console opens.

23. (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.
    • After you have installed the Infrastructure Management server using a non-root user, ensure that you do not restart the cell as a root user.

Step B: To perform post-install tasks after installing on the primary host computer

1. Stop the primary Infrastructure Management Server processes and take a backup of the installationDirectory/pw/ folder. 
2. Shutdown the primary host computer.

Step C: To install the Infrastructure Management server on the recovery host computer

Install the Infrastructure Management server on the recovery host computer using the same steps that you used while installing on the primary computer. While registering the recovery Infrastructure Management server with the Presentation Server, ensure that you specify the same alias name that you used for the primary server.

Step D: To perform post-install tasks after installing on the recovery host computer

1. Stop the recovery Infrastructure Management Server processes and restore a backup of the installationDirectory/pw/ folder on the recovery windows host.
2. Restart the TrueSight Presentation Server service.
3. Restart both the primary and recovery Infrastructure Management servers.

Step E: To verify that the disaster recovery server is functional

1. Add  Integration Services and PATROL Agents to the Infrastructure Management Server and observe the data collection.
2. Complete the following configurations to ensure automatic failover when any of the Infrastructure Management servers goes down. If these configurations are not completed, you need to manually restart the Presentation Server each time one of the Infrastructure Management servers goes down (indicated by the Initializingstatus on the Administration > Components page).
   
   1. Configure the primary and recovery servers to use the same alias name on the DNS server.
   2. Configure DNS replication for both the primary and recovery servers.
   3. While registering Infrastructure Management with the Presentation Server, ensure that you specify the same alias name for both the primary and recovery servers.

Troubleshooting installation issues

Next step in the Installation process