Applying service packs on the Integration Service and Remote Cell in the standalone mode using the wizard


Where you are in the Applying service packs process

Service packs contain a full installation of the Infrastructure Management Integration Service.

If you have already installed an earlier version of the Integration Service, you can upgrade it. If not, you can install a fresh version of the Integration Service.

As a best practice, BMC recommends that both the Infrastructure Management server and the Integration Service are of the same version.

To install a fresh version of the remote Integration Service or remote cell

  1. Install the service pack from either the service pack installation files or from the TrueSight console:
    • From the
      seervice pack installation files:
      1. Access the TSIMAgent\<OS> folder and extract the contents of the TSIMAgent file. From the extracted TSIMAgent folder, access the Disk1 folder.
      2. (Windows) Right-click the install.cmd file and select the Run as administrator option to launch the Integration Service installer. Do not use the setup.exe file.
        (UNIX) Run the ./install.sh command.

    • From the TrueSight console:
      1. In the navigation pane, expand Configuration and select Managed Devices.
      2. Select the Infrastructure Management Server where you want to download the software.
      3. Click the common action menu and select Launch Download Console.

        The Downloads page opens in a new browser tab or window.
      4. From the Infrastructure Management Administrator Console Software table, select the appropriate Integration Service installation utility depending on the operating system, and save the file to the computer on which you want to install the software.

      5. Extract the contents of the TSIMAgent file and access the Disk1 folder.
      6. (Windows) Right-click the install.cmd file and select the Run as administrator option to launch the Integration Service installer. Do not use the setup.exe file.
        (UNIX) Run the ./install.sh command.

      Tip

      Do not run the installer from within a compressed file. Always extract the contents of the compressed file that contains the installer before running it.

     
  2. On the Welcome page, click Next.
  3. On the License Agreement page, select I agree to the terms of the license agreement, and click Next.
    The pre-installation check utility verifies whether the computer meets the requirements for installing the Integration Service. If the pre-installation check fails, the errors or warnings are listed in the Notification page. In that case, ensure that you correct the issues, and restart the installation process.
    A warning is displayed if the Microsoft .NET Framework is not installed on the computer. Install Microsoft .NET Framework version 3.0
  4. Select the installation directory and click Next.

    Note

    • (Windows) Do not install the product in a root directory (for example, C: or D: ), shared drive, or directly in the Documents and Settings folder.
    • (Linux) Do not install the product in the root directory.
    • (Linux) The directory in which the the product is installed and all its parent directories must have 755 permissions (read, write, and execute permissions to owner, groups, and others) and must be owned by root as well as others. Without these permissions and ownership, you will not be able to log in to the TrueSight Infrastructure Management Server.
  5. Select the components to install - Integration Service, Remote cell, or both.
  6. Enter details for the components you choose. You can also configure the Remote cell for High Availability.
  7. Click Install.
    The installer configures the components and starts the installation process. This might take some time. After the installation, the Installation Summary dialog box displays a summary. To view the installation logs, click View Log.
  8. Click Done to complete the installation process.

    Do the following after you complete installing as a non-root user on a Linux operating system:

    • Manually copy the S81pronto.<User_ID>.<Agent_Instances> file from the /pw/pronto/bin directory to the /etc/rc.d/rc<Runlevel_Directory>.d directory.

      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

    • Open the /etc/rc.d/rc.local file, comment the pre-existing S81pronto file entries, and add a fresh entry of S81pronto.<User_ID>.<Agent_Instances> in the /etc/rc.d/rc.local file as shown in the following example:

      #/etc/rc2.d/S81pronto.0.2
      #/etc/rc2.d/S81pronto.0.2
      #/etc/rc2.d/S81pronto.0.2
      /etc/rc2.d/S81pronto.1004.1

    • Revoke the write permissions for the non-root users from the following directories:
      • /etc/patrol.d
      • /etc/init.d/etc/rc.d/rc0.d/etc/rc.d/rc1.d/etc/rc.d/rc3.d, and /etc/rc.d/rc5.d
  9. To verify that the Integration Service is running:

    • (Windows) Check if the Integration Service(portNumber) service status is Started.

    • (Linux) Navigate to the installationDirectory/pw/pronto/bin/ directory and run the pw agent status command. Verify that the pronet_agent process is listed. 

      If the pronet_agent process is not listed, run the pw agent start command. This command restarts all the Integration Service processes.

    Notes

    • If you modify the control port of a service explicitly through the pronet.conf file, the port number is not updated in the Add/Remove Programs applet and in the Agent Service display name field.
    • Each Integration Service on a system runs on a separate Java Virtual Machine (JVM).
    • You can check the version number of the Integration Service in the AGENT_VERSION file
      • (Windows) installationDirectory\Agent\pronto\bin\AGENT_VERSION
      • (Linux) installationDirectory/pw/pronto/bin/AGENT_VERSION
    • If you are monitoring the Integration Service for a process crash using the Microsoft Debug Diagnostics Tool (DebugDiag tool), BMC recommends that in the Services window, you stop and start the service, instead of restarting the service.

