Upgrading the Integration Service and Remote Cell using the wizard

Where you are in the upgrade process

Recommendations for upgrading Integration Service and Remote Cell

• If the Integration Service cell KB has any customizations, ensure that your existing customized KB is merged with the new 11.3.01 version. 
• Ensure that the computer on which you are upgrading the Integration Service adheres to the hardware, operating system, platform, and software requirements listed in  System requirements and product compatibility for Infrastructure Management.
• If you have installed only the Integration Service and not the cell but the cell directory (\Agent\server directory) exists in the computer, the upgrade installer upgrades the Integration Service as well as installs the cell. If you do not want to install the cell, rename the cell directory and proceed with the Integration Service upgrade. Post upgrade, you can rename the cell directory to the original name.
• With TrueSight Infrastructure Management 10.5 release, the upgrade of the Integration Service is not supported on the Solaris or AIX operating systems.
• On the Solaris operating system:
  • If you have only Remote cell installed, you can upgrade it.
  • If you have both Integration Service and Remote cell installed, you cannot upgrade any of these components.
• On the AIX 7.1 operating system, you cannot upgrade Integration Service or Remote cell.
• You can read the S81pronto file under /etc/rc3.d/ to find the location of the installation directory for an already installed Integration Service on the Linux computer.
  
• If you have manually changed the standalone or High Availability (HA) mode for the cell after installation, see  Preparing to upgrade Integration Service and Remote cell.
• Ensure that you have root permissions for the computer on which you want to upgrade the Integration Service.
• Ensure that you have access to the 11.3.01 files that you have downloaded (in binary mode) from the BMC Electronic Product Download site or from the TrueSight console.
• Ensure that you use the binary mode when you are moving files from one system to another.
• If you have installed only the Integration Service and not the cell but the cell directory (/pw/server directory) exists in the computer, the upgrade installer upgrades the Integration Service as well as installs the cell. If you do not want to install the cell, rename the cell directory and proceed with the Integration Service upgrade. Post upgrade, you can rename the cell directory to the original name.
• Ensure that the /tmp/agentlist file is present. If it is not present, then create the file and add an entry for the installed Integration Service. For example, if you have two Integration Services installed at /opt/bmc/TSIMAgent and /data1/bmc/TSIMAgent on ports 12124 and 12125 respectively, add the following two entries in the agentlist file:
  

  BMC TrueSight Agent 10.5 build 231209006(12124);/opt/bmc/TSIMAgent

  BMC TrueSight Agent 10.7 build 231209006(12125);/data1/bmc/TSIMAgent

To upgrade the Integration Service and Remote Cell

You can read the S81pronto file under /etc/rc3.d/ to find the location of the installation directory for an already installed Integration Service on the Linux computer.

Do the following:

1. Log in to the host computer (as a root user if you are using Linux) on which you want to install the Integration Service and Remote Cell, and delete all the files from the temporary directory: 

   1. (Windows) %temp%
   2. (Linux) /tmp

2. Extract the downloaded zip files (the installer) to a temporary directory.

3. Save the TSIMAgent.zip file on your drive and extract its contents. 

