Applying feature packs or fix packs on the Infrastructure Management server in the standalone mode using the wizard

Where you are in the Applying feature packs or fix packs process

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

This topic presents the following information:

To install the Fix Pack on the Infrastructure Management server (Microsoft Windows)

1. From the extracted installation files, access the appropriate folder for the operating system. 

2. Under the TSIMServerFixPack\Disk1 directory and run one of the following installers with the Run as administrator option. Do not use the setup.exe file.
   

   Command
   install.cmd
   install.cmd –J BMC_TS_KEY_SZ=<128/256>

3. In the Welcome screen, click Next.

4. Read and agree to the terms of the license agreement and click Next.
   The installer performs the pre-installation checks. 

5. In the Fix Pack Installation Confirmation screen, only if you have completed all the prerequisites, select Yes and then click Next.

   Note (Windows)

   If you cancel the installation after you click Next, you must enable the Task Schedulers in one of the following ways:

   • Enable the Task Schedulers by using the Windows Operating system tool:
     1. On your keyboard, press the Windows key + R.
     2. In the Run window, type taskschd.msc and press Enter.
     3. In the Task Scheduler window, click Task Scheduler Library.
     4. Select all TrueSight Infrastructure Management Task Schedulers. These Task Schedulers start with Pn_.
     5. Right-click the Task Schedulers and click Enable.

   • Run one of the following scripts in the <InstallationDirectory>\pw\pronto\bin directory depending on your database:
     Enable_Tasks_Schedulers.bat sybase
Enable_Tasks_Schedulers.bat oracle
     These scripts are deployed after you clicked Next earlier in this step.

   If you select No, the installation does not proceed.
   The installer proceeds to stop the Infrastructure Management server.

6. On the Configuring KB Migration Path screen, do one of the following:

   • If you have already migrated customized KB definitions, 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.

     Note

     You must migrate and merge your KB only if the KB and the mcell.conf file located at MCELL_HOME\etc\cellName\ contain any customizations. 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.

   • If you have not migrated customized KB definitions, select No, and click Next. The installer validates whether the POMEnabled property is set to Yes in the mcell.conf file of your KB. If the property is set to No, you must set it to Yes before proceeding. If the property does not exist, you must add it in the mcell.conf file, and set it to Yes.

     Warning

     If you select No, the existing KB is used for deployment. The default KB is not used. You must run the mmigrate utility to merge the changes from the latest KB to the existing KB.

7. Click Install.
   The installer configures the Infrastructure Management server components and starts the installation process. This might take some time. After the installation, the Installation Summary dialog box displays a summary of the components installed. 

8. Click Done to complete the installation process.

To install the Fix Pack on the Infrastructure Management server (Linux)

1. From the extracted installation files, access the appropriate folder for the operating system.

2. Under the TSIMServerFixPack/Disk1 directory, run install.sh.

   Command
   To run the upgrade with the default ProductRegistry.xml path
   ./install.sh
   ./install.sh –J BMC_TS_KEY_SZ=<128/256>
   To run the upgrade with a user-specified ProductRegistry.xml path  More information Running the following command is important only if in a previous version, you moved the ProductRegistry.xml file from the default location (/opt/bmc/) to a custom location. Thus, while applying the fix pack, you need to provide the new path of the ProductRegistry.xml file (as described in the following command syntax).
   ./install.sh -J PRODUCT_CONFIGURATION_FILE_PATH=<ProductRegistryFilePath>
   Notes: If you are upgrading as a non-root user, ensure that you start a new session to run the upgrade. Do not use the su command to start a non-root session. Ensure that you have set the DISPLAY environment variable. In the preceding commands, <ProductRegistryFilePath> refers to the full path to the ProductRegistry.xml file. Example: ./install.sh -J PRODUCT_CONFIGURATION_FILE_PATH=/data1/userA/ProductRegistry.xml

3. The Welcome screen is displayed. Click Next.
4. Read and agree to the terms of the license agreement and click Next.
   The installer performs the pre-installation checks. 
5. In the Fix Pack Installation Confirmation screen, select Yes and then click Next. If you select No, the installation does not proceed.
   The installer proceeds to stop the Infrastructure Management server.

6. On the Configuring KB Migration Path screen, do one of the following:

   • In the Configuring KB Migration Path screen, if you had already migrated customized KB definitions, 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.

     Note

     You must migrate and merge your KB only if the KB and the mcell.conf file located at MCELL_HOME\etc\cellName\ contain any customizations. 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.

   • If you have not migrated customized KB definitions, select No, and click Next. The installer validates whether the POMEnable property is set to Yes in the mcell.conf file of your KB. If the property is set to No, you must set it to Yes before proceeding. If the property does not exist, you must add it in the mcell.conf file, and set it to Yes.

     Warning

     If you select No, the existing KB is used for deployment. The default KB is not used. You must run the mmigrate utility to merge the changes from the latest KB to the existing KB.

7. Click Install.
   The installer configures the Infrastructure Management server components and starts the installation process. This might take some time. After the installation, the Installation Summary dialog box displays a summary of the components installed. 

8. Click Done to complete the installation process.

To configure Infrastructure Management after installing the Fix Pack

After installing the Fix Pack on the Infrastructure Management server, perform the following tasks:

Verify if the Fix Pack was installed successfully

1. 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 11.3.xx <build number> applied

2. Access the TrueSight console and verify the following:
   1. From the Administration > Components tab that the Infrastructure Management server is in Connected status.
   2. From the Configuration > Managed Devices tab that the Integration Service nodes and PATROL Agents are in Connected status.
   3. From the Dashboards tab that any configured dashboard is displaying data.

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 does not migrate the KBs.

To migrate the KBs for custom cells, perform the following steps:

1. Follow the instructions at Using the mmigrate utility.
2. Compile and restart the custom cells. For more information, see  Compiling a Knowledge Base - mccomp

Reinitialize the BMC Atrium CMDB integration

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:

• Using the Operator console: 
  
  1. Go to Options > Administration and click Edit next to the Integrations option.
  2. Clear and then select the BMC AR Server / CMDB checkbox.
  3. Click Apply to reinitialize the BMC Atrium CMDB integration.
• Using pclassinfo:
  1. 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.
  2. 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.
  3. Recompile the cell's Knowledge Base and restart the cell.
     1. mccomp –n pncell_<Infrastructure Management server Hostname>
     2. mkill –n pncell_<Infrastructure Management server Hostname>
     3. mcell –n pncell_<Infrastructure Management server Hostname>

Reintegrate with BMC Service Resolution 3.5.01

After installing the Fix Pack, perform the following steps to reintegrate with BMC Service Resolution 3.5.01:

1. 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.
2. Modify the intelligentticketing.properties file under the installedDirectory\integrations\EventIntegrator directory:
   Add the entry bsrversion=3.5.01 at the end of the file.
3. 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.
4. 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.
5. Recompile the cell's Knowledge Base and restart the cell.
   1. mccomp –n pncell_<Infrastructure Management server Hostname>
   2. mkill –n pncell_<Infrastructure Management server Hostname>
   3. mcell –n pncell_<Infrastructure Management server Hostname>
6. Restart the SDIG service on the Infrastructure Management server host computer.
7. Reintegrate the Atrium CMDB and SDIG using the Operator console.
8. Clear the Mid-tier cache and restart the Apache Tomcat service on the ITSM host computer.

Where to go from here

Step 3 Phase C — Now that you have successfully installed the feature pack or fix pack on the Infrastructure Management server, you must apply it on the administrator console.