To upgrade an existing remote Integration Service or remote cell

  1. Upgrade the Integration Service from either the service pack installation files or from the TrueSight console:
    • From the Fix Pack installation files:
      1. Access the TSIMAgent\<OS> folder and extract the contents of the TSIMAgent file. From the extracted TSIMAgent folder, access the Disk1 folder.
      2. (Windows) Right-click the install.cmd file and select the Run as administrator option to launch the Integration Service installer. Do not use the setup.exe file.
        (UNIX) Run the ./install.sh command.

    • From the TrueSight console:
      1. In the navigation pane, expand Configuration and select Managed Devices.
      2. Select the Infrastructure Management Server where you want to download the software.
      3. Click the common action menu and select LaunchDownload Console.

        The Downloads page opens in a new browser tab or window.
      4. From the Infrastructure Management Administrator Console Software table, select the appropriate Integration Service installation utility depending on the operating system, and save the file to the computer on which you want to install the software.

      5. Extract the contents of the TSIMAgent file and access the Disk1 folder.
      6. (Windows) Right-click the install.cmd file and select the Run as administrator option to launch the Integration Service installer. Do not use the setup.exe file.
        (UNIX) Run the ./install.sh command.

      Tip

      Do not run the installer from within a compressed file. Always extract the contents of the compressed file that contains the installer before running it.

  2. Review the Welcome page, and click Next.
  3. Read the license agreement, agree to the terms, and click Next
  4. On the Existing Installed Instances Detected page, select Maintain or update the instance of this application selected below.

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

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

    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"
  7. On the Configuring KB Migration Path page, do the following:

Browse to select the migrated KB directory path that ends with the cellname folder

During the upgrade, the installer copies the following:

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

    • (Linux) Copies the migrated KB from the <migratedpath>\cellname directory and overwrites them in the default <installationDirectory>/pw/server/etc/cellName directory

Note

  • 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.
  • If migrated KB have a different cellname folder, the installation completes with the following warning message in logs:

Cell's Kb does not exist or name does not contain the cell name.

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

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

  3. Click Done.
    The Integration Service is upgraded.

  4. (applicable only to custom cells created using the mcrtcell command) Start the custom cells manually.

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

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

Note

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

Note

There are major changes for cell KB in 11.3.05 version. You must migrate the cell KB during or after installation of 11.3.05 service pack. If not migrated, it will impact the existing cell functionalities.

For more information, see Using the mmigrate utility.

To configure the remote Integration Service or remote cell after installing the service pack 

Migrate Knowledge Bases for custom cells

The service pack installer upgrades and migrates the cell created by the installer. For custom cells that are created manually, the installer upgrades the cell binaries but does not migrate the KBs.

To migrate the KBs for custom cells, perform the following steps:

  1. Follow the instructions at Using the mmigrate utility.
  2. Compile and restart the custom cells. For more information, see  Compiling a Knowledge Base - mccomp Open link

Recreate the boot script for the remote cell on Linux operating system

If you have upgraded remote cell on Linux operating system as a non-root user, do the following:

  1. Go to the <InstallationDirectory>/pw/server/bin/ directory.
  2. Run the following command:

    #Syntax
    mcrtcell -n <cell_name> -fb -ba -r
    
    
    #Example
    #Ensure that the cell name that you specify in the following command exists before running this command.
    mcrtcell -n mycell -fb -ba -r

    This command recreates the boot script for the mycell cell without modifying the configuration and Knowledge Base files.

To install multiple Integration Services on a single computer 

By installing multiple Integration Services on a single computer, you can partition the monitoring into different domains and maximize hardware usage. Multiple TrueSight Infrastructure Management Servers in different locations can connect to different Integration Services running on the same computer. Each Integration Service can collect a different set of data authorized for its respective TrueSight Infrastructure Management Server. 

Note

  • Installing multiple Integration Services on a single computer adds additional load on the computer in terms of CPU, IO, Memory, and TCP buffer.
  • Do not install an earlier version of the Integration Service on a computer that has a later version installed.
  • When installing multiple integration services on a single computer, only the first integration service installed is installed with a cell. Subsequent integration service installations update the cell installed with the first integration service.

You can choose to install a new instance of the Integration Service or alternatively, you can upgrade an existing Integration Service by selecting from the list displayed. If you want to upgrade an existing Integration Service, see  Upgrading Open link .

The procedure to install multiple integration services is similar to installing the Integration Service for the first time.

  1. Perform the installation procedure as described above.
  2. (Windows) If WinPCAP application is installed, on the local agent Installation dialog box, click Yes to overwrite the IP Top10 detailed diagnostics.
  3. Click Finish.

Where to go from here

Step 3 Phase B — Now that you have successfully installed the feature pack or fix pack on the Integration Service and Remote Cell, you must install it on the Infrastructure Management server.

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

Comments