Upgrading the Infrastructure Management server on Linux

The following sections explain how to upgrade to the current version of Infrastructure Management Server on Linux. These instructions are also applicable while upgrading from ProactiveNet or TrueSight Infrastructure Management 9.6.00.002. For more information, see Supported-upgrade-paths-for-Infrastructure-Management.

Related topics

Upgrading-the-Infrastructure-Management-server-on-Microsoft-Windows 

Upgrading-the-Integration-Service

Upgrade-issues-for-Infrastructure-Management

Before you begin

Before you start the upgrade, ensure that you have performed all the tasks listed in Prerequisites-for-Infrastructure-Management-Server-upgrade.

To upgrade to TrueSight Infrastructure Management Server on Linux

  1. Archive the old installation files including the user apps, PERL libraries, and any other customizations.

    1. Run the pw system stop command to stop the TrueSight Infrastructure Management Server.
    2. 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.
    3. Save the Crontab entries (especially the database archive entry).
    4. Restart the TrueSight Infrastructure Management Server by using the pw system start command.
    5. Save any custom Apache settings.
  2. Access the installation program by using one of these methods:

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

    chmod -R 777 installationDirectoryFolderName 

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

  4. Run one of the following commands to set the DISPLAY environment to enable the installation program UI to launch:

    • export DISPLAY=targetHostName:0.0
    • setenv DISPLAY targetHostName:0.0

    targetHostName is the name of the computer on which you want to display the installation program UI.

  5. Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.
  6. On the Welcome page, click Next.
  7. On the license agreement page, select I agree to the terms of the license agreement, and click Next.
  8. On the Upgrade Confirmation page, click Yes, and click Next. The upgrade routine checks the system to see that it meets the upgrade prerequisites. It mentions that you must install TrueSight Presentation Server before installing TrueSight Infrastructure Management. It displays any errors that it discovers. You can correct them and then return to the upgrade sequence.
  9. (When upgrading from ProactiveNet or Infrastructure Management 9.6.00.002) On the TrueSight Presentation Server Integration and Registration page, if you want to migrate Infrastructure Management data during the upgrade, select Yes. Furthermore, provide details of the Presentation Server and Remedy Single Sign-On server described in the table that follows.Optionally, select No to migrate data post upgrade by using the migration utility. For more information about this process, see Migrating data from ProactiveNet or Infrastructure Management.
    Best practiceIf you plan to migrate a large volume of data, it is recommended that you perform the migration post upgrade by using the migration utility. Doing so can help reduce the downtime required for completing the migration.
    NoteWhen migrating data to Presentation Server, the following Infrastructure Management policies are migrated:
    • Policies associated with the specified tenant name
    • Policies associated with GLOBAL tenant
    • Policies with no tenant specified
    Policies with unspecified tenants are not migrated and are exported to the exported_policies_failed_to_import folder located at <installdirectory>/pw/pronto/lib/DataMigrator/exported_policies.You can manually import the failed policies by running the migration utility with the export_policies option. For more information, see Migrating data from ProactiveNet or Infrastructure Management.
    Field
    Description
    Presentation Server FQDN
    The host name or Fully Qualified Domain Name (FQDN) for the Presentation server.
    Presentation Server Port
    The HTTPS connector port for the Tomcat Apache server. The default ports are 443 (Windows) and 8043 (Linux).
    Presentation Server User
    User name (with super admin permissions) for accessing the Presentation Server.
    Presentation Server Password
    Password corresponding to the user name used for accessing the Presentation Server.
    Remedy SSO Server FQDN
    The host name or Fully Qualified Domain Name (FQDN) for Remedy Single Sign-On.
    Remedy SSO Port
    The port number corresponding to the Remedy Single Sign-On host name.
    Remedy SSO Admin Password
    The admin password for accessing Remedy Single Sign-On.
    Remedy SSO Tenant
    Tenant associated with the admin user that is used for accessing Remedy Single Sign-On. The admin user is the same user that is used for accessing Presentation Server.Note: When migrating data to the Presentation Server, ensure that the central server and child server are migrated to the same tenant. Otherwise, the related configurations will not be applied to these servers.
    Remedy SSO Protocol
    Protocol to be used while connecting with Remedy Single Sign-On.By default, the HTTPS protocol is used for connecting with Remedy Single Sign-On.
  10. On the Listening Address Configuration page, confirm the Fully Qualified Domain Name (FQDN).
    NoteEnsure that the TrueSight Infrastructure Management server FQDN is reachable from other BMC products.
  11. In the Cloud-vista enabled environment, the Configuring Infrastructure Management environment deployment information screen is displayed. Provide the following details, and click Next.Select any one of the following options based on your Infrastructure Management environment.
    • Single Server Environment Installation: Upgrades the Infrastructure Management Server as a standalone server.
    • Multiple Server Environment Installation: Upgrades the 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).

  12. On the Configuring KB Migration Path page, if you have already migrated customized KB definitions to the new standard 11.0 KB, select Yes, and browse to the path of the customized KB directory.

    Important

    You must apply a re-propagate rule, which is used for propagating all open events from the Infrastructure Management Server to the Presentation Server. If you select Yes, you must apply this rule before proceeding with the upgrade. If you select NO, apply this rule after the upgrade is complete. It is recommended to apply this rule for all child server upgrades and a single server upgrade.

    The file path should follow this hierarchy structure:
    <topLevelDirectory>/mergedKB/server/etc/cellName, where /server/etc/cellName is the standard subdirectory

    Warning

    If you have KBs to migrate but have not done so, pause the upgrade process and migrate them before proceeding. See Migrating the configuration of cells.

    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.

  13. Click Next.
  14. On the Installation Preview page, click Install.
  15. On the Installation Summary window, select View Logs to open the installation logs, or click Done.After you successfully upgrade the Infrastructure Management server, the following folders are created under the installation directory, in the BMC Software folder.You can manually delete the files if you do not want them.

On the Configuring KB Migration Path page, do one of the followingif you have already migrated customized KB definitions to the new standard 11.0 KB, select Yes, and browse to the path of the customized KB directory.

Important

You must apply a re-propagate rule, which is used for propagating all open events from the Infrastructure Management Server to the Presentation Server. If you select Yes, you must apply this rule before proceeding with the upgrade. If you select NO, apply this rule after the upgrade is complete. It is recommended to apply this rule for all child server upgrades and a single server upgrade.

The file path should follow this hierarchy structure:
<topLevelDirectory>/mergedKB/server/etc/cellName, where /server/etc/cellName is the standard subdirectory

Post-upgrade tasks when upgrading from ProactiveNet or TrueSight Infrastructure Management 9.6.00.002

The following table lists the post-upgrade tasks:

Upgrade notes

  • During the upgrade, the pronet.db log returns warning messages due to repetitive registration of monitors. You can ignore these warnings because they do not cause any problem to the upgrade.

  • Review the installation logs for the mposter command warnings. If you find such warnings, see Troubleshooting.

  • If there were modifications in the Tomcat Server web.xml or server.xml file before the upgrade, you must manually add the modifications to the Tomcat server web.xml or server.xml file after the upgrade.

Where to go from here

Upgrade the Integration Service and remote cells

 

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