Migrating Customizations Manually

If you have only a few customizations, you might find manual migration easier than migrating using the PATROL migration tools. 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 PATROL HL KM.
3. Install the new version of PATROL HL KM as described in the section First-Time-Installation.
4. Identify and record the coding changes, which represent your customizations, in

PATROL HL KM by comparing the content of the ASCII files in the newly installed PATROL HL KM 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.

1. Incorporate your customizations to the new PATROL HL KM by performing the following steps:
2. Restart the PATROL console.
3. Load the newly installed PATROL HL KM.
4. 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 may 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 Software, 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 Software) outside of a .km file, or if you created new PSL code (not shipped by BMC Software) and embedded it in a .km file that was shipped by BMC Software, use the pslsearch utility to search your .km, .psl, and .ctg files for terms that you may have used that have since been adopted by BMC Software as PSL keywords. Rename any terms that pslsearch identifies as matching existing keywords. Reapply your changes by using a PATROL developer console. For instructions about using the pslsearch utility, see the PATROL Migration Tools User Guide.