4. (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.

   Example: chmod -R 755 Disk1


   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.
   
   

   Note

   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 -J MINIMAL=true argument.

   • 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.

5. Navigate to the Disk1 directory of the extracted folder, and run the installer:
   

   • (Windows) install.cmd with the Run as administrator option

   • (Linux) ./install.sh as a root user

   
   

6.  Review the Welcome page, and click Next.
7. Read the license agreement, agree to the terms, and click Next. 

8. On the Existing Installed Instances Detected page, select Maintain or update the instance of this application selected below.

9. Select the Integration Service or Remote Cell instance to upgrade, and click Next.

10. On the Upgrade Confirmation page, click Yes, and click Next.
    The installer automatically checks for the upgrade requirements. If it finds any errors, it displays them on a separate window. You can quit the upgrade process at this point, correct the indicated discrepancies, and then rerun the upgrade. 

    Do the following if you are upgrading as a non-root user on a Linux operating system:

    • Ensure that the S81pronto.<User_ID>.<Agent_Instances> file exists in the /etc/rc.d/rc<Runlevel_Directory>.d folder. If the file does not exist in this folder, the installer stops and it needs to be manually copied from the /pw/pronto/bin folder as a root user.

      User_ID - User ID of the logged in user

      Agent_Instances - Number of Integration service instances on the computer

      Runlevel_Directory - Number of runlevel directory

    • If the following warning message is displayed in the tsim_agent_install.log file, run the chmod command to manually update the file permissions.

      LOG EVENT

      {Description=[<AGENT_INSTALL> Unable to execute command successfully. Command: [/tmp/BPPMAGENTSCRIPTS/./restoreISFilePermissions.sh, /tmp/BPPMAGENTSCRIPTS/filesList.properties]

      Run the following commands to update the file permissions.

      chmod 664 $BPPM_AGENT_HOME/pw/monitors/monitors/NodePingMon/libNodePingMon.sl
      chmod 664 $BPPM_AGENT_HOME/pw/server/etc/mcell.propagate
      chmod 664 $BPPM_AGENT_HOME/pw/server/etc/mcxa.conf
       #Cell is installed on same server
      chmod 774 "/etc/mcell/setup_env.sh"
      chmod 774 "/etc/mcell/setup_env.csh"

11. 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 directory path must follow this hierarchy structure for each cell KB to be migrated:
    (Windows) \topLevelDirectory\mergedKB\server\etc\cellName, where \server\etc\cellName is the standard subdirectory

    (Linux) /topLevelDirectory/mergedKB/server/etc/cellName, where /server/etc/cellName is the standard subdirectory
    
    

    Note

    If you have KBs to migrate but you have not migrated yet, you can stop the upgrade process and migrate the KBs by using the mmigrate utility. For more information, see Using the mmigrate utility . After you successfully migrate the KB to version 11.3.01, you can continue with this procedure.

    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.

    During the upgrade, the installer copies the KBs in the:

    (Windows) \mergedKB\server\etc\cellName directory and overwrites them in the default installationDirectory\pw\server\etc\cellName directory

    (Linux) /mergedKB/server/etc/ directory and overwrites them in the default installationDirectory/pw/server/etc/cellName directory

12. On the Installation Preview window, click Install.
    When the upgrade is complete, the upgrade automatically starts the Integration Service processes.

    Important

    After upgrading the Integration Service and Cell on the primary server, stop the Integration Server processes on the primary server and proceed with the upgrade of Integration Service and Cell on the secondary server. After the upgrade is completed on the secondary server, you must start the processes on the primary server.

13. On the Installation Summary window, click View Log to display the installation/upgrade log.

14. Click Done.

    The Integration Service is upgraded.

15. If you are installing on the AIX platform and using DB2 Database monitors, see  Finishing the upgrade process on the AIX platform .

16. Restore original SSL certificates for Integration Service. For instructions, see  Restoring original security certificates for Integration Service .

17. To verify that the Integration Service is running:

    • (Windows) ensure that the Integration Service Ver x.xbuild yyyy(portNumber) service status is started. If the Infrastructure Management Integration Service Ver x.xbuild yyyy(portNumber) service is not running, start it. 

    • (Linux) navigate to the installationDirectory/pw/pronto/bin/ directory, and run the pw agent status command. Verify that the tsim_agent process is listed. If the tsim_agent process is not listed, run the pw agent start command. This command restarts all the Integration Service processes. 

    • If any exceptions occur, check the following log files that are stored on the TrueSight Infrastructure Management Server at installationDirectory\pw\pronto\logs:

      • TrueSight.log
      • TSIMAgent.log

    • If you are not able to identify the problem, contact  BMC customer support  for assistance.

      Note

      Ensure that you restore the mcell.dir file that you had taken a back up before upgrading the Integration service.

    • On both Microsoft Windows and Solaris platforms, to verify that the cell is running, run the mcstat -n cellName command to check the cell's status. If the cell is not running, use the appropriate start procedure. (On Solaris, source the setup_env.sh file in the /installationDirectory/pw/server/bin directory to run the mcstat command.)

    • If you have any problems with the cell, see  Cells troubleshooting .

To upgrade multiple Integration Services on a single 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.

Restoring original security certificates for Integration Service

During the Integration Service upgrade, the installer automatically takes a backup of the keystore, and keystore password files in the <installationDirectory\Agent\backup_security_<oldversion> location. After the upgrade is completed, these backed up files are automatically restored to the following directory location.

• (Microsoft Windows) <installationDirectory>\pw\pronto\conf
• (Solaris or Linux) <installationDirectory>/pw/pronto/conf

Troubleshooting upgrade issues

If you face issues during upgrade, see Troubleshooting an Integration Service deployment.

Next step in the Upgrade process

Now that you have successfully upgraded Integration Service and cell, upgrade the other TrueSight Operations Management components as per your requirements. For instructions, see Upgrading.