Creating DB2 databases and validating database connections

If you need new DB2 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:

  1. Create required databases.
    • Create a database for Business Space if you did not have one in the source environment.
    • Create a common database for each deployment environment if you are migrating from multiple deployment environments.
    • 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\DB2\Create\createDatabase.sql
  2. 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 extracted information using the BPMConfig -migrate command. Update the properties in the file 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.