Part 3 of 4: Migration
This entry is continued from Part 2 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 migration of custom nodes and upgrading the Business Process Choreographer (BPC) database.
- Edit the wsadmin.properties file in the WebSphere Process Server V7.x custom node to change the com.ibm.ws.scripting.host and com.ibm.ws.scripting.port parameters to point to the remote target IBM Business Process Manager Advanced V8.0 deployment manager that you created in step 18.
Take a backup of the C:\WPS70\profiles\Custom01\properties\wsadmin.properties file and then change the values for following parameters:
Note: host and port values from newly created IBM Business Process Manager Advanced V8.0 target deployment manager are set in the source custom node wsadmin.properties file for each federated node in the source environment.
- Run the syncNode command. For example:
C:\WPS70\profiles\Custom01\bin>syncNode vmwbil2w7d 8879 -username admin -password admin
Check C:\WPS70\profiles\Custom01\logs\syncNode.log file.
- If target IBM Business Process Manager Advanced V8.0 custom node is on a different system than the one hosting the newly created target V8.0 deployment manager then repeat steps 3, 14, and 15 from part 1 of 4 .
- Repeat steps 16 to 20 from part 2 of 4 for each target custom node.
Note: Change the command parameter values, as appropriate, for your custom node profiles.
Note: Take a back up of the deployment manager and custom node after completing step 27 in case if you need to restore the deployment manager or the custom node.
- Run the BPMGenerateUpgradeSchemaScripts command-line utility to generate SQL scripts for Business Process Choreographer database that is to be upgraded.
Open the c:\Dmgr_snapshot\DatabaseInfo.txt file and note the database and schema name for Business Process Choreographer database to be used for BPMGenerateUpgradeSchemaScripts command.
C:\BPM80\bin>BPMGenerateUpgradeSchemaScripts.bat BPEDB.BPEDB c:\Custom01
Note: BPEDB.BPEDB is the dabatase.Schemaname of Business Process Choreographer database for this exercise. Replace that value, as appropriate, for your environment.
Important note: Provide the right values for tablespaces when you are prompted by the command.
- Run the following commands to upgrade Business Process Choreographer database.
C:\>db2 connect to BPEDB user BPMUSER using password
C:\>db2 -tvf C:\Custom1\DB2\BPEDB.BPEDB\upgradeSchema_SchemaStatus.sql
C:\>db2 -tvf C:\Custom01\DB2\BPEDB.BPEDB\upgradeSchema7003.sql > C:\Custom01\DB2\BPEDB.BPEDB\sql1.log
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 versions than what is used in this exercise.
Important note: If you have not enabled the "Shared Work Items" feature that was introduced in WebSphere Process Server V7.0.0 Fix Pack 3, then run the upgradeSchema700.sql file instead of the upgradeSchema7003.sql file in the 4th command for this step.
If your source environment is WebSphere Process Server V7.0.0 Fix Pack 3, 4, or later minor versions, you will have two versions of upgrade schema scripts generated for the Business Process Choreographer database. If you enabled the "Shared Work Items" feature that was introduced in WebSphere Process Server V7.0.0 Fix Pack 3, you must remove those generated scripts with "700" in the file name before executing the upgradeSchema.bat or upgradeSchema.sh command. If that is not the case you must remove the script with "7003" in the file name.
Note: The BPMUSER that is used for connecting to the Business Process Choreographer database is required to have the necessary permissions as explained in the Databases topic within the information center.
Note: For Microsoft SQL Servers, there are two types of upgrade schema scripts that are generated for the Business Process Choreographer database: One is ugradeSchemaXXX.sql (where "XXX" is the source version) and the other is upgradeSchemaXXXUnicode.sql . The upgradeSchemaXXXUnicode.sql script is for a Microsoft SQL Server with Unicode support. You must remove the upgradeSchemaXXX.sql script before executing the upgradeSchema.bat or upgradeSchema.sh script if the Microsoft SQL Server in your environment is Unicode supported. If the Microsoft SQL Server in your environment is not Unicode supported, you must remove the upgradeSchemaXXXUnicode.sql script.
- Start the custom node. For Example:
- Migrate the cluster configuration for the clustered nodes. Migrate the cluster-scoped configuration using the BPMMigrateCluster command from the <target install root>/bin directory on the system that contains the deployment manager. For example:
C:\BPM80\bin>BPMMigrateCluster.bat C:\Dmgr_snapshot DE1.Messaging Dmgr01
After using the BPMMigrateCluster command, the following log files are generated under the C:\Dmgr_snapshot\logs directory:
BPMMigrateCluster.dmgrprofilename.clustername.timestamp.log / trace
Note: TheC:\Dmgr_snapshot directory is the deployment manager snapshot directory.
DE1.Messaging is the cluster name
Dmgr01 is the deployment manager profile name
- Repeat step 31 for each cluster ( Messaging, Support, AppTarget ) in your environment.
Note: Take a backup of the deployment manager and custom nodes.
- Run the syncNode command from each node to manually synchronize the nodes.