Whether you are upgrading and migrating customizations or simply upgrading, you must first back up the current installation. If the .kml file or any of the .km files for the new version of PATROL for Exchange Servers has a different file name from the previous version, you must remove those files from the list of KMs that are preloaded on the PATROL Agent.
If you have a previous version of PATROL for Exchange Servers installed on the target computer, you have two options for upgrading to the new version of PATROL for Exchange Servers.
Only customizations to KMs must be migrated.
Whether you choose to save and migrate your KM customizations or not, the customizations you have made to
are preserved and incorporated into the new version automatically.
Customized KMs and PSL files are also stored in the cache but they are NOT automatically preserved and incorporated.
Before migrating customizations, you must determine whether or not your customizations to PATROL for Exchange Servers can be migrated to the new version of PATROL for Exchange Servers. See the following table to determine whether migration is supported for your current version of PATROL for Exchange Servers. If migration is supported, select one of the following installation procedures to migrate your customizations:
PATROL for Exchange Servers version 5.3.00 does not support a migration path by using a merge map file. PATROL for Exchange Servers supports upgrading by preserving previously configured Roundtrip sessions. Use the PATROL Configuration Manager to deploy custom threshold settings.
Versions that you can migrate
PATROL for Exchange 2003 Servers
PATROL for Exchange 2007 Servers
PATROL for Exchange 2007 Servers
Use the following table to help you choose an upgrade procedure.
Choosing an upgrade procedure
Use this procedure
If you have this situation
Upgrading Without Saving KM Customizations
Upgrading and Preserving KM Customizations
Made customizations to the KM files in your previously installed version of PATROL for Exchange Servers and want to save those customizations and migrate them to the new version of PATROL for Exchange Servers
During the installation process, the PATROL Installation Utility records where it installs PATROL components in environment variables. To function properly, various components of the PATROL product, such as the PATROL Configuration Manager, require the information stored in these variables. Two important variables are
Throughout this book, all references to PATROL_HOME represent %PATROL_HOME% in a Windows environment and $PATROL_HOME in a UNIX environment. All references to PATROL_CACHE represent %PATROL_CACHE% in a Windows environment and $HOME/patrol in a UNIX environment.
If you do not specify a location for the PATROL installation, the installer uses the following preprogrammed default locations and stores these locations in environment variables.
Default values for PATROL location variables
C:\Program Files\BMC Software\PATROL3 (Windows)
To view the value of PATROL_HOME, PATROL_CACHE, and other environment variables, perform the appropriate procedure for your operating system or shell:
Microsoft Windows 2000 Microsoft Windows 2003
Using the Control Panel tools
Note: The System application displays PATROL_CACHE only if it is set to a value other than its default value.
Using the PATROL Environment Probe
Bourne and Korn
At the shell command prompt, type export and press ENTER. The shell displays a list of environment variables and their values.
If PATROL_HOME is not set, run
At the shell command prompt, type setenv and press ENTER. The shell displays a list of environment variables and their values.
If PATROL_HOME is not set, run
If you do not want to save any customizations of .km files, PSL code, alarm thresholds, or events, you can simply install the new version of PATROL for Exchange Servers over your previous version after moving or deleting PATROL for Exchange Servers files from the PATROL_CACHE and PATROL_HOME directories. See First-time Microsoft Exchange Servers installation for instructions.
Customizations applied using PATROL Configuration Manager or operator overrides are automatically saved in the agent configuration database. They will take effect automatically unless the parameter name or application name has changed. In either of those cases, you must reapply the customizations.
If you want to upgrade to the new version of PATROL for Exchange Servers, and you want to preserve any customizations you have made to the .km files in the previous version of PATROL for Exchange Servers, you must either migrate your customizations manually or use the PATROL Configuration Manager.
Customizations made to PATROL for Exchange Servers can include changes to the parameter alarm ranges, states, or other parameter properties.
Migration of .km files with the PATROL Configuration Manager is automated, with the following exceptions:
After you install the new version of PATROL for Exchange Servers, use the PATROL Configuration Manager rules and rulesets to migrate your customizations into PATROL for Exchange Servers version 5.3.00.
Back up your customizations so that you can restore the current installation if you want to roll back your upgrade.
Remove the following obsolete or changed .kmfiles from the list of preloaded KMs on each PATROL Agent:
Obsolete Knowledge Module files
PATROL for Exchange Servers version
Obsolete .km files
Obsolete .kml files
Perform a full backup of the directories where PATROL files are typically stored. These directories are listed in the following table:
Executables and data
Executables & Data
PATROL_HOME for agent and console installation directories on Windows
PATROL_HOME/.. for console installation directories on UNIX
PATROL_CACHE for the console working cache on Windows
PATROL_CACHE for the console working cache on UNIX
If you have only a few customizations, you might find manual migration easier than migrating using the PATROL Configuration Manager. 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.
You must move the current PATROL for Exchange Servers files from the PATROL_CACHE directory for the console. If you do not, old product files in PATROL_CACHE are loaded instead of the newly installed files from PATROL_HOME.
Copy the PATROL for Exchange Servers files with the following naming patterns to a directory outside the PATROL installation and delete them from PATROL_CACHE\knowledge and PATROL_CACHE\psl:
Customizations made to PATROL Script Language (PSL) code are not automatically migrated. These customizations might be embedded in .km files or stored in separate .psl files. Migrate these customizations manually, using the following guidelines:
If you have a customized 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 the PATROL 3.5 compiler.
Use the AS_CHANGESPRING KM, a component of the PATROL Configuration Manager, to migrate customizations to PATROL for Exchange Servers. The AS_CHANGESPRING KM identifies all of your customizations and creates a RuleSet equivalent to these customizations. Use this RuleSet to apply the customizations to the new version of PATROL for Exchange Servers.
For more information about creating and using RuleSets, see the PATROL Configuration Manager User Guide.