Upgrading the Integration Service and Remote Cell using the wizard

Where you are in the upgrade process

1Preparing to upgrade TrueSight Operations Management solution
2Upgrade Remedy Single Sign-On
3Upgrade TrueSight Presentation Server
4Upgrade Infrastructure Management — Phase A
Upgrade Infrastructure Management — Phase B (You are here)
5Upgrade Application Visibility Manager
6Upgrade Real End User Experience Monitoring Software Edition 
7Upgrade TrueSight IT Data Analytics

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.04 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. Open link

  • 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. Open link
  • 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.04 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 the Integration Service without cell but manually configured mcell.dir in a cell directory on the same host, refer to this.
  • While upgrading the Integration Service, the TLS configurations are reverted to default TCP communication. Ensure that after the upgradation you revert back to TLS configurations.

To upgrade the Integration Service and Remote Cell


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

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.


    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:

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


    {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, select one of the following:

    • Yes: Select this option if you have already migrated KBs using the mmigrate utility Open link . Browse to select the migrated KB directory path. 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

      During the upgrade, the installer copies the following:

      • (Windows) Copies the migrated KBs from the \mergedKB\server\etc\cellName directory and overwrites them in the default <installationDirectory>\pw\server\etc\cellName directory

      • (Linux) Copies the migrated KBs from the /mergedKB/server/etc/ directory and overwrites them in the default <installationDirectory>/pw/server/etc/cellName directory


      For custom cells (created using the mcrtcell command), you must manually copy the migrated KB to the pw\server\etc directory after the upgrade is completed.

    • No: Select this option if you want to migrate the KBs after upgrading. 
      With this option, KB customizations will be retained after the upgrade, but the new KB changes from 11.3.04 cell will not be part of the upgraded KB. 

      Ensure that you run the mmigrate utility to migrate KBs after upgrading. The mmigrate utility will merge the customized KB changes with the latest KB changes and create a migrated KB. For more information, see  Using the mmigrate utility. Open link

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


    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. (applicable only to custom cells created using the mcrtcell command) Start the custom cells manually.

  16. 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 Open link  for assistance.


      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 Open link .


  • After you upgrade an Integration Service, in the Windows Services snap-in, the Description column of the upgraded Integration Service is not automatically updated. It is updated after you restart the Integration Service.
  • As the TLS configurations are reverted to default TCP communication, ensure that post upgradation you revert back to TLS configurations.
    For more information about enabling TLS configuration, see
    • Step b-1 Configuring Integration Service to Infrastructure Management server communication to enable TLS 1.2 Open link
    • Step b-2 Configuring Integration Service to cell communication to enable TLS 1.2 Open link

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.


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/libdirectory, and restart the Integration Service.

To upgrade Integration Service (without cell) with mcell.dir configuration on the Integration Service host

If you have installed only the Integration Service and not the cell, and the cell directory (\Agent\server folder) is created using steps mentioned for the Event Destination property in the 'Integration Service properties' section at  Managing Integration Services Open link , then:


Before upgrade take a backup of the server folder while renaming it (Sample folder name: server.backup) and proceed with the Integration Service upgrade. Post upgrade, rename the server folder to the original name (\Agent\server).

In case, if the server folder gets created post upgrade and the mcell.dir file does not have a cell entry, then copy the mcell.dir file present at the server backup folder (server.backup) and replace it.

After restarting the Integration Service, check whether the Integration Service is connected to the appropriate cell to verify the connection to the upstream cell by running the following command:
(Linux) netstat -aon | grep 1828
(Windows) netstat -aon | findstr 1828

Troubleshooting upgrade issues

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

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.

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


  1. Oscar Alvarez

    For section below: 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:

    At least from upgrading from 11.3.03 to 11.3.04 was confirmed that /tmp/agentlist file is not required, wizard installer automatically recognizes all instances already deployed on the same server.

    Dec 15, 2020 05:04
    1. Krutarth Mohakud

      Hi @Oscar Alvarez, thanks for the suggestion. I have discussed this with the concerned team and removed the point from version 11.3.04.

      Jan 20, 2021 11:51