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.
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 |
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) |
Used as a local database for standalone profile. |
DB2 UDB for iSeries (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 |
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. |
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.
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.
For Network Deployment, you must configure the Common Event Infrastructure server through the Administrative console. For more information, see "Configuring the Common Event Infrastructure"
In standalone environment, the event database and tables are created, and scripts are exported to profile_root/dbscripts/CEI_event directory.
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"
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}
Many tables are created. Look under the generated scripts to see which tables are generated for the given database product.
configuration_root/app_server_root/profiles/profilename/event/dbscripts/dbtype