This blog is split into the following 3 parts to keep it simple and compact:
Part 2 of 3: Process Center migration
- Install the migration target product, IBM Business Process Manager Standard V8.0, with the required interim fixes. To obtain the interim fixes, see Installing the required fixes for the IBM Business Process Manager V8.0 products and IBM Business Monitor V8.0.
- Use the custom installation option as the default profile that is created using the Typical installation does not have the option to delay the database table creation process.
- Using the v7.5.x existing database during a typical installation will corrupt the database and make your environment unusable.
- Create a response file for stand-alone Process Center. For example:
dbHostName=<database host system>
Keep the following points in mind:
- The target profile name can be different from the source profile name.
- The hostName=vmwbil2w7b value represents the new target system name. This value can be the same system used for V7.5.x.
- The adminUserName=admin and adminPassword=admin vaues should be the same
administrator user name and password that is used in the source environment if you
are using the file user registry for WebSphere security.
- The dbName=CMNDB value is the
database name that is used for Business Space ( common database ) in V8.0 and
this is a new addition to other databases from V7.5.x.
- The dbHostName value should be pointing to the existing database that is used for V7.5.x.
- Ensure that the dbDelayConfig=true value is set to true to
generate scripts and not create the database during profile creation.
- Set the procSvrDbName=BPMDB and perfDWDbName=PERFDB values to the existing databases that are used for V7.5.x (Process Server and
Performance Data Warehouse) that you will be upgrading and using with
IBM Business Process Manager V8.
- Run the manageprofiles command from the E:\IBM\bpm80\bin directory. For example:
E:\IBM\bpm80\bin>manageprofiles -response E:\IBM\bpm80\BPM\samples\manageprofiles\PCStd_StandAlone_DB2.response
- Check the E:\IBM\bpm80\logs\manageprofiles\<Profile_Name>_create.log file for INSTCONFSUCCESS. If you see INSTCONFFAILED, search for SEVERE or error.
- Complete the database activities for business space database. The database user requires administrator privileges for some of the SQL commands.
(a) Copy the createDatabase.sql and createTable_BusinessSpace.sql files from E:\IBM\bpm80\profiles\<profile name>\dbscripts\BusinessSpace\<node name_Server name>\DB2\CMNDB\ to the database host system.
(c) db2 ATTACH to DB2 user db2admin using <password>
Note: DB2 is the default instance name, change if your database instance name is different
(d) db2 -tvf E:\IBM\bpm80\profiles\PC_BPM80\dbscripts\BusinessSpace\PC_BPM80_Node01_ProcCtrServer\DB2\CMNDB\createDatabase.sql
Note: db2admin is the user name that is used for Process Server and Performance Data Warehouse data sources in this exercise. Change them as appropriate to your environment. Note that the createDatabase.sql script grants administrator privilege to the user that is used for business space ( commondb) data source.
(e) db2 connect to CMNDB user db2admin using <password>
(f) db2 -tvf E:\IBM\bpm80\profiles\<profile name>\dbscripts\BusinessSpace\PC_BPM80_Node01_ProcCtrServer\DB2\CMNDB\createTable_BusinessSpace.sql
- Customize the new environment to match the customizations made to the previous (source) environment. Refer to the Migrating to IBM BPM V8.0 topic in the information center for more details.
(a) Apply the changes that you made to the configuration settings in the files, such as 100Custom.xml, 99Local.xml, and 00Static.xml
(b) If you are using a file user registry for WebSphere security, then migrate the users as described in the Applying customizations topic in the information center.
- Run the upgrade command. The database upgrade tool must access the metadata tables and views of the database, the user who is assigned to access the process database, and the Performance Data Warehouse database. The SIB database must have DBA privileges. Ask your database administrator to grant the necessary privilege temporarily and then remove it after the database is upgraded successfully. The upgrade utility is located in <BPM-install-root>\BPM\Lombardi\tools\upgrade\upgrade_7x directory. Here's an example of the command:
E:\IBM\bpm80\BPM\Lombardi\tools\upgrade\upgrade_7x>upgrade_7x.bat -profileName PC_BPM80
Note: The -profileName PC_BPM80 parameter value is the stand-alone process center profile name in this exercise.
Check the upgrade logs for "All upgrade steps have been completed successfully." The upgrade log files are located at: E:\IBM\bpm80\profiles\PC_BPM80\logs\upgrade_7x_<time_stamp>.log
If Create tables option is not enabled for the messaging engine data sources, then generate the scripts and create the tables manually by running the scripts against the Process server and Performance Data Warehouse databases respectively.
- Generate the SQL scripts for messaging engines by running the sibDDLGenerator command from the E:\IBM\bpm80\bin directory.
E:\IBM\bpm80\bin>sibDDLGenerator -system db2 -platform windows -schema MEDPS00 -user BPMUSER > E:\IBM\bpm80\profiles\ProcCtr\dbscripts\SIB\ProcessServer_ME.sql
E:\IBM\bpm80\bin>sibDDLGenerator -system db2 -platform windows -schema MEDPE00 -user BPMUSER > E:\IBM\bpm80\profiles\ProcCtr\dbscripts\SIB\PerformanceDW_ME.sql
Note: The MEDPS00 and MEDPE00 schema names that are
used for ProcessServer and PerformanceDW respectively are the default names. These names should not be changed unless you use a DbDesignGenerator command to
generate dbDesign file and plan to use it while creating the profile.
Output files are created in the E:\IBM\bpm80\profiles\ProcCtr\dbscripts\SIB directory as redirected in the previous command.
Note: This step is required only if the messaging engine tables are set to not be created during the server start up process.
- Start the Process Center Server and check the SystemOut.log files for any errors.
- Update the existing dependencies of the System Data toolkit by opening the Designer view in IBM Process Designer and following these steps for each process application and toolkit:
(a) Update the System Data toolkit from the process application. Open your process application. Under Toolkits, right-click System Data toolkit and select Change Version of dependency.
(b) Update the System Data toolkit from the custom toolkit. Open the custom toolkit in Process Designer. Under Toolkits, right-click System Data toolkit and select Change Version of dependency.
Continue to Part 3