Feature packs and fix packs contain a full installation of the Infrastructure Management Integration Service.
If you have already installed version 10.5.00 or 10.5.00.001 of the Integration Service, you can upgrade it. If not, you can install a fresh version of the Integration Service.
Note
Version 10.5.00.001 and later of the Infrastructure Management server and the Integration Service support the TLS 1.2 protocol. Earlier versions of the Integration Service support the SSLv3 protocol.
After upgrading the Infrastructure Management server, ensure to also upgrade the Integration Service to version 10.5.00.001 or later, if configured to communicate over SSLv3.
As a best practice, BMC recommends that both the Infrastructure Management server and the Integration Service are of the same version.
(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 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.
./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.
(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 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.
./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.
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
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.
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:
If you installed the pproxsrv
service on the remote Integration Server for configuring the HP-OM and Tivoli adapters, the Integration Service installer removes the pproxsrv
service when you upgrade the Integration Service. The pns.reg file entries are also removed.
After upgrading the Integration Service, perform the following steps:
pproxsrv -install -p <port number> -m
If you installed or upgraded the Integration Service on Linux as a non-root user, perform the following step:
Have an administrator of the Integration Service host machine copy the S81pronto.xxxx file from installedDirectory/pw/pronto/bin to the /etc/rc.d/rc5.d directory.
The S81pronto.xxxx file is needed to automatically start the Integration Service after a restart of the host machine.
This step is required only if you configured the remote Integration Service to run as a Network Service user before upgrading to 10.5 Fix Pack 2.
After upgrading to 10.5 Fix Pack 2, the remote Integration Service reverts to run as a Local System user. Reconfigure it to run as a Network Service user. For more information, see Configuring TrueSight Operations Management components to run as a Network Service user.
Fix Pack 1 (10.5.00.001) for the Integration Service supports the TLS protocol with SHA-256 certificate support on the PATROL Agent to Integration Service communication channel. This requires the
BMC PATROL Agent 10.0
or later.
After upgrading the Integration Service, perform the following steps to enable the Integration Service and PATROL Agent communication to be TLS-compliant.
Stop the Integration Service by running the following command:
pw is stop
Run the following command:
#Syntax ./set_unset_tls_IS.sh <$BMC_ROOT> <SET_TLS;UNSET_TLS> <security_level> #Example $set_unset_tls_IS.sh "/opt/TSIMAgent/pw" SET_TLS 3
Modify the bppmpis.plc file from the /etc/patrol.d/_opt_bmc_TSIMAgent_pw/security_policy_v3.0 directory with the following changes:
At the end of the server
section, add the following entries :
service = SSL provider = bmcsslNull module_name = libbmcnss.so
In the server
section, update the identity and password values with the custom certificate values. Example provided below:
Original: password = 17fa9e37f011ec79ef0b32d00cbc98c4f4ca367272714f6b, sample.bin identity = server Updated: password = 67f3e6095553374389b1556afa7e0e4437f6ba5e80295d50acd965c0c603286f, sample.bin identity = server - Frisky
Modify the access file from the $BMC_ROOT/pw/patrol/common/security/keys directory and add the highlighted lines:
For security levels 0-2 | [SSL_SERVER] NSS_DB_HOME = sql:”server certificate path” |
For security levels 3-4 | [SSL_SERVER] NSS_DB_HOME = sql:”server certificate path”
NSS_DB_HOME = sql:”client certificate path” |
Stop the Integration Service:
Navigate to Start > Settings > Control Panel.
Click Yes to close the warning message that is displayed.
The status for the Integration Service changes from Started to (blank).
Navigate to the <Integration Service installation directory>\TSIMAgent\patrol\common\security\config_v3.0 directory.
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\BMC Software\TSIMAgent" SET_TLS 3 -serverDbPath "C:\Certificates\server_db" -identity bmcpatrol
Install the Fix Pack on the Infrastructure Management server. For more information, see Applying feature packs or fix packs on the Infrastructure Management server.
Configuring TrueSight Infrastructure Management to enable TLS 1.2
Applying feature packs or fix packs on Infrastructure Management in high availability cluster mode
Applying feature packs or fix packs silently on Infrastructure Management