Part 4 of 4: Migration
This entry is continued from Part 3 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 business space data and configuring the additional features for IBM Business Process Manager Advanced V8.0.
- Copy the preMigrateBusinessSpace700.sql script from C:\BPM80\profiles\Dmgr01\dbscripts\BusinessSpace\DE1.Support\DB2\WPRCSDB to the database host machine and run the following commands:
C:\>db2 connect to WPRCSDB user BPMUSER using password
C:\>db2 -tvf C:\bus_space_DBScript\preMigrateBusinessSpace700.sql
Note: This script might need to be modified if the default values do not match your environment.
Note: The script is located in the following directory: <Dmgr profile>/dbscripts/BusinessSpace/cluster_name/DBType/<database name>
Note: BPMUSER might need permissions to create tablespace, schema, table, index and alter table, and drop table as explained in the Databases topic within the information center.
- Run the upgradeBSpaceSchema command from the <install_root>/BusinessSpace/scripts directory. For example:
C:\BPM80\BusinessSpace\scripts>upgradeBSpaceSchema.bat -profileName Dmgr01 -clusterName DE1.Support
After running the upgradeBSpaceSchema command, the following log/trc files are created in the C:\BPM80\profiles\Dmgr01\logs\ directory:
Note: The -clusterName parameter value is the support cluster and the -profileName parameter value should be the deployment manager profile.
- Migrate the Business Space schema. Copy the migrateBusinessSpaceSchema700.sql file from <the Dmgr profile>/dbscripts/BusinessSpace/<cluster name>/<DBType>/<database name> directory to the database host and run the following command:
C:\>db2 -tvf C:\wps_apps\migration\bus_space\migrateBusinessSpaceSchema700.sql
Note: The BPMUSER that is used for connecting to the business space database is required to have necessary permissions as explained in the Databases topic in the information center.
- To prevent timeout errors, modify the com.ibm.SOAP.requestTimeout property by editing the soap.client.props file, which is located in the properties subdirectory of the profile_root directory. Change the com.ibm.SOAP.requestTimeout value from 180 to a larger value, such as 1800. Set the com.ibm.SOAP.requestTimeout=1800 property and value in the <profile root>/properties/soap.client.props file to avoid possible connection timeout issue.
- Sometimes you might run into transaction time out errors, depending upon the network and database speed. You might need to change the transaction time out values on all servers. In the Administrative Console, click Servers > Server Types > WebSphere application servers > server_name > Container Services > Transaction Service and change the values for the Total transaction lifetime timeout and Maximum transaction timeout to 800
Note: Apply these changes only if they are required for your environment.
- Start the messaging cluster.
- Start the support cluster.
- Migrate the business space data. On the node for which the target server was started, run the migrateBSpaceData script using the -dbcopy option to copy the business space data from version 7.0.x to 8.0. For example:
C:\BPM80\BusinessSpace\scripts>migrateBSpaceData -host vmwbil2w7d -port 8882 -user admin -password admin -dbcopy
After using the migrateBSpaceData command, the following log/trc files are created in C:\BPM80\logs directory:
Note: The -host parameter is the business space server host name, the -port parameter refers to the SOAP port number of the business space server in the cluster.
- Stop each of the migration target servers in the support cluster. For example:
C:\BPM80\profiles\Custom01\bin>stopServer.bat <server name> -username <user name> -password <password>
- Modify the oobLoadedStatus.properties file to confirm that the following three values are true. Check all of your nodes for the oobLoadedStatus.properties file (this file will exist on only one of the nodes), and make all modifications. The oobLoadedStatus.properties file is located at <install root>\profiles\<Custom profile name>\BusinessSpace\<cluster name>\mm.runtime.prof\public\ directory.
Set the following values to true:
- Start each server in the support cluster.
- Run the migrateBSpaceData script using the -dbupgrade option to upgrade the business space data from Version 7.0.x to 8.0. For example:
C:\BPM80\BusinessSpace\scripts>migrateBSpaceData -host vmwbil2w7d.eng1 -port 8882 -user admin -password admin -dbupgrade
Note: The -host parameter is the business space server host name and the -port parameter refers to the SOAP port number of the Business Space server in the cluster.
- Remove the obsolete database tables for business space. For example:
Copy postMigrateBusinessSpace700.sql from C:\BPM80\profiles\Dmgr01\dbscripts\BusinessSpace\DE1.Support\DB2\WPRCSDB to database host system
C:\>db2 connect to WPRCSDB user BPMUSER using password
C:\>db2 -tvf C:\bus_space_DBScript\postMigrateBusinessSpace700.sql
Note: The postMigrateBusinessSpace700.sql file is located in the <Dmgr profile>/dbscripts/BusinessSpace/<Cluster name>/<DBType>/<database name>directory.
- Create the database design file by using the database design tool DBDesignGenerator, which are located in the <install root>/util/dbUtils directory in target Business Process Manager Advanced Version 8.0 system.
Important: Select appropriately to generate scripts for the process server, performance data warehouse databases and process server, and performance data warehouse messaging engines.
For more information, see Configuring the Process Server and Performance Data Warehouse using a command the information center.
- Copy the generated database scripts to database host system and run the scripts to create the required databases and database objects. Refer to step 15 in Creating a Remote Messaging, Remote Support and Web pattern ( RMRSW)-based Network Deployment environment for IBM Business Process Manager Standard Version 8.0 (Part 3) for reference. Apply only the required steps and change it appropriately for your environment.
- Configure the Process Server, Performance Data Warehouse, and Process Portal by running the BPMConfigureProcessServer comman. For example:
C:\BPM80\profiles\Dmgr01\bin>BPMConfigureProcessServer.bat -psClusterName DE1.AppTarget -perfDWClusterName DE1.Support -processPortalClusterName DE1.Support -dbDesign C:\BPM80\util\dbUtils\bpm.standard.nd.dbDesign
After you run the BPMConfigureProcessServer command, the following log/trc files are created in C:\BPM80\profiles\Dmgr01\logs\ directory:
C:\BPM80\profiles\Dmgr01\logs\BPMConfigureProcessServer.<Dmgr profile name>.<time stamp>.log file
Note: With 3 Clusters: Process Server deployed to application cluster, Process Portal and Performance Data Warehouse deployed to support cluster, all the bus members deployed to messaging engine cluster.
Note: -psClusterName DE1.AppTarget refers to the application target, -perfDWClusterName DE1.Support and -processPortalClusterName DE1.Support refers to Support cluster, -dbDesign refers to the DBDesign file that was created in step 47.
- Run the bootstrapProcessServerData script. For example:
C:\BPM80\profiles\Dmgr01\bin>bootstrapProcessServerData -dbJDBCClasspath C:\BPM80\jdbcdrivers\DB2 -clusterName DE1.AppTarget
After running the bootstrapProcessServerDat command, the following log/trc files are generated in the C:\BPM80\profiles\Dmgr01\logs directory:
bootstrapProcesServerData.DE1.<AppTarget cluster Name>.<Time stamp>.log
Note: -clusterName DE1.AppTarget refers to the application target cluster.
- Configure a routing server for the IBM Business Process Manager Process Portal as described in the Configuring a routing server for IBM Business Process Manager (BPM) Process Portal in a three or four cluster topology technote.
- Restart your environment.
- Remove the Compatibility Mode. For example: