Applying feature packs or fix packs on the Integration Service and Remote Cell in the standalone mode silently
Where you are in the Applying feature packs or fix packs process
Step | Task |
---|---|
1 | Prepare to apply the feature pack or fix pack |
2 | Apply the feature pack or fix pack on the TrueSight Presentation Server |
3 | Apply the feature pack or fix pack on Infrastructure Management — Phase A (You are here) |
Apply the feature pack or fix pack on Infrastructure Management — Phases B and C | |
4 | Apply the feature pack or fix pack on App Visibility Manager |
Feature packs and fix 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
To perform a fresh installation of the Integration Service or remote cell silently, see Installing the Integration Service silently.
To upgrade an existing remote Integration Service or remote cell
To upgrade the Integration Service silently, perform the following steps:
To customize the options file
Navigate to the downloaded TSIMAgent.zip file and extract its contents.
Open the bmc_tsim_is_upgrade.options file in a text editor.
Under Product Install Location, specify a valid directory for the Integration Service or remote cell:
-P installLocation=<INSTALL DIR>
<INSTALL DIR> is the installation location.
Under User Input Properties, enter the Integration Service and remote cell installation configuration information.
-J name=value
name
is the name of the parametervalue
is the value for the parameterParameter
Description
OLD_CELL_INSTALL_LOCATION Location of the earlier installation of cell. OLD_INSTALL_LOCATION Location of the earlier installation of the Integration Service. IS_CELL_UPGRADE Parameter to enable the cell upgrade.
IS_I_S_UPGRADE Parameter to enable the Integration Service upgrade.
PATROL_STAGING_ADAPTER_PORT Use this parameter only if you have specified a custom staging adapter port. AGENT_PORT Use this parameter only if you have specified a custom PATROL Agent port. Consider the following scenarios with example parameters:
Scenario
Parameters to run
When both Integration Service and cell are installed in the same folder -J OLD_CELL_INSTALL_LOCATION=C:\Program Files\BMC Software\TSIMAgent
-J OLD_INSTALL_LOCATION=C:\Program Files\BMC Software\TSIMAgent
-J IS_CELL_UPGRADE=true
-J IS_I_S_UPGRADE=true
Note: You cannot upgrade only the Integration Service or cell if they are both installed in the same folder. You must upgrade both at the same time. The installer displays an error message to upgrade both Integration Service and cell.
When the Integration Service and cell are installed in different folders Upgrade any one component at a time.
Important
If you are upgrading the remote Integration Service and remote cell as a non-root user on Linux, first upgrade only the remote cell and then upgrade the remote Integration Service.
After upgrading the remote Integration Service, check if the /server folder exists under the remote Integration Service base installation folder. Delete the folder if it exists.
Upgrade Integration Service only #-J OLD_CELL_INSTALL_LOCATION=C:\Program Files\BMC Software\TSIMAgent
-J OLD_INSTALL_LOCATION=C:\Program Files\BMC Software\TSIMAgent
-J IS_CELL_UPGRADE=false
-J IS_I_S_UPGRADE=true
Upgrade cell only -J OLD_CELL_INSTALL_LOCATION=C:\Program Files\BMC Software\TSIMAgent
#
-J OLD_INSTALL_LOCATION=C:\Program Files\BMC Software\TSIMAgent-J IS_CELL_UPGRADE=true
-J IS_I_S_UPGRADE=false
Post-installation, if you manually set the cell to high-availability mode, set the value of the following parameter to
true
-J HA_MODE_SELECTED=<false/true>
(Optional) If you have already migrated customized KB definitions to the new standard 11.0 KB, set the value of the
MIGRATED_KB
parameter totrue
and provide the path of the customized KB directory:-J MIGRATED_KB=<true/false> -J MIGRATED_KB_HOME=<KB migration path>
Parameter
Description
MIGRATED_KB Setting to enable KB migration. The default value is true
.MIGRATED_KB_HOME Path of the customized KB directory
To install the Fix Pack on the Integration Service and remote cell silently on Microsoft Windows
- Open a command prompt with the Run as administrator option. Navigate to the TSIMAgent\Disk1 folder that contains the install.cmd file.
Run the following command to install the Fix Pack on the Integration Service and remote cell by using the bmc_tsim_is_upgrade.options file:
install.cmd -i silent -DOPTIONS_FILE="<fullyQualifiedPath>\bmc_tsim_is_upgrade.options"
where fullyQualifiedPath indicates the complete path where you have saved the bmc_tsim_is_upgrade.options file. The path must be enclosed within double quotes.Example
install.cmd -i silent -DOPTIONS_FILE=
"C:\Temp\
bmc_tsim_is_upgrade.options"Installation-related information is not displayed on the console when silent installation begins. However, installation occurs in the background. The installation progress is logged in a temporary folder during installation. Navigate to the Temp folder, and view the tsim_agent_install_log.txt file.
To install the Fix Pack on the Integration Service and remote cell silently on Linux
Note
If you are installing the Fix Pack as a non-root user, ensure that the S81pronto.<User_ID>.<Agent_Instances> file exists in the /etc/rc.d/rc<Runlevel_Directory>.d folder. If the file does not exist in this folder, the installer stops and you need to manually copy the file from the /pw/pronto/bin folder as a root user.
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 a command prompt. Navigate to the TSIMAgent\Disk1 folder that contains the install.sh file.
Run the following command to install the Fix Pack on the Integration Service and remote cell by using the bmc_tsim_is_upgrade.options file:
./install.sh -i silent -DOPTIONS_FILE="<fullyQualifiedPath>/bmc_tsim_is_upgrade.options"
where fullyQualifiedPath indicates the complete path where you have saved the bmc_tsim_is_upgrade.options file. The path must be enclosed within double quotes.
Example
./install.sh -i silent -DOPTIONS_FILE="/tmp/bmc_tsim_is_upgrade.options"
Installation-related information is not displayed when silent installation begins. However, installation occurs in the background. Open /tmp or /var/tmp and view the tsim_agent_install_log.txt file for the installation progress details.
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:
- Follow the instructions at Using the mmigrate utility.
- Compile and restart the custom cells. For more information, see Compiling a Knowledge Base - mccomp
Reinstall the pproxsrv service
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:
- From the pw command prompt window, run the following command:
pproxsrv -install -p <port number> -m
- Load the pns.reg file.
Copy the S81pronto file
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.
Reconfigure the remote HA primary cell on SUSE Linux Enterprise Server
Perform the following steps after upgrading the remote cells in a high availability SUSE Linux Enterprise Server environment.
- Stop the primary and secondary remote cells, if they are running.
- Perform the following steps on the primary and secondary remote cells:
- Rename the bin folder located under the $MCELL_HOME folder to bin_64.
- Rename the bin_32 folder located under the $MCELL_HOME folder to bin.
- Start the secondary remote cell, followed by the primary remote cell.
- Run the following mposter commands on the primary remote cell only:
- mposter -q -n <cell name> -d -a <time zone> -b “description='(UTC+00:00) UTC';tzid='UTC';utc_offset=0;dst_offset=0”
- mposter -q -n <cell name> -d -a <time zone> -b “description='(UTC+00:00) GMT';tzid='GMT';utc_offset=0;dst_offset=0”
Note
You can ignore any warnings related to mquery for DDEN_MATCH_TABLE.
(Optional) To configure the Integration Service and PATROL Agent to enable TLS communication
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.
UNIX
Stop the Integration Service by running the following command:
pw is stop
- Navigate to the <Integration Service installation directory>/TSIMAgent/pw/patrol/common/security/config_v3.0 directory.
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]
;
ALLOW_ACL = *@bmc.com,*@BMC.COMNSS_DB_HOME = sql:”server certificate path”For security levels 3-4
[SSL_SERVER]
;
ALLOW_ACL = *@bmc.com,*@BMC.COMNSS_DB_HOME = sql:”server certificate path”
[SSL_CLIENT]
;NSS_DB_HOME = sql:”client certificate path”
Windows
Stop the Integration Service:
Navigate to Start > Settings > Control Panel.
- Double-click the Services icon to launch the Services dialog box.
- Locate the BMC TrueSight Infrastructure Management Integration Service in the list of services, highlight, and click Stop.
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
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.
Comments
Log in or register to comment.