WebSphere Process Server uses a number of database tables to hold, store and track information. Some of the components that comprise WebSphere Process Server use their own database tables. You can create these database tables during profile creation or you can choose to create them separately using scripts.
During normal operation of WebSphere Process Server a large amount of 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 Process Server 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.
Component | Database (default name) | Notes |
---|---|---|
Business Process Choreographer | BPEDB | You do not need to create this database before you start WebSphere Process Server, but it is mandatory before you invoke any business process choreographer components. |
Common Event Infrastructure | CEIDB (stores events) | You do not need to create this database before you start WebSphere Process Server, but it is mandatory for the monitoring of events. |
Relationships | WPRCSDB (the Common database) | You must create the Common database before you start WebSphere Process Server. |
Mediation | WPRCSDB (the Common database) | You must create the Common database before you start WebSphere Process Server. |
Recovery | WPRCSDB (the Common database) | You must create the Common database before you start WebSphere Process Server. |
Application scheduler | WPRCSDB (the Common database) | You must create the Common database before you start WebSphere Process Server. |
Selectors/Business rules | WPRCSDB (the Common database)/Repository DB (Cloudscape™) | You must create the Common database before you start WebSphere Process Server. |
SIBus | User created | |
Enterprise service bus | EsbLogMedDB |
Details of the supported databases including versions, are provided in the WebSphere Process Server system requirements. Each database is represented by a parameter dbType which is a character string. The dbType parameter is used in file naming and file paths. The values of dbType for the supported databases are shown in Table 2.
Database | dbType |
---|---|
Cloudscape | Cloudscape |
DB2® UDB for iSeries™ (Native) | DB2iSeries |
DB2 UDB for iSeries (Toolbox) | DB2iSeries |
DB2 UDB for z/OS and OS/390 V7.1 | DB2zOSV7 |
DB2 UDB for z/OS V8.1 | DB2zOSV8 |
DB2 CLI | DB2 |
DB2 Universal Express | DB2 |
DB2 Universal | DB2 |
Informix® Dynamic Server | Informix |
Microsoft SQL Server Embedded | SQLServer |
Microsoft SQL Server Data Direct | SQLServer |
Oracle OCI | Oracle |
Oracle Thin | Oracle |
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 Process Choreographer | ProcessChoreographer |
Common Event Infrastructure | CEI |
Common database | CommonDB |
Enterprise service bus logger mediation database | EsbLoggerMediation |
install_root/dbscripts/feature/dbTypegiving a unique location for the SQL scripts for each database. This holds for both the Common database and the Business Process Choreographer database. The Common Event Infrastructure database and the enterprise service bus Logger Mediation (EsbLoggerMediation) database use the locations:
install_root/profiles/profileName/event/dbscripts/dbTypeand
install_root/util/EsbLoggerMediation/dbTyperespectively.
The creation of JDBC providers is still performed during profile creation, based upon the database parameters that you provide. However, if a suitable JDBC provider is located on the server, the existing JDBC provider is used and the creation of a new one is omitted.
Last updated: Wed 01 Nov 2006 07:47:12
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)