×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC TrueSight Operations Management 11.3.04 Upgrading

Upgrading the Presentation Server in the high-availability mode silently

Where you are in the Upgrade process

StepTask
1Preparing to upgrade TrueSight Operations Management solution
2Upgrade Remedy Single Sign-On
3Upgrade TrueSight Presentation Server (You are here)
4Upgrade TrueSight Infrastructure Management 
5Upgrade App Visibility Manager 
6Upgrade Real End User Experience Monitoring Software Edition 
7Upgrade 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.

Note

The Load Balancer Health Check URL formats have changed between TrueSight Operations Management versions 10.x and 11.x. For more information, see Guidelines for load balancers.

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.

Preparing the primary server by verifying the XML properties


Perform the following steps on the computer where the existing version of the primary Presentation Server is installed:

  1. Edit the <Primary Server Installation Directory>/TrueSightPServerInstalledConfiguration.xml file.

  2. Locate and change the following property values. If the following properties are not present, add them by obtaining it from the ha.conf file in the <Primary Server Installation Directory>\TrueSightPServer\truesightpserver\conf\ha directory:

    <property>
    <name>TrueSight_high_availability_enabled</name>
    <value>1</value>
    </property>
    <property>
    <name>TrueSight_high_availability_type</name>
    <value>1</value>
    </property>
    <property>
    <name>TrueSight_high_availability_server_pair_name</name>
    <value>truesight</value>
    </property>
    <property>
    <name>TrueSight_high_availability_secondary_server_fqdn</name>
    <value>secondary_server_fqdn</value>
    </property>
    <property>
    <name>TrueSight_high_availability_secondary_database_port</name>
    <value>5432</value>
    </property>
    <property>
    <name>TrueSight_high_availability_secondary_cache_replication_port</name>
    <value>7800</value>
    </property>
    <property>
    <name>TrueSight_high_availability_primary_cache_port</name>
    <value>7800</value>
    </property>
    <property>
    <name>TrueSight_high_availability_primary_control_port</name>
    <value>8800</value>
    </property>
    <property>
    <name>TrueSight_high_availability_secondary_control_port</name>
    <value>8800</value>
    </property>

    In the preceding properties, ensure that the value is set as follows:

    • TrueSight_high_availability_enabled: Indicates that the high availability is enabled. Value must be set to 1.

    • TrueSight_high_availability_type: Indicates the type of server - primary or secondary. Value must be set to 1.

  1. On the primary computer, 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

  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.

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

      -J precedes Java properties

      Property nameDescription
      -J TrueSight_sso_hostnameType the FQDN of Remedy SSO.Example: -J TrueSight_sso_hostname=rsso.bmc.com
      -J TrueSight_sso_portType the Remedy SSO server port number.Default value:(Windows) 448(Linux) 8048Example:-J TrueSight_sso_port=448
      -J TrueSight_sso_passwordType 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_protocolType 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_CERTIFICATEType 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. Open link
      • 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_HOMEIf 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 typeCommand
    Production environment with the existing encryption setting
    • (Windows) setup.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

    • (Windows) setup.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
    • (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

    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.



    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. 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 message: TrueSight Presentation Server 11.3.0x install succeeded.



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

  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:

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

  8. (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 
  9. (Applicable if you customized Tomcat files before the upgrade) Manually re-add the modifications in the web.xml and server.xml files.

  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.

    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.

  11. (Optional) Perform the steps mentioned in the  Troubleshooting a failed deployment Open link 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.

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

Preparing the secondary server by verifying the XML properties

Before you upgrade TrueSight Presentation Server on the secondary computer, perform the following steps:

  1. Ensure that the primary computer is running and in active mode. To know the primary computer status, run the tssh ha status command.

  2. Perform the following steps on the computer where the existing version of the secondary Presentation Server is installed:

    1. Ensure that the ha-shared.conf file is available at the location set in the <Secondary Server Installation Directory>/TrueSightPServerInstalledConfiguration.xml file TrueSight_high_availability_configuration_file property. 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 location set in the <Secondary Server Installation Directory>/TrueSightPServerInstalledConfiguration.xml file TrueSight_high_availability_configuration_file property.

    2. Edit the <Secondary Server Installation Directory>/TrueSightPServerInstalledConfiguration.xml file.

    3. Locate and change the following property values. If the following properties are not present, add them:

      <property>   
      <name>TrueSight_high_availability_enabled</name>   
      <value>1</value>   
      </property>   
      <property>   
      <name>TrueSight_high_availability_type</name>   
      <value>2</value>   
      </property>   
      <property>   
      <name>TrueSight_high_availability_configuration_file</name>   
      <value>ha-shared.conf_FileLocation<value/>   
      </property> 

      In the preceding properties, ensure that the value is set as follows:

      • TrueSight_high_availability_enabled: Indicates that the high availability is enabled. Value must be set to 1. 

      • TrueSight_high_availability_type: Indicates the type of server - primary or secondary. Value must be set to 2.

      • TrueSight_high_availability_configuration_file: Specify the complete location path of the ha-shared.conf file copied from the primary server.

  1. On the secondary computer, 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

  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 typeCommand
    Production environment with the existing encryption setting
    • (Windows) setup.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

    • (Windows) setup.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
    • (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

    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.


    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.

  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 message: TrueSight Presentation Server 11.3.0x install succeeded.



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

    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.

  10. (Optional) Perform the steps mentioned in the  Troubleshooting a failed deployment Open link 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

  • Ensure that you review the information in the Troubleshooting version 11.3.04 upgrade and post-upgrade issues topic after you upgrade.
  • 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. Open link

  • 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 Open link .

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. Open link .

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
Last modified by Harihara Subramanian on Dec 03, 2020
upgrading tsps task high_availability silent

Comments

Log in or register to comment.

Upgrading the Presentation Server in the standalone mode silently
Migrating the configuration of Infrastructure Management cells
© Copyright 2013-2022 BMC Software, Inc. © Copyright 2013-2020 BladeLogic, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2023 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.