Before following these steps, see Migrating from IBM Business Process Manager Standard V7.5 to 8.5 Part 1
Part 2 of 2:
Run the BPMExtractSourceInformation utility to take a snapshot of your previous environment so that you can apply the same changes to your new environment.
a. If you have modified the 100Custom.xml file for Process Server or Performance Data Warehouse, make sure that the 100Custom.xml files on the managed node are synchronized with the 100Custom.xml files on the deployment manager. If they are not synchronized, manually copy the 100Custom.xml files from the node profile to the deployment manager profile.
b. Run remote_migration_utility\bin\BPMExtractSourceInformation.bat -backupFolder snapshot_folder -propertiesFile migration_properties_file
BPMExtractSourceInformation.bat -backupFolder c:\snapshot -propertiesFile "C:\remote_migration_utility\util\migration\resources\migration.properties"
- The snapshot_folder variable is the directory where the extracted information is stored.
The migration_properties_file variable is the full path to the migration properties file in which you specified the configuration information for the source environment.
Shut down the source environment.
- Stop the clusters.
- Stop the nodes.
Stop the deployment manager.
Copy the snapshot zip file from source to the target computer and extract it there.
Back up the databases.
Generate the SQL scripts and configure the new database components. Drop the messaging engine tables if you want to reuse your previous messaging engine database.
Run the BPMGenerateUpdateSchemaScripts command from the target environment to generate the SQL scripts to update the schemas.
For example: BPM_home\bin\BPMGenerateUpgradeSchemaScripts.bat -propertiesFile "c:\BPM_HOME\util\migration\resources\migration.properties"
The c:\BPM_HOME\util\migration\resources\migration.properties value is the full path to the migration properties file in which you specified the configuration information for the target environment. Use the information from step 8 as a reference.
The SQL scripts are generated in the target_deployment_manager_profile\dbscripts\Upgrade directory, under the following subdirectories:
Initialize the new database components and run the create SQL scripts that you generated in the step 14.
Configure a new Business Space database if not already exists by running the scripts in the following order:
db2 connect to CMNDB USER username USING password
db2 -tvf profiles/DmgrProfile/dbscripts/Upgrade/de1/DB2/CMNDB.schema/createTablespace_BusinessSpace.sql
db2 -tvf profiles/DmgrProfile/dbscripts/Upgrade/de1/DB2/CMNDB.schema/createSchema_BusinessSpace.sql
db2 -tvf profiles/DmgrProfile/dbscripts/Upgrade/de1/DB2/CMNDB.schema/createTable_BusinessSpace.sql
db2 connect reset
Note: Create the messaging engine database if it not already created for the target environment. Drop the messaging engine tables if you want to reuse your previous messaging engine database.
Upgrade the databases.
Upgrade your existing schemas and data so that your databases work with the new version of IBM Business Process Manager V8.5.
Run the DBUpgrade command to modify your existing database schemas and data for use with IBM Business Process Manager V8.5. This command updates the following components:
- System Data toolkit
- Process Portal process application
- Hiring Sample tutorial process application
For example: c:\BPM_HOME\bin\DBUpgrade.bat -propertiesFile "c:\BPM_HOME\util\migration\resources\migration.properties" -backupFolder c:\snapshot
Note: Ensure that you have shut down the source environment before you you run this command
Start the target deployment environment:
- Start the deployment manager.
- Start the nodes.
Start the clusters
Import the migration snapshot from the source environment into the target environment
For example: BPM_home\bin\BPMMigrate.bat -backupFolder c:\snapshot -propertiesFile "c:\BPM_HOME\util\migration\resources\migration.properties"
Note: c:\BPM_HOME\util\migration\resources\migration.properties is the full path to the migration properties file in which you specified the configuration information for the target environment. Use the information from step 8 as a reference.
Moving your custom configuration to the target environment.
If you modified the 100Custom.xml file for the Process Center (Process Server) or Performance Data Warehouse, verify that it has been copied to the correct folder.
Restart the target environment:
- Stop the target environment.
- Stop the deployment manager and the nodes.
- Start the deployment manager and the nodes.
- Start the target environment