Upgrading the Infrastructure Management server for application high-availability

Where you are in the Upgrade process

StepTask
1Preparing to upgrade TrueSight Operations Management solution
2Upgrade Remedy Single Sign-On
3Upgrade TrueSight Presentation Server
4Upgrade TrueSight Infrastructure Management — Phase A (You are here)
Upgrade TrueSight Infrastructure Management — Phase B
5Upgrade App Visibility Manager
6Upgrade Real End User Experience Monitoring Software Edition
7Upgrade TrueSight IT Data Analytics

You need to perform the following tasks to upgrade the Infrastructure Management server for application high-availability:

Application high-availability is supported only with the Oracle database. Upgrade the TrueSight Infrastructure Management server on the primary computer.

Best Practice

BMC recommends that you deploy the Oracle database and TrueSight Infrastructure Management Server on separate servers.

To upgrade the Infrastructure Management server on the primary computer

  1. Stop the secondary TrueSight Infrastructure Management server before you proceed with the upgrade. For more information, see  Starting and stopping the TrueSight Operations Management components .
  2. Log in to the host computer on which you want to upgrade the Infrastructure Management Server, and delete all the files from the temporary directory: 

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

    • (WindowsC:\Program Files
    • (Linux) /opt

    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. (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) Perform the following to archive the old installation files including the user apps, PERL libraries, and any other customization:
    1. Run the pw system stop command to stop the TrueSight Infrastructure Management server.
    2. Tar the /usr/pw directory and place the resulting file in a secure location such as on another server, another file partition, or a directory that lies above /usr/pw.
    3. Save the Crontab entries (especially the database archive entry).

    4. Restart the TrueSight Infrastructure Management Server by using the pw system start command.
    5. Save any custom Apache settings.
  6. (Linux) Run one of the following commands to set the DISPLAY environment to enable the installation program UI to launch:

    • export DISPLAY=targetHostName:0.0

    • setenv DISPLAY targetHostName:0.0

    targetHostName is the name of the computer on which you want to display the installation program UI.


  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 typeCommand

    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

  8. Review the welcome page, and click Next.
  9. Read the license agreement, agree to the terms, and click Next.
  10. On the Upgrade Confirmation page, click Yes, and click Next. The upgrade routine checks the system to see that it meets the upgrade prerequisites, and displays any errors that it discovers. Correct these errors before proceeding with the upgrade.
  11. (Applicable only if you are upgrading from TrueSight Infrastructure Management 10.7) The installer detects the FQDN of the host computer and populates the FQDN field automatically. Confirm this, and click Next
    If you modify the FQDN:

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

    • Do not leave this field empty

    • Ensure that the TrueSight Infrastructure Management server FQDN is accessible from other BMC products.

  12. In the Cloud-vista enabled environment, the Configuring TrueSight Infrastructure Management environment deployment information screen is displayed. Provide the following details, and click Next.

    Select any one of the following options based on your TrueSight Infrastructure Management environment.

    • Single Server Environment Installation: Upgrades the TrueSight Infrastructure Management server as a standalone server.

    • Multiple Server Environment Installation: Upgrades the TrueSight Infrastructure Management server as following:

      • BMC TrueSight Infrastructure Management Central Server: Upgrades this instance as a central server.

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

    FieldDescription
    Host Name/IP AddressFQDN name and IP address of the Central Server Router. FQDN name comprises the host name and the domain name.
    ProtocolProtocol with which to communicate to the Central Server Router. It can be either HTTP or HTTPS protocol.
    PortPort number with which to communicate to the Central Server Router. The default HTTP ports are 80 (Windows) and 8080 (Linux). The default HTTPS ports are 443 (Windows) and 8043 (Linux).
  13. On the Configuring KB Migration Path page, if you have already migrated customized KB definitions to the new standard 11.3.01 KB, select Yes, and browse to the path of the customized KB directory.

    The file path should follow this hierarchy structure:
    \topLevelDirectory\mergedKB\server\etc\cellName , where \server\etc\cellName is the standard sub-directory.

    Warning

    If you have KBs to migrate but have not done so, pause the upgrade process and migrate them before proceeding. See Migrating the configuration of Infrastructure Management cells.

    During the upgrade, the routine copies the KB under the \mergedKB\server\etc\cellName  path and overwrites the KB in the default  installationDirectory \pw\server\etc\cellName path.

  14. Review the installation details, click Install, and click Next.
  15. Select View Logs to open the installation logs, and click Done.

    After you successfully upgrade the TrueSight Infrastructure Management server, the following folder is created under the installation directory, in the BMC Software folder. You can manually delete the files if you do not want them.

    Folder nameDescription
    <installationDirectory>11. (where  x  is the version that you are upgrading from)

    Contains backup files of the earlier TrueSight Infrastructure Management installation.

  16. Ensure that the primary Infrastructure Management server has successfully started by running the pw license list command.
  17. If you have customized service management data in the di_models.baroc file present in the <Infrastructure Management Server Install Directory>\pw\server\etc directory, copy the publishing server kb from the backup directory to the <Infrastructure Management Server Install Directory>\pw\server\etc\<psname> directory.

Important

The system requirements are validated every time you restart the host computer or product services. If the system requirements are not met, the product services are not started. To force-start the product services, see Starting and stopping the TrueSight Operations Management components.


To upgrade the Infrastructure Management server on the secondary computer

  1. Stop the primary TrueSight Infrastructure Management server.
  2. Synchronize the cell database (MCDB) on the primary and secondary servers:
    1. Delete all content in the installedDirectory\TrueSight\pw\server\var\<secondary_cell_name> folder of the secondary server.
    2. Copy all content from the installedDirectory\TrueSight\pw\server\var\<primary_cell_name> folder of the primary server to the above location on the secondary server.
  3. Log in to the host computer on which you want to upgrade the Infrastructure Management Server, and delete all the files from the temporary directory: 

    • (Windows%temp%
    • (Linux/tmp
  4. Extract the downloaded zip files (the upgrade installer) to a temporary location outside the following location to avoid any file sharing conflicts:

    • (WindowsC:\Program Files
    • (Linux) /opt

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

  6. (Linux) Perform the following to archive the old installation files including the user apps, PERL libraries, and any other customization:
    1. Run the pw system stop command to stop the TrueSight Infrastructure Management server.
    2. Tar the /usr/pw directory and place the resulting file in a secure location such as on another server, another file partition, or a directory that lies above /usr/pw.
    3. Save the Crontab entries (especially the database archive entry).

    4. Restart the TrueSight Infrastructure Management Server by using the pw system start command.
    5. Save any custom Apache settings.
  7. (Linux) Run one of the following commands to set the DISPLAY environment to enable the installation program UI to launch:

    • export DISPLAY=targetHostName:0.0

    • setenv DISPLAY targetHostName:0.0

    targetHostName is the name of the computer on which you want to display the installation program UI.


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

    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

  9. Review the welcome page, and click Next.
  10. Read the license agreement, agree to the terms, and click Next.
  11. On the Upgrade Confirmation page, click Yes, and click Next. The upgrade routine checks the system to see that it meets the upgrade prerequisites, and displays any errors that it discovers. Correct these errors before proceeding with the upgrade.
  12. (Applicable only if you are upgrading from TrueSight Infrastructure Management 10.7) The installer detects the FQDN of the host computer and populates the FQDN field automatically. Confirm this, and click Next
    If you modify the FQDN:

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

    • Do not leave this field empty

    • Ensure that the TrueSight Infrastructure Management server FQDN is accessible from other BMC products.

  13. In the Cloud-vista enabled environment, the Configuring TrueSight Infrastructure Management environment deployment information screen is displayed. Provide the following details, and click Next.

    Select any one of the following options based on your TrueSight Infrastructure Management environment.

    • Single Server Environment Installation: Upgrades the TrueSight Infrastructure Management server as a standalone server.

    • Multiple Server Environment Installation: Upgrades the TrueSight Infrastructure Management server as following:

      • BMC TrueSight Infrastructure Management Central Server: Upgrades this instance as a central server.

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

    FieldDescription
    Host Name/IP AddressFQDN name and IP address of the Central Server Router. FQDN name comprises the host name and the domain name.
    ProtocolProtocol with which to communicate to the Central Server Router. It can be either HTTP or HTTPS protocol.
    PortPort number with which to communicate to the Central Server Router. The default HTTP ports are 80 (Windows) and 8080 (Linux). The default HTTPS ports are 443 (Windows) and 8043 (Linux).
  14. On the Configuring KB Migration Path page, if you have already migrated customized KB definitions to the new standard 11.3.01 KB, select Yes, and browse to the path of the customized KB directory.

    Note

    When installing on the secondary server, do not use the KB folder migrated from the primary server. Use the migrated KB folder from the secondary server. 

    The file path should follow this hierarchy structure:
    \topLevelDirectory\mergedKB\server\etc\cellName , where \server\etc\cellName is the standard sub-directory.

    Warning

    If you have KBs to migrate but have not done so, pause the upgrade process and migrate them before proceeding. See Migrating the configuration of Infrastructure Management cells.

    During the upgrade, the routine copies the KB under the \mergedKB\server\etc\cellName  path and overwrites the KB in the default  installationDirectory\pw\server\etc\cellName path.

  15. Review the installation details, click Install, and click Next.
  16. Select View Logs to open the installation logs, and click Done.

    After you successfully upgrade the TrueSight Infrastructure Management server, the following folder is created under the installation directory, in the BMC Software folder. You can manually delete the files if you do not want them.

    Folder nameDescription
    <installationDirectory>11. (where  x  is the version that you are upgrading from)

    Contains backup files of the earlier TrueSight Infrastructure Management installation.

  17. Stop the secondary TrueSight Infrastructure Management server.
  18. Synchronize the cell database (MCDB) on the primary and secondary servers:
    1. Delete all content in the installedDirectory\TrueSight\pw\server\var\<primary_cell_name> folder of the primary server.
    2. Copy all content from the installedDirectory\TrueSight\pw\server\var\<secondary_cell_name> folder of the secondary server to the above location on the primary server.
  19. Start the primary TrueSight Infrastructure Management server.
  20. Start the secondary TrueSight Infrastructure Management server.
  21. If you have customized service management data in the di_models.baroc file present in the <Infrastructure Management Server Install Directory>\pw\server\etc directory, copy the publishing server kb from the backup directory to the <Infrastructure Management Server Install Directory>\pw\server\etc\<psname> directory.
  22. To detect the active and standby nodes, check the HTTP response codes for the following URLs:

    https://<primary hostname>/jsp/ShowError.jsp

    https://<secondary hostname>/jsp/ShowError.jsp

    HTTP response 200 - active node
    HTTP response 503 - standby node

Important

The system requirements are validated every time you restart the host computer or product services. If the system requirements are not met, the product services are not started. To force-start the product services, see Starting and stopping the TrueSight Operations Management components.

Troubleshooting upgrade issues

If you face issues during the upgrade, see  Troubleshooting an Infrastructure Management deployment .

Next step in the Upgrade process

Step 4 Phase B — Now that you have successfully upgraded the Infrastructure Management Server, you must upgrade the Integration Service and remote cells.

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

Comments

  1. Sistemas Securitas direct

    The page has visualization errors such as: tsomd113:Upgrading the Infrastructure Management server in the standalone mode using the wizard was not found. Please check/update the page name used in the 'multiexcerpt-include macro.

    check it please. Thanks!

    Jun 26, 2019 08:28
    1. Rashmi Gokhale

      Hi,

      I have fixed the error and updated the document.

      Sorry for the inconvenience caused.

      Thanks

      Jun 28, 2019 02:18