Download PDF (1.3 MB) - IBM Redbooks

Use the following steps to place all messaging engines into the same database:
1. Create one schema definition for each messaging engine with the following command:
WAS Install\bin\sibDDLGenerator.bat -system db2 -version 8.1 -platform windows
-statementend ; -schema BPCMSG -user user >createSIBSchema_BPCMSG.ddl
In this syntax (used on a Windows operating system), WAS Install represents the
Business Process Manager installation directory, and user represents the user name.
2. Repeat the command for each schema or messaging engine.
3. To distribute the database across several disks, edit the created schema definitions, and
put each table in a table space, named after the schema used. For example, SCAAPP
becomes SCANODE_TS, CEIMSG becomes CEIMSG_TS, and so on. After editing, the
schema definition should look like Example 4-1.
Example 4-1 Schema definition
CREATE SCHEMA CEIMSG;
CREATE TABLE CEIMSG.SIBOWNER (
ME_UUID VARCHAR(16),
INC_UUID VARCHAR(16),
VERSION INTEGER,
MIGRATION_VERSION INTEGER
) IN CEIMSG_TB;
CREATE TABLE CEIMSG.SIBCLASSMAP (
CLASSID INTEGER NOT NULL,
URI VARCHAR(2048) NOT NULL,
PRIMARY KEY(CLASSID)
) IN CEIMSG_TB;
….
Another possibility is to separate table spaces for the various tables. Optimal distribution
depends on application structure and load characteristics. In this example, one table
space per data store is used.
4. After creating all schema definitions and defined table spaces for the tables, create a
database named SIB.
5. Create the table spaces and distribute the containers across available disks by issuing the
following command for a system managed table space:
DB2 CREATE TABLESPACE CEIMSG_TB MANAGED BY SYSTEM USING( '\CEIMSG_TB' )
Place the database log on a separate disk, if possible.
6. Create the schema of the database by loading the four schema definitions into the
database.
For more information about database and DB2 tuning, see the following sections:
► 4.13, “General database tuning” on page 80
► 4.14, “DB2-specific database tuning” on page 82
68 IBM Business Process Manager V8.0 Performance Tuning and Best Practices