Migration Guide ( v6.2 to v7.0 ). Part-3 of 4, Migration
SSharath 2000004H00 Visits (5553)
Continued from Part-2 of 4. It is highly recommended that you check for errors and warnings in the log files at each step. This part explains the migration of nodes and clustered scope profiles, BPC db, and Business Space db.
MIGRATION STEPS (This blog will discuss steps 5 through 10 below:)
5) Migrate other nodes one by one - Follow steps 2a through 2d as described in Part-2 of 4 for each custom node.
6) Migrate the cluster scoped profiles
BPMMigrateCluster - The BPMMigrateCluster command migrates cluster scoped application and configuration information for the cluster specified by the cluster_name parameter copied from the deployment manager's profile located in the directory specified by the snapshot_directory and dmgr
Run BPMMigrateCluster command on the system that hosts the deployment manager for each cluster one by one. Use the following syntax to migrate the messaging / support / Application cluster.
Note: Use this command after all the nodes have been migrated.
After the execution of BPMMigrateCluster command, according to each cluster the following two log/trace files will be generated under the snapshot_dir/logs directory:
7) Synchronize the managed nodes - From each migrated node, execute syncNode command manually.
syncNode <deploymgr host> <deploymgr port>
Note: Make sure the node is stopped when executing the syncNode command.
8) Upgrading the Business Process Choreographer database schema
a) During migration, a database design file crea
Example - copy C:\w
b) Customize the database design file - Start the DB design tool to edit the DB configuration defined in the above properties file.
c) Answer all the questions, or press enter to accept the default values. In particular, make sure to select the migration scenario and the database name, the database schema qualifier, and tablespace names are correct.
d) Generate the upgrade scripts
Run the database design tool on the above modified DB design file to generate the upgrade scripts.
Note: If you do not provide the -d option to specify an output directory, the generated files will be written to a subdirectory of the current directory.
e) Copy the generated folder (e.g. DB2-
f) Execute the generated db scripts to upgrade the database schema on the database machine.
db2 connect to DBPEDB user db2admin using <pw>
db2 -tf upgr
9) Migrating the Business Space database schema
a) Copy the folder <dmg
b) On the DB machine, execute migrateSchema.bat under the above copied folder to migrate BusinessSpace database schema
10) Migrating the Business Space database data
a) Start one of the servers in a target cluster where Business Space is configured.
b) Log in to Business Space and verify that the Business Space database schema upgrade has completed successfully. If Business Space does not look updated, then clear the cache on your Web browser, restart the server, and restart Business Space.
c) Run the migrateBSpaceData script to migrate Business Space V6.2 to Business Space V7.0.
Execute the following on support cluster member node1:
host: support cluster member host
port: support cluster member SOAP
d) Migrate the widget catalog
On deployment manager machine, execute upda
e) Restart the whole migrated environment
FYI: Stay tuned for Part 4 of 4 on Post Migration Considerations.