Installing the Infrastructure Management server in the high-availability cluster mode using the wizard

Where you are in the Installation process

You need to perform the following tasks to install the Infrastructure Management server in the high-availability cluster mode using the wizard:

• Step A: To install the Infrastructure Management server on the primary computer (Windows and Linux)
• Step B: To perform post-install tasks after installing on the primary computer
  
  • Post-install tasks on Windows
  • Post-install tasks on Linux
• Step C: To install the Infrastructure Management server on the secondary computer
  
  • Installing on Windows
  • Installing on Linux
• Step D: To perform post-install tasks after installing on the secondary computer
  
  • Post-install tasks on Windows
  • Post-install tasks on Linux

Step A: To install the Infrastructure Management server on the primary computer

You can manually install the TrueSight Infrastructure Management server on the primary computer. Automatic Failover is handled by the Microsoft Cluster Server software. 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. 

Do the following: 

1. Log in to the host computer on which the cluster is installed. Ensure that the cluster is pointing to the host computer on which you plan to install the primary Infrastructure Management server.

2. Delete all the files from the temporary directory:

   • (Windows) %temp%
   • (Linux) /tmp
3. Extract the downloaded zip files (the installer) to a temporary location outside the following location to avoid any file sharing conflicts:
   • (Windows) S:\Program Files
   • (Linux) /opt
     

