Creating DB2® databases (deprecated)

To create the databases before you create the profiles or before you use the Deployment Environment wizard to create your deployment environment, you can use the createDatabase.sql template that is provided with your IBM Business Automation Workflow installation.

Complete the following steps for each database that you want to create:

1. Navigate to the BPM_HOME/BPM/dbscripts/DB2/Create directory and make a copy of the createDatabase.sql file.
2. In the copied file, replace @DB_NAME@ with the name that you want to use for the database and replace @DB_USER@ with the user name that you want to use for the database. Save the file.
3. For each createDatabase.sql file that was generated, run the following command on your local or remote database server to create the Common database (CMNDB), Process database (BPMDB), and Performance Data Warehouse database (PDWDB):

   db2 -tvf createDatabase.sql

   Note: The CMNDB database only needs to be created once, which means that you only need to run the command in one of the two CMNDB subdirectories.
4. Create the Content database (CPEDB) and manually create the table spaces for it.
   If you plan to use an external Content Platform Engine instead of the embedded Content Platform Engine during deployment environment creation, you can skip this step.
   1. Update the database creations files with the correct values for your environment.
      In the createDatabase_ECM.sh file, replace the following variables:

      • @DB_DIR@
      • @DB_NAME@
      • @DOS_SCHEMA@
      • @TOS_SCHEMA@

      Replace @DB_DIR@ with your Db2® instance home directory. Replace @DB_NAME@ with the name that you want to use for the database (such as CPEDB). Replace @DOS_SCHEMA@ with DOSSA and replace @TOS_SCHEMA@ with TOSSA. Remember the name you chose for the database. You will enter it in the launchpad.

      In the createDatabase_ECM.sql file, replace the following variables:

      • @DB_DIR@
      • @DB_USER@
      • @DB_NAME@

      Replace @DB_DIR@ and @DB_NAME@ with the same values as in the previous file, and replace @DB_USER@ with the user name.
   2. Run the createDatabase_ECM.sh command to create the Content database.
      Notes:

      • If you see the following error, shut down and restart Db2.

        SQL1363W One or more of the parameters submitted for immediate modification
        were not changed dynamically. For these configuration parameters, the database
        must be shutdown and reactivated before the configuration parameter changes
        become effective.

      • If you drop the Content database, you must manually remove the directories that were created for it.
   3. Copy the install_root\BPM\dbscripts\DB2\Create\createTablespace_ECM.sql file to two files in your working directory. Name them createTablespace_ECM_DOS.sql (for the Design Object Store) and createTablespace_ECM_TOS.sql (for the Target Object Store).
      Update and run the two new files to create the table spaces.

      In createTablespace_ECM_DOS.sql:

      • Replace @DB_DIR@, @DB_NAME@, and @DB_USER@ with the names that you used in the previous files.
      • Replace @SCHEMA@ with the DOS schema value that you chose in substep a, such as DOSSA. Later, you must enter this DOS schema value in the Design Object Store database schema name field on the Configure databases page of the Deployment Environment wizard.
      • Replace the table spaces @ECM_DATA_TS@, @ECM_IDX_TS@, and @ECM_LOB_TS@ with DOSDATTS, DOSIDXTS, and DOSLOBTS.
      • Run:

        db2 -tvf createTablespace_ECM_DOS.sql

      In createTablespace_ECM_TOS.sql:

      • Replace @DB_DIR@, @DB_NAME@, and @DB_USER@ with the names that you used in the previous files.
      • Replace @SCHEMA@ with the TOS schema value you chose in substep a, such as TOSSA. Later, you must enter this TOS schema value in the Target Object Store database schema name field on the Configure databases page of the Deployment Environment wizard.
      • Replace the table spaces @ECM_DATA_TS@, @ECM_IDX_TS@, and @ECM_LOB_TS@ with TOSDATTS, TOSIDXTS, and TOSLOBTS.
      • Run:

        db2 -tvf createTablespace_ECM_TOS.sql

5. Create the IBM Content Navigator database and the table spaces for it.
   If you plan to use an external IBM Content Navigator instead of the embedded IBM Content Navigator during deployment environment creation, you can skip this step.
   1. Create the database if you have not already done so.
      Note: If you created a Content database in the previous step, do not create an IBM Content Navigator database. Create the IBM Content Navigator table spaces in the Content database.

      To create the database, run:

      createDatabase_ICN.sql
      

   2. Update and run the file to create the IBM Content Navigator table spaces.
      • Copy the install_root/BPM/dbscripts/DB2/Create/createTablespace_ICN.sql file to your working directory.
      • Replace @ECMClient_SCHEMA@ with the IBM Content Navigator schema value you choose, such as ICN. Later, you must enter this ICN schema value in the IBM Content Navigator database schema name field on the Configure databases page of the Deployment Environment wizard.
      • Replace @ECMClient_TBLSPACE@ with ICNTS.
      • Run:

        db2 -tvf createTablespace_ICN.sql

After you create the profiles, you can use the Deployment Environment wizard to create the deployment environment and generate the database scripts. The scripts are populated with the configuration values that you specified in the wizard. You can use some of these scripts to create the databases if you chose to defer the creation of the database tables.

1. On the computer where you created the deployment manager profile, navigate to one or more of the following default subdirectories where the SQL database scripts were generated:
   • dmgr_profile_root/dbscripts/cell_name/DB2/CMNDB
   • dmgr_profile_root/dbscripts/cell_name.deployment_environment_name/DB2/CMNDB
   • dmgr_profile_root/dbscripts/cell_name.deployment_environment_name/DB2/BPMDB
   • dmgr_profile_root/dbscripts/cell_name.deployment_environment_name/DB2/PDWDB
   • dmgr_profile_root/dbscripts/cell_name.deployment_environment_name/DB2/CPEDB

   These directories contain the createDatabase.sql and createDatabase_ECM.sql scripts that you can use to create the databases.

   The number of subdirectories that are generated depends on the deployment environment type and the number of databases that were configured in the Deployment Environment wizard.

2. For each createDatabase.sql file that was generated, run the following command on your local or remote database server to create the Common database (CMNDB), Process database (BPMDB), and Performance Data Warehouse database (PDWDB):

   db2 -tvf createDatabase.sql

   Note: The CMNDB database only needs to be created once, which means that you only need to run the command in one of the two CMNDB subdirectories.
3. Create the Content database (CPEDB) and manually create the table spaces for it.
   1. Run the following command to create the Content database:
      Tip: In some Content database scripts, there is a @DB_DIR@ variable that should be replaced manually.

      createDatabase_ECM.sh

      Notes:

      • If you plan to use an external Content Platform Engine instead of the embedded Content Platform Engine during deployment environment creation, you need only the IBM Content Navigator database and can run db2 -tvf createDatabase_ICN.sql instead of createDatabase_ECM.sh.
      • If you see the following error, shut down and restart Db2.

        SQL1363W One or more of the parameters submitted for immediate modification
        were not changed dynamically. For these configuration parameters, the database
        must be shutdown and reactivated before the configuration parameter changes
        become effective.

      • If you drop the Content database, you must manually remove the directories that were created for it.
   2. Manually create the table spaces for the Content database by running the createTablespace_Advanced.sql, createTablespace_Standard.sql, or createTablespace_Express.sql script.

      db2 -tvf createTablespace_DeType.sql

      Tip: In some Content database scripts, there is a @DB_DIR@ variable that should be replaced manually.