Performing the upgrade

This information describes how to upgrade your installed version of BMC PATROL for Apache Tomcat and Generic Java Server KM to the latest version.

Conditions for upgrading

Use the following table as a guide for the upgrade procedure that is most relevant for you.

  Choosing an upgrade procedure

Monitoring environment changes during upgrading

If you have configured multiple environments for monitoring, the Java and some additional parameters that you configured for these environments can change due the upgrade procedure.

After the new KM version installation begins, these parameters are changed based on the first environment that is encountered with configured Java Home parameters.

For the PATROL console, the following parameters are located in the Defining Java Virtual Machine arguments dialog box:

• Java Home directory
• Local Administrator OS account
• Local Administrator OS password
• JVM arguments

Upgrading without saving KM customizations

If you do not want to save any customizations of .km files, PSL code, alarm thresholds, or events, you can simply install the new version of BMC PATROL for Apache Tomcat and Generic Java Server KM over your previous version after moving or deleting BMC PATROL for Apache Tomcat and Generic Java Server files from the PATROL_CACHE. For installation instruction, see Installing.

If you have made customizations to the PATROL Script Language (PSL) code, you must manually migrate those customizations. This task contains a procedure for manually migrating each kind of customization.

To migrate customizations to KM files manually

1. Ensure that you have made a record of your customizations and have backed up the customized files in the  PATROL_HOME  and  PATROL_CACHE  directories.
2. Uninstall the old version of BMC PATROL for Apache Tomcat and Generic Java Server KM.
3. Install the new version of BMC PATROL for Apache Tomcat and Generic Java Server KM as described in Installing.
4. Identify and record the coding changes, which represent your customizations, in BMC PATROL for Apache Tomcat and Generic Java Server by comparing the content of the ASCII files in the newly installed BMC PATROL for Apache Tomcat and Generic Java Server version with the content of the customized ASCII files with the same name that is saved in the directory to which you moved the old version.
5. Incorporate your customizations to the new BMC PATROL for for Apache Tomcat and Generic Java Server KM by performing the following steps:
   1. Restart the PATROL console.
   2. Load the newly installed BMC PATROL for Apache Tomcat and Generic Java Server KM.
   3. Using a PATROL developer console, enter the customizations that you identified in step 4, one by one.

To migrate customized PSL code

Customizations made to PATROL Script Language (PSL) code are not automatically migrated. These customizations can be embedded in .km files or stored in separate .psl files. Migrate these customizations manually, using the following guidelines:

• If you modified .psl files that were shipped by BMC, you must manually re-edit the PSL code in the new KM by using a PATROL developer console to reapply your changes.
• If you modified PSL code embedded in a .km file, that code will be overwritten when you install a new version of the product. You must manually edit the new .km files by using a PATROL developer console to reapply your changes.
• If you created a new PSL file (not shipped by BMC) outside of a .km file, Installing PATROL for Microsoft Cluster Server.

Upgrading and preserving KM customizations

Use the appropriate task in this section if you want to upgrade to the new version of PATROL for Windows Servers and you want to preserve any customizations you have made to the .km files in the previous version of BMC PATROL for Apache Tomcat and Generic Java Server KM. 

You must first migrate your customizations from the old version of BMC PATROL for Apache Tomcat and Generic Java Server to the new version, and then install the result into your environment. You should complete this process on a limited number of computers in the test environment first, test the merged KMs thoroughly, and then deploy them to your production environment.