Applying service packs on the Infrastructure Management server in the standalone mode silently
Where you are in the Applying service packs process
Failed to execute the [excerpt-include] macro.
Applying feature packs or fix packs on the Infrastructure Management server automatically updates the following components:
- Infrastructure Management server
- Infrastructure Management Self-Monitoring Service
- Infrastructure Management local Administration Console
- Infrastructure Management local Integration Service
To apply service packs on the Infrastructure Management server silently
Customize the options file
Before you install the service packs silently, customize the server_servicepack_silent.options file as required. This file is available in the <OS>\TSIMServerFixPack\Disk1 directory.
- Set the following parameter to true:
-J SERVICEPACK_CONFIRM_SERVER_RESTART=true Provide the path of the customized KB directory:
-J MIGRATED_KB=true
-J MIGRATED_KB_HOME=<KB migration path>
Microsoft Windows
To install the Infrastructure Management server by using the server_servicepack_silent.options file, run one of the following commands:
Linux
To install the Infrastructure Management Server by using the server_servicepack_silent.options file, run one of the following commands:
To configure Infrastructure Management after installing the Service Pack
After installing the Service Pack on the Infrastructure Management server, perform the following tasks:
Verify if the Service Pack was installed successfully
From the pw command prompt window, run the pw viewhistory command and verify if the following line is displayed:
BMC TrueSight Infrastructure Management Server ServicePack 11.3.xx <build number> applied- Access the TrueSight console and verify the following:
- From the Administration > Components tab that the Infrastructure Management server is in Connected status.
- From the Configuration > Managed Devices tab that the Integration Service nodes and PATROL Agents are in Connected status.
- From the Dashboards tab that any configured dashboard is displaying data.
Migrate Knowledge Bases for custom cells
The Service 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:
- Follow the instructions at Using-the-mmigrate-utility.
Compile and restart the custom cells. For more information, see Compiling a Knowledge Base - mccomp
Reinitialize the BMC Atrium CMDB integration
After installing the Service 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:
- Using the Operator console:
- Go to Options > Administration and click Edit next to the Integrations option.
- Clear and then select the BMC AR Server / CMDB checkbox.
- Click Apply to reinitialize the BMC Atrium CMDB integration.
- Using pclassinfo:
- From a command prompt window, run pclassinfo -x -o mc_sm_object.baroc.
An mc_sm_object.baroc file is created in the current directory. - Replace the existing mc_sm_baroc.object file of the target cell in the installationDirectory/pw/server/etc/cellName/kb/classes directory with the mc_sm_object.baroc file created in the previous step.
- Recompile the cell's Knowledge Base and restart the cell.
- mccomp –n pncell_<Infrastructure Management server Hostname>
- mkill –n pncell_<Infrastructure Management server Hostname>
- mcell –n pncell_<Infrastructure Management server Hostname>
- From a command prompt window, run pclassinfo -x -o mc_sm_object.baroc.
Reintegrate with BMC Service Resolution 3.5.01
After installing the Service Pack, perform the following steps to reintegrate with BMC Service Resolution 3.5.01:
- Modify the .load file in the installedDirectory\server\etc\pncell_<Infrastructure Management server host name>\kb\rules directory:
Change the order of the 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. - Modify the intelligentticketing.properties file under the installedDirectory\integrations\EventIntegrator directory:
Add the entry bsrversion=3.5.01 at the end of the file. - From a command prompt window, run pclassinfo -x -o mc_sm_object.baroc.
An mc_sm_object.baroc file is created in the current directory. - Replace the existing mc_sm_baroc.object file of the target cell in the installationDirectory/pw/server/etc/cellName/kb/classes directory with the mc_sm_object.baroc file created in the previous step.
- Recompile the cell's Knowledge Base and restart the cell.
- mccomp –n pncell_<Infrastructure Management server Hostname>
- mkill –n pncell_<Infrastructure Management server Hostname>
- mcell –n pncell_<Infrastructure Management server Hostname>
- Restart the SDIG service on the Infrastructure Management server host computer.
- Reintegrate the Atrium CMDB and SDIG using the Operator console.
- Clear the Mid-tier cache and restart the Apache Tomcat service on the ITSM host computer.