Upgrading the Presentation Server in the standalone mode using the wizard

Where you are in the Upgrade process

To upgrade the TrueSight Presentation Server in the wizard-based mode

  1. Extract the downloaded files (the upgrade installer) to a temporary location outside the following location to avoid any file sharing conflicts:

    • (Windows) C:\Program Files

    • (Linux) /opt

      Note

      (Applicable for upgrade on a Linux computer) If you do not extract the upgrade installation files on the Presentation Server host computer (on which you want to perform the upgrade), it is possible that the install.sh and setup.bin files do not have the required executable permissions. You might need to provide executable permissions to these files by running the chmod -R 755 installationDirectoryFolderName command.
      For example, chmod -R 755 /Linux/Disk1.

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

    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.

    Requirements for upgrade
    • 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. (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.

  4. Navigate to the Disk1 directory of the extracted folder, use one of the following options to run the installer.

    Note: You can ignore the following message displayed on the Linux console immediately after you started running the install.sh:

    Ensure to run Disk1/utility/PreinstallConfig.sh script to configure env before running installer with non-root user ulimit now set to 65536.
  5. Review the welcome page, and click Next.
  6. Read the license agreement, agree to the terms, and click Next. 
  7. On the Upgrade Confirmation page, click Yes, and click Next.

  1. (Applicable if you are upgrading from a version earlier than 11.0) Provide the following details for Remedy SSO and click Next. 

    1. Type the FQDN of the host computer on which you have installed Remedy SSO. 
    2. Type the tomcat port number that you have configured while installing Remedy SSO. The default port number for Remedy SSO is:
      • (Windows) HTTPS: 448 and HTTP: 88
      • (Linux) HTTPS: 8048 and HTTP: 8088
    3. Type the Remedy SSO server superuser password. The Remedy SSO superuser name is Admin.
    4. Select HTTP or HTTPS depending on the Remedy SSO configuration. By default, Remedy SSO is configured in the HTTPS mode.
    5. Select Yes or No to import the Remedy SSO private certificate. If you select:

  2. Preview the details, and verify the configurations.

  3. Click Install to start the upgrade. A local upgrade may take upto 15 minutes.
    After the upgrade is complete, the Installation Summary page is displayed.

  4. Click View Log to view the upgrade log details on the screen. From the log view, you can expand and view the log messages. You can also navigate to the following default location of logs:

    • (Windows) \Temp\truesightpserver_install_log.txt
    • (Linux)/tmp/truesightpserver_install_log.txt
  5. Click Done to exit the installer.
    Note: (Optional) After the installation is complete, you can revoke the write permission on the /opt directory.

  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:

    • (Windows) tssh server start
    • (Linux) tssh 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. Launch the TrueSight Presentation Server application with the following URL:

    • (Windows) http(s)://<TSPS_FQDN>
    • (Linux) http(s)://<TSPS_FQDN>:<tomcat_port>

  9. Type the default Admin credentials (User name: admin, Password: admin12345), and click Log In.

    The TrueSight console opens.

    By default, only External Report attribute set type is displayed when you upgrade. Other native attribute set types are not displayed. To see native attribute set types, see Troubleshooting Infrastructure Management. 

  10. (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" />
        NoteThe 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.

  11. (Linux only) Register the BMCTSPSSvc.service service by performing the following steps:Note: The systemd service BMCTSPSSvc.service is supported only from version 11.3.04. For more information on this service, see Starting-and-stopping-the-TrueSight-Operations-Management-components.
    1. As a root user, run the tssh service register <Non-RootUserName>. This command registers the BMCTSPSSvc.service service under the /etc/systemd/system folder.
    2. (SUSE Linux Enterprise Server only) Run the chkconfig --add BMCTSPSSvc.service command.
    If you restart the TrueSight Presentation Server  host without registering the BMCTSPSSvc service, the processes do not come up and you will need to start the TrueSight Presentation Server manually.Verify whether the service is registered with the following steps:
    1. Ensure that you have read and write permissions for the installedDirectory\truesightpserver\logs\tssh.log file.
    2. Running the systemctl status BMCTSPSSvc.service command.
    To start and stop the service, run the following commands:
    • systemctl start BMCTSPSSvc.service
    • systemctl stop BMCTSPSSvc.service 

  1. (Optional) Perform the steps mentioned in the Troubleshooting a failed deployment only if both of the following statements are true:

    • You have upgraded the TrueSight Presentation Server to version 11.3.04, but you are not planning to upgrade your Integration Service or TrueSight Infrastructure Management server (they are running on one of the lower versions, such as 11.3.03 or earlier.)
    • You are using the BMC-provided security certificates.



Post-upgrade notes

  • 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, you can ignore the following messages in these two log files:

    • database.stdout.log

      ERROR: role "admin" already exists
      STATEMENT: CREATE ROLE admin;
      ERROR: database "truesight" already exists

    • DBBackupAndRestoreErrorLog.log

      psql:C:/NDL/TrueSightPServer/db_backup.sql:14: ERROR: role "admin" already exists
      psql:C:/NDL/TrueSightPServer/db_backup.sql:28: ERROR: database "truesight" already exists

  • If you have configured any custom tuning parameters, check and ensure that they 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.

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.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*