This topic explains how to upgrade the Presentation Server from version 10.1 or 10.5 to the current version. You can upgrade the Presentation Server using the upgrade wizard, or you can use the silent upgrade  procedure.

Before you begin


To provide required permissions to non-root users on Linux

On Linux computers, you can upgrade the Presentation Server only as a non-root user. Though the non-root user may already have ownership permissions for the destination directory, you must provide ownership permissions for the executables to the non-root user.

  1. Log on as a root user.
  2. Provide ownership permissions to non-root users for all installation files by running the following command: 

    chown -R nonrootuser installationDirectoryFolderName

    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. Apply executable rights to the installation files by running the following command:

    chmod -R 755 installationDirectoryFolderName

    For example,   chmod -R 755 /Linux/Disk1  

To upgrade the Presentation Server

Note

    Page not found for multiexcerpt macro.
The page: Upgrading the Infrastructure Management server on Microsoft Windows was not found. Please check/update the page name used in the 'multiexcerpt-include macro.

  1. Launch the installation wizard:
    • (Windows) Navigate to Windows\Disk1 and double-click setup.exe.

    • (Linux) As a non-root user, navigate to Linux/Disk1 and run ./setup.bin.

      Note

      Ensure that you have set the DISPLAY environment variable.

  2. On the Welcome page, click Next.
  3. On the License Agreement page, read the agreement and select the I agree to the terms of the license agreement option, and click Next
    If you do not agree to the terms of the license agreement, the installation process will not continue.
  4. On the Upgrade Confirmation page, click Yes, and click Next.
    The installer automatically verifies the upgrade requirements. If it finds any errors, it displays them in a separate window. You can quit the upgrade process at this point, correct the indicated discrepancies, and then rerun the upgrade.

    Important

    After you confirm, the Presentation Server is stopped temporarily and is started automatically post-upgrade.

  5. Verify that the information on the Installation Preview page reflects your upgrade correctly. Click Previous  to make changes, or click Install .
  6. After the upgrade is complete, click View Log to view the log files and confirm that the upgrade process was successful.
  7. Click Done to exit the installation wizard.
  8. (Optional) If you had configured the Presentation Server for HTTP access before the upgrade, reconfigure it again:

    1. In a text editor, edit the <Presentation Server installation directory>\truesightpserver\modules\tomcat\conf\web.xml file.
      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>

      -->

    2. Run the following commands from the <InstalledDirectory>\truesightpserver\bin folder to restart the Presentation Server:
      tssh server stop
      tssh server start

      Note

      On Linux, run the commands as the non-root user that initially installed the Presentation Server.

After the upgrade completes, the installation files are stored in the truesightpserver folder. The previous version files are backed up to the truesightpserver_<version> folder (For example, truesightpserver_10.1.0).

To upgrade the Presentation Server in a high availability deployment

  1. On the computer where the existing version of the secondary Presentation Server is installed, open a CLI command prompt.
  2. Navigate to (WindowsTrueSightPServer\truesightpserver\bin or (LinuxTrueSightPServer/truesightpserver/bin directory and run the following command to stop the secondary server:
    tssh server stop secondary
  3. On the computer where the existing version of the primary Presentation Server is installed, perform steps 1–7 751822671.
  4. (Optional) If you had configured the Presentation Server for HTTP access before the upgrade, reconfigure it again:

    1. In a text editor, edit the <Presentation Server installation directory>\truesightpserver\modules\tomcat\conf\web.xml file.
      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>

      -->

    2. Run the following commands from the <InstalledDirectory>\truesightpserver\bin folder to restart the Presentation Server:
      tssh server stop
      tssh server start

      Note

      On Linux, run the commands as the non-root user that initially installed the Presentation Server.

  5. (Optional) If you have installed the Presentation Server in the High Availability mode, you can configure aliases and hosts to access the Presentation server. For more information, see Configuring aliases and hosts for high availability mode.
  6. On the computer where the existing version of the secondary Presentation Server is installed, perform steps 1–7 751822671.

    Before you upgrade the Presentation Server on the secondary node, make sure that the ha-shared.conf file is available at the location mentioned against the TrueSight_high_availability_configuration_file property in the <Secondary Server Installation Directory>/TrueSightPServerInstalledConfiguration.xml file. If the ha-shared.conf file is not available, copy the file from the <Primary Server Installation Directory>/truesightpserver/conf directory and paste it in the directory mentioned against the TrueSight_high_availability_configuration_file property.

  7. (Optional) If you had configured the Presentation Server for HTTP access before the upgrade, reconfigure it again:

    1. In a text editor, edit the <Presentation Server installation directory>\truesightpserver\modules\tomcat\conf\web.xml file.
      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>

      -->

    2. Run the following commands from the <InstalledDirectory>\truesightpserver\bin folder to restart the Presentation Server:
      tssh server stop
      tssh server start

      Note

      On Linux, run the commands as the non-root user that initially installed the Presentation Server.

If the upgrade is not successful and if you want to restore to the earlier version, see Restoring the earlier version of the Presentation Server if the upgrade fails.

Where to go from here

If you have a High Availability environment for your Presentation Server, see Configuring aliases and hosts for high availability mode.

See Verify the Presentation Server upgrade to understand how to verify that the Presentation Server is successfully upgraded.

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

1 Comment

  1.  

© Copyright 2013-2017 BMC Software, Inc.
© Copyright 2013-2017 BladeLogic, Inc.
Legal notices