This entry is continued from Part-1 of 4. It is highly recommended that you check for errors and warnings in the log files at each step.This part walks you through the actual migration of Dmgr and commonDB. Migrate WebSphere Process Server V6.2 Network Deployment (ND) environment to WebSphere Process Server V7.0 ND.
MIGRATION STEPS (This blog will discuss steps 1 through 4 below:)
- Install WebSphere Process Server V7.0
- Migrate the deployment manager to WebSphere Process Server V7.0
- Upgrade the Common database schemas
- Start the migrated deployment manager
- Migrate other custom nodes one by one
- Migrate the cluster scoped profiles
- Synchronize the managed nodes
- Upgrade the Business Process Choreographer database schema
- Migrate the Business Space database schema
- Migrate the Business Space database data
1) Install WebSphere Process Server V7.0- refer to the Information Center topic below:
Installing WebSphere Process Server
2) Migrate the deployment manager to WebSphere Process Server V7.0 - Using BPM command-line utilities:
Create a copy of the configuration files in the source profile that will be migrated to the target profile using the BPMSnapshotSourceProfile command from the install_root/bin directory. The user-specified snapshot directory should not be located in the source or target product installation directories, so those directories can be removed later if necessary without impacting the configuration files in the snapshot directory.
Use the following syntax to copy a source profile named Dmgr01 located in the C:\wps62 directory to the C:\backup62 snapshot directory.
C:\wps7\bin>BPMSnapshotSourceProfile.bat -trace finest -traceFile C:\backupwps62\logs\DmgrSnapshotTrace.log C:\wps62 Dmgr01 C:\backupwps62
After the BPMSnapshotSourceProfile command is complete, the 3 log files below are generated in the C:\backupwps62\logs directory:
Use the following syntax to create a target profile named Dmgr01 under C:\wps7\profiles\Dmgr01 for the migration using the source profile named Dmgr01 copied to the C:\backupwps62 snapshot directory.
C:\wps7\bin>BPMCreateTargetProfile.bat -targetProfileName Dmgr01 -targetProfileDirectory C:\wps7\profiles\Dmgr01 C:\backupwps62 Dmgr01 After the BPMCreateTargetProfile command finishes, the log file will be generated under the C:\backupwps62 \logs directory snapshot_dir\logs).
Migrate the source profile to the target profile using the BPMMigrateProfile command. This command reads the configuration information from the snapshot directory specified by the BPMSnapshotSourceProfile command and migrates it to the target profile.
Use the following syntax to migrate the source profile named Dmgr01 copied into the C:\backupwps62 directory to the target profile named Dmgr01.
C:\wps7\bin>BPMMigrateProfile.bat -username wsadmin -password <*****> -targetProfileName Dmgr01 -scriptCompatibility true -trace fine -traceFile C:\backupwps62 \logs\DmgrMigrateProfileTrace.log C:\backupwps62 Dmgr01
After the BPMMigrateProfile command is complete, the following log files will get generated under C:\backupwps62\logs (snapshot_dir/logs) directory:
Use the following BPMMigrationStatus command to verify the current state of the migration:
3) Upgrade the Common database schema - commonDB requires just the upgrades of schema with no data migration involved.
Copy the Common database migration and upgrade scripts to the database system
On the target migration system, find the Common database migration and upgrade commands and scripts that are customized to your database type and copy them to your database system. The commands and scripts are located in the following directories: install_root/dbscripts/CommonDB/database_type. In our environment, it is the following: C:\wps7\dbscripts\CommonDB\DB2.
Upgrade the CommonDB by executing the migration scripts on the DB machine
On a Windows machine, you can run upgradeSchema.bat to upgrade the CommonDB.
Note: Backup the target deployment manager after Dmgr profile migration.
4) Start the target (migrated) deployment manager.
Use the following syntax:
See Part-3 of 4 which is a continuation of this blog and contains Steps 5 through Step 10 of the migration process.