If you need new DB2 for z/OS databases, create
the databases before creating your deployment environment. Even if
you have no new databases, validate that all database connections
are correctly configured before you continue.
Procedure
For each deployment environment that
you are creating, complete the following steps:
- Create required databases.
If you are migrating to
IBM® BPM
Standard:
- Create a database for Business Space if you did not have one in
the source environment.
- Create a messaging engine database if you want to use a single
messaging engine bus in the new environment (recommended). If you
want to use multiple buses, you can reuse the previous messaging engine
database and schema.
If you are migrating to
IBM BPM
Advanced:
- Create a database for Business Space if you did not have one
in the source environment.
- Create a Business Process Choreographer database.
- Create a messaging engine database if you want to use a single
messaging engine bus in the new environment (recommended). If you
want to use multiple buses, you can reuse the previous messaging engine
database and schema.
For each database, make any required changes
and run the following script:
install_root/BPM/dbscripts/DB2zOS/Create/createDatabase.sql
Use the DB2® command
line processor to run the createDatabase.sql files
on the database server; for example:db2 -tvf cell_scoped_subdir/createDatabase.sql
db2 -tvf cluster_scoped_subdir/createDatabase.sql
- On the target deployment manager computer,
validate that all database connections are correctly configured by
running the BPMConfig -validate command. Use
the following syntax:
target_install_root/bin/BPMConfig -validate -db configuration_properties_file
where - configuration_properties_file is the full path
and name of the properties file that you copied over to the target
environment after you migrated the configuration using the BPMConfig
-migrate command. The BPMConfig -validate -db command
uses the database properties and the database-related authentication
alias properties (including passwords) from the configuration properties
file. If necessary, you can update these database properties in the
file, such as adding the properties for any new databases that you
created.
The command checks each connection and
displays a message similar to the following message:
A JDBC connection to the 'BusinessSpaceDb' (CMNDB.bpmadmin) has been successfully established.
Results
After all connections are checked,
you see a message that the BPMConfig -validate command
completed successfully.