Part 2 of 4: Migration
This entry is continued from Part 1 of 4. See the other parts of this blog at the following locations:
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 deployment manager and the commonDB.
- Create a snapshot of the source profile. Run the BPMSnapshotSourceProfile command from the C:\WPS70\migration80\util\bin directory where remoteMigrationUtilities.zip is extracted in step 15. For example:
C:\WPS70\migration80\util\bin>BPMSnapshotSourceProfile.bat -remoteMigration true "C:\WPS70" Dmgr01 C:\Dmgr_snapshot
After the BPMSnapshotSourceProfile command is complete, the following log files are generated in the C:\Dmgr_snapshot\logs directory:
WASPreUpgrade.profilename.timestamp.log / trace
BPMSnapshotSourceProfile.profilename.timestamp.log / trace
Check the C:\Dmgr_snapshot\logs\BPMSnapshotSourceProfile.Dmgr01.timestamp.log file for the "CWMCO0823I: The BPMSnapshotSourceProfile command finished successfully" message.
Note: The snapshot directory for this exercise is C:\Dmgr_snapshot. Change it, as appropriate, for your environment. This directory should not be located in the source or target product installation directories.
Note: The -remoteMigration parameter in the command indicates that
the target profile will not be created on the same machine.
- Copy the source snapshot directory (C:\Dmgr_snapshot) from step 16 to the same directory on the remote target system. For example:
C:\>robocopy C:\Dmgr_snapshot \\ <remote target IP>\c$\Dmgr_snapshot /E
Note: You can use robocopy or alternative tools on Windows operating systems as it helps to avoid running into paths that are too long errors.
Note: Now, you have the C:\Dmgr_snapshot directory on the target system.
- Create the target profile. For example:
C:\BPM80\bin>BPMCreateTargetProfile.bat -remoteMigration true c:\Dmgr_snapshot Dmgr01
After the BPMCreateTargetProfile command finishes, the following log files are generated under the C:\Dmgr_snapshot\logs directory:
Check the C:\Dmgr_snapshot\logs\BPMCreateTargetProfile.profilename.timestamp.log file for the "CWMCO0838I: The profile was created or augmented successfully" message.
Note: This profile will not be ready for use until the BPMMigrateProfile command is used to migrate the source profile to the new target profile.
- Migrate the source profile to the target profile. For example:
C:\BPM80\bin>BPMMigrateProfile.bat -username admin -password admin c:\Dmgr_snapshot Dmgr01
After the BPMMigrateProfile command is complete, the following log files are generated under the C:\Dmgr_snapshot\logs directory:
BPMMigrateProfile.profilename.timestamp.log / trace
WASPostUpgrade.profilename.timestamp.log / trace
BPMProfileUpgrade.profilename.timestamp.log / trace
Check the C:\Dmgr_snapshot\logs\BPMMigrateProfile.profilename.timestamp.log file for the "CWMCO0822I: The BPMMigrateProfile command finished successfully" message.
- Check the migration status by using the BPMMigrationStatus command to verify the current state of the migration. For example:
Note: Scan the file system under the profile directory for occurrences of the old host name value. Analyze the configuration where the old host name is still being used and replace it with the new host name unless the old host name is needed, such as if the database is still present on the old host name machine.
- Run the BPMGenerateUpgradeSchemaScripts command-line utility to generate SQL scripts for each database that you are going to upgrade. Open the c:\Dmgr_snapshot\DatabaseInfo.txt file and note the database and schema name for CommonDB to be used for BPMGenerateUpgradeSchemaScripts command.
C:\BPM80\bin>BPMGenerateUpgradeSchemaScripts WPRCSDB.WPRCSDB C:\Dmgr_snapshot
After the BPMGenerateUpgradeSchemaScripts command, database scripts are generated in the C:\Dmgr_snapshot\<DB Type>\<Database name.Schema Name> directory.
Note: WPRCSDB.WPRCSDB is the dabatase.Schemaname for this exercise. Replace that value, as appropriate, for your environment.
Note: The DatabaseInfo.txt file in the snapshot_directory lists the
deployment targets with the corresponding component mapping to a
database schema. The values are defined as name-value pairs with values in the form of DatabaseName.SchemaName.
- Copy the generated database scripts onto the database host system and run the following commands:
C:\>db2 connect to WPRCSDB user <WPS commonDB user> using password
C:\>db2 -tvf C:\DBScript\DB2\WPRCSDB.WPRCSDB\upgradeSchema_SchemaStatus.sql
Note: The WebSphere Process Server commonDB user needs to have the create table privilege. Otherwise, the database administrator needs to run this SQL script and grant permissions to the WebSphere Process Server commonDB user on the table that is created.
Note: The upgradeSchema700_DirectDeploy.sql is not required for IBM Business Process Manager Advanced V8.0.
Important note: Alternatively, you can run the SQL scripts using the upgradeSchema.bat | sh file that was generated along with the SQL scripts. The upgradeSchema.bat | sh file is recommended if you are at a different source and/or target version than what is used in this exercise. The number of scripts to be run and their names might change for a different version. Refer to the information center for details on your specific version.
- Start the target (migrated) deployment manager.
Note: Back up the new deployment manager in case you need to rollback and restore from a custom node failure.
Continue to Part 3