Upgrading DB2 databases

For DB2, upgrade your existing schemas and data so that your databases work with the new version of IBM® Business Process Manager.

Figure 1. Sample environment after existing schemas and data are updated. The source environment is not running and the databases are not in use. The databases contain updated schemas and data. The target is not running but contains a deployment environment.

The details of the diagram are provided in the figure caption.

Run the DBUpgrade command to modify your existing database schemas and data for use with IBM Business Process Manager V8.5. The DBUpgrade utility updates the following items to V8.5:

System Data toolkit
Process Portal process application
Hiring Sample tutorial process application

Note: Although the DBUpgrade utility updates the System Data toolkit to IBM Business Process Manager V8.5, it does not automatically update existing dependencies. The dependencies must be updated after migration.

The DBUpgrade utility also converts encrypted passwords to work with the encryption algorithm used by IBM Business Process Manager V8.5. Encrypted passwords can be stored in the database for secure web service integrations users.

Note: Encrypted passwords can be stored in the database for Microsoft SharePoint integrations users.

Before you begin

Ensure that you have shut down the source environment before you proceed with the migration.

Verify that the users that are configured to access your DB2 databases have the necessary privileges to upgrade the databases. The following database privileges are needed to modify existing DB2 database schemas and data for use with IBM Business Process Manager V8.5.

The CONNECT and CREATETAB privileges are required on the database level.
The upgrade process accesses system views and procedures. Grant the SELECT and EXECUTE privileges to the user who performs the upgrade. These privileges are already granted to the public group by default; it is not necessary to grant them again unless they were revoked.
```
syscat.tables
syscat.views
syscat.columns
syscat.indexes

PROCEDURE ADMIN_CMD and REORG authority
```

For a list of supported database versions, refer to the system requirements.

Procedure

Based on your source environment and the location of the target environment, perform the following step:

Current® version of IBM Business Process Manager Standard or WebSphere® Lombardi Edition	File system where IBM BPM V8.5 is to be installed	Steps to take
WebSphere Lombardi Edition 7.1.0 that is previously upgraded from Teamworks® 7.0.0 or 7.0.1 WebSphere Lombardi Edition 7.2.0 that is previously upgraded from Teamworks 7.0.0 or 7.0.1 to WebSphere Lombardi Edition 7.1.0 and then upgraded to WebSphere Lombardi Edition 7.2.0	Same file system as the existing WebSphere Lombardi Edition installation	In the `installation_root`/util/DBUpgrade directory, modify the `upgrade.properties` file to set the value of the `previous.lombardi.install.dir` property to be your source environment installation directory. Note: If this property is missing or not valid, the upgrade script is unable to migrate encrypted passwords, but can still perform other upgrade processing.
WebSphere Lombardi Edition 7.1.0 that is previously upgraded from Teamworks 7.0.0 or 7.0.1. WebSphere Lombardi Edition 7.2.0 that is previously upgraded from Teamworks 7.0.0 or 7.0.1 to WebSphere Lombardi Edition 7.1.0 and then upgraded to WebSphere Lombardi Edition 7.2.0	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 `installation_root/AppServer/lib/ext`

To upgrade the databases to V8.5, run the DBUpgrade utility.
Important: Ensure that your deployment manager and all the managed nodes in the source environment have been stopped before running this utility.
```
BPM_home\bin\DBUpgrade.bat -propertiesFile migration_properties_file -backupFolder snapshot_folder
```
where:
- migration_properties_file is the full path to the migration properties file in which you specified the configuration information for the target environment. Ensure that the value of the target.config.property.file property is set to the full path of the configuration properties file that you used to create your target environment. You must also set the value of profile.name.
- snapshot_folder is the directory that contains the information that was extracted from the source environment
For example:
```
BPM_home\bin\DBUpgrade.bat -propertiesFile "C:\bpm 85\util\migration\resources\migration.properties" -backupFolder C:\snapshot
```
If you get an out-of-memory error indicating too many or too large data records, you can try to increase the heap size of the JVM for the DBUpgrade command, or decrease the value of database.batch.size (the size of the records to be updated as a batch) in the following file: BPM_home\util\dbUpgrade\upgrade.properties.
V8.5 no longer supports the Lombardi database user registry. Users that were maintained by the Lombardi database user registry are moved to the WebSphere Application Server file-based user registry. After migration, you can maintain these users in the WebSphere Application Server administrative console.

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 Business Process Manager V8.5.

What to do next

You might see warning messages similar to the following in the upgrade log: Couldn't load Resource META-INF*****. These messages can safely be ignored.