Page tree

This Fix Pack contains a full installation of the BMC ProactiveNet Integration Service.

If you have already installed version 9.6.00 or 9.6.00.001 of the Integration Service, you can upgrade it to version 9.6.00.002. If not, you can install a fresh 9.6.00.002 version of the Integration Service.

Note

  • If you do not install the Fix Pack on the Integration Service, the Integration Service and the BMC ProactiveNet Servers will be out of sync and will not function properly.
  • To correct certain security issues related to Apache Tomcat, install Fix Pack 2 for the Integration Service.

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

  1. Install the Fix Pack from either the Fix Pack installation files or from Central Monitoring Administration:
    • From the Fix Pack installation files:
      1. Access the BPPMAgent\<OS> folder and extract the contents of the BPPMAgent file. From the extracted BPPMAgent 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 Central Monitoring Administration:
      1. From the Repository drawer, click Integration Services.
      2. Select and download the installation file that corresponds to the operating system on which you want to install the Integration Service.
      3. Extract the contents of the BPPMAgent file and access the Disk1 folder.
      4. (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.
  4. Select the installation directory and click Next.
  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.

To upgrade an existing remote Integration Service or remote cell

  1. Upgrade the Integration Service from either the Fix Pack installation files or from Central Monitoring Administration:
    • From the Fix Pack installation files:
      1. Access the BPPMAgent\<OS> folder and extract the contents of the BPPMAgent file. From the extracted BPPMAgent 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 Central Monitoring Administration:
      1. From the Repository drawer, click Integration Services.
      2. Select and download the installation file that corresponds to the operating system on which you want to upgrade the Integration Service.
      3. Extract the contents of the BPPMAgent file and access the Disk1 folder.
      4. (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.
  4. The installer lists existing Integration Service instances, if any.
    Choose to install a new instance or upgrade an existing instance. Highlight the instance you want to upgrade and click Next.
  5. If you are upgrading an Integration Service instance, the Upgrade Confirmation screen is displayed. Select Yes to confirm and click Next.
  6. On the KB Migration Path screen, indicate if you have already migrated customized BMC Event Manager KBs to the BMC ProactiveNet KB.
    The default option is No. Select Yes if you have already migrated the customized KB and select the migrated KB folder.
  7. Click Install.
    The installer configures the components and starts the upgrade 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.

    Note

    After the upgrade completes successfully on Linux, the following warning message is displayed in the log. There is no impact to functionality and you can ignore this warning.

    LOG EVENT {Description=[/bin/sed: -e expression #1, char 2: unterminated `s' command]} 

  8. Click Done to complete the upgrade process.
  9. If the Impact Manager cell instances are not running, start them manually.

Note

If you manually delete the default remote cell created by the installer before installing the Fix Pack, the installer recreates the default remote cell during the Fix Pack installation. There is no impact to functionality. 

To configure the remote Integration Service or remote cell after installing the Fix Pack

Migrate Knowledge Bases for custom cells

The Fix 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 Migrating the configuration of BMC ProactiveNet cells.
  2. Compile and restart the custom cells. For more information, see Compiling a Knowledge Base - mccomp.

Add missing cell-specific parameters

If you migrated the customized KB during the cell upgrade, parameters in mcell.conf that were added by new features in the product do not reflect in the cell-specific mcell.conf.

Solution: Compare the parameters in the InstalledDirectory\pw\server\etc\mcell.conf file with the InstalledDirectory\pw\server\etc\<cell name>\mcell.conf file and add the missing parameters to the relevant cell-specific mcell.conf file.

Configure the Integration Service and PATROL Agent to enable TLS communication

After installing the Fix Pack, perform the following steps to enable the Integration Service and PATROL Agent communication to be TLS compliant:

  1. Stop the Integration Service (UNIX) by running the following command: 

    pw is stop
  2. To stop the Integration Service (Microsoft Windows), navigate to Start > Settings > Control Panel.

  3. Double-click the Services icon to launch the Services dialog box.
  4. Locate the BMC ProactiveNet Integration Service on the list of services, highlight, and click Stop
  5. Click Yes to close the warning message that is displayed. 
    The status for the Integration Service changes from Started to (blank).

  6. Navigate to the <Integration Service installation directory>\Agent\patrol\common\security\config_v3.0 directory by running the following command:

    # Microsoft Windows operating system
    $cd <Integration Service installation directory>\Agent\patrol\common\security\config_v3.0
    
    # Unix operating system
    $cd <Integration Service installation directory>/Agent/patrol/common/security/config_v3.0
  7. Run the following command:

    #Syntax
    set_unset_tls_IS.cmd <$BMC_ROOT> <SET_TLS;UNSET_TLS> <security_level> -serverDbPath <serverDbPath> -identity <identity>
    #Example
    $set_unset_tls_IS.cmd "C:\Program Files (x86)\BMC Software\TSIM Agent" SET_TLS 3 -serverDbPath "C:\Certificates\server_db" -identity bmcpatrol

Where to go from here

Install the Fix Pack on the BMC ProactiveNet Server. For more information, see Installing the Fix Pack on the BMC ProactiveNet Server.

Related topics

Downloading the Fix Pack

Installing the Fix Pack silently

8 Comments

  1.  

    1.  

  2.  

  3. How about adding uninstall steps for fp2.

    • http://jira-cor.bmc.com/browse/CRE-3128 is fixed
    • below text should be removed.  
    • If you have installed multiple Integration Service instances, the Fix Pack installer stops all the instances before installing the Fix Pack and restarts only the specific instance that the Fix Pack is installed on. You need to manually restart all the other instances.
    1.  

  4. During the Fix Pack 2 Integration Service upgrade (9.6 build 241230420 to build 261331948) on Windows, the /Agent/Server folder gets moved or modified so the install fails.  This occurred on both my IS servers. Luckily I backup up the Agent folder and replaced the folder Server back to /Agent and re-installed.  It works the second time. 

    Please fix this.

     

  5. Correction to above, the Server folder gets removed or modified. Not moved.

    Error is mcwela does not exist in INSTALL_DIR\Agent\server\bin

    This occurred on both my IS servers.