Upgrading and preserving KM customizations

Use the appropriate task in this section if you want to upgrade to the later version of BMC PATROL for Remedy AR Server and you want to preserve any customizations you have made to the .km files in your current version of BMC PATROL for Remedy AR Server. 

You must first migrate your customizations from your current version of BMC PATROL for Remedy AR Server to the later version, and then install the result into your environment. You must complete this process on a limited number of computers in the test environment first, test the merged KMs thoroughly, and then deploy them to your production environment.

Before you begin

• If you plan to migrate your customizations, determine whether you can migrate from a earlier version of BMC PATROL for Remedy AR Server. 
• Uninstall the current installation.
• Backup the Agent configuration file 
• Ensure PATROL_HOME/arskm directory is empty.

Determining whether you can migrate KM customizations

Before migrating customizations, you must determine whether your customizations to BMC PATROL for Remedy AR Server can be migrated to the later version of BMC PATROL for Remedy AR Server. If migration is supported, select the following installation procedure to migrate your customizations:

• Migrating customizations with the PATROL Configuration Manager

For more information, see Migrating your KM customization.

Backup the Agent configuration file

Whether you are upgrading and migrating customizations or simply upgrading, you must first back up the Agent configuration file. If the .kml file or any of the .km files for the later version of BMC PATROL for Remedy AR Server has a different file name from the current version, you must remove those files from the list of KMs that are preloaded on the PATROL Agent.

To back up the Agent configuration file

Back up your customizations so that you can restore the current installation if you want to roll back your upgrade.

1. Shut down any PATROL Agents, consoles, and related services that are currently running.
2. Ensure that no one is accessing any PATROL files or directories.
3. Perform a full backup of the directories where PATROL files are typically stored. These directories are listed in the following tables:

Removing files from PATROL_HOME/arskm  and PATROL_CACHE directories 

Before you install, you must remove the current BMC PATROL for Remedy AR Server files from the PATROL_HOME/arskm  and PATROL_CACHE directories for the console. If you do not, old product files in PATROL_CACHE are loaded instead of the newly installed files from PATROL_HOME. You might want to create a backup copy of the files elsewhere on your system before deleting the files.

Determining the location of PATROL

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 migration tools, require the information stored in these variables. Two important variables are PATROL_HOME and PATROL_CACHE. 

Throughout this section, all references to PATROL_HOME represent %PATROL_HOME% if you are using Windows and $PATROL_HOME if you are using UNIX. All references to PATROL_CACHE represent %PATROL_CACHE% if you are using Windows and $HOME/patrol if you are using UNIX.

Default values for PATROL location variables

If you do not specify a location for the PATROL installation, the installer uses the following default locations and stores these locations in environment variables: 

Default values for PATROL location variables 

Viewing environment variables set by PATROL

To view the value of PATROL_HOME, PATROL_CACHE and other environment variables, perform the appropriate procedure for your operating system: