Migrating Customizations with the PATROL Configuration Manager

BMC recommends that if you have customized KMs that these customizations should be migrated to PATROL Configuration Manager rulesets. PATROL Configuration Manager rulesets allow you to manage customizations to KMs, depending on the type of customization.

1. If you have localized parameters or global parameters that have customized poll times or thresholds, use the AS_CHANGESPRING KM to migrate these customizations into PATROL Configuration Manager rulesets as described in the PATROL Configuration Manager User Guide.
2. If you have created custom recovery actions, follow these steps:
   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 PATROL KM for UNIX.
   3. Install the later version of PATROL KM for UNIX as described in the section Installing-for-the-First-Time.
   4. Ensure that you have made a record of your custom recovery actions.
   5. Use the Recovery Action Event Management commands as described in the PATROL Configuration Manager User Guide to migrate your custom recovery actions to the PATROL Configuration Manager.

All other customizations must be migrated manually, as described in Migrating-Customizations-Manually.