WebSphere® ESB uses a number of database tables to hold, store and track information. Creating these database tables is part of the process of configuring the WebSphere ESB. You can create these database tables during profile creation or you can choose to create them separately using scripts.
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. You can create and configure these database tables when you create a WebSphere ESB profile. Alternatively you can select not to create the database tables during profile creation and perform the same operations after your profile creation is complete, using scripts provided as part of the product installation.
In some instances, you have the option of creating the tables and schemas in the administrative console through the Create Tables check box in the page. See "Table and schema creation matrices" for more information.
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 | EsbLogMedDB | 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 manageprofile commands. 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. |
Derby Network Server | DERBY_NETWORK | This is the default database type used for network deployment topologies. |
DB2 Universal | DB2_Universal | |
DB2 for z/OS v8 DB2 for z/OS v9 | DB2UDBOS390_V8_1 |
The installation wizard will not be able to create a new database of this type. |
![]() DB2 UDB for iSeries (Native) |
DB2UDBISERIES_NATIVE | This database type does not support network deployment topologies. |
![]() DB2 UDB for iSeries (Toolbox) |
DB2UDBISERIES_TOOLBOX | This is the default database type used for network deployment topologies. |
Informix Dynamic Server | INFORMIX | Business Space does not support this database type. |
Microsoft SQL Server (Embedded) | MSSQLSERVER_EMBEDDED | |
Microsoft SQL Server (DataDirect) | MSSQLSERVER_DATADIRECT | Business Space does not support this database type. |
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 | MSSQLSERVER_MICROSOFT | Business Space does not support this database type. |
Oracle 9i |
Oracle9i |
The installation wizard will not be able to
create a new database of this type for Oracle 9i, Oracle 10g, and Oracle 11g. Note: Use the
Oracle10g parameter for Oracle 10g and Oracle 11g
|
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 |
WPS_INSTALL_ROOT/dbscripts/feature/dbTypewhere feature can be:
The creation of most JDBC providers is performed during profile creation, 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.
Table 4 describes what drivers are needed to connect remotely with i5/OS. The required driver depends on the systems involved and which database is being used. This driver must be on the source system in order to connect remotely to the target system.