Preparing to apply feature packs or fix packs on Infrastructure Management

Before you install feature packs or fix packs, perform the following steps:

Infrastructure Management server

(UNIX) Ensure that x11 is installed and configured. Both 32-bit and 64-bit RPMs must be installed.
(Windows) Ensure that:
- Disable User Account Control (UAC) and turn off Data Execution Prevention (DEP) for install.cmd.
- Stop the Infrastructure Management server by running the pw system stop command and restart the host machine to unlock any process running in the background.
- Run the pw process list command to ensure that all processes are running before you begin the upgrade.
If installing on a virtual machine (VM), back up the VM before installing the Fix Pack.
If installed on a physical computer, back up the complete Infrastructure Management server installation, so that the original Infrastructure Management server installation can be restored in case of an issue with the Fix Pack installation. For more information, see backing up the installation on Windows or UNIX.
Back up the database files. For more information, see for Oracle and for SAP Sybase SQL Anywhere.
If you are using an Oracle database, ensure that it is running before and during installation of the Fix Pack on the Infrastructure Management server.
Ensure that the BPPM_SERVER_HOME environment variable is set to the server installation directory. For example, on a Windows computer, this environment variable is set to C:\Program Files\BMC Software\TrueSight.

To back up the Infrastructure Management server files on Microsoft Windows

Check the size of the InstalledDirectory\TrueSight\pw folder and verify that you have sufficient disk space for the backup.
Stop the Infrastructure Management server by running the pw system stop command.
Ensure that none of the processes are running by running the pw process list command.
Create an archive of the Infrastructure Management server installation directory. For example, if the Infrastructure Management server is installed at C:\Program Files\BMC Software\TrueSight, create an archive of the entire TrueSight directory.
Restart the Infrastructure Management server by running the pw system start command.

To back up the Infrastructure Management server files on UNIX

Check the size of the InstalledDirectory/TrueSight/pw folder and verify that you have sufficient disk space for the backup.
Stop the Infrastructure Management server by running the pw system stop command.
Ensure that none of the processes are running by running the pw process list command.
Create an archive of the Infrastructure Management server installation directory. For example, if the Infrastructure Management server is installed under /opt/bmc/TrueSight/pw then go to /opt/bmc/TrueSight and run the following command:
tar -cvf <backupfilename>.tar pw
Restart the Infrastructure Management server by running the pw system start command.

Remote Integration Service and remote cell

Perform the following steps before you install the Fix Pack on the remote Integration Service and remote cell:

Update the remote Integration Service and administrator console installers

To ensure that the updated installers for the remote Integration Service and administrator console are available from the Infrastructure Management server, perform the following steps:

Remote Integration Service:
1. From the downloaded Fix Pack installation files, access the TSIMAgent\<OS> folder and copy the TSIMAgent file to the installedDirectory\pw\pronto\web\html\download\<OS> directory of the Infrastructure Management server.
2. To easily identify the installer version, rename the TSIMAgent file. For example, TSIMAgent_10.7FP1 to indicate the 10.7.00 Fix Pack 1 installer.
3. Repeat the preceding steps for each operating system installer file.
Administrator console:
1. From the downloaded Fix Pack installation files, access the TSIMAdmin\<OS> folder and copy the Admin file to the installedDirectory\pw\pronto\web\html\download\<OS> directory of the Infrastructure Management server.
2. To easily identify the installer version, rename the Admin file. For example, Admin_10.7FP1 to indicate the 10.7.00 Fix Pack 1 installer.
3. Repeat the preceding steps for each operating system installer file.

Delete any dormant /server folder

On UNIX, check if any dormant /server folder exists under the remote Integration Service base installation folder. These dormant folders would not contain any cell-related information. Delete such dormant folders if they exist.

Ensure that the cell is running in 64-bit mode

Run the mswitchbit 64 command to convert the cell to 64-bit mode. No changes are made if the cell is already running in 64-bit mode.

