Upgrading the Infrastructure Management server in the standalone mode using the wizard
Where you are in the Upgrade process
|1||Preparing to upgrade TrueSight Operations Management solution|
|2||Upgrade Remedy Single Sign-On|
|3||Upgrade TrueSight Presentation Server|
|4||Upgrade TrueSight Infrastructure Management — Phase A (You are here)|
|Upgrade TrueSight Infrastructure Management — Phase B|
|5||Upgrade App Visibility Manager|
|6||Upgrade Real End User Experience Monitoring Software Edition|
|7||Upgrade TrueSight IT Data Analytics|
To upgrade the TrueSight Infrastructure Management server
Do the following:
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
Extract the downloaded zip files (the upgrade installer) to a temporary location outside the following location to avoid any file sharing conflicts:
- (Windows) C:\Program Files
- (Linux) /opt
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
- 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.
(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.
chmod -R 755 Disk1
- (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
sucommand to start a non-root session.
- (Linux) Perform the following to archive the old installation files including the user apps, PERL libraries, and any other customization:
- Run the
pw system stopcommand to stop the TrueSight Infrastructure Management server.
- Tar the /usr/pw directory and place the resulting file in a secure location such as on another server, another file partition, or a directory that lies above /usr/pw.
Save the Crontab entries (especially the database archive entry).
- Restart the TrueSight Infrastructure Management Server by using the
pw system startcommand.
- Save any custom Apache settings.
- Run the
(Linux) Run one of the following commands to set the DISPLAY environment to enable the installation program UI to launch:
setenv DISPLAY targetHostName:0.0
targetHostName is the name of the computer on which you want to display the installation program UI.
Navigate to the Disk1 directory of the extracted folder, use one of the following options to run the installer.
BMC recommends that you run the installer by using
You must right-click on install.cmd and select Run as administrator.
Environment type Command
Production environment with the default encryption setting
Production environment with user-specified encryption setting
install.cmd –J BMC_TS_KEY_SZ=<128/256>
./install.sh –J BMC_TS_KEY_SZ=<128/256>
Test environment with the default encryption setting
install.cmd -J MINIMAL=true
./install.sh -J MINIMAL=true
Test environment with with user-specified encryption setting
install.cmd –J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true
./install.sh –J BMC_TS_KEY_SZ=<128/256> -J MINIMAL=true
- Review the welcome page, and click Next.
- Read the license agreement, agree to the terms, and click Next.
- On the Upgrade Confirmation page, click Yes, and click Next. The upgrade routine checks the system to see that it meets the upgrade prerequisites, and displays any errors that it discovers. Correct these errors before proceeding with the upgrade.
(Applicable only if you are upgrading from TrueSight Infrastructure Management 10.7) The installer detects the FQDN of the host computer and populates the FQDN field automatically. Confirm this, and click Next.
If you modify the FQDN:
Do not manually type any IP address in the FQDN field.
Do not leave this field empty.
Ensure that the TrueSight Infrastructure Management server FQDN is accessible from other BMC products.
In the Cloud-vista enabled environment, the Configuring TrueSight Infrastructure Management environment deployment information screen is displayed. Provide the following details, and click Next.
TrueSight Infrastructure Management environment.Select any one of the following options based on your
Single Server Environment Installation: Upgrades the TrueSight Infrastructure Management server as a standalone server.
Multiple Server Environment Installation: Upgrades the TrueSight Infrastructure Management server as following:
BMC TrueSight Infrastructure Management Central Server: Upgrades this instance as a central server.
BMC TrueSight Infrastructure Management Child Server: Enter the following Server Router details:
Field Description Host Name/IP Address FQDN name and IP address of the Central Server Router. FQDN name comprises the host name and the domain name. Protocol Protocol with which to communicate to the Central Server Router. It can be either HTTP or HTTPS protocol. Port Port number with which to communicate to the Central Server Router. The default HTTP ports are 80 (Windows) and 8080 (Linux). The default HTTPS ports are 443 (Windows) and 8043 (Linux).
On the Configuring KB Migration Path page, if you have already migrated customized KB definitions to the new standard 11.3.01 KB, select Yes, and browse to the path of the customized KB directory.
The file path should follow this hierarchy structure:
\topLevelDirectory\mergedKB\server\etc\cellName , where \server\etc\cellName is the standard sub-directory.
If you have KBs to migrate but have not done so, pause the upgrade process and migrate them before proceeding. See
During the upgrade, the routine copies the KB under the \mergedKB\server\etc\cellName path and overwrites the KB in the default installationDirectory \pw\server\etc\cellName path.
- Review the installation details, click Install, and click Next.
Select View Logs to open the installation logs, and click Done.
After you successfully upgrade the TrueSight Infrastructure Management server, 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.
Run the following command to verify that the Infrastructure Management Server is upgraded successfully:
# pw system status
# pw system status
A list of pw server processes is displayed.(Windows) Sample list
pserver 4217(Linux) Sample list
httpd 10069 21446 24238 28619 30746
oracle Running on <host name>:<port number>
If errors occur, restart the BMC TrueSight Infrastructure Management Server by running the following command:
# pw system start
# pw system start
- 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, once you upgrade the TrueSight Infrastructure Management server. For detailed instructions, see .
- 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.
The system requirements are validated every 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
Troubleshooting upgrade issues
If you face issues during the upgrade, see .