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
(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.
./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.
./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
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]}
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 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.
After installing the Fix Pack, perform the following steps to enable the Integration Service and PATROL Agent communication to be TLS compliant:
Stop the Integration Service (UNIX) by running the following command:
pw is stop
To stop the Integration Service (Microsoft Windows), 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>\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
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
Install the Fix Pack on the BMC ProactiveNet Server. For more information, see Installing the Fix Pack on the BMC ProactiveNet Server.
8 Comments
Michael Ashall
Sanjay Prahlad
Bryan Meranda
Ashwini Pagade
How about adding uninstall steps for fp2.
Sithesh V.V
Sanjay Prahlad
Cmichael White-eagle
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.
Cmichael White-eagle
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.