Upgrading the Presentation Server in the high-availability mode silently

Where you are in the Upgrade process

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

Before you begin

Go to the secondary computer and stop the TrueSight Presentation Server:

  • (Windows) Navigate to the TrueSightPServer\truesightpserver\bin directory, and run tssh server stop command.
  • (Linux) Navigate to the TrueSightPServer/truesightpserver/bin directory, and run ./tssh server stop command.

To upgrade the TrueSight Presentation Server in the high-availability mode using the silent installer

You need to perform the following tasks to upgrade TrueSight Presentation Server in a high-availability environment.

No additional steps are required to configure the load balancer.

Step A: Upgrade the TrueSight Presentation Server on the primary computer

Tip

To know whether the computer on which you plan to upgrade is the primary computer or the secondary computer, run the tssh ha status command.

  1. On the primary computer, extract the downloaded files to an appropriate directory:
    • (WindowsC:\Program Files

    • (Linux) /opt

  2. (Linux) Perform the following steps to provide ownership permissions to the non-root user for all the upgrade-related installation files:

    1. Log on as a root user.
    2. Run the following command:

      chown -R <nonrootuser> <installationDirectoryFolderName>

      In the preceding command, the following definitions apply:

      • <nonrootuser> is the name of the non-root user.

      • <installationDirectoryFolderName> is the name of the folder that contains the installation files. 

      For example, chown -R nonrootuser /Linux/Disk1.

  3. (applicable if you are upgrading from a version earlier than 11.0) You need to provide details of the Remedy Single Sign-On server that you plan to use with the TrueSight Presentation Server:
    1. You will need to type the database administrator password and the Remedy Single Sign-On password in an encrypted form in the silent options file. Encrypt the password using the TrueSightPServerMaintenanceTool through the wizard or command line interface.

        Encrypt password using the wizard
      1. Open the TrueSightPServerMaintenanceTool by navigating to:
        • (Windows<DownloadLocation>\Windows\Disk1\Utility
        • (Linux<DownloadLocation>/Linux/Disk1/Utility
      2. Run the tool, and click the Encrypt tab.
      3. Type the password, confirm it, and click Encrypt.
      4. Note down the encrypted password. (Example: DES\:097133405e7ea7a6bcc58bbe70ece4c2)
        Encrypt password using the command line interface
      1. Navigate to the following directory:
        • (Windows<DownloadLocation>\Windows\Disk1\Utility
        • (Linux<DownloadLocation>/Linux/Disk1/Utility
      2. Run the following command:
        • (Windows)TrueSightPServerMaintenanceTool.cmd -silent -encrypt -encrypt -password=<password> -confirm_password=<password>
        • (Linux)./TrueSightPServerMaintenanceTool.sh -silent -encrypt -encrypt -password=<password> -confirm_password=<password>

          Note

          ( Linux ) If the password contains special characters, enclose the password using single quotes as shown in the following example: ./TrueSightPServerMaintenanceTool.sh -silent -encrypt -encrypt -password='<password>' -confirm_password='<password>'
      3. Note down the encrypted password. (Example: DES\:097133405e7ea7a6bcc58bbe70ece4c2)
    2. Go to the extracted folder, and locate the silent options file:
      • (Windows) <DownloadLocation>\Windows\Disk1\server-silent-options-upgrade-windows.txt
      • (Linux<DownloadLocation>/Linux/Disk1/server-silent-options-upgrade-linux.txt
    3. Edit the silent options file. This is a text file that defines the installation properties in the form of a prefix tag followed by a property name and value pair. You can either retain the default values or change them and save the file.

        Property details

      -J precedes Java properties

      Property name Description
      -J TrueSight_sso_hostname Type the FQDN of Remedy SSO.Example: -J TrueSight_sso_hostname=rsso.bmc.com
      -J TrueSight_sso_port Type the Remedy SSO server port number.Default value:(Windows) 448(Linux) 8048Example:-J TrueSight_sso_port=448
      -J TrueSight_sso_password Type the Remedy SSO server superuser password in an encrypted format. The Remedy SSO superuser name is Admin.Example:-J TrueSight_sso_password=
      DES\:097133405e7ea7a641f019bca8781280e74e86a9fec4ad58
      -J TrueSight_sso_protocol Type the protocol in which Remedy SSO is configured.By default, Remedy SSO is configured in the HTTPS mode.Example:-J TrueSight_sso_protocol=https
      -J IS_SSO_SERVER_CERTIFICATE Type one of the following values:
      • false: Indicates that you can import the Remedy SSO certificate after the installation is completed.
        For more information, see Applying Remedy Single Sign-On Server private certificate to the TrueSight Presentation Server.
      • true: Indicates that you need to import the Remedy SSO private certificate during the TrueSight Presentation Server installation.
      Default value: falseExample: -J IS_SSO_SERVER_CERTIFICATE=false
      J SSO_CERTIFICATE_HOME If you have set the IS_SSO_SERVER_CERTIFICATE property to true, type the complete path of the Remedy SSO certificate as the value of this property. Example: -J SSO_CERTIFICATE_HOME=<RSSO install directory>\rssocert.crt


    Note

    Ensure that the following system requirements are met. If your target computer does not meet these requirements, you cannot proceed with the upgrade. 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
  4. At the command prompt, run one of the following commands to start the upgrade. Type the complete path to the silent options file in the command. If the path includes a blank space, enclose the path within double quotes.

    Environment type Command
    If you are upgrading from version 11.0
    Production environment with the existing encryption setting
    • (Windowssetup.exe -i silent
    • (Linux - as a non-root user)./setup.bin -i silent
    Test environment with the existing encryption setting
    • (Windowssetup.exe -J MINIMAL=TRUE -i silent
    • (Linux - as a non-root user)./setup.bin -J MINIMAL=TRUE -i silent
    If you are upgrading from a version earlier than 11.0
    Production environment with the existing encryption setting
    • (Windowssetup.exe -i silent -DOPTIONS_FILE="<path_to_server-silent-options-upgrade-windows.txt_file>"
    • (Linux - as a non-root user)./setup.bin -i silent -DOPTIONS_FILE="<path_to_server-silent-options-upgrade-linux.txt_file>"

    Example

    • (Windowssetup.exe -i silent -DOPTIONS_FILE=C:\tempfolder\Disk1\server-silent-options-upgrade-windows.txt
    • (Linux)./setup.bin -i silent -DOPTIONS_FILE=/opt/tempfolder/Disk1/server-silent-options-upgrade-linux.txt
    Test environment with the existing encryption setting
    • (Windowssetup.exe -J MINIMAL=TRUE -i silent -DOPTIONS_FILE=C:\Disk1\server-silent-options-upgrade-windows.txt
    • (Linux - as a non-root user)./setup.bin -J MINIMAL=TRUE -i silent -DOPTIONS_FILE=/opt/Disk1/server-silent-options-upgrade-linux.txt

    Example

    • (Windows) setup.exe -J MINIMAL=TRUE -i silent -DOPTIONS_FILE=C:\Disk1\server-silent-options-upgrade-windows.txt
    • (Linux - as a non-root user)./setup.bin -J MINIMAL=TRUE -i silent -DOPTIONS_FILE=/opt/Disk1/server-silent-options-upgrade-linux.txt
    Note: On Linux, ensure that you start a new session as a non-root user to run the upgrade. Do not use the su command to start a non-root session.

  5. The upgrade might take upto 15 minutes. You can periodically check the installation status by checking the truesightpserver_install_log.txt file located at: 

    • (Windows) %temp%
    • (Linux /tmp

  6. Locate the following log message in the truesightpserver_install_log.txt file to ensure that the Presentation Server is upgraded successfully:

    Log messageTrueSight Presentation Server 11.3.01 install succeeded.

  7. Verify the TrueSight Presentation Server status:

    • (Windows) Navigate to the TrueSightPServer\truesightpserver\bin directory, and run the tssh server status command.
    • (Linux) Navigate to the TrueSightPServer/truesightpserver/bin directory, and run the ./tssh server status command.

    A list of include Presentation Server processes are displayed as shown in the following example.

    Process status
    ================================
    Core Server     Running (13176)
    Index Server    Running (11028)
    Database Server Running (6052)

    If errors occur when you run the tssh server status command, restart the TrueSight Presentation Server by running the following command:

    • (Windowstssh server start

    • (Linuxtssh server start&
      The & character at the end of the tssh server start command ensures that the process runs in the background, and you can continue to use the shell.
  8. (Applicable if you customized Tomcat files before the upgrade) Manually re-add the modifications in the web.xml and server.xml files.
  9. (Applies only if you had configured HTTP access before the upgrade) Reconfigure the TrueSight Presentation Server for HTTP access as described in the steps.

      Steps for configuring HTTP access
    1. Log in to the Presentation Server host computer, and navigate to the following directory:

      • (Windows): <Presentation Server installation directory>\truesightpserver\modules\tomcat\conf
      • (Linux): <Presentation Server installation directory>/truesightpserver/modules/tomcat/conf
    2. In a text editor, edit the \web.xml file and comment out the security-constraint section so that it reads as follows:

      <!--

      <security-constraint>

              <web-resource-collection>

                  <web-resource-name>Secure context</web-resource-name>

                  <url-pattern>/*</url-pattern>

                  </web-resource-collection>

                  

                  <user-data-constraint>

                  <transport-guarantee>CONFIDENTIAL</transport-guarantee>

                  </user-data-constraint>

          </security-constraint>

      -->

    3. In a text editor, edit the <Presentation Server installation directory>\truesightpserver\modules\tomcat\conf\server.xml file:
      1. Modify the following line:

        <Connector connectionTimeout="20000" enableLookups="false" port="80" protocol="HTTP/1.1" redirectPort="443"/>

        Then, remove the redirectPort information and copy the compressableMimeType, compression, and compressionMinSize property information from the HTTPS connector so that it reads as follows:

        <Connector connectionTimeout="20000" enableLookups="false" port="80" protocol="HTTP/1.1" compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript,application/json" compression="on" compressionMinSize="1024" />

        Note

        The default port for Windows is 80 and Linux is 8080. If you specified a custom port during installation, enter that port number instead.

      2. Comment out the following line so that it reads as follows:

        <!-- <Connector SSLEnabled="true" ciphers="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
        TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,
        TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_SHA256,
        TLS_ECDHE_RSA_WITH_AES_128_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_SHA,TLS_ECDHE_RSA_WITH_AES_256_SHA384,
        TLS_ECDHE_ECDSA_WITH_AES_256_SHA384,TLS_ECDHE_RSA_WITH_AES_256_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_SHA,
        TLS_DHE_RSA_WITH_AES_128_SHA256,TLS_DHE_RSA_WITH_AES_128_SHA,TLS_DHE_DSS_WITH_AES_128_SHA256,
        TLS_DHE_RSA_WITH_AES_256_SHA256,TLS_DHE_DSS_WITH_AES_256_SHA,TLS_DHE_RSA_WITH_AES_256_SHA"
        clientAuth="false" compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript,application/json" compression="on" compressionMinSize="1024" keystoreFile="C:/Program Files/BMC Software/TrueSightPServer/truesightpserver/conf/secure/loginvault.ks" keystorePass="changeit" maxThreads="150" port="4435" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslProtocol="TLSv1.2" useServerCipherSuitesOrder="true"/>
        -->

    4. From the <Presentation Server installation directory>\truesightpserver\truesightpserver\bin folder, use a command prompt to run the following commands:

      tssh properties set tspsPreferredWebServiceProtocol http

      tssh properties set tsps.xsrf.cookie.secure false

    5. If you want to use the TrueSight console to deploy and install packages on a PATROL Agent, from the <Presentation Server installation directory>\truesightpserver\truesightpserver\bin folder, use a command prompt to run the following command:

      tssh properties set server.port.websrv.protocol http

    6. Restart the TrueSight Presentation Server. 
    7. On each Infrastructure Management server connected to the TrueSight Presentation Server, set the following properties In the <Infrastructure Management installation directory>\pw\custom\conf\pronet.conf file:

      • tsps.tsim.http.enabled=true

      • pronet.xsrf.token.secure=false

    8. On each Infrastructure Management server, reload the newly updated properties of the Infrastructure Management server running the pw jproperties reload command.

Step B: Upgrade the TrueSight Presentation Server on the secondary computer

Note

Before you upgrade TrueSight Presentation Server on the secondary computer, the primary computer must be running and in active mode.

To know the primary computer status, run the tssh ha status command.

  1. On the secondary computer, extract the downloaded files to an appropriate directory:
    • (WindowsC:\Program Files

    • (Linux) /opt

  2. (Linux) Perform the following steps to provide ownership permissions to the non-root user for all the upgrade-related installation files:

    1. Log on as a root user.
    2. Run the following command:

      chown -R <nonrootuser> <installationDirectoryFolderName>

      In the preceding command, the following definitions apply:

      • <nonrootuser> is the name of the non-root user.

      • <installationDirectoryFolderName> is the name of the folder that contains the installation files. 

      For example, chown -R nonrootuser /Linux/Disk1.


    Note

    Ensure that the following system requirements are met. If your target computer does not meet these requirements, you cannot proceed with the upgrade. 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
  3. At the command prompt, run one of the following commands to start the upgrade. Type the complete path to the silent options file in the command. If the path includes a blank space, enclose the path within double quotes.

    Environment type Command
    If you are upgrading from version 11.0
    Production environment with the existing encryption setting
    • (Windowssetup.exe -i silent
    • (Linux - as a non-root user)./setup.bin -i silent
    Test environment with the existing encryption setting
    • (Windowssetup.exe -J MINIMAL=TRUE -i silent
    • (Linux - as a non-root user)./setup.bin -J MINIMAL=TRUE -i silent
    If you are upgrading from a version earlier than 11.0
    Production environment with the existing encryption setting
    • (Windowssetup.exe -i silent -DOPTIONS_FILE="<path_to_server-silent-options-upgrade-windows.txt_file>"
    • (Linux - as a non-root user)./setup.bin -i silent -DOPTIONS_FILE="<path_to_server-silent-options-upgrade-linux.txt_file>"

    Example

    • (Windowssetup.exe -i silent -DOPTIONS_FILE=C:\tempfolder\Disk1\server-silent-options-upgrade-windows.txt
    • (Linux)./setup.bin -i silent -DOPTIONS_FILE=/opt/tempfolder/Disk1/server-silent-options-upgrade-linux.txt
    Test environment with the existing encryption setting
    • (Windowssetup.exe -J MINIMAL=TRUE -i silent -DOPTIONS_FILE=C:\Disk1\server-silent-options-upgrade-windows.txt
    • (Linux - as a non-root user)./setup.bin -J MINIMAL=TRUE -i silent -DOPTIONS_FILE=/opt/Disk1/server-silent-options-upgrade-linux.txt

    Example

    • (Windows) setup.exe -J MINIMAL=TRUE -i silent -DOPTIONS_FILE=C:\Disk1\server-silent-options-upgrade-windows.txt
    • (Linux - as a non-root user)./setup.bin -J MINIMAL=TRUE -i silent -DOPTIONS_FILE=/opt/Disk1/server-silent-options-upgrade-linux.txt
    Note: On Linux, ensure that you start a new session as a non-root user to run the upgrade. Do not use the su command to start a non-root session.

  4. The upgrade might take upto 15 minutes. You can periodically check the installation status by checking the truesightpserver_install_log.txt file located at: 

    • (Windows) %temp%
    • (Linux /tmp

  5. Locate the following log message in the truesightpserver_install_log.txt file to ensure that the Presentation Server is upgraded successfully:

    Log messageTrueSight Presentation Server 11.3.01 install succeeded.

  6. Verify the TrueSight Presentation Server status:

    • (Windows) Navigate to the TrueSightPServer\truesightpserver\bin directory, and run the tssh server status command.
    • (Linux) Navigate to the TrueSightPServer/truesightpserver/bin directory, and run the ./tssh server status command.

    A list of include Presentation Server processes are displayed as shown in the following example.

    Process status
    ================================
    Core Server     Running (13176)
    Index Server    Running (11028)
    Database Server Running (6052)

    If errors occur when you run the tssh server status command, restart the TrueSight Presentation Server by running the following command:

    • (Windowstssh server start

    • (Linuxtssh server start&
      The & character at the end of the tssh server start command ensures that the process runs in the background, and you can continue to use the shell.
  7. (Applicable if you customized Tomcat files before the upgrade) Manually re-add the modifications in the web.xml and server.xml files.
  8. (Applies only if you had configured HTTP access before the upgrade) Reconfigure the TrueSight Presentation Server for HTTP access as described in the steps.

      Steps for configuring HTTP access
    1. Log in to the Presentation Server host computer, and navigate to the following directory:

      • (Windows): <Presentation Server installation directory>\truesightpserver\modules\tomcat\conf
      • (Linux): <Presentation Server installation directory>/truesightpserver/modules/tomcat/conf
    2. In a text editor, edit the \web.xml file and comment out the security-constraint section so that it reads as follows:

      <!--

      <security-constraint>

              <web-resource-collection>

                  <web-resource-name>Secure context</web-resource-name>

                  <url-pattern>/*</url-pattern>

                  </web-resource-collection>

                  

                  <user-data-constraint>

                  <transport-guarantee>CONFIDENTIAL</transport-guarantee>

                  </user-data-constraint>

          </security-constraint>

      -->

    3. In a text editor, edit the <Presentation Server installation directory>\truesightpserver\modules\tomcat\conf\server.xml file:
      1. Modify the following line:

        <Connector connectionTimeout="20000" enableLookups="false" port="80" protocol="HTTP/1.1" redirectPort="443"/>

        Then, remove the redirectPort information and copy the compressableMimeType, compression, and compressionMinSize property information from the HTTPS connector so that it reads as follows:

        <Connector connectionTimeout="20000" enableLookups="false" port="80" protocol="HTTP/1.1" compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript,application/json" compression="on" compressionMinSize="1024" />

        Note

        The default port for Windows is 80 and Linux is 8080. If you specified a custom port during installation, enter that port number instead.

      2. Comment out the following line so that it reads as follows:

        <!-- <Connector SSLEnabled="true" ciphers="TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
        TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,
        TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_SHA256,
        TLS_ECDHE_RSA_WITH_AES_128_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_SHA,TLS_ECDHE_RSA_WITH_AES_256_SHA384,
        TLS_ECDHE_ECDSA_WITH_AES_256_SHA384,TLS_ECDHE_RSA_WITH_AES_256_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_SHA,
        TLS_DHE_RSA_WITH_AES_128_SHA256,TLS_DHE_RSA_WITH_AES_128_SHA,TLS_DHE_DSS_WITH_AES_128_SHA256,
        TLS_DHE_RSA_WITH_AES_256_SHA256,TLS_DHE_DSS_WITH_AES_256_SHA,TLS_DHE_RSA_WITH_AES_256_SHA"
        clientAuth="false" compressableMimeType="text/html,text/xml,text/plain,text/css,text/javascript,application/javascript,application/json" compression="on" compressionMinSize="1024" keystoreFile="C:/Program Files/BMC Software/TrueSightPServer/truesightpserver/conf/secure/loginvault.ks" keystorePass="changeit" maxThreads="150" port="4435" protocol="org.apache.coyote.http11.Http11NioProtocol" scheme="https" secure="true" sslProtocol="TLSv1.2" useServerCipherSuitesOrder="true"/>
        -->

    4. From the <Presentation Server installation directory>\truesightpserver\truesightpserver\bin folder, use a command prompt to run the following commands:

      tssh properties set tspsPreferredWebServiceProtocol http

      tssh properties set tsps.xsrf.cookie.secure false

    5. If you want to use the TrueSight console to deploy and install packages on a PATROL Agent, from the <Presentation Server installation directory>\truesightpserver\truesightpserver\bin folder, use a command prompt to run the following command:

      tssh properties set server.port.websrv.protocol http

    6. Restart the TrueSight Presentation Server. 
    7. On each Infrastructure Management server connected to the TrueSight Presentation Server, set the following properties In the <Infrastructure Management installation directory>\pw\custom\conf\pronet.conf file:

      • tsps.tsim.http.enabled=true

      • pronet.xsrf.token.secure=false

    8. On each Infrastructure Management server, reload the newly updated properties of the Infrastructure Management server running the pw jproperties reload command.

    Your upgrade is now complete.

    You do not need additional configurations for the load balancer.

Notes

  • The system requirements are validated each 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.

  • In the previous installation, if an IP address was used to access the TrueSight console, post upgrade, map the IP address to the FQDN in the following file:
    • (Windows)System32\drivers\etc\hosts
    • (Linux) \etc\hosts

    After mapping, update bookmarked IP addresses (in browsers) to refer to this FQDN.

  • Post upgrade, check to ensure custom tuning parameters, if any, are correct. If required, restore them by using the backup files located at installationDirectory\TrueSightPServer\truesightpserver_<version>\conf\services and copy them to the installationDirectory\conf\custom folder.

  • (Applicable if you are upgrading from a version earlier than 11.0) If you were using an IP address to access or cross-launch the TrueSight Infrastructure Management servers, you need to change the IP address to the FQDN.

      Steps for changing the IP address to the FQDN
    1. On the TrueSight console, navigate to Administration > Components.
    2. Edit the TrueSight Infrastructure Management components.
    3. Change the host name from the IP address to the FQDN and save the details.


Troubleshooting upgrade issues

If you face issues related to upgrade, see  Troubleshooting the Presentation Server deployment .

After an unsuccessful upgrade, if you want to restore to the earlier version, see Restoring the earlier version of the Presentation Server if the upgrade fails. .

Next step in the Upgrade process

Now that you have successfully upgraded the TrueSight Presentation Server, upgrade the other TrueSight components as per your requirements. For instructions, see Upgrading.

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

Comments