Preparing to upgrade the Presentation Server

Before upgrading the TrueSight Presentation Server, ensure that your environment meets the upgrade requirements, and complete the tasks described in this section.

Complete the pre-upgrade tasks

  1. Review the  System requirements for Presentation Server Open link  to ensure that your system meets the new requirements before starting the upgrade.
  2. Review the Troubleshooting version 11.3.04 upgrade and post-upgrade issues to ensure that you are aware of workarounds before starting the upgrade.
  3. If you have custom security certificates for the internal communication between the TrueSight Presentation Server and TrueSight App Visibility Manager, ensure that your files are not overwritten by the upgrade process. See instructions  in Applying private certificates between the App Visibility portal and the Presentation Server. Open link
  4. As a best practice and to avoid a file lock happening during the upgrade process, exclude the installation directory from the on-access virus scanner. For more information, see Disable on-access virus scanners. Open link

  5. Ensure the following Health Check Tool tasks are completed:

    1. Download, install, and run the latest version of the TrueSight Health Check Tool Open link at least once in the 24-hour period preceding the upgrade process.
    2. From the TrueSight Health Check Tool report saved at the following location, search for the Upgrade Impact  issues:
      • (Windows)%TRUESIGHTPSERVER_HOME%\utility\TrueSightHealthCheck\reports
      • (Linux)$TRUESIGHTPSERVER_HOME$/utility/TrueSightHealthCheck/reports
    3. Resolve all the issues.
    4. Run the TrueSight Health Check Tool again and ensure that there are no issues found in the report.

    Note: The installer will not allow you to continue the upgrade process if there are issues found in the Health Check Tool report.

  6. Stop any components that are connected to the TrueSight Presentation Server (for example, Infrastructure Management or App Visibility Manager).
  7. (On Linux) Verify and ensure that you have the fontconfig-2.13.0-4.3.el7.x86_64.rpm font file has been installed as follows:
    1. Run the fc-list : file command to verify if the font exists. 
    2. (If the font is not present) Download the fontconfig-2.13.0-4.3.el7.x86_64.rpm file.
    3. Run the yum install -y dejavu-serif-fonts command to install the font.
  8. Verify and ensure that the following properties in the <Installation_Directory>/TrueSightPServer/TrueSightPServerInstalledConfiguration.xml file is up-to-date. Update them, if required:
    • TrueSight_sso_hostname - Update this property only if have changed the Remedy SSO hostname after installation. 

    • IS_SSO_SERVER_IN_HA_MODE - Update this property to 'true' if you have newly added a Remedy SSO certificate or to 'false' if you have removed an existing Remedy SSO certificate. 

    • SSO_CERTIFICATE_HOME - Only if you set the "IS_SSO_SERVER_IN_HA_MODE" property to true, set this property to some dummy path. For example, (Linux) /tmp/rsso.cer or (Windows) C:\tmp\rsso.cer. Otherwise, it can be left blank.

  9. Back up the following:
    • Database: Run the tssh database startbackup command to back up the database.
    • Files: Manually back up the following files:
      • /opt/bmc/ProductRegistry.xml (Linux)
      • C:\Windows\ProductRegistry.xml (Windows)
        (This file contains details about the currently installed product such as the installation directory, product version, and so on. If the ProductRegistry.xml file is not present, contact BMC Support.)
      • <Installation_Directory>/TrueSightPServer/TrueSightPServerInstalledConfiguration.xml
  10. Ensure that you have the following privileges:

    • (Windows) Administrator privileges or permissions.
    • (Linux) Non-root user permissions. To be able to perform the installation, a non-root user needs the following permissions:

      • Execute permission for the /Linux/Disk1/setup.bin and /Linux/Disk1/install.sh files.
      • Read, write, and execute permissions for the /tmp directory.
      • Read and write permissions for the /opt/bmc directory.

      Note: After the installation is complete, you can revoke the write permission on /opt/bmc directory.

  11. Ensure that you have set the following property to 4096 in the /etc/security/limits.conf file or the limits file in the /etc/security/limits.d directory.

    <TSPS_OWNER_NAME> soft nproc 4096

    <TSPS_OWNER_NAME> hard nproc 4096

    Notes:

      • Precedence: The values you set in the limits file in the /etc/security/limits.d directory takes higher precedence.

      • Install Error: Do not set different values for the same properties in the /etc/security/limits.conf file and the limits file in the /etc/security/limits.d directory. Either both files must contain the same settings or there are do not set any properties in the limits file in the /etc/security/limits.d directory. If the values are different in these two files, you may get an installation error.

  12. Ensure that the TrueSight Presentation Server is running before starting the upgrade.  For information about starting the service, see  Starting and stopping the TrueSight Operations Management components. Open link

    Note

    Before starting the upgrade, ensure that the status of the TrueSight Presentation Server is Running.

  13. Ensure that the host machine has a disk space equivalent to the following before upgrading the TrueSight Presentation Server:
    Size of the TrueSight Presentation Server installation directory excluding the size of the cma folder at <Installation_Directory>\modules\cma with an additional 2 GB capacity for the TrueSight Presentation Server installer.

  14. Close all the files and folders opened in the current session. Also, close other user sessions on the server before starting the upgrade.

Complete the additional tasks for high-availability mode

The following steps are applicable only if the Presentation Server is in the high-availability mode.

  1. Stop the primary and secondary Presentation Server.

  2. On both the primary and the secondary servers, do the following:

    1. Tar or zip the TRUESIGHTPSERVER_HOME directory.

    2. Back up the /opt/bmc/ProductRegistry.xml and /opt/bmc/ProductRegistry.xsd files.
  3. Start the primary Presentation Server.
  4. Ensure that the logon page is displayed.
  5. Verify the load balancer configuration. For more information, see Guidelines for load balancers.

Where to go from here

If you are upgrading the product, perform the other pre-upgrade tasks listed in the Preparing to upgrade TrueSight Operations Management solution page. 

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

Comments

  1. Sachin Aru

    Step 6
    Backup files: ProductRegistry.xml

    Can you confirm if this is platform-dependent? If not can you list location for both Unix and Windows?

    Nov 18, 2020 10:13
    1. Krutarth Mohakud

      Sachin Aru , thanks for the remark. I have updated the location for Windows.

      Dec 10, 2020 03:42
  2. Giles Day

    Please update file paths for Windows

    Dec 08, 2020 09:08
    1. Krutarth Mohakud

      Hi Giles Day , thanks for the suggestion. We have updated the paths for Windows ProductRegistry.xml.

      Dec 10, 2020 05:12