You can find logger mediation database table specifications for WebSphere® ESB. The specifications contain information about supported database types, script names and their locations, profile creation configuration actions, schema upgrades, and user ID privileges.
The logger mediation database tables are used by the Message Logger mediation primitive in WebSphere ESB. The Message Logger primitive stores message information in the common database. The common database is the default for the WebSphere ESB logger mediation database, but you can use an external database. During the profile augmentation phase, the system creates the ESB_MESSAGE_LOGGER_QUALIFIER variable, which is set to the value of the chosen common database schema qualifier.
The database is created automatically for a stand-alone configuration. You can use Data Definition Language (DDL) files to use additional databases for a stand-alone server configuration or for a network deployment environment.
For a stand-alone configuration that uses a DB2® for z/OS® database, or for a managed node or deployment manager in a network deployment configuration, you must create the WebSphere ESB database and storage groups first. Then you can run the configuration script for IBM® Process Server for z/OS.
| Database Types | Considerations |
|---|---|
| DB2 Express® | Used as the default database type for a stand-alone profile. |
| DB2 Universal | Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations. |
| DB2 Data Server | Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations. |
DB2 for z/OS v8 |
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 network deployment 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. |
The user credentials that you provide in the Profile Management Tool 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. For more information, see "Users and schemas for databases" and "Database privileges".
The common database is used for both stand-alone environments and network deployment environments at cell scope. However, you can manually create as many other instances as you require. Each message logger mediation primitive can be configured to use a different data source and therefore a different database.
For the stand-alone profiles and deployment manager profiles, the WebSphere ESB logger profile executes the createTable common database script in the common database. For more information, see "Common database specifications".
The createTable_ESB.sql SQL script is located in the install_root/dbscripts/CommonDB/DBTYPE directory.
The createMessageLoggerResource.jacl and removeMessageLoggerResource.jacl scripts are located in the install_root/bin directory, and can be used to create or delete tables in the requested database type.
The common database JDBC provider and data source are used by default:
You can configure the Message Logger mediation to use a different data source.
There are no known restrictions.
The WebSphere ESB logger mediation database uses the MSGLOG table in the common database. However, you can choose not to use the common database, and use an external database instead.
The database scripts are exported to the install_root/dbscripts/CommonDB/DBTYPE/dbName directory.
No schema upgrade involved for MSGLOG table. When you migrate to IBM Business Process Manager V6.1, IBM Business Process Manager continues to use the MessageLogger databases used in prior releases. There is no support to migrate this data into the IBM Business Process Manager common database.