Use the upgradeProcessData command to modify your existing database schemas and data for use with IBM® Business Process Manager V8.0.1.
If you are migrating from Teamworks® 7.0.0 or 7.0.1, this includes converting encrypted passwords to work with the encryption algorithm used by IBM BPM V8.0.1. Encrypted passwords may be stored in the database for users defined through the internal security provider, for secure web service integrations, or for Microsoft SharePoint integrations.
In addition, the upgradeProcessData command updates the following items to IBM BPM V8.0.1:
The following table lists any steps you should take before performing the database upgrade.
Current® version of IBM Business Process Manager Standard, Teamworks, or WebSphere® Lombardi Edition | File system where IBM BPM 8.0.1 is to be installed | Steps to take |
---|---|---|
|
Same file system as the existing Teamworks or WebSphere Lombardi Edition installation | In the install_root/BPM/Lombardi/tools/upgrade/upgradeProcessData directory,
modify the upgrade.properties file to set the value
of the previous.lombardi.install.dir property to
be your current installation directory. Note: If this property is missing
or not valid, the upgradeProcessData command is
unable to migrate encrypted passwords, but can still perform other
upgrade processing.
|
|
Different file system from the existing Teamworks installation | Copy utility.jar from [Teamworks_home]/process-center/lib or [Teamworks_home]/process-server/lib in the older installation to install_root/BPM/Lombardi/process-center/lib on the file system of the new installation. In the install_root/BPM/Lombardi/tools/upgrade/upgradeProcessData directory, modify the upgrade.properties file to set the value of the previous.lombardi.install.dir to [install_dir]. |
|
Different file system from the existing WebSphere Lombardi Edition installation | If [Lombardi_home_710]/AppServer/lib/ext/jcrypt.jar or [Lombardi_home_720]/AppServer/lib/ext/jcrypt.jar is present in your installation, copy it to install_root/AppServer/lib/ext |
|
The same file system as the existing installation or a different file system | No additional steps are required. |
|
The same file system as the existing installation or a different file system | No additional steps are required. |
To perform the database upgrade:
Review the script, and, if necessary, edit the file to replace the following symbolic variables with the actual values for the schema name, database name, storage group, and buffer pool for large objects and tables: @SCHEMA@, @DB_NAME@, @STOGRP@, @BPLOB4K@, @BPTABLE4K@, and @BPTABLE8K@.
Locate the two CREATE PROCEDURE statements in the upgradeSchema750_ProcessServer.sql or upgradeSchema751_ProcessServer.sql script, and cut and paste these statements into a new text file with a .sql extension. In this new file, also include the DB2 --#SET TERMINATOR @ control statement to set the SQL terminator to the @ character, as required for stored procedures. Save your amendments to the .sql scripts.
Connect to the DB2 for z/OS database, and run the upgradeSchema750_ProcessServer.sql or upgradeSchema751_ProcessServer.sql script against the database by using your preferred tool. Then run the newly-created .sql script to create the stored procedures.
Review the script, and, if necessary, edit the file to replace the following symbolic variables with the actual values for the schema name, database name, storage group, and buffer pool for large objects and tables: @SCHEMA@, @DB_NAME@, @STOGRP@, @BPLOB4K@, @BPTABLE4K@, and @BPTABLE8K@. Then connect to the DB2 for z/OS database, and run the script against the database by using your preferred tool.
database.is.db2zos=true
Operating system | Command |
---|---|
Windows | upgradeProcessData.bat |
Unix | ./upgradeProcessData.sh |
The following parameters are available for use with the upgradeProcessData command:
Parameter | Description |
---|---|
-profileName | This parameter is optional and should be used if you want to run the upgrade against a profile that is different from the default profile for your environment. Specify the name of the deployment manager profile that you want to use. |
-nodeName (Required in network deployment environments) | This parameter is required for network deployment environments. The upgrade command fails if you do not specify this parameter and the -serverName parameter in network deployment environments. Specify the node name of an application cluster member in your network deployment environment, which must not be running. |
-serverName (Required in network deployment environments) | This parameter is required for network deployment environments. The upgrade command fails if you do not specify this parameter and the -nodeName parameter in network deployment environments. Specify the server name of an application cluster member in your network deployment environment, which must not be running. |
-perfNodeName pdw_node_name | The name of any Performance Data Warehouse cluster node. This parameter is required if Performance Data Warehouse is configured on a different cluster from Process Server. |
-perfServerName pdw_server-name | The name of any member of the Performance Data Warehouse cluster on the node specified by pdw_node_name. This parameter is required if Performance Data Warehouse is configured on a different cluster from Process Server. |
If Performance Data Warehouse is configured on a different cluster, for example, when using one of the "Remote Support" topology patterns, you must also supply the -perfNodeName pdw_node_name and -perfServerName pdw_server-name parameters, where pdw_node_name is the name of any Performance Data Warehouse cluster node, and pdw_server-name is the name of any member of the Performance Data Warehouse cluster on that node.
If V8.0.1 is installed in a network deployment configuration, run the upgrade against the deployment manager profile of your network deployment environment.
The upgradeProcessData command changes passwords saved in the database for tw_admin, tw_user, tw_author, and tw_webservice internal users with the same passwords used for the administrative user set during profile creation. For better security, reset these passwords after migration. Refer to "Changing the default administrative password."
The utility updates existing schemas and migrates data. If you previously upgraded to WebSphere Lombardi Edition 7.1.0 or WebSphere Lombardi Edition 7.2.0 from Teamworks 7.0.0 or 7.0.1, the script also converts encrypted passwords to work with IBM BPM V8.0.1.
The log file is located in the install_root/profiles/profile_name/logs directory. profile_name is the value that you specified for the -profileName parameter. If you did not specify this parameter, profile_name is the default profile name of the cell. The log file name contains the name of the tool as the prefix and the timestamp of the current time. If you set the -nodeName and -serverName parameters, these are also part of the log file name.
SQLCODE=-904, SQLSTATE=57011, SQLERRMC=00C900A3
-DISPLAY DATABASE(<PS_DB_NAME>) SPACENAM(*) RESTRICT
Couldn't load Resource META-INF*****
These
messages can safely be ignored.