Use the enterprise service bus logger mediation database specifications for locating information about supported database types; script names and their locations; profile creation configuration actions; schema upgrades and user ID privileges.
The enterprise service bus logger mediation database is used by the MessageLogger mediation primitive in WebSphere® ESB. The Message Logger primitives stores message information in the Common database. The Common database is the default for the enterprise service bus logger mediation database, but you can use an external database. During the profile augmentation phase, the system creates a variable called ESB_MESSAGE_LOGGER_QUALIFIER which is set to the value of the chosen Common database schema qualifier.
When you run the WebSphere ESB for z/OS® configuration script, make sure that the Enterprise Service Bus database and storage group names in the response file match the names that you set when you created the database and storage groups. For information on database and storage groups, see "Creating databases and storage groups".
A Derby database is created automatically when you run the configuration script with the stand-alone response file (standAloneProfile.rsp). You can manually create databases for all the other supported database types, using the appropriate DDL file. The DDL file is called Table.ddl and is found in the configuration_root/app_server_root /util/EsbLoggerMediation/dbType directory. You can use the same file to create the EsbLogMedDB for a network deployment environment.
Database Types | Considerations |
---|---|
Derby Embedded | Used as the default database type for a standalone server. |
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. |
The Common database is used for both the standalone and network deployment environments at cell scope. However, users can manually create as many other instances as they require (each message logger mediation primitive can be configured to use a different data source and hence a different database).
Deployment manager configuration:
Manually create the database using ${profile_path}/dbscripts/CommonDB/Dbtype/Dbname/createTable_EsbLoggerMediation.sql.
The file createMessageLoggerResource.jacl is located in configuration_root/app_server_root/bin and is used during the product configuration. DDL files for all database types are located in the ${profile_path}/dbscripts/CommonDB/Dbtype/Dbname/createTable_EsbLoggerMediation.sql directories.
The Common database JDBC provider and data source are used by default:
You can create your own data source configuring the Message Logger mediation to use a different data source.
The enterprise service bus logger mediation database uses the MSGLOG table in the Common database. You can choose not to use the Common database, and you can use an external database if desired.
No schema upgrade involved for MSGLOG table. When you migrate to WebSphere ESB version 6.1, WebSphere ESB continues to use the MessageLogger databases used in prior releases. There is no support to migrate this data into the WebSphere ESB Common database.