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


Database configurations

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 Resources > JDBC > Data Sources page. See "Table and schema creation matrices" for more information.

Note: The Common database can be created before you create a profile. The Profile Management Tool has an option to use an existing database for the Common database.

You have three options for configuring the database tables needed by WebSphere ESB:

Default database names

Table 1 lists the components of WebSphere ESB that require a database table and the default names of the databases where the tables associated with these components are stored.
Note: You can change these names if you choose.
Table 1. WebSphere ESB components that require database tables and the default names of the databases where the tables are stored.
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 .

Database by dbType value

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.

Table 2. Supported database types, their associated dbType values and restrictions
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
DB2UDBOS390_V9_1

The installation wizard will not be able to create a new database of this type.
For i5/OS operating system

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

DB2UDBISERIES_NATIVE This database type does not support network deployment topologies.
For i5/OS operating system

DB2 UDB for iSeries (Toolbox)
DB2 for i5/OS (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
Oracle 10g
Oracle 11g

Oracle9i
Oracle10g

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
For i5/OS operating system 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).

Database by feature

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.

Table 3. Databases and their associated feature name.
Database Feature
Business Space BusinessSpace
Common Event Infrastructure CEI
Common database CommonDB
Enterprise service bus logger mediation database EsbLoggerMediation
When you install WebSphere ESB, database scripts are created in the following locations:
WPS_INSTALL_ROOT/dbscripts/feature/dbType
where feature can be:
  • CommonDB
  • EsbLoggerMediation
  • ProcessChoreographer

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.

i5/OS database consideration for driver connections

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.

Table 4. i5/OS considerations for driver connections
Source System Target System Database Driver
i5/OS i5/OS (local)
  • DB2 UDB for iSeries (Native)
  • DB2 for i5/OS (Native)
Native JDBC driver
i5/OS
Note: Source system must have remote database entry as an alias for the target database system.
i5/OS (remote access)
  • DB2 for i5/OS (Toolbox)
  • DB2 UDB for iSeries (Toolbox)
IBM Toolbox for Java™ JDBC driver
i5/OS i5/OS Derby Network Server Derby Network Server JDBC driver
i5/OS non-i5/OS system
  • Informix Dynamic Server
  • Oracle
  • Microsoft® SQL Server
  • DB2 Universal
  • DB2 Universal Runtime Client
  • Derby Network Server
A type 4 driver for the selected database.
non-i5/OS system i5/OS
  • DB2 UDB for iSeries (Toolbox)
  • DB2 for i5/OS (Toolbox)
IBM Toolbox for Java JDBC driver
non-i5/OS system i5/OS Derby Network Server Derby Network Server JDBC driver

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