Applying the Fix Pack on the Infrastructure Management server automatically updates the following components:
This topic presents the following information:
In the Configuring KB Migration Path screen, if you had already migrated customized KB definitions to the standard 10.0 KB, select Yes, and browse to the path of the customized KB directory.
The file path should follow this hierarchy structure:
\topLevelDirectory\mergedKB\server\etc\cellName, where \server\etc\cellName is the standard sub-directory.
Warning
If you have KBs to migrate but have not done so, pause the upgrade process and migrate them before proceeding. See Using the mmigrate utility.
The installer copies the KB under the \mergedKB\server\etc\cellName path and overwrites the KB in the default installationDirectory\pw\server\etc\cellName path.
Click Done to complete the installation process.
Restart the computer.
To install the Fix Pack as a non-root user
To install the Fix Pack as a non-root user, run the following command as a root user:
chown -R <non-root user name>:root ./<installation directory>/
For example, chown -R oper:root ./TrueSight/
In the Configuring KB Migration Path screen, if you already migrated customized KB definitions to the standard 10.0 KB, select Yes, and browse to the path of the customized KB directory.
The file path should follow this hierarchy structure:
\topLevelDirectory\mergedKB\server\etc\cellName, where \server\etc\cellName is the standard sub-directory.
Warning
If you have KBs to migrate but have not done so, pause the upgrade process and migrate them before proceeding. See Using the mmigrate utility.
The installer copies the KB under the \mergedKB\server\etc\cellName path and overwrites the KB in the default installationDirectory\pw\server\etc\cellName path.
Restart the computer.
After installing the Fix Pack on the Infrastructure Management server, perform the following tasks:
From the pw command prompt window, run the pw viewhistory
command and verify if the following line is displayed:
BMC TrueSight Infrastructure Management Server FixPack 10.0.500.001 <build number> applied
If you have specified a custom RMI port, it is replaced with port 2100 after installing the Fix Pack.
To update the custom RMI port number, perform the following steps:
Update the following attribute and replace 2100
with the custom RMI port number.
<attribute name="RmiPort">2100</attribute>
pw sys start
command.The Fix Pack installer upgrades and migrates the cell created by the installer. For custom cells that are created manually, the installer does not migrate the KBs.
To migrate the KBs for custom cells, perform the following steps:
After installing the Fix Pack, publishing might fail with a pclassinfo
error. This is caused due to a class information sync issue.
To resolve this issue, perform either one of the following steps:
pclassinfo -x -o mc_sm_object.baroc
.mccomp –n pncell_<Infrastructure Management server Hostname>
mkill –n pncell_<Infrastructure Management server Hostname>
mcell –n pncell_<Infrastructure Management server Hostname>
After installing the Fix Pack, perform the following steps to reintegrate with BMC Service Resolution 3.5.01:
outage
entry such that it is not the last entry in the .load file. Move the outage
entry under email_to_event
in the .load file.bsrversion=3.5.01
at the end of the file.pclassinfo -x -o mc_sm_object.baroc
.mccomp –n pncell_<Infrastructure Management server Hostname>
mkill –n pncell_<Infrastructure Management server Hostname>
mcell –n pncell_<Infrastructure Management server Hostname>
If you have an integration with BMC Remedy ITSM, install the BMC CMDB Extensions. If not, install the remote Administration Console.