WebSphere® ESB uses a number of database tables to hold, store and track information.
During normal operation of WebSphere ESB data is being accessed, moved and supplemented. This data is housed in a number of database tables that you create. If you are configuring a stand-alone server using Derby, the database objects, including tables, are created during configuration. If, however, you are using DB2® for a stand-alone or network deployment node, create the database objects later by using the scripts that are generated during the configuration.
Server component | Database (default name) | Notes® |
---|---|---|
Business Space | WPRCSDB (the Common database) | For stand-alone profiles, you must create the Common database before you start WebSphere ESB. For other profiles, you must use the administrative console to configure Business Space. Configuring a Business Space database is mandatory for using Business Space powered by WebSphere, which provides a common interface for application users to create, manage and integrate Web interfaces across the IBM® WebSphere Business Process Management portfolio. |
Common Event Infrastructure | EVENT (stores events) | You do not need to create this database before you start WebSphere ESB, but it is mandatory for the monitoring of events. |
Relationships | WPRCSDB (the Common database) | You must create the Common database before you start WebSphere ESB. Note: The
WPRCSDB tables need to be configured either during the start up of
the deployment manager or stand-alone server or prior to starting
the deployment manager or stand-alone server.
|
SIBus | User created | These tables need to be configured either during the startup of the messaging engine or prior to starting the messaging engine. You can use a filestore with SIBus in a stand-alone environment during profile creation. However, you can not use a filestore with SIBus in a network deployment environment. |
Enterprise service bus | ESBDB | These tables need to be configured either during startup of the deployment manager or stand-alone server or prior to starting deployment manager or stand-alone server . |
Details of the supported databases including versions, are provided in the WebSphere ESB system requirements. Each database is represented by a parameter dbType which is a character string. The dbType parameter is used as a parameter in response files. The values of dbType for the supported databases are shown in Table 2.
Supported database | dbType value | Restrictions and notes |
---|---|---|
Derby Embedded | DERBY_EMBEDDED | This database type does not support network deployment topologies. Derby is the default database type used for a stand-alone profile. You can use this database type for the Business Process Choreographer database. |
DB2 for z/OS v8 DB2 for z/OS v9 | DB2UDBOS390_V8_1 |
You can use DB2 for z/OS® for either network deployment or stand-alone server configurations. |
A second parameter used in file path and file naming conventions is feature, which indicates which of the various databases (see Table 1) is under consideration. Table 3 lists the databases and the associated feature parameter.
Database | Feature |
---|---|
Business Space | BusinessSpace |
Common Event Infrastructure | CEI |
Common database | CommonDB |
Enterprise service bus logger mediation database | EsbLoggerMediation |
/WebSphere/V6R2/AppServer/dbscripts/CEIand
/WebSphere/V6R2/AppServer/util/EsbLoggerMediation/dbType
The creation of most JDBC providers is performed during configuration, based upon the database parameters that you provide. However, the Business Process Choreographer JDBC providers may be created later using scripts or the administrative console. If a suitable JDBC provider is located on the server or cluster, the existing JDBC provider is used and the creation of a new one is omitted.