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.

Upgrade warning

If you have the App Visibility Manager version (Fix Pack 3) configured to work with the SAML authentication type, and want to upgrade your TrueSight Operations Management to version 11.3.01, you must also apply the Fix Pack version 11.3.02 for the SAML authentication type to work.

Complete the pre-upgrade tasks

  1. Review the  System requirements for Presentation Server  to ensure that your system meets the new requirements before starting the upgrade.
  2. 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.

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

  4. Stop any components that are connected to the TrueSight Presentation Server (for example, Infrastructure Management or App Visibility Manager).
  5. 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 

    • TrueSight_sso_port

    • TrueSight_sso_protocol

    • TrueSight_sso_password



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


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

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

Complete the additional tasks if you are upgrading from version 10.7

If you are upgrading from version 10.7, you need to perform the following additional tasks:

Migrate data from Atrium Single Sign-On to Remedy Single Sign-On

Perform these steps:

  1. Install Remedy SSO
  2. Migrate internal user data from Atrium Single Sign-On to Remedy Single Sign-on. 
    For more information, see  Migrating internal user data from Atrium Single Sign-On to Remedy Single Sign-On. .

Migrate data format

Before you start the upgrade, you must run the dataUpgrade utility. This utility migrates the format of the data in TrueSight Presentation Server to the format required after running the upgrade. For more information, see Migrating the data format before upgrading the Presentation Server .

Configure settings on a Linux host

On a Linux host, you need to configure particular system configuration settings.

As a root user, you can change the configurations either manually or by running the script. The script uses ulimit commands to perform the configuration changes.

Ensure that the minimum system configurations required are met by doing one of the following:

  • Configure the properties by running the script

    1. On the host computer, navigate to the <Download location>/Linux/Disk1/utility/ folder, and run the script:

      sh <TSPS_OWNER_NAME>

      <TSPS_OWNER_NAME> is the non-root username with which you want to deploy TrueSight Presentation Server.


      • The TrueSight Presentation Server installation or upgrade on a Linux host must be run as a non-root user.
      • System configuration file settings override the user settings. In case of an error that instructs you to run the script again, ensure that you modify these configuration settings as per the error message before you rerun the script.

      The script changes the system configurations automatically to the values as listed in the System configuration settings table.

    2. After you run the script, open a new Linux user session and log in as a non-root user before launching the TrueSight Presentation Serverinstaller.

  • Configure the properties manually

    1. As a root user, add the properties as listed in the System configuration settings table to the limits.conf file and the sysctl.conf file.


      <TSPS_OWNER_NAME> is the non-root username with which you want to deployTrueSight Presentation Server.

    2. After configuring the virtual memory, run the following command to refresh the configuration changes:

      sysctl -p

    3. Open a new Linux user session, and log in as a non-root user before launching the TrueSight Presentation Serverinstaller.

System configuration settings

File nameProperty and ValueNotes



Ensure that the limits for open files and processes mentioned in the /etc/security/limits.conf and /etc/security/limits.d files are same or the limits in the /etc/security/limits.d file is blank or removed. If the limits are different in these two files, you may get an installation error.

<TSPS_OWNER_NAME> soft nofile 65536

<TSPS_OWNER_NAME> hard nofile 65536

The number of open files must be at least 65536.

<TSPS_OWNER_NAME> soft nproc 4096

<TSPS_OWNER_NAME> hard nproc 4096

The number of open processes must be at least 4096.

<TSPS_OWNER_NAME> soft memlock unlimited

<TSPS_OWNER_NAME> hard memlock unlimited

The memory lock should be set to unlimited.

<TSPS_OWNER_NAME> soft as unlimited

<TSPS_OWNER_NAME> hard as unlimited

The maximum virtual memory should be unlimited.

To configure the value for non-root user, some operating systems require that root user should also have unlimited maximum virtual memory. In such instances, add the following lines:

root soft as unlimited
root hard as unlimited
/etc/sysctl.confvm.max_map_count=262144Maximum Map Count  is the maximum number of memory map areas a process may have.The virtual memory property max_map_count must be configured to at least 262144.

Merge customizations performed in the configuration files

While upgrading the TrueSight Presentation Server, the following files are copied from the %TRUESIGHTPSERVER_HOME%\truesightpserver\conf\services directory to the %TRUESIGHTPSERVER_HOME%\truesightpserver\conf\custom directory.

  • csr.conf 
  • idxsrv.conf

If you have customized these configuration files, your changes are retained as specified in the following table (for the given properties). If you have customized any other properties, you must manually merge the changes in the respective files in the %TRUESIGHTPSERVER_HOME%\truesightpserver\conf\custom directory.


After the upgrade, the configuration files in the %TRUESIGHTPSERVER_HOME%\truesightpserver\conf\custom directory are given preference over the files in the %TRUESIGHTPSERVER_HOME%\truesightpserver\conf\services directory.

While upgrading from version 11.0 or later the complete %TRUESIGHTPSERVER_HOME%\truesightpserver\conf\custom directory is copied over to the new version and therefore these changes are not required.

File namePropertyRemarks
csr.confvm.args.system.2=-Xmx4096m - maximum heap size value settingThe higher value between the customized and default values is retained.
vm.args.system.14=-Datsso.log.roll=3 - atsso rolled over log files countThe value from the version that you upgraded from is retained.
vm.args.system.15=-Datsso.log.limit=1000000The value from the version that you upgraded from is retained. value from the version that you upgraded from is retained.
idxsrv.confvm.args.system.2=-Xmx4096m - maximum heap size value settingThe higher value between the customized and default values is retained.
vm.args.system.2=-Xms256m - minimum heap size value settingThe value is changed to be the same as the maximum heap size value. The maximum and minimum heap size values must be identical for the Elastic Search container to start.
vm.args.system.4=-Xss256k - thread stack sizeThe higher value between the customized and default values is retained.

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