Applying feature packs or fix packs on the Infrastructure Management server 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*)
3	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
5	Apply the feature pack or fix pack on IT Data Analytics

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

11.3.03 instructions

Click here to view the 11.3.03 instructions...

To apply feature packs or fix packs on the Infrastructure Management server silently

Customize the options file

Before you install the Fix Pack 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
(Optional) If you have already migrated customized KB definitions, set the value of the MIGRATED_KB parameter to true 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. For example, C:\Program Files\BMC Software\TrueSight\pw\server\etc\cellname

Microsoft Windows

To install the Infrastructure Management server by using the server_servicepack_silent.options file, run one of the following commands:

Environment type Command

Production environment with the default encryption setting

install.cmd -i silent -DOPTIONS_FILE="<fullyQualifiedPath>\server_servicepack_silent.options"

Example (With space): install.cmd -i silent -DOPTIONS_FILE="C:\temp folder\Disk1\server_servicepack_silent.options"

Production environment with user-specified encryption setting

install.cmd –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="<fullyQualifiedPath>\server_servicepack_silent.options"

Example (With space): install.cmd –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="C:\temp folder\Disk1\server_servicepack_silent.options"

In the preceding commands, fullyQualifiedPath indicates the complete path where you have saved the server_servicepack_silent.options file. If the fullyQualifiedPath parameter contains a space in it, enclose the path within double quotes.

Backing up and resetting server restart parameter

Perform all the backup procedures mentioned in the Preparing to upgrade Infrastructure Management and set the following parameter to true:

-J SERVICEPACK_CONFIRM_SERVER_RESTART

If you have not set this to true, the silent installation fails. Either you can edit the server_servicepack_silent.options file and change it to true or append -J SERVICEPACK_CONFIRM_SERVER_RESTART=true to all the above commands.

For example, install.cmd -i silent -DOPTIONS_FILE="<fullyQualifiedPath>\server_servicepack_silent.options" -J SERVICEPACK_CONFIRM_SERVER_RESTART=true

Note

Based on whether you are using SAP SQL Anywhere or Oracle, the TrueSight Infrastructure Managementupgrade may take between 20 to 60 minutes to complete.

Installation-related information is not displayed on the console when the silent installation begins. However, installation occurs in the background. The progress of the installation is logged in a temporary folder during the installation. Go to Start > Run, enter %temp% in the Open box, and see the tsim_servicepack_log.txt file for the installation progress details and for the database-related progress details.

Linux

To install the Infrastructure Management Server by using the server_servicepack_silent.options file, run one of the following commands:

