IBM BPM, V8.0.1, All platforms > Install IBM BPM > Plan for IBM BPM > Plan the database configuration > Plan the component-specific database configurations

Plan to configure the messaging engine database

The messaging engine database specifications list supported database type, scripts and their locations, profile creation types, and necessary user ID privileges.

The messaging engine database is used to store operating information. Essential objects that the messaging engine needs for recovery in the event of a failure are also stored.

The messaging engine database is used by the message engines for Service Component Architecture (SCA) modules, Business Process Choreographer, and Common Event Infrastructure (CEI). The default database name for the SCA messaging engine is SCADB. For the other messaging engines, the default database name is MEDB. The default schema name is IBMWSSIB.

Important: Multiple schemas are not supported by all database types. See your database documentation.

In a stand-alone environment, you can use the administrative console to configure your SCA messaging engine. In a patterned ND environment, the messaging engines are configured during deployment environment creation. For a custom ND environment, you need to configure the messaging engines manually.

You have control over the messaging engine databases.

For example, you can create a database for each messaging engine or you can use a single database for all the messaging engines. Each messaging engine must have either its own database or a schema.


Supported database types

The messaging engine database can use the following database products:

Supported database products
Database Types Considerations
DB2 Express Used as the default database type for a stand-alone profile.
DB2 Universal Used as the database in ND configurations. Optionally, can be used as the database in stand-alone server configurations.
DB2 Data Server Used as the database in ND configurations. Optionally, can be used as the database in stand-alone server configurations.

DB2 for z/OS v8
DB2 for z/OS v9

DB2 for z/OS

Important: When creating a profile for a server that uses DB2 for z/OS v9, the server must be able to connect to the DB2 database. Used as the database in ND configurations. Optionally, can be used as the database in stand-alone server configurations.

Microsoft SQL Server (Microsoft)  
Oracle You need system database administrator privileges to create the database, tables, and schemas. If you do not have these privileges, you might receive errors when you create or access the tables and schemas.

User ID privileges

The user credentials that you provide in pmt.sh must have the permissions necessary to create table spaces, tables, schemas, indexes, and stored procedures. For the Create new database option, the user ID must have the necessary privileges to create a database. If the user who is running the script has the authority to create tables, the script does not require an authentication ID within the script. See Database privileges and User ID or schema name privileges.

For a ND environment, you need all necessary permissions for user privileges specified during configuration from the administrative console.

Important: For DB2 V9.7, grant the appropriate authority to the newly created user, because the user creation process does not automatically grant the user the necessary authority.


Database Management Service (DBMS) instances

Each messaging engine has its own database or schema:

The following list contains the naming conventions for the JDBC data source that the messaging engine uses to interact with the database:

Configuration actions during profile creation

Network deployment

No messaging engine databases are created automatically. After the profile is created, you can use the Configure your Network Deployment Environment guided activity to configure a server or a cluster for SCA. To access this guided activity from the administrative console of the dmgr, expand Guided Activities and click Configure your ND Environment.

You can view the SCA configuration of your server from the Application servers > servername > Service Component Architecture panel of the administrative console.

The following administrative tasks are performed during profile creation:

For more information about these tasks, see "configSCAAsyncForCluster command" and "configSCAAsyncForServer command".

When you perform asynchronous SCA configuration for a server or cluster, a messaging engine is created for the SCA system bus. When you perform the JMS element of the SCA configuration for a server or cluster, a messaging engine is created for the SCA application bus. For both messaging engines, create a database or schema.

The Business Process Choreographer messaging engines are created during Business Process Choreographer configuration. Business Process Choreographer is configured for patterned deployment environments only. See Plan the topology, setup, and configuration path.

To configure the Common Event Infrastructure messaging engine, use the deployEventService administrative task to configure the event server and the Common Event Infrastructure bus.

Database actions invoked by the product configuration script

Stand-alone profile

The message engine database is created during the installation and configuration.

Network deployment

You can configure the message engines for Service Component Architecture with Application servers > servername > Service Component Architecture panel in the administrative console.

