This blog entry is an addendum to the detailed migration procedure from WebSphere Process Server V7.0.0 to IBM Business Process Manager Advanced V8.0, which was described by Sharath Srinivas here. The document was co-authored by Werner Tod and Matthias Benda, who are IBM consultants for the IBM Business Process Management family of products.
This blog describes the necessary extra steps for the migration of a WebSphere Process Server V7 environment with WebSphere Business Monitor V7 that is implemented in the same WebSphere cell.
To ensure the proper sequence of migration steps, we reference the migration step numbers from Sharath’s migration procedure. In case we need to add activities to a migration step, we add an “A” to the original step number. For example, “1A”.
For details regarding the individual migration steps, see the corresponding information in the IBM Business Process Manager and IBM Business Monitor V 8.0.1 product documentation.
2A. In addition to IBM Business Process Manager V8.0.1 Fix Pack 2, also install IBM Business Monitor 8.0.1 Fix Pack 2 on the target systems.
2A.1 Select to automatically deploy Cognos BI service, which used by IBM Business Monitor instead of the previously used AlphaBlox, during the profile migration process or manually by running the configuration wizard from the administrative console. To deploy Cognos BI automatically during the profile migration process, you must set some parameters for deploying the Cognos BI service. Even if your source version is 7.5.x, you must set the parameters because the Cognos BI service configuration cannot be migrated to the target environment without setting the parameters.
Complete the following steps:
(a) From the install_dir/scripts.wmb/migration/ directory, run the CognosConfig script.
(b) From the command line, set the following parameters to appropriate values: Cognos database, Cognos database username, Cognos database password, Admin user name, Admin password, Cluster/Server/Node.
(c) Manually publish the cube after completing the product migration:
1. Open the Admin Console at Applications > Monitor Models.
2. Select the version of a monitor model under Version properties.
3. Click Manage Cognos cubes.
4. Select the monitor model version and click Publish
Before creating the snapshot of the source profile, you have to migrate the WebSphere adapter configuration (if you use additional adapters) and copy the third-party libraries (if you use any in your environment). The adapter migration is described in detail in the IBM Business Process Manager and IBM Business Monitor product documentation. Make sure that your third-party libraries are compatible with the target version of IBM Business Process Manager and that they are copied to the same location as in the source environment.
In some cases, the old host names still show within URLs in the target profile. You have to replace those occurrences in the target environment before you can continue!
Steps 21A and 22A:
The database schema upgrade also has to be applied to the Monitor database. Create and run the appropriate scripts in addition to those for the Common database and the BPC database.
After upgrading the schema of the Monitor database, you also have to migrate the existing Monitor data:
Run the DataMigration script to migrate the database: 801monitor_root/scripts.wbm/migration/DataMigration/DataMigration.sh
Run the DataMigration script using the following parameters:
DataMigration.sh -dbType database_type -dbName database_name -dbSchema database_schema_name -host database_host_name -port database_port -dbUser database_user_name -dbPassword database_password -dbDriverType jdbc_driver_type
database_type is the type of database. The value must be one of the following values:
database_name is the name of the IBM Business Monitor database (by default, MONITOR)
database_schema_name is the schema name of the IBM Business Monitor database (by default, MONITOR)
database_host_name is the fully qualified host name or IP address of the node where the IBM Business Monitor database is installed
database_port is the database port
database_user_name is a user with access to the IBM Business Monitor database
database_password is the password for the user
jdbc_driver_type is the JDBC driver type that is used to connect to the IBM Business Monitor database. This parameter is required only when the database type is DB2ZOS. The value must be 2 if the database is local and 4 otherwise.
If you chose to deploy the IBM Cognos BI service automatically during profile migration, you must create the database that IBM Cognos BI uses for the content store. If the database that the IBM Cognos BI service uses for the content store is a remote database, ensure that a local database client is installed on the Cognos server and that the MONITOR database is cataloged. The cataloged database name must match the database name that is configured in the WebSphere data source for the MONITOR database.
To create the database that IBM Cognos BI uses for the content store, complete the following steps:
From the IBM Business Monitor V8.0.1 monitor_root/dbscripts/Cognos/DB2/ directory, open the createDatabase.sql script in a text editor and change the database name.
Replace the values for the following variables with the values for your environment:
@COG_DB_NAME@ - Required for SQL Server and DB2 on z/OS
@COG_DB_PASSWORD@ - Required for SQL Server and Oracle
@COG_DB_USER@ - Required for SQL Server and DB2
@STORGRP@ - Required only for DB2 on z/OS
@TSDIR@ - Required only for Oracle
@SCHEMA@ - Required only for Oracle
Save your changes and close the file. Important: If you are using a remote database and prefer not to run the scripts on the installation program of the database server, you must copy the scripts to the database server before continuing.
From the command line, run the script using the following command for your database software:
db2 -tf createDatabase.sql
Note: If you migrated from V7.5.x and the IBM Cognos BI service was deployed in the earlier environment, you can reuse the existing database instead of creating one.
Steps 25A, 26A and 27A:
Go through all these steps in order to also migrate the WebSphere Business Monitor profile to the target IBM Business Monitor profile. Remember to include steps 16A and 20A!
Before migrating the business space, it is a good practice or even necessary to complete the steps to implement the additional configuration for Business Process Choreographer. These steps are documented in the IBM Business Process Manager product documentation as part of the post-migration activities. However, they should already be implemented at this stage.
We welcome your feedback! Share your comments below.
interior glass stair steps Mar-2013 (modified) credit: (cc) Some rights reserved by Mrodaikusek