IBM BPM, V8.0.1, All platforms > Install IBM BPM > IBM BPM Advanced for z/OS: Process Server > Configure IBM BPM Advanced for z/OS: Process Server > Create the databases

Create the messaging engine data stores

If the messaging engine data stores have not already been created, use the database design tool to generate the database scripts that the database administrator will use to create the tables for the messaging engine data stores.

Before you create and run the database scripts, decide which service integration bus components you want to create in your ND configuration.

You must create and populate a messaging engine data source for each of the following components that you configure:

• Service Component Architecture system bus
• Service Component Architecture application bus

• Process Server
• Performance Data Warehouse
• Business Process Choreographer
• Common Event Infrastructure

You can create all the database objects in one or more databases in the DB2 for z/OS subsystem. Take note of the following considerations:

• All messaging engines use the same table names. Therefore, the tables for each messaging engine require a unique schema qualifier.

• When you use the database design tool to define the database configuration for each messaging engine, you can specify a prefix for table space names:

  • If you intend to use a single database for all the messaging engines, specify a unique table space prefix for each messaging engine to make its table space name unique within the database.

  • If you intend to use a separate database for each messaging engine, the table space prefixes that you specify for the messaging engines can be identical or unique.

The following naming convention is used for the table space names for messaging engines:

• table_space_prefixOWN (for example, A6S1AOWN)
• table_space_prefixOTS (for example, A6S1AOTS)
• table_space_prefixMAP (for example, A6S1AMAP)
• table_space_prefixLST (for example, A6S1ALST)
• table_space_prefix00T (for example, A6S1A00T)
• table_space_prefix00L (for example, A6S1A00L)
• table_space_prefix01T (for example, A6S1A01T)
• table_space_prefix01L (for example, A6S1A01L)
• table_space_prefix02T (for example, A6S1A02T)
• table_space_prefix02L (for example, A6S1A02L)
• table_space_prefixXAT (for example, A6S1AXAT)
• table_space_prefixKEY (for example, A6S1AKEY)

Procedure

1. For each messaging engine to generate the required database scripts:

   1. Run the database design tool (DbDesignGenerator.sh) from the WAS_HOME/util/dbUtils directory.

   2. Select option (2)Create a database design for a single component, and then select the appropriate option for the messaging engine.

   3. Complete the remaining prompts in the tool to define the database configuration and to generate the scripts.
   See Create a database design file for a specific component.

   Tip: As an alternative to running the database design tool multiple times to generate scripts for each of the messaging engines, you can run the tool once using option (1)Create a database design for Standalone profile or Deployment Environment. With this option, you can define the database configuration and generate database scripts for the following components in a single pass through the tool: Common database, Business Process Choreographer, Performance Data Warehouse, Process Server, Business Space, and the six messaging engines. For more information, see Create a database design file and database scripts for a stand-alone profile or deployment environment.

2. Run the generated scripts using the tool of your choice. See Create databases in the DB2 for z/OS subsystem.

3. If you need to rerun the scripts to create the database tables for a messaging engine, you can use the sample sibDropxx.ddl script, which is stored in the im_INSTALL_ROOT/zOS-config/samples directory, to drop the table spaces. (In this directory path, im_INSTALL_ROOT represents the root directory for the product code installed with Installation Manager.) Before you run the sibDropxx.ddl script, you must edit the file to set the appropriate values for the @DB_NAME@ and @SCHEMA@ variables.

Results

The messaging engine data stores are created.

Create the databases