Preparing to upgrade Integration Service and Remote cell

This section lists the tasks that you must perform before you begin to upgrade the Integration Service and remote cell:

• Ensure to close all the files and folders opened in the current session as well as close other user sessions on the server before starting an upgrade.

• Ensure that you take a backup of the earlier installation directory of the Integration Service and remote cell. If they are installed on virtual machines, take snapshots of the virtual machines.
• Ensure that you take a backup of the ProductRegistry.xml file. While performing the upgrade as a non-root user, ensure that the non-root user has read, write, and execute permissions for the ProductRegistry.xml file.
• Ensure that you take a backup of the Integration Service keystore files, and keystore password files located in the installationDirectory\pw\pronto\conf directory.
• If you deleted the default cell that is created through the installer and a custom cell is set as the default cell, edit the following parameters in the installedDirectory\TSIMAgent\BPPMAgentInstalledConfiguration.xml file:
  <name>CELL_NAME</name>
<value>custom_cell_name</value>
• In you have configured cell HA, update the host name as represented in the mcell.dir of respective HA cells.
   <name>CELL_PRIMARY_HOST</name>
 <value>primary_host_name</value> 

  <name>CELL_SECONDARY_HOST</name>
<value>secondary_host_name</value>

• You can directly upgrade the TrueSight Infrastructure Management Integration Service from version 9.6.00.002, 10.5.xx or 10.7.xx to TrueSight Infrastructure Management  Integration Service version 11.3.01 See  Supported upgrade paths for Infrastructure Management  to determine the upgrade path for your version of Integration Service. BMC recommends that you upgrade the existing Integration Service for optimum efficiency and reliability of Integration Service operations and to fully utilize the Infrastructure Management features.

• Before upgrading TrueSight Infrastructure Management  Integration Service, if your KB has customizations, you must install a Integration Service on a separate computer. 

• You can upgrade multiple Integration Services, one at a time. However, you cannot launch multiple Integration Service upgrades simultaneously. If you launch multiple Integration Service upgrades sequentially, keep only the initial installation window open, and close the remaining windows. The routine does not ask for the Integration Service port number. Consider the following guidelines:

  • Having multiple Integration Services on a single computer puts an additional load on the computer in terms of CPU, IO, Memory, and TCP buffer.
  • When you upgrade multiple Integration Services on a single computer, you also upgrade the cell that was installed with the first Integration Service.
  • The computer requires time to upgrade information. BMC recommends that you wait a minimum of five seconds between Integration Service upgrades.
  • In a multiple Integration Service scenario, only one cell is installed or upgraded per host system.

  Note

  If you are upgrading the cell on AIX and using DB2 Database monitors, after the upgrade script is finished, copy the libdb2.a library from the DB2 Administration Client installation directory (installationDirectory/sqllib/lib) to the /usr/lib directory, and restart the Integration Service.

Remote cell knowledge base migration

If a cell that resides on the computer has a customized knowledge base and configuration, you must run the  mmigrate utility to successfully migrate these. For information about the cell migration, see  Cell configuration migration (cells).

When you upgrade an Integration Service, you also upgrade the following components:

• Self-monitoring Service
• Event Manager
• BMC Event Adapters
• cell

After you upgrade an existing Integration Service, it starts the BMC Event Adapter. For supported Perl versions for the BMC Event Adapters, see  System requirements and product compatibility for Infrastructure Management.

Manually stopping Perl and msend processes

Stopping the Perl based-adapters service does not stop the Perl process. Because the Perl service is still running, one of its msend processes continues to run. Killing the Perl process does not kill the msend process. This prevents the upgrade utility and the uninstallation utility from cleaning up and causes multiple Perl processes to be running if the service is restarted. 

To prevent this issue from occurring, perform the following steps before upgrading or uninstalling BMC Event Adapters:

• Manually stop the BMC Event Adapters service.
• Ensure that all Perl and msend processes are stopped. If necessary, stop the msend and Perl processes by using the Windows Task Manager.

Upgrading cell when the standalone or High Availability mode is manually changed 

If you have manually changed the standalone or High Availability (HA) mode for the cell after installation, note the following points before proceeding with the upgrade:

• If the cell was initially installed in the standalone or secondary mode and then manually converted to the primary cell in the HA mode, open the Command Prompt and perform one of the following steps:
  • For Windows, navigate to the  <installLocation>\Windows\TSIMAgent\Disk1 directory, and run the following command:
    setup.exe -J HA_MODE_SELECTED=true -J CELL_MODE=primary
  • For Linux, navigate to the  <installLocation>\Linux\TSIMAgent\Disk1 directory, and run the following command:
    setup.bin -J HA_MODE_SELECTED=true -J CELL_MODE=primary

• If the cell was initially installed in the standalone or primary mode and then manually converted to the secondary cell in the HA mode, open the Command Prompt and perform one of the following steps:

  • For Windows, navigate to the <installLocation>\Windows\TSIMAgent\Disk1 directory, and run the following command:
    setup.exe -J HA_MODE_SELECTED=true -J CELL_MODE=secondary

  • For Linux, navigate to the <installLocation>\Linux\TSIMAgent\Disk1 directory, and run the following command:
    setup.bin -J HA_MODE_SELECTED=true -J CELL_MODE=secondary

• If a cell  was initially installed in the HA mode and then manually converted to the standalone mode, open the Command Prompt and perform one of the following steps:

  • For Windows, navigate to the <installLocation>\Windows\TSIMAgent\Disk1 directory, and run the following command:
    setup.exe -J HA_MODE_SELECTED=false -J CELL_MODE=standalone

  • For Linux, navigate to the <installLocation>\Linux\TSIMAgent\Disk1 directory, and run the following command:
    setup.bin -J HA_MODE_SELECTED=false -J CELL_MODE=standalone

Update the S81pronto script on SUSE Linux Enterprise Server

Perform the following steps before upgrading the Integration Service on SUSE Linux Enterprise Server:

Root user

1. Manually create the S81pronto.0.<instance number> script in all the etc/rc.d/rc<runLevel>.d
2. If multiple instances of Integration Services are installed, create that number of S81pronto.0 with respective instance number. For example:
   1. S81pronto.0.1
   2. S81pronto.0.2
   3. S81pronto.0.3

3. Update the installation directory in the S81pronto file, as per the installed Integration Service.

   # # Start BMC ProactiveNet Agent processes # if [ -x <INSTALLATION-DIRECTORY>/pw/pronto/bin/startremotepw ] ; then   /opt/bmc/TSIMAgent/pw/pronto/bin/startremotepw &   /bin/echo  'BMC ProactiveNet Agent\c' fi

4. Provide the required execute permissions to all S81pronto.* files.

Non-root user

1. If you installed the Integration Service as a non-root user, the S81pronto.0.<instance number> script is created in <installationDirectory>/pw/pronto/bin folder.
2. Manually copy the s81pronto.xxxx file from <installationDirectory>/pw/pronto/bin to all the etc/rc.d/rc<runLevel>.d.

Next step in the Upgrade process

If you are upgrading the product, perform the other pre-upgrade tasks listed in the Preparing to upgrade TrueSight Operations Management solution.