BMC Software, Inc., Confidential and Proprietary Information
Installing and Migrating PATROL for BEA WebLogic 2-25
After you have finished this procedure, see “Migrate Your
Customizations” on page 2-33 for instructions about incorporating your
customizations into the new version. You should complete this process on
a limited number of machines in the test environment first, test the
merged KMs thoroughly, and then deploy them to your production
environment.
Note
To upgrade and preserve customizations, you must either migrate your
customizations manually or use the PATROL Migration Tools version 3.5
(no KMDS required), or have the latest version of KMDS installed as
well as any available patches.
Determine Whether You Can Migrate
Before migrating customizations, you must determine whether or not the
customizations to the previous version of PATROL for BEA WebLogic
that you have installed can be migrated to the new version of PATROL
for BEA WebLogic. See Table 2-4 to determine whether migration is
supported for your current version of PATROL for BEA WebLogic. If
migration is supported, choose one of the following installation
procedures to migrate your customizations:
• migrating customizations using the PATROL Migration Tools version
3.5 (page 2-26)
• migrating customizations using the PATROL Migration Tools version
3.4.11 and the PATROL KMDS(page 2-26)
• migrating customizations manually (page 2-28)
Table 2-4 Versions That You Can Migrate
Component Version
PATROL for BEA WebLogic 2.1.00, 2.1.01
PATROL for BEA WebLogic 1.3.00
PATROL for BEA WebLogic 1.2.00
PATROL for BEA WebLogic 1.1.02
