Upgrading the Infrastructure Management Server in the standalone mode silently

Where you are in the Upgrade process

Infrastructure Management Server can be upgraded silently with the existing settings such as database (Oracle or SAP SQL Anywhere), cell details, and firewall configurations. 

To upgrade the Infrastructure Management server

Do the following:

1. Log in to the host computer on which you want to upgrade the Infrastructure Management server, and delete all the files from the temporary directory:

   • (Windows) %temp%

   • (Linux) /tmp and /var/tmp

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

   • (Windows) C:\Program Files

   • (Linux) /opt

   Note

   Ensure that the following system requirements are met. If your target computer does not meet these requirements, you cannot proceed with the installation. 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

   By default, the TrueSight Infrastructure Management Server uses 256-bit encryption. However, AES 256-bit encryption is not allowed in some countries due to import regulations. You can change the default encryption key size when you invoke the installer.

   
   

3. (Linux) Apply executable rights to all the installation files by running the following command: 

   chmod -R 755 installationDirectoryFolderName 

   installationDirectoryFolderName is the name of the folder that contains all the installation files.

   For example, chmod -R 755 Disk1

4. (Linux) If you are upgrading as a non-root user, ensure that you start a new session to run the upgrade. Do not use the su command to start a non-root session.
   
5. (Windows) Do the following:
   1. (Windows) Stop and disable all the scheduled tasks on the Infrastructure Management server.
   2. (Windows) Stop the pwtray process.
   3. (Windows) Ensure that you close all the files and folders opened in the current session as well as in the other user sessions on the Infrastructure Management server.
   4. (Windows) Ensure that the pw folder is not locked by any process.

6. Go to the extracted folder, and locate the silent options file, and edit this 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:

   • (Windows) <DownloadLocation>\Windows\Disk1\server_upgrade.options

   • (Linux) <DownloadLocation>/Linux/Disk1/server_upgrade.options

    Property details

   -J precedes Java properties

   Property name	Description
   -J MIGRATED_KB	true/false
   -J MIGRATED_KB_HOME	KB migration path
   # Set the following values only if you are upgrading from release 9.6.x and want to migrate the policies during the upgrade. # Cloud Vista should not be integrated for Policy Migration
   -J INTEGRATE_WITH_TSPS	Type true if you want to migrate the policies during the upgrade. Default value: false Example: -J INTEGRATE_WITH_TSPS=true
   -J TSPS_HOST_NAME	Type the FQDN of the Presentation Server host computer. Example: -J TSPS_HOST_NAME=tsps_host.fqdn.com
   -J TSPS_PORT	Type the configured Apache tomcat port number. Default value - https port: (Windows) 443 (Linux) 8043 Default value - http port: (Windows) 80 (Linux) 8080 Example: -J TSPS_PORT=443 Note: You can run the tssh properties list command to check the configured port and the protocol details. You can update the TSPS_PORT property based on the command output.
   -J TSPS_PROTOCOL	Type the protocol (HTTP/HTTPS) in which the Presentation Server is configured. Example: -J TSPS_PROTOCOL=HTTPS Note: You can run the tssh properties list command to check the configured port and the protocol details. You can update the TSPS_PROTOCOL property based on the command output.
   -J TSPS_USERNAME	Type the Presentation Server administrator user name. Example: -J TSPS_USERNAME=Admin
   -J TSPS_PASSWORD	Type the relevant password.
   The following section is 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.
   -J SSO_HOSTNAME	Type the FQDN of the Remedy Single Sign-On Server host computer. Example: -J SSO_HOSTNAME=rsso_host.fqdn.com
   -J SSO_TOMCAT_SECURED_PORT	Type the Remedy SSO server port number. Example: -J SSO_TOMCAT_SECURED_PORT=8443
   -J SSO_ADMIN_PASSWORD	Type the Remedy Single Sign-On password in an encrypted form. Example: -J SSO_ADMIN_PASSWORD=DES\:097133405e7ea7a641f019bca8781280e74e86a9fec4ad58 Note: You can encrypt the password using the TrueSightPServerMaintenanceTool through the wizard or command line interface. For details, see Installing Remedy SSO in the standalone mode using the TrueSight installer silently .
   -J SSO_TENANT	Type the default tenant name. Example: -J SSO_TENANT=*
   -J SSO_PROTOCOL	Type the protocol in which Remedy SSO is configured. By default, Remedy SSO is configured in the HTTPS mode. Example: -J SSO_PROTOCOL=HTTPS
   # Set the following value if you are upgrading from TrueSight Infrastructure Management Server older than version 10.0
   -J TRUESIGHT_HOSTNAME_FQDN	Type the FQDN of the TrueSight Infrastructure Management Server host computer. Example: -J TRUESIGHT_HOSTNAME_FQDN=TSIMhost.bmc.com

