BMC Software, Inc., Confidential and Proprietary Information
Installing and Migrating PATROL for BEA WebLogic 2-33
Migrate Your Customizations
Customizations made to PATROL for BEA WebLogic may include
changes to the parameter alarm ranges, recovery actions, states, or other
parameter properties.
You can migrate customizations manually or through the KMDS.
Migration of
.km files through the KMDS is automated, with the
following exceptions:
• modified PSL code, whether it is embedded in
.km files or in .psl files
• parameter overrides done with a PATROL Operator Console
• new Knowledge Modules that you created
Note
Even if you are not using the PATROL KMDS, you can use the PATROL
migration tools to help you migrate customizations. For more
information about the PATROL migration tools, see the PATROL
Migration Tools User Guide.
Preparing to Migrate
Before you migrate the customizations from the previously installed
version of PATROL for BEA WebLogic to the newly installed version of
PATROL for BEA WebLogic, you must remove any obsolete
KMs from
the list of preloaded KMs on each PATROL Agent. See the PATROL
Agent Reference Manual for instructions on removing KMs from the
preload list.
To Migrate Using the PATROL Migration Tools Version 3.5
The following procedure is a general workflow for using the PATROL
Migration Tools version 3.5 to migrate your customizations to the new
version of PATROL for BEA WebLogic. For detailed explanation and
instruction on using the migration tools, see the PATROL Migration Tools
User Guide.