Messaging engine database specifications

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

The messaging engine database is used by the message engines for Service Component Architecture (SCA), Business Process Choreographer, and Common Event Infrastructure. The default database name for the SCA messaging engine is SCADB, for the other messaging engines it is MEDB. For the embedded Cloudscapeâ„¢ database, each messaging engine will have its own database or schema. The default schema name is IBMWSSIB.
Note: Multiple schemas are not supported by all database types, refer to your database documentation for details.

Configure your SCA messaging engine using the administrative console via the Service Component Architecture Configuration panel.

You have a lot of 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. Similarly you can use many database schemas, or a single one. Each messaging engine must have either its own database or schema.

Supported database types

All of the databases supported for WebSphere Application Sever can be used as the messaging engine database. See the WebSphere Application Server supported software page.

Database Management Service (DBMS) instances

Each messaging engine has its own database or schema:
  • One is used to host each messaging engine for the SCA system bus.
  • Another is used to host each messaging engine for the SCA application bus.
  • Another is used to host each messaging engine for the Common Event Infrastructure bus.
  • Another is used to host each messaging engine for the Business Process Choreographer bus.
The naming convention for the JDBC data source that the messaging engine uses to interact with the database is:
  • System bus: <node><server><cluster>-SCA.SYSTEM.<cell>.Bus
  • Application bus: <node><server><cluster>-SCA.APPLICATION.<cell>.Bus
  • Common Event Infrastructure bus: <node><server>|<cluster>-CommonEventInfrastructure_Bus
  • Business Process Choreographer bus: <node><server>.-BPC.<cell>.Bus
The Cloudscape database naming convention is shown below:
  • System bus: install_root/profiles/profilename/databases/com.ibm.ws.sib/(<node>.<server>|<cluster>)-SCA.SYSTEM.<cell>.Bus
  • Application bus: install_root/profiles/profilename/databases/com.ibm.ws.sib/(<node>.<server>|<cluster>)-SCA.APPLICATION.<cell>.Bus
  • Common Event Infrastructure bus: install_root/profiles/profilename/event/CloudScapeEventBusDB/(<node>.<server>|<cluster>)-CommonEventInfrastructure_Bus
  • Business Process Choreographer bus: install_root/profiles/profilename/databases/com.ibm.ws.sib/(<node>.<server>|<cluster>)-BPC.<cell>.Bus
The default for <cell> is the cell name in most cases. However, when a stand-alone profile is federated (only allowed when it is the first node of the cell) then <cell> is the name of that stand-alone profile.

Configuration actions during profile creation

Stand-alone profile

The standalone server is configured for SCA, and the messaging engine databases are created.

Network deployment

No databases are created automatically.

After the profile is created, you can configure a server or a cluster for the Service Component Architecture using the guided activity: Configure your Network Deployment Environment. Access this guided activity from the administrative console of the deployment manager by expanding Guided Activities and clicking Configure your Network Deployment 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:
  • Remote Destination Location:
    • configSCAAsyncForServer, configSCAJMSForServer (remoteMELocation is true)
    • configSCAAsyncForCluster, configSCAJMSForCluster (remoteMELocation is true)
  • Local Destination Location:
    • configSCAAsyncForServer, configSCAJMSForServer
    • configSCAAsyncForCluster, configSCAJMSForCluster

Details of the use of these tasks can be found in configSCAAsyncForCluster command and configSCAAsyncForServer command.

Performing asynchronous SCA configuration for a server or cluster causes a messaging engine to be created for the SCA system bus. Performing the JMS element of the SCA configuration for a server or cluster causes a messaging engine to be created for the SCA application bus. Both the messaging engines require a database or schema to be created.

For Business Process Choreographer the messaging engine configuration is performed using the bpeconfig.jacl script. For Common Event Infrastructure the provided scripts can be used to configure the messaging engine.

SQL scripts

No messaging engine database SQL scripts are created as part of the WebSphere Process Server product. Existing WebSphere Application Server Network Deployment, version 6 scripts can be used to create messaging engine database and tables if necessary. In a network deployment environment, each messaging engine database or schema needs to be created before the messaging engine can be fully configured and started.

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. This usually means that 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 under templates/system (profiles configuration) is searched for a matching JDBC provider. The provider is matched also against the implementation class.

Business Process Choreographer

The JDBC provider creation for the messaging engine database is similar to the approach followed in the creation of the BPEDB database. See Business Process Choreographer database specifications for more details.

Common Event infrastructure

The JDBC provider creation for messaging engine database is similar to the approach followed in the creation of the CEIDB database. See Common Event Infrastructure database specifications for more details.

Restrictions

There are no known restrictions.

Tables

For information on the tables, see the topic Data stores in the WebSphere Application Server Network Deployment, version 6 information center.

Exported scripts

No scripts are exported during profile creation.

User ID privileges

The user credentials that you provide in the Profile wizard must have the permissions required to create tablespaces, tables, indexes, and stored procedures.


Last updated: Wed 01 Nov 2006 07:47:12

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)