The following administrative tasks are performed when the profile is created:

For both tasks, the following parameters are handed over:

  • busDataSource
  • meAuthAlias
  • busSchemaName
  • createTables
  • systemBusId (the default is the cell name)

For Business Process Choreographer and Common Event Infrastructure, the messaging engines are configured in the administrative console for an ND configuration, and during the augment process in a stand-alone configuration.

For Business Process Choreographer, use the bpeconfig.jacl script to configure the messaging engine. For Common Event Infrastructure, use the provided scripts to configure the messaging engine.

SQL scripts

No SQL scripts are created as part of the product. You can use existing base WebSphere Application Server scripts to create database and tables if necessary. To create the MEDB manually before it is configured, use the Servers > Server Types > WebSphere application servers > servername > Service Component Architecture panel of the administrative console.

Use the sibDDLGenerator command to create the scripts for messaging engine data base objects. See "The sibDDLGenerator command".


JDBC provider

Service Component Architecture

The JDBC provider is reused when the JDBC provider implementation class has to match with the one chosen in the advanced configuration.

If the same database types are used, then the implementation classes usually match. If no matching JDBC provider is found in the resource.xml file, then the jdbc-resource-provider-templates.xml file in the templates/system directory (profiles configuration) is searched for a matching JDBC provider. The provider is matched also against the implementation class.

Business Process Choreographer

The Business Process Choreographer reuses the JDBC provider for the SCA messaging engine. See Configure Business Process Choreographer.

Common Event Infrastructure

The JDBC provider creation for messaging engine database is similar to the approach followed in the creation of the CEIDB database.

Data source names

  • System bus: : _( node. server| cluster)-SCA.SYSTEM. cell.Bus/ cel/ cluster/ server/ node

  • Application bus: _( node. server| cluster)-SCA.APPLICATION. cell.Bus/ cell/ cluster/ server/ node
  • Common Event Infrastructure: _( node. server| cluster-CEI. cellName.BUS/ cluster/ server/ node
  • Business Process Choreographer:_( node. server| cluster)-BPC. cell.Bus/ cell/ cluster/ server/ node

Data source JNDI names

  • System bus: jdbc/com.ibm.ws.sib/( node. server| cluster)-SCA.SYSTEM. cell.Bus/ cell/ cluster/ server/ node

  • Application bus: jdbc/com.ibm.ws.sib/( node. server| cluster)-SCA.APPLICATION. cell.Bus/ cell/ cluster/ server/ node
  • Common Event Infrastructure: Jdbc/ com.ibm.ws.sib /( node. server| cluster)-CEI. cellName.BUS/ cluster/ server/ node
  • Business Process Choreographer bus: jdbc/com.ibm.ws.sib/( node. server| cluster)-BPC. cell.Bus/ cell/ cluster/ server/ node

Restrictions

There are no known restrictions.

Tables

For information on the tables, see the topic "Data stores" in the WebSphere Application Server ND information center.

Tables

For information on the tables see the WebSphere Application Server topic on "Data stores".

Exported scripts

You can use the sibDDLGenerator script in WAS_INSTALL_ROOT/bin to create the SQL scripts for messaging engines database. Use the sibDDLGenerator script for creating SQL scripts for use in production environment especially on the DB2 for z/OS platform. See the "The sibDDLGenerator command".

These scripts contain only basic create database/tablespace/table statements. A database administrator might still need to tailor these scripts to meet their database needs, especially on DB2 for z/OS.


Configure messaging engine and server behavior when a data store connection is lost

The connection between a running messaging engine and its data store might sometimes be lost due to a failure or because you stop the database.

You can determine the behavior of your system through a custom property on the messaging engine.

If you set the sib.msgstore.jdbcFailoverOnDBConnectionLoss custom property, you can enhance the automatic recovery of a highly available IBM BPM environment.

For information on the sib.msgstore.jdbcFailoverOnDBConnectionLoss property, including information how to set this property, see Configure messaging engine and server behavior when a data store connection is lost.

Plan the component-specific database configurations