Environment type	Command
To run the upgrade with the default ProductRegistry.xml path
Production environment with the default encryption setting	`./install.sh -i silent -DOPTIONS_FILE="<fullyQualifiedPath>/server_servicepack_silent.options"` Example (With space): `./install.sh -i silent -DOPTIONS_FILE="/home/tsim user/Linux/Disk1/server_servicepack_silent.options"`
Production environment with user-specified encryption setting	`./install.sh –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="<fullyQualifiedPath>/server_servicepack_silent.options"` Example (With space): `./install.sh –J BMC_TS_KEY_SZ=256 -i silent -DOPTIONS_FILE="/home/tsim user/Linux/Disk1/server_servicepack_silent.options"`
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).
Production environment	`./install.sh -J PRODUCT_CONFIGURATION_FILE_PATH=<ProductRegistryFilePath> -i silent -DOPTIONS_FILE="<fullyQualifiedPath>/server_servicepack_silent.options"`
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. 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 -i silent -DOPTIONS_FILE="/home/tsim user/Linux/Disk1/server_servicepack_silent.options"` In the preceding commands, `fullyQualifiedPath` indicates the complete path where you have saved the `server_servicepack_silent`.options file. If the fullyQualifiedPath parameter contains a space in it, enclose the path within double quotes.

Backing up and resetting server restart parameter

Perform all the backup procedures mentioned in the Preparing to upgrade Infrastructure Management and set the following parameter to true:

-J SERVICEPACK_CONFIRM_SERVER_RESTART

If you have not set this to true, the silent installation fails. Either you can edit the server_servicepack_silent.options file and change it to true or append -J SERVICEPACK_CONFIRM_SERVER_RESTART=true to all the above commands.

For example, ./install.sh -J PRODUCT_CONFIGURATION_FILE_PATH=<ProductRegistryFilePath> -i silent -DOPTIONS_FILE="<fullyQualifiedPath>/server_servicepack_silent.options" -J SERVICEPACK_CONFIRM_SERVER_RESTART=true

Note

Based on whether you are using SAP SQL Anywhere or Oracle, the TrueSight Infrastructure Managementupgrade may take between 20 to 60 minutes to complete.

Installation-related information is not displayed on the console when the silent installation begins. However, installation occurs in the background. The progress of the installation is logged in a temporary folder during the installation. Access the /tmp directory and see the tsim_servicepack_log.txt file for the installation progress details and for the database-related progress details.

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:
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 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:
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 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.
1. mccomp –n pncell_<Infrastructure Management server Hostname>
2. mkill –n pncell_<Infrastructure Management server Hostname>
3. 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.

11.3.02 instructions

Click here to view the 11.3.02 instructions...

To apply feature packs or fix packs on the Infrastructure Management server silently

Customize the options file

Before you install the Fix Pack silently, customize the server_fixpack_silent.options file as required. This file is available in the <OS>\TSIMServerFixPack\Disk1 directory.

(Optional) If you have already migrated customized KB definitions, set the value of the MIGRATED_KB parameter to true 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. For example, C:\Program Files\BMC Software\TrueSight\pw\server\etc\cellname

Microsoft Windows

To install the Infrastructure Management server by using the server_fixpack_silent.options file, run one of the following commands:

Environment type Command

Production environment with the default encryption setting

install.cmd -i silent -DOPTIONS_FILE="<fullyQualifiedPath>\server_fixpack_silent.options"

Example (With space): install.cmd -i silent -DOPTIONS_FILE="C:\temp folder\Disk1\server_fixpack_silent.options"

Production environment with user-specified encryption setting

install.cmd –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="<fullyQualifiedPath>\server_fixpack_silent.options"

Example (With space): install.cmd –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="C:\temp folder\Disk1\server_fixpack_silent.options"

In the preceding commands, fullyQualifiedPath indicates the complete path where you have saved the server_fixpack_silent.options file. If the fullyQualifiedPath parameter contains a space in it, enclose the path within double quotes.

Backing up and resetting server restart parameter

Perform all the backup procedures mentioned in the Preparing to upgrade Infrastructure Management and set the following parameter to true:

-J SERVICEPACK_CONFIRM_SERVER_RESTART

If you have not set this to true, the silent installation fails. Either you can edit the server_fixpack_silent.options file and change it to true or append -J SERVICEPACK_CONFIRM_SERVER_RESTART=true to all the above commands.

For example, install.cmd -i silent -DOPTIONS_FILE="<fullyQualifiedPath>\server_fixpack_silent.options" -J SERVICEPACK_CONFIRM_SERVER_RESTART=true

Note

Based on whether you are using SAP SQL Anywhere or Oracle, the TrueSight Infrastructure Managementupgrade may take between 20 to 60 minutes to complete.

Installation-related information is not displayed on the console when the silent installation begins. However, installation occurs in the background. The progress of the installation is logged in a temporary folder during the installation. Go to Start > Run, enter %temp% in the Open box, and see the tsim_fixpack_log.txt file for the installation progress details and for the database-related progress details.

Linux

To install the Infrastructure Management Server by using the server_fixpack_silent.options file, run one of the following commands:

Environment type	Command
To run the upgrade with the default ProductRegistry.xml path
Production environment with the default encryption setting	`./install.sh -i silent -DOPTIONS_FILE="<fullyQualifiedPath>/server_fixpack_silent.options"` Example (With space): `./install.sh -i silent -DOPTIONS_FILE="/home/tsim user/Linux/Disk1/server_fixpack_silent.options"`
Production environment with user-specified encryption setting	`./install.sh –J BMC_TS_KEY_SZ=<128/256> -i silent -DOPTIONS_FILE="<fullyQualifiedPath>/server_fixpack_silent.options"` Example (With space): `./install.sh –J BMC_TS_KEY_SZ=256 -i silent -DOPTIONS_FILE="/home/tsim user/Linux/Disk1/server_fixpack_silent.options"`
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).
Production environment	`./install.sh -J PRODUCT_CONFIGURATION_FILE_PATH=<ProductRegistryFilePath> -i silent -DOPTIONS_FILE="<fullyQualifiedPath>/server_fixpack_silent.options"`
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. 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 -i silent -DOPTIONS_FILE="/home/tsim user/Linux/Disk1/server_fixpack_silent.options"` In the preceding commands, `fullyQualifiedPath` indicates the complete path where you have saved the `server_fixpack_silent`.options file. If the fullyQualifiedPath parameter contains a space in it, enclose the path within double quotes.

Backing up and resetting server restart parameter

Perform all the backup procedures mentioned in the Preparing to upgrade Infrastructure Management and set the following parameter to true:

-J SERVICEPACK_CONFIRM_SERVER_RESTART

If you have not set this to true, the silent installation fails. Either you can edit the server_fixpack_silent.options file and change it to true or append -J SERVICEPACK_CONFIRM_SERVER_RESTART=true to all the above commands.

For example, ./install.sh -J PRODUCT_CONFIGURATION_FILE_PATH=<ProductRegistryFilePath> -i silent -DOPTIONS_FILE="<fullyQualifiedPath>/server_fixpack_silent.options" -J SERVICEPACK_CONFIRM_SERVER_RESTART=true

Note

Based on whether you are using SAP SQL Anywhere or Oracle, the TrueSight Infrastructure Managementupgrade may take between 20 to 60 minutes to complete.

Installation-related information is not displayed on the console when the silent installation begins. However, installation occurs in the background. The progress of the installation is logged in a temporary folder during the installation. Access the /tmp directory and see the tsim_fixpack_log.txt file for the installation progress details and for the database-related progress details.

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

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
```
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:

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 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:

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.
1. mccomp –n pncell_<Infrastructure Management server Hostname>
2. mkill –n pncell_<Infrastructure Management server Hostname>
3. 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.

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.