4. (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

5. (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

6. (Linux) Change the host name of the primary computer to the logical host name configured for the cluster by entering hostname logicalHostName. For example, hostname bmccluster.bmc.com.
   

   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.

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

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

8. Review the welcome page, and click Next.
9. Read the license agreement, agree to the terms, and click Next. 

10. (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.

11. (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.

12. (Windows) On the Cluster Group Configuration page, select one of the following Cluster Group types, type the cluster group name, and click Next:

    • Default cluster group

    • Custom cluster group

    

    Note

    BMC recommends that you install the Infrastructure Management server using a custom cluster group. Ensure that the custom cluster group and the custom cluster that you plan to use are already created and functional. The custom cluster group name must be the same as the custom cluster name.

13. Set the installation directory.

    • (Windows) The default directory is S:\Program Files\BMC Software\TrueSight 

    • (Linux) During the installation, choose the cluster file system (/global) that is shared on both the primary and secondary computers as the installation location.

    On Windows

    • Do not install Infrastructure Management server in the root directory (for example C: or D: ) or in the Documents and Settings folder.
    • While installing Infrastructure Management server on a 64-bit Windows computer, ensure that you do not install it in the Program Files (x86) directory path.
    • 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.

    On Linux

    • Do not install Infrastructure Management server in the root directory.
    • The directory in which the 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.
    • (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.

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

    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.

15. (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.

16. (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.

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

18. Select View Logs to open the installation logs.

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

    • $BPPM_SERVER_HOME

    • $BMC_PROACTIVENET_HOME

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

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

22. (Linux) After successful installation of the Infrastructure Management server, change the logical host name back to the host name of the primary computer by entering hostname primaryHostName.

23. (Linux) Remove the following files so that the Infrastructure Management server processes do not start automatically:

    • /etc/rc3.d/S81BMCTrueSight
    • /etc/rc0.d/K09BMCTrueSight
    • /etc/rc1.d/K09BMCTrueSight

24. (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.

    Linux operating system

    The Infrastructure Management Server installation on the primary computer running the Linux operating system is completed successfully. Proceed to Step B: To perform post-install tasks after installing on the primary computer.

25. (Windows) Go to the <DownloadLocation>\TSIMServer\Disk1\utility directory, and open the TrueSightIMMaintenanceTool.
26. (Windows) Run the tool, and click the Logs tab.
27. (Windows) Click Install Log to view the tsim_server_install_log.txt file.
28. (Windows) Click File and use the Save as command to open the Save as dialog box.
29. (Windows) Select Project Options File from the Save As Type list.
30. (Windows) Type the file name and click Browse to navigate to the directory where you want to save the options file as shown in the following example:
    
31. (Windows) Click OK to save the file.

32. (Windows) Open (or edit) the options file and update the INSTALL_TYPE property as SECONDARY as shown in the following code block:

    INSTALL_TYPE=SECONDARY

33. (Windows) Copy the options file to the shared drive. 
    Note: After the cluster points to the secondary computer, the options file will be accessible by the computer on which you plan to install the secondary Infrastructure Management Server.
    
    

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

Post-install tasks on Windows

1. Stop the TrueSight Infrastructure Management server on the primary server.
2. Move the cluster control to the secondary server.

Post-install tasks on Linux

1. Stop all processes on the primary computer by running the following command:
   pw sys stop.

2. Move the shared disk from the primary computer to the secondary computer by running the following commands on the primary computer:
   (For RHEL 6.x) clusvcadm -r logicalhostname -n Standbymodehostname
(For RHEL 7.x) pcs resource move <resource group name> Standbymodehostname
Do not execute the above commands on the shared disk. 

   Note

   You can use the pcs status command to find the resource group name on the primary host computer.

Step C: To install the Infrastructure Management server on the secondary computer

Installing on Windows

Do the following: 

1. Log in to the host computer on which the cluster is installed. Ensure that the cluster is pointing to the host computer on which you plan to install the secondary Infrastructure Management server.

2. Delete all the files from the temporary directory:
   %temp%

3. Extract the downloaded zipped files (the installer) to a temporary location outside the following directory location to avoid any file sharing conflicts:
   S:\Program Files
   
   

   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.

4. Navigate to the Disk1 directory of the extracted folder, and run one of the following commands from the command prompt: 

   • Ensure that after installing the primary Infrastructure Management Server, the options file is copied to the shared drive.
     
   • Type the name of the options file located in the shared drive for the <OPTIONS_FILE_GENERATED_IN_ABOVE_STEP> parameter in the following command.

   
   

   Environment type	Command
   Production environment with the default encryption setting	install.cmd -J INSTALL_TYPE=SECONDARY –J BMC_TS_KEY_SZ=<128/256> -DOPTIONS_FILE=<OPTIONS_FILE_GENERATED_IN_ABOVE_STEP>
   Production environment with user-specified encryption setting	install.cmd -J INSTALL_TYPE=SECONDARY -DOPTIONS_FILE=<OPTIONS_FILE_GENERATED_IN_ABOVE_STEP>
   Test environment with the default encryption setting	install.cmd –J BMC_TS_KEY_SZ=<128/256> -J INSTALL_TYPE=SECONDARY -J MINIMAL=true -DOPTIONS_FILE=<OPTIONS_FILE_GENERATED_IN_ABOVE_STEP>
   Test environment with user-specified encryption setting	install.cmd -J MINIMAL=true -J INSTALL_TYPE=SECONDARY -DOPTIONS_FILE=<OPTIONS_FILE_GENERATED_IN_ABOVE_STEP>

   
   

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

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

8. (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.

9. If required, you can change the following default installation directory, and click Next: 

   S:\Program Files\BMC Software\TrueSight

   Notes

   • (Windows) Do not install Infrastructure Management server in the root directory (for example C: or D: ), on a shared drive directly, or in the Documents and Settings folder.
   • (Windows) While installing Infrastructure Management server on a 64-bit Windows computer, ensure that you do not install it in the Program Files (x86) directory path.

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

11. Select View Logs to open the installation logs.

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

    pw system status

     A list of pw server processes is displayed. 

     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
acell 4916

     If errors occur, restart the Infrastructure Management server by running the following command:

     pw system start

Installing on Linux

Do the following:

1. Copy the /etc/patrol.d folder from the primary computer to the secondary computer (in the same location). 
   This step is needed to enable the PATROL Agent to connect to the Integration Service.
2. On the secondary computer, perform the following steps to create environment variables:

   1. Copy the bmc_profile and the bmc_cshrc files from the user's home directory on the primary computer to the secondary computer (in the same location).

   2. On the secondary computer, perform the following actions:

      1. In the <User-Home-Directory>/.bash_profile file, add the following entry, and save the file.

         • <User-Home-Directory>/.bmc_profile

         • /home/jack/.bmc_profile

      2. In the <User-Home-Directory>/.bashrc file, add the following entry, and save the file.

         • <User-Home-Directory>/.bmc_cshrc

         • /home/jack/.bmc_cshrc


      3. Log out and then log in to the secondary computer so that the changes made in the preceding steps are applied.
3. On the secondary computer, create the required links for the Infrastructure Management server by entering the following commands:
   

   • ln -s /serverInstallDirectory/pw /usr/pw

   • ln -s /usr/pw/pronto /usr/pronto

   • ln -s /usr/pw/pronto/bin/pw /bin/pw

4. Start all processes on the secondary computer. Use the following command:
   pw sys start 
5. On the secondary computer, check for the Infrastructure Management server crontab entries:
   1. Identify the crontab entries by using the crontab -l command and check for all entries between the lines # begin_pronto and # end_pronto. 
   2. If the crontab entries are missing, open the command prompt, navigate to the <installDirectory>\pw\scripts folder, and run the following command:
      
      CreateCrontabEntries.sh linux <Database>

where <Database> can be Oracle or SAP SQL Anywhere
      For example, CreateCrontabEntries.sh linux Oracle

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

Post-install tasks on Windows

After you complete the installation on the secondary computer, do the following:

1. Run the pns.reg file located at installationDirectory\pw\pproxy\PNS\security. If you do not run this file, existing policy configurations are not applied on the PATROL Agent during a failover, and therefore policy creation and update fails.

2. Go to installationDirectory\pw\patrol\pis\security\bppmpis.reg, and find all the keys that contain single slashes in the path value. Replace the single slashes with double slashes. Use the following examples:

   Instead of... "bindir64"="S:\Program Files\BMC Software\TrueSight\pw\\patrol\\common\\security\\bin_v3.0\\Windows-x86-64" Use... "bindir64"="S:\\Program Files\\BMC Software\\TrueSight\\pw\\patrol\\common\\security\\bin_v3.0\\Windows-x86-64"

   Instead of... "securitydir"="S:\Program Files\BMC Software\TrueSight\pw\\patrol\\common\\security\\keys" Use... "securitydir"="S:\\Program Files\\BMC Software\\TrueSight\\pw\\patrol\\common\\security\\keys"

   Instead of... "logdir"="S:\Program Files\BMC Software\TrueSight\pw\\patrol\\common\\security\\log_v3.0" Use... "logdir"="S:\\Program Files\\BMC Software\\TrueSight\\pw\\patrol\\common\\security\\log_v3.0"

   Instead of... "bindir"="S:\Program Files\BMC Software\TrueSight\pw\\patrol\\common\\security\\bin_v3.0\\Windows-x86" Use... "bindir"="S:\\Program Files\\BMC Software\\TrueSight\\pw\\patrol\\common\\security\\bin_v3.0\\Windows-x86"

   Instead of... "sksdir"="S:\Program Files\BMC Software\TrueSight\pw\\patrol\\common\\security\\sks" Use... "sksdir"="S:\\Program Files\\BMC Software\\TrueSight\\pw\\patrol\\common\\security\\sks"

3. Import the installationDirectory\pw\patrol\pis\bppmpis.reg file in the registry.

4. Create dependencies for the Infrastructure Management server cluster resource.

   1. Stop the Infrastructure Management server using the pw system stop command.

   2. Go to Start > All Programs > Administrative Tools > Failover Cluster Manager and click on the cluster name.

   3. Scroll down to the Cluster Core Resources section, right-click PnService, and click Properties.

   4. In the PnService Properties dialog box, click the Dependencies tab.
   5. Click Insert to add a resource.
   6. From the Resource list, select a cluster name and click Insert.
   7. Select the cluster resource with the ‘AND’ option. Similarly, add all the resources (Name, IP address, and Disk).
   8. Click Apply and OK.
   9. Restart the Infrastructure Management server using the pw system start command.

5. Restart both the primary and secondary servers. 

   Notes

   • After the Infrastructure Management server is installed on both the primary and secondary servers, a “PnService” resource is created on the cluster.

     If this resource is not created automatically, you may receive warnings. To create the resource, perform the following steps:

     1. Go to the <installation directory>\Agent directory and execute the following file:
        (Windows Server 2008 R2) GenericService.bat
        (Windows Server 2012) GenericService.ps1
     2. Execute the following command to enable the PnService cluster resource:
(Windows Server 2008 R2) cluster.exe resource PnService /ONLINE /WAIT:500
        (Windows Server 2012)powershell.exe Start-ClusterResource -Name PnService -Wait 500
   • The Infrastructure Management server takes time to come up during a failover, as it runs on a Microsoft active/passive cluster. If the server (cluster resource) does not come up in a few minutes, select the online option to manually set the status.

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

      • (Linux) Type the logical host name of the computer that you used while installing on Linux.
      • Type the hostname of the cluster group that you used while installing the Infrastructure Management server.
      • 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 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.

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

8. Type the default Admin credentials (User name: admin, Password: admin12345), and click Log In.
   The Infrastructure Management console opens.

Post-install tasks on Linux

Do the following:

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

      • (Linux) Type the logical host name of the computer that you used while installing on Linux.
      • Type the hostname of the cluster group that you used while installing the Infrastructure Management server.
      • 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.

2. After moving the shared disk from the primary computer to the secondary computer, the status of all the TrueSight Infrastructure Management components must be displayed as Connected on the TrueSight console.

3. The Infrastructure Management server must successfully connect to Integration Service and PATROL Agent.

Related topics

For information about adding a failover domain and other post-installation tasks, see:

• Setting up the cluster in Linux 6.x
  
• Setting up the cluster in Linux 7.x
  
• Setting up the service to run in high-availability cluster mode in Linux

Next step in the Installation process