After upgrading the cell, you can switch it back to 32-bit if required. For more information, see the mswitchbit command.

Back up the remote Integration Service files

The local Integration Service files are backed up when you back up the Infrastructure Management server files. You need to manually back up all the remote Integration Services that are connected to the Infrastructure Management server. The default installation paths are:

(Windows) \Program Files\BMC Software\TSIMAgent
(UNIX) /opt/bmc/TSIMAgent

Stop the remote Integration Services and remote cells before you start the backup.

Check the size of the installation directory and verify that you have sufficient disk space for the backup.

Update the S81pronto script on SUSE Linux Enterprise Server

Perform the following steps before upgrading the Integration Service on SUSE Linux Enterprise Server:

Root user

Manually create the S81pronto.0.<instance number> script in all the etc/rc.d/rc<runLevel>.d
If multiple instances of Integration Services are installed, create that number of S81pronto.0 with respective instance number. For example:
1. S81pronto.0.1
2. S81pronto.0.2
3. S81pronto.0.3

Update the installation directory in the S81pronto file, as per the installed Integration Service.

#
# Start BMC ProactiveNet Agent processes
#
if [ -x <INSTALLATION-DIRECTORY>/pw/pronto/bin/startremotepw ] ; then
  /opt/bmc/TSIMAgent/pw/pronto/bin/startremotepw &
  /bin/echo  'BMC ProactiveNet Agent\c'
fi

Provide the required execute permissions to all S81pronto.* files.

Non-root user

If you installed the Integration Service as a non-root user, the S81pronto.0.<instance number> script is created in <installationDirectory>/pw/pronto/bin folder.
Manually copy the s81pronto.xxxx file from <installationDirectory>/pw/pronto/bin to all the etc/rc.d/rc<runLevel>.d.
Provide the required execute permissions to all S81pronto.* files.

Configure custom cells and HA cells

If you deleted the default cell that is created through the installer and a custom cell is set as the default cell, edit the following parameters in the installedDirectory\TSIMAgent\BPPMAgentInstalledConfiguration.xml file:
<name>CELL_NAME</name> <value>custom_cell_name</value>
In you have configured cell HA, update the host name as represented in the mcell.dir of respective HA cells.
<name>CELL_PRIMARY_HOST</name>
<value>primary_host_name</value>
<name>CELL_SECONDARY_HOST</name>
<value>secondary_host_name</value>

To install the Fix Pack on UNIX as a non-root user

On Linux computers, you can install the Infrastructure Management Server or the Integration Service as a root user as well as a non-root user. However, you must provide certain permissions to the non-root user as the root user.

Provide read, write, and execute permissions for the following directories:
- Installation directory (destination directory where you are planning to install the product)
- /opt/bmc directory or the parent installation directory to create the ProductRegistry.xml file
- /etc directory for set environment variable
- /etc/init.d directory for create service
- /tmp and /var/tmp directories
- (Infrastructure Management Server only) /usr and /usr/bin directories for create softlink
- (Integration Service only) /etc/patrol.d directory for create patrol security
- (Remote cell on SUSE Linux Enterprise Server only) /home directory
Provide read and write permissions for the following files and directories:
- /etc/csh.cshrc file
- /etc/profile directory for set environment variable permission
- (Remote cell on AIX only) /home directory

If the init file is not copied to the /etc/rc3.d directory, the Integration Service corresponding to the init file is not listed as installed (in the list of existing Integration Service installations) during installation of other integration services.
Verify if the non-root user owns the /etc/bmc.cshrc and /etc/bmc.profile files. If not, run the following commands as a root user:
chown <non-root user name> /etc/bmc.cshrc
chown <non-root user name> /etc/bmc.profile

Where to go from here

Install or upgrade the remote Integration Service and remote cell. For more information, see Installing or upgrading the remote Integration Service and remote cell.

Page tree