Performing the upgrade
The following topics describe how to upgrade your installed version of BMC PATROL for JBoss Application Server to the latest version.
Conditions for upgrading
Use the following table to help you choose an upgrade procedure.
Choosing an upgrade procedure
Use this procedure | If you have this situation |
|---|---|
Upgrading without saving KM customizations |
|
Upgrading and preserving KM customizations | Made customizations to the KM files in your previously installed version of BMC PATROL for JBoss Application Server and want to save those customizations and migrate them to the new version of BMC PATROL for JBoss Application Server. |
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 JBoss Application Server over your previous version after moving or deleting BMC PATROL for JBoss Application Server files from the PATROL_CACHE. See Installing-for-the-first-time for instructions.
Migrating customizations manually
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
- 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.
- Uninstall the old version of BMC PATROL for JBoss Application Server.
- Install the new version of BMC PATROL for JBoss Application Server as described in Performing the installation.
- Identify and record the coding changes, which represent your customizations, in BMC PATROL for JBoss Application Server by comparing the content of the ASCII files in the newly installed BMC PATROL for JBoss Application 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.
- Incorporate your customizations to the new BMC PATROL for JBoss Application Server by performing the following steps:
- Restart the PATROL console.
- Load the newly installed BMC PATROL for JBoss Application Server.
- 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 JBoss Application Server.
You must first migrate your customizations from the old version of BMC PATROL for JBoss Application 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.