Upgrading
This topic provides an overview of the upgrade process.
If you already have BMC PATROL for Oracle e-Business Suite, you might want to preserve any customizations you have made and incorporate them in the new version.
Upgrading of .km files is automated, with the following exceptions:
- PSL code modifications must be migrated manually.
- Customizations to .ctg files (application-specific event catalogs) must be re-created after installing the new KM.
Upgrading and migrating customizations
This section describes the tasks you must perform before and after a regular installation (see Installing-KM-components) if you want to upgrade to BMC PATROL for Oracle e-Business Suite 3.4.10 and migrate the customizations made to the prior version.
Before installing
- Shut down any BMC PATROL Agents, Consoles, and related services that are currently running.
- Ensure that no one is accessing any PATROL files or directories.
- Perform a full backup of the directories where PATROL executables and data are typically stored (PATROL_HOME directory for agent and console and PATROL_CACHE directory for the console).
- Delete the PATROL_CACHE for the console.
After installing
- Start the BMC PATROL Agent and Console.
- Remove any obsolete KMs from the list of preloaded KMs on each BMC PATROL Agent.
- Unload the old version of the KMs, load the new versions, and save the configuration.
- Select OA Configuration from the Oracle_Apps MainMap hostName menu. The KM-Configuration-for-Oracle-Applications-dialog-box appears.
- Modify configurations as necessary.
Depending on the version from which you upgraded, you might need to redefine the Application Oracle Home and Application TNS Home, as well as configure the middle-tier servers (especially the Apache server).
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*