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


Common Event Infrastructure database configurations

The Common Event Infrastructure database specifications list the types of supported databases, script locations, profile configuration types, and necessary User ID privileges.

Use the Common Event Infrastructure database to store events that are captured when monitoring WebSphere® ESB.

You create the Common Event Infrastructure database for a stand-alone profile by default and for each instance of a Common Event Infrastructure server in a network deployment environment. To create the database, you can use the installation procedure, the Profile Management Tool or the administrative console.

The Common Event Infrastructure database is an internal device and you do not interact directly with it. All interactions with the Common Event Infrastructure database must be performed using the supported Common Event Infrastructure APIs.

See "Configuring the event database" for more information.

Supported Database Types

The Common Event Infrastructure 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 instances

Each deployment target of the Common Event Infrastructure server has one database. The Common Event Infrastructure database is only created for a stand-alone server profile so there is one instance of the Database Management Service (DBMS) for each server.

Configuration actions during profile creation

How the Common Event Infrastructure is created depends on the type of environment:
Standalone Environment
Configuration of the Common Event Infrastructure database is done as part of the profile creation by the profile template Apache ANT script configCei.ant. This script invokes the Common Event Infrastructure administrative tasks with all the necessary properties for the desired configuration.

In the stand-alone environment, the event database and tables are created, and scripts are exported toprofile_root/dbscripts/CEI_event by default. If you use the optional outputScriptDir parameter, the default location of the scripts is profile/databases/event/node/server/dbscripts/dbtype.

In the Profile Management Tool or when you use manageProfile command, the default location for standalone CEI environment profile_root/dbscripts/CEI_DBNAME.

Network Deployment Environment
In the Network Deployment Environment, the deployment manager profile creation or managed profile creation does not include the automatic creation of the Common Event Infrastructure database. To create the Common Event Infrastructure database, see "Configuring the event database."

For Network Deployment, you must configure the Common Event Infrastructure server through the Administrative console. For more information, see "Configuring the Common Event Infrastructure"

Common Event Infrastructure provides an administrative task configEventServiceDB to:
  • Create event database and tables by setting the createDB parameter to true
  • Export the SQL scripts by setting the createDB parameter to false

SQL scripts

Common Event Infrastructure provides an administrative task configEventService<DBTYPE>DB to:
  • Create event database and tables by setting the createDB parameter to true
  • Export the SQL scripts by setting the createDB parameter to false

In standalone environment, the event database and tables are created, and scripts are exported to profile_root/dbscripts/CEI_event directory.

JDBC provider

The Common Event Infrastructure administrative task configEventServiceDBTYPEDB creates the JDBC provider and the data sources. The format is profile_root/databases/event/deployment_environment/dbscripts/dbName directory where deployment_environment is either a cluster or server.

The JNDI names of the components are:

jndiName="jdbc/cei"

jndiName="jdbc/eventcatalog"

Data source names are:
  • event
  • eventcatalog

The scripts that are used for creating the JDBC provider for the Common Event Infrastructure database are stored in the following location: configuration_root/app_server_root/profiles/profilename/event/dsscripts/${dbtype}

Tables

Many tables are created. Look under the generated scripts to see which tables are generated for the given database product.

Exported scripts

Shell scripts are created in the following directory to be used to run the generated SQL scripts.
configuration_root/app_server_root/profiles/profilename/event/dbscripts/dbtype

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_cei_db_specs.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).