Prerequisites for Infrastructure Management Server upgrade

This section lists the tasks that you must perform before you begin to upgrade the TrueSight Infrastructure Management Server:

General prerequisites

  • Access the installation program by using one of these methods:
  • Ensure that you have prepared your setup for upgrade. See Prerequisites for upgrade.
  • In the distributed service model environment, ensure that you add the isDSIMEnabled=true entry in the /pw/custom/conf/pronet.conf file and restart the TrueSight Infrastructure Management server using the following pw command: #pw system start on both central and child servers.

  • In the cloud-enabled environment, ensure that the isCloudDeployment=true entry is present in the /pw/custom/conf/pronet.conf file.
  • Ensure that you have merged any customized KBs in your Infrastructure Management 10.5 or 10.5.xx implementation and ProactiveNet (or Infrastructure Management) 9.6.00.002 implementation. Note the file path where the merged KB directory resides. See Cell configuration migration (cells).
  • Ensure that you have migrated the customized KBs in your Infrastructure Management 11.0 implementation. Follow the procedure for using the mmigrate utility as described in Using the mmigrate utility.

    Note

    You must migrate and merge your KB only if the KB and the mcell.conf file located at MCELL_HOME\etc\cellName\ contain any customizations.


    When satisfied that the merged KB is working properly, you can begin the server upgrade procedure. Note the directory path of each migrated KB. The directory path should follow this hierarchy structure: /topLevelDirectory/mergedKB/serve/etc/cellName, where /server/etc/cellName is the standard subdirectory.
  • Close all open BMC related application windows.
  • (Microsoft Windows) If you are upgrading to Infrastructure Management on German and French operating systems and using the Oracle database, then before the upgrade, you must manually grant Administrator access to the dbuser file located in the pw\pronto\conf directory.
  • (Microsoft WindowsIf you are upgrading the Infrastructure Management Server on an IPv6 Windows host, ensure that the IP helper service is started.

  • Ensure that you have upgraded the TrueSight Presentation Server to the latest version.

  • Stop access to the TrueSight Infrastructure Management database from other BMC products such as TrueSight Operations Management Reporting, or TrueSight Capacity Optimization. You can restore access to the database once the upgrade process is complete.

  • Disconnect all the Integration Services that are connected to the Infrastructure Management server from the Configuration > Managed Devices page in the TrueSight console.
  • Ensure that you can ping the local host. For example, if you are using the IPv6 protocol on Linux, use the ping6 command to make sure that the local host is available.

  • Run the Preinstall check utility.

  • If you have custom cells created in your environment, ensure that you stop them before the upgrade and then restart them after the upgrade.

  • If you have imported the custom CA certificate for the associated Remedy Single Sign-On server, you need to run the following command on the ProactiveNet (or Infrastructure Management) server to import the custom certificate: 

    keytool -importcert -alias "<alias name>" -file "<.cert file path>" -keystore "<cacerts path>" -noprompt -storepass changeit

    Example:

    keytool -importcert -alias ssoserver -file C:\HostA.bmc.com -keystore ..\lib\security\cacerts -storepass changeit

  • If you have customized service management data in the di_models.baroc file present in the <Infrastructure Management Server Install Directory>\pw\server\etc\<psname> directory, do the following before upgrading the Infrastructure Management Server to ensure that the customized service management data is retained after the upgrade:

    Do the following before upgrading the Infrastructure Management Server to ensure that the customized service management data is retained:

    Standalone deployment of Infrastructure Management Server

    Do the following:

    1. Take a backup of the <Infrastructure Management Server Install Directory>\pw\server\etc\<psname> directory in a location that is outside the Infrastructure Management Server installation directory.

    2. Ensure that you run the mmigrate utility to merge the cell KB before upgrading the Infrastructure Management Server. This action ensures that the mc_sm_object.baroc file and its customizations are retained after the upgrade.
      Note: Skip this step, if you have already run the mmigrate utility to merge the cell KB.
    3. Upgrade the Infrastructure Management Server.
    4. Copy the publishing server kb from the backup directory to the <Infrastructure Management Server Install Directory>\pw\server\etc\<psname> folder

    High-availability deployment of Infrastructure Management Server

    Perform the steps that are listed for the standalone Infrastructure Management Server first on primary followed by secondary Infrastructure Management Server.


Prerequisites to upgrade Infrastructure Management as a non-root user

To upgrade Infrastructure Management as a non-root user on a Linux server, you need to provide a set of permissions. You can set these permissions by running the config_nonroot.sh script as a root user. For more information, about running the script, see Preparing Linux computers for Infrastructure Management.

If you had previously installed Infrastructure Management (or ProactiveNet) as a root user and you want to upgrade Infrastructure Management (or ProactiveNet) as non-root user, you need to run a script described at https://bmcsites.force.com/casemgmt/sc_KnowledgeArticle?sfdcid=000028108. Additionally, you need to perform the following steps:

  1. Go to the computer where you want to upgrade Infrastructure Management (or ProactiveNet).

  2. Copy the /etc/bmc.profile and the /etc/bmc.cshrc files to the non-root user's home directory, as follows:

    mv /etc/bmc.profile /home/<Non-Root-User-Name>/.bmc_profile

    mv /etc/bmc.cshrc /home/<Non-Root-User-Name>/.bmc_cshrc

    Example

    mv /etc/bmc.profile /home/jack/.bmc_profile

    mv /etc/bmc.cshrc /home/jack/.bmc_cshrc

  3. Remove the following entry from the /etc/profile file and then save the file.

    . /etc/bmc.profile

  4. Remove the following entry from the /etc/csh.cshrc file and then save the file.

    . /etc/bmc.cshrc

  5. In the <Non-Root-User-Home-Dir>/.bash_profile file, add the following entry, and save the file.

    . <Non-Root-User-Home-Dir>/.bmc_profile

    Example

    . /home/jack/.bmc_profile

  6. In the <Non-Root-User-Home-Dir>/.bashrc file, add the following entry, and save the file.

    . <Non-Root-User-Home-Dir>/.bmc_cshrc

    Example

    . /home/jack/.bmc_cshrc

  7. Log out and then log on to the computer as a non-root user so that the changes made in the preceding steps are applied.
  8. Verify if the LD_LIBRARY_PATH environment variable contains the value, /usr/pw/apache/lib
    If this value does not exist, append the LD_LIBRARY_PATH variable value in the following files:
    • <Non-Root-User-Home-Dir>\.bmc_profile
    • <Non-Root-User-Home-Dir>\.bmc_cshrc

Where to go from here

For upgrading Infrastructure Management Server on Microsoft Windows, see Upgrading the Infrastructure Management server on Microsoft Windows.

For upgrading Infrastructure Management Server on Linux, see Upgrading the Infrastructure Management server on Linux.

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

Comments