Unsupported content This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Prerequisites for Infrastructure Management Server upgrade

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

  • Ensure that you have prepared your setup for upgrade. See Prerequisites for upgrade.

  • In the multi-server environment, you must first upgrade the Child Server and then the Central Server. You must also ensure that the Child Server is disconnected from the Central Server before upgrading the Central Server. 
  • Take a backup of the existing Central Monitoring Administration policies using the cmapolicymigration.bat/cmapolicymigration.sh command line utility. For information about running this command, see cmapolicymigration. Note that this command does not export staging policies or clusters. 
  • You must import or copy the older versions of the repository to the TrueSight Presentation Server installation directory; otherwise, the Central Monitoring Administration policies will not be migrated. For more information, see Migrating the Central Monitoring Administration repository.
  • Ensure that Knowledge Modules are displayed in Central Monitoring Administration. For more information, see Importing-the-Central-Monitoring-Repository-for-Infrastructure-Management.
  • Ensure that the /opt/bmc/ProductRegistry.xml file is present with the installed product details such as the installation directory path and the product version. If the ProductRegistry.xml is not available, contact BMC Support.
  • 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 BMC ProactiveNet 9.5.xx or 9.6.xx, or Infrastructure Management 9.6.xx 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 10.0 implementation. Follow the procedure for executing the KB Migration Wizard described in Migrating-the-configuration-of-Infrastructure-Management-cells. 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.
  • (Solaris and Linux) Ensure that you have root permissions for the computer on which you want to upgrade the Infrastructure Management Server.
  • (Microsoft Windows) BMC recommends that you remove all the files or folders named "Program" or those that begin with "Program" from the drive where BMC ProactiveNet or BMC TrueSight Infrastructure Management is installed. For example, if BMC ProactiveNet is installed under C:\Program Files, but another folder C:\Program exists on the same drive, the upgrade can fail. (This recommendation applies for all upgrades, including hot fixes.)
  • Close all open BMC related application windows.
  • (Microsoft Windows) If you are upgrading to Infrastructure Management 10.0 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.
  • If you are upgrading from BMC ProactiveNet Server version 9.5 Service Pack 1 to the Infrastructure Management Server 10.0, apply the hot fix to BMC ProactiveNet Central Server version 9.5 Service Pack 1 before upgrading to 10.0. For more information, see Knowledge Base article KA425666 (Support logon ID required). 
  • (Linux) If you are upgrading from BMC ProactiveNet 9.5, 9.5 SP1, or 9.5 SP2 to the Infrastructure Management Server 10.0, ensure that the following entries are present in the mcell.dir file in the specified order. If not, edit the file, add these entries, and restart the BMC ProactiveNet Server:

cell pncell_<hostname> mc <hostname>:1828gateway.imcomm gw_ps_pncell_<hostname> mc <hostname>:1839

  • Before upgrading from BMC ProactiveNet or BMC Infrastructure Management version 9.6 that is integrated with BMC Atrium Single Sign-On, perform the following steps:

    1. Delete or comment out the following properties from the pronet.conf file located in the <installationDirectory>\pw\custom\conf folder.

      pronet.sso.integrated=true
      pronet.sso.enable=true
    2. Open the BPPMServerInstalledConfiguration.xml file located in the installation directory, and make the following changes:
      1. Update the CONFIGURE_SSO_INTEGRATIONS property to false.

      2. Remove the complete property tag for the following properties:

        ATRIUM_SSO_HOSTNAME

        ATRIUM_SSO_SEARCHERID

        ATRIUM_SSO_TOMCAT_SECURED_PORT

        ATRIUM_SSO_AMADMIN_PASSWORD

        ATRIUM_SSO_SEARCHERID_PASSWORD

        ATRIUM_SSO_GROUPS_LIST

        ATRIUM_SSO_GROUP_NAME

        IS_SSO_CONFIGURED_PROPERLY

    3. Restart the BMC ProactiveNet or TrueSight Infrastructure Management server.

Where to go next

For upgrading Infrastructure Management Server on Microsoft Windows, see Upgrading-to-Infrastructure-Management-Server-10-0-on-Microsoft-Windows.

For upgrading Infrastructure Management Server on Linux or Solaris, see Upgrading-to-Infrastructure-Management-Server-10-0-on-Solaris-or-Linux.

 

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