Skip to Content

Migrating customizations manually

Use the following procedures to manually migrate customizations from an earlier version of PATROL for Microsoft SQL Server to the new version.

To migrate customizations manually

  1. Move the earlier PATROL for Microsoft SQL Server installation to a new directory that is different from PATROL_HOME.
  2. Identify the customizations in PATROL for Microsoft SQL Server by comparing the content of the text file of the KM in the current PATROL for Microsoft SQL Server version with the content of the text file for the customized KM that is saved in the PATROL console cache backup directory.
  3. Incorporate your customizations to the new PATROL for Microsoft SQL Server by performing the following steps:
    1. Restart the PATROL console.
    2. Load the newly installed PATROL for Microsoft SQL Server.
    3. Using a PATROL Developer Console, enter the customizations that you identified in step 2, one by one.

To migrate customized PATROL Script Language 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, 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 that was shipped by BMC Software, 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 match existing keywords. Reapply your changes by using a PATROL Developer Console .
Warning

Note

If you have customized a PSL library that was compiled with an earlier version of the PSL compiler than the version that was provided with PATROL 3.2.09i, you must manually recompile the library by using a PATROL 3.5 or later compiler.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for Microsoft SQL Server 9.5