WebSphere Enterprise Service Bus, Version 6.2.0 Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows


Enterprise service bus logger mediation database configurations

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.

The database is created automatically for a stand-alone configuration. A set of DDL files are provided to allow you to use additional databases either in a stand-alone server configuration or for a network deployment environment.

For a stand-alone configuration using a DB2® for z/OS® database, or for a managed node or deployment manager in a Network Deployment configuration, you must create the Enterprise Service Bus database and storage groups before running the WebSphere Process Server for z/OS configuration script.

Supported database types

The enterprise service bus logger mediation database can use the following database products:
Table 1. Supported database products
Database Types Considerations
Derby Embedded Used as the default database type for standalone profile.
Derby Network Server Used as the default database type in network deployment environment.
DB2 Universal 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
DB2 for z/OS v9

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.

DB2 UDB for iSeries (Native)
DB2 for i5/OS (Native)

Used as a local database for standalone profile.

DB2 UDB for iSeries (Toolbox)
DB2 for i5/OS (Toolbox)

Used as a remote database for network deployment environment or as a local database for a standalone profile.Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations.
DB2 Universal Runtime Client Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations.
Informix Dynamic Server  
Microsoft SQL Server (Embedded)  
Microsoft SQL Server (DataDirect)  
Microsoft SQL Server (Microsoft) - Support for the Microsoft SQL Server JDBC Driver, version 1.2 was added in WebSphere Process Server, version 6.2.0.1  

Oracle 9i
Oracle 10g
Oracle 11g

You need sysdba privilege to create the database, tables and schemas. Failure to have the correct sysdba privilege can result in errors creating and accessing the tables and schemas.
Important: On i5/OS, there is a single global database in which you define all schemas for all functional components. You must make sure that all schema names are unique within the logical partition (LPAR).

User ID privileges

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 identity must have the necessary privileges to create a new database. See "Users and schemas for databases" and "Database privileges" for more information.
Note: If the user running the script has enough authority to create tables, the script will not require an authentication ID within the script.

Database Management Service (DBMS) instances

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).

Configuration actions during profile creation

For the standalone and deployment manager profiles the enterprise service bus logger profile will execute the Common database script createTable in the Common database. See the"Common database specifications" for more information.

Stand-alone profile

In a default stand-alone environment a Derby database is automatically created named EsbLogMedDB.

Network deployment environment

The default enterprise service bus database is not automatically selected during network deployment profile creation. You must chose either the default database or one of the supported databases.

SQL scripts

The SQL script createTable_ESB.sql is located in install_root/dbscripts/CommonDB/DBTYPE.

The scripts createMessageLoggerResource.jacl and removeMessageLoggerResource.jacl are located in install_root/bin and can be used to create or delete tables in the requested database type.

JDBC provider

The Common database JDBC provider and data source are used by default:

Data source name:
  • WPS DataSource
Data source JNDI name:
  • jdbc/WPSDB

You can create your own data source configuring the Message Logger mediation to use a different data source.

Restrictions

There are no known restrictions.

Tables

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.

Exported scripts

The database scripts are exported to the following location: install_root/dbscripts/CommonDB/DBTYPE/dbName

Schema upgrade scripts

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.

If you want to maintain a single location for message information, you can
  • Manually move the data from the old database to the new database
  • Continue to use the old database
  • Use the createMessageLoggerResource.jacl script to move the data.

concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.doc/doc/cins_esb_logger_db_specs.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).