7. From the command prompt, run one of the following commands to start the upgrade. Type the complete path to the server_upgrade.options file in the command. If the path includes a blank space, enclose the path within double quotes. Upgrade-related information is not displayed when the silent upgrade begins. However, upgrade occurs in the background.

   Environment type	Command
   Production environment with the default encryption setting	(Windows) install.cmd -i silent -DOPTIONS_FILE="<DownloadLocation>\server_upgrade.options" (Linux)./install.sh -i silent -DOPTIONS_FILE="<DownloadLocation>/server_upgrade.options" Example (Windows - With space) install.cmd -i silent -DOPTIONS_FILE="C:\temp folder\Disk1\server_upgrade.options" (Linux- With space)./install.sh -i silent -DOPTIONS_FILE="/home/tsim user/Linux/Disk1/server_upgrade.options"
   Production environment with user-specified encryption setting	(Windows) install.cmd –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="<DownloadLocation>\server_upgrade.options" (Linux)./install.sh -i silent -DOPTIONS_FILE="<DownloadLocation>/server_upgrade.options" Example (Windows - With space) install.cmd –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="C:\temp folder\Disk1\server_upgrade.options" (Linux- With space)./install.sh –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="/home/tsim user/Linux/Disk1/server_upgrade.options"
   Test environment with the default encryption setting	(Windows) install.cmd -J MINIMAL=true -i silent -DOPTIONS_FILE="<DownloadLocation>\server_upgrade.options" (Linux)./install.sh -J MINIMAL=true -i silent -DOPTIONS_FILE="<DownloadLocation>/server_upgrade.options" Example (Windows) install.cmd -J MINIMAL=true -i silent -DOPTIONS_FILE="C:\temp folder\Disk1\server_upgrade.options" (Linux)./install.sh -J MINIMAL=true -i silent -DOPTIONS_FILE="/home/tsim user/Linux/Disk1/server_upgrade.options"
   Test environment with user-specified encryption setting	(Windows) install.cmd -J MINIMAL=true –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="<DownloadLocation>\server_upgrade.options" (Linux)./install.sh -J MINIMAL=true –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="<DownloadLocation>/server_upgrade.options" Example (Windows) install.cmd -J MINIMAL=true –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="C:\temp folder\Disk1\server_upgrade.options" (Linux)./install.sh -J MINIMAL=true –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="/home/tsim user/Linux/Disk1/server_upgrade.options"

   Note

   Based on whether you are using SAP SQL Anywhere or Oracle, the TrueSight Infrastructure Managementupgrade may take between 20 to 60 minutes to complete.

8. Installation-related information is not displayed on the console when the silent installation begins. However, installation occurs in the background. The progress of the installation is logged in a temporary folder during the installation. To see the installation progress details and for the database-related progress details:
   • (Windows) Go to Start > Run, enter %temp% in the Open box, and see the tsim_server_install_log.txt file
     
   • (Linux) Open /tmp or /var/tmp , and see the tsim_server_install_log.txt file
9. If there were customizations in the Tomcat Server file (web.xml or server.xml) before the upgrade, you must manually add these customizations to the same web.xml or server.xml file after the upgrade.

10. After the TrueSight Infrastructure Management server is upgraded successfully, the following folder is created under the installation directory, in the BMC Software folder. You can manually delete the files if you do not want them.

    Folder name	Description
    <installationDirectory>11.x  (where  x  is the version that you are upgrading from)	Contains backup files of the earlier TrueSight Infrastructure Management installation.

11. If you have imported custom certificates for TrueSight Infrastructure Management server, ensure that you edit the custom certificate and key entries in the httpd-ssl.conf file after you upgrade the TrueSight Infrastructure Management server. For detailed instructions, see  Implementing private certificates in the TrueSight Infrastructure Management.

12. If you have customized service management data in the di_models.baroc file present in the <Infrastructure Management Server Install Directory>\pw\server\etc directory, copy the publishing server kb from the backup directory to the <Infrastructure Management Server Install Directory>\pw\server\etc\<psname> directory.

13. Run the following command to verify that the Infrastructure Management Server is upgraded successfully:

    (Windows) # pw system status
    (Linux)# pw system status

    A list of pw server processes is displayed.
    
    

     (Windows) Sample list

    ------------------------
Servers/Daemon Processes
------------------------
services 4820
httpd 6152
jserver 10660
pronet_agent 4680
pronet_cntl 3968
tunnelproxy 7792
rate 3976
dbsrv 6560
mcell 4952
pserver 4217

     (Linux) Sample list

    ------------------------
Servers/Daemon Processes
------------------------
pronet_agent 21256
services 21046
httpd 10069 21446 24238 28619 30746
jserver 21940
mcell 20930
pronet_cntl 21381
tunnelproxy 21660
rate 21540
oracle Running on <host name>:<port number>

    If errors occur, restart the BMC TrueSight Infrastructure Management Server by running the following command:

    (Windows)# pw system start
    (Linux) # pw system start

    
    

    BMCTrueSight.service (Applicable only to version 11.3.04 and later on Linux)

    You can use the systemd service BMCTrueSight.service located in the /etc/systemd/system directory to start and stop the Infrastructure Management server on Linux. For more information, see Starting and stopping the TrueSight Operations Management components.

Post-upgrade task

• Ensure that you review the information in the Troubleshooting version 11.3.04 upgrade and post-upgrade issues topic after you upgrade.
  
  
• If you have customized the password for the bppmws_internal user account before the TrueSight Infrastructure Management Server upgrade, use one of the following options to sync the password after the upgrade. In a HA environment, ensure that you run these steps on both the HA nodes.
  • Option 1:Update the properties file manually
  1. On the Infrastructure Management server, go to the following backup file location:
     <InstallationDirectory><OLD_VERSION>/pw/pronto/conf/bppmws_internal.properties
     <OLD_VERSION> is the version that you are upgrading from.
     
  2. Copy the value for the property bppmws_internal_key from the preceding properties backup file and replace the value in the following file:
     <InstallationDirectory>/pw/pronto/conf/bppmws_internal.properties
  3. Restart theTrueSight Infrastructure Management server.
  • Option 2:Update the properties file using CLI command
  1. Open a command prompt on the Infrastructure Management server and run the following command:
     pw internaluser change_passwd

  2. Enter the new password.
     The new password is validated with Remedy SSO and then updated.
  3. Restart the Infrastructure Management server.
     
     
• Due to security reasons, the following property is set to false during the upgrade.

http.enabled:false

If you want to monitor the Elasticsearch, set the above property to true in the elasticsearch.yml file at the following directory path after the upgrade as applicable:

• (On Linux)<TRUESIGHTPSERVER_HOME>/truesightpserver/modules/elasticsearch/config/
• (On Windows) <TRUESIGHTPSERVER_HOME>\truesightpserver\modules\elasticsearch\config\

Troubleshooting upgrade issues

If you face issues during the upgrade, see  Troubleshooting an Infrastructure Management deployment.

Next step in the Upgrade process

Step 4 Phase B — Now that you have successfully upgraded the Infrastructure Management Server, you must upgrade the Integration Service and remote cells.