Creating DB2 databases and validating database connections

For each deployment environment that you are creating, complete the following steps:

1. Create required databases.
   If you are migrating to a Standard deployment 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 an Advanced deployment 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/DB2/Create/createDatabase.sql

2. For case management, you must create at least one additional database. You can create either one database (CPEDB) or three databases, one for IBM Content Navigator (ICN), one for the design object store (DOS), and one for the target object store (TOS). This step assumes that you are creating three separate databases.
   1. Find the files to create the databases in install_root/BPM/dbscripts/DB2/Create.
   2. To create the IBM Content Navigator database, replace the parameters in the following file:

      createDatabase_ICN.sql

      where:

      • @DB_NAME@ is the database name of the IBM Content Navigator (ICN) database, for example, ICNDB.
      • @DBUSER@ is the user name for the database.
   3. Copy the file to the database computer and run it to create the IBM Content Navigator database.

      createDatabase_ICN.sql

   4. To create the databases for IBM Enterprise Content Management, using the embedded Content Platform Engine, find the following database creation files.

      createDatabase_ECM.sh
      createDatabase_ECM.sql

      Make two copies of the files. Name them:

      createDatabase_ECM_DOS.sh
      createDatabase_ECM_TOS.sh
      createDatabase_ECM_DOS.sql
      createDatabase_ECM_TOS.sql

      Replace the parameters with the design object store (DOS) parameters in one file and with the target object store (TOS) parameters in the other file.

      • @DB_NAME@ is the name of the database. For example, the names could be DOSDB and TOSDB.
      • @DB_DIR@ is the data directory of your database, for example, BPMINST/Node0000.
        Important: Make sure that the @DB_DIR@/@DB_NAME@ path already exists on your database computer. You will use this value when you update the properties file later.
      • @ECM_DATA_TS@ is the data table space used by the design object store (DOS) or the target object store (TOS). The default value for DOS is WFDOSDATATS. The default value for TOS is WFTOSDATATS. You can set these values in the SQL files.
      • @ECM_IDX_TS@ is the index table space used by DOS or TOS. The default value for DOS is WFDOSINDEXTS. The default value for TOS is WFTOSINDEXTS. You can set these values in the SQL files.
      • @ECM_LOB_TS@, is the LOB table space used by DOS or TOS. The default value for DOS is WFDOSLOBTS. The default value for TOS is WFTOSLOBTS, You can set these values in the SQL files.
      • @DB_USER@ is the user name for the database.
      • @DOS_SCHEMA@ is the schema for DOS, for example, DOSSA. The name must not be longer than five characters.
      • @TOS_SCHEMA@ is the schema for TOS, for example, TOSSA. The name must not be longer than five characters.
   5. Copy the following four files to the database computer:

      createDatabase_ECM_DOS.sh
      createDatabase_ECM_TOS.sh
      createDatabase_ECM_DOS.sql
      createDatabase_ECM_TOS.sql

   6. Run the files to create the Enterprise Content Management databases.
      For example:

      createDatabase_ECM_DOS.sh
      createDatabase_ECM_TOS.sh

3. 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.