BMC Software, Inc., Confidential and Proprietary Information
Installing and Migrating PATROL for BEA WebLogic 2-35
After you have checked your customizations to the previous version of
PATROL for BEA WebLogic into the KMDS, use the following steps to
migrate your customizations to the new version of PATROL for BEA
WebLogic. For detailed instructions about migrating customizations
using the KMDS, see the PATROL Migration Tools User Guide.
Step 1 Use the Probe and Merge tools to identify, preserve, and merge
customizations from the prior version of PATROL for BEA WebLogic
into the newly installed version of PATROL for BEA WebLogic. See the
PATROL Migration Tools User Guide to run the Probe and Merge tools.
Step 2 When prompted during the merge phase of the migration, enter:
weblogic_2_2_00.map
Warning
Make sure that you use the merge map file that was shipped with the new
version of PATROL for BEA WebLogic. The default location is
PATROL_HOME\lib\migration\new\lib\kmmergemap.
Step 3 Use KMDS to merge.
Step 4 After you have completed the migration of your changes, load the new
version and save the configuration.
To Migrate Customizations Manually
If you do not want to use the KMDS to migrate customizations, use the
following steps to migrate your customizations manually:
Step 1 Move the old PATROL for BEA WebLogic to a new directory that is
different from
PATROL_HOME.
Step 2 Identify the customizations in PATROL for BEA WebLogic by
comparing the content of the text file of the KM in the current PATROL
for BEA WebLogic version with the content of the text file for the
customized KM that is saved in the PATROL Console cache backup
directory.
Step 3 Incorporate your customizations to the new PATROL for BEA WebLogic
by performing the following steps:
