Common database specifications

The Common database is optionally created when you create a WebSphere Process Server profile. This database acts as a repository by various components. If you prefer you can create the database before creating the profile, or defer the database creation until after the creation of your profile.

The WebSphere Process Server Common database (CommonDB) is used by the following product components: You can create the Common database before, during, or after WebSphere Process Server profile creation. You can create the Common database using the scripts that are created at product installation time. These scripts require editing with information from your database administrator. You can instead create the database using the Profile wizard or using scripts which are generated during profile creation. This second set of scripts include the database information that you provided during the profile creation.

Supported database types

The following databases are supported for use as the Common database:
  • Cloudscape™ – Cloudscape is the default database type for a stand-alone profile. Cloudscape is disabled for network deployment environments. The selector and business rule group components do not use the Common database when Cloudscape is selected.
  • DB2 Universal Database™ – DB2 Universal Database™ is the default database type for network deployment environments.
  • DB2 Universal Database for z/OS and OS/390 V7.1
  • DB2 Universal Database for z/OS V8.1
  • DB2® Call Level Interface (DB2_CLI)
  • Informix® Dynamic Server
  • Microsoft® SQL Server Embedded
  • Microsoft SQL Server DataDirect
  • Oracle OCI client
  • Oracle Thin

Database Management Service (DBMS) instances

There is one DBMS instance per cell.

Configuration actions during profile creation

The Common database is optionally created during profile creation using the profile action scripts. The profile action scripts are sample scripts. If you wish to use them to manually create your database tables you must edit them with your specific database information. If you use the scripts to manually create your database tables before you create a profile, you are then able to choose the option of using an existing database in the Profile wizard.

If you are creating WebSphere Process Server profiles using a profile creation script, the parameter -dbDelayConfig {true|false} must be set correctly. If set to true the database configuration is not performed during profile creation and you must use the provided scripts to configure the databases.

If you choose to defer creation of the database until after profile creation then default scripts, which include parameters gathered during profile creation, are created in the following location:

install_root/profiles/profileName/dbscripts/feature/dbType/dbName
Note: If you are creating the database at the same time as the profile any mistakes in the database parameters that you provide will yield errors in the overall profile creation. However, if you are delaying the database creation, the profile will be created without errors, but the generated database scripts will contain errors and therefore must be edited before the database can be created.

The script naming convention is shown in Table 1.

Table 1. Common database script naming convention
Type of script Script name
Component specific scriptName_componentName.sql
Component independent scriptName.sql

Stand-alone profile

The profile action scripts are located in the following directory after installation of WebSphere Process Server:

install_root/dbscripts/CommonDB/dbType

or if you defer creation of the database until after you have created the profile the scripts will be found in:

install_root/profiles/profilename/dbscripts/CommonDB/dbType/dbName

The scripts are ready to execute, but you can edit them to include any specific requirements. If you try to start WebSphere Process Server before creating the database you will receive an error message.

The scripts perform the following steps:
  • Create a new database if asked (valid only for a local database), depending on your choices in the Database configuration panel in the Profile wizard. See Restrictions for details on database commands that are not supported by the Profile wizard.
    Note: Even though you can defer creation of the database until after the profile creation is complete, it is necessary to enter valid information in the Database configuration panel of the Profile wizard. This information is used to create the data source for the WebSphere Process Server.
  • Create the data source on the JDBC provider.

Deployment manager profile

The profile action scripts are located at the following directory after installation of WebSphere Process Server:

install_root/dbscripts/CommonDB/dbType

or if you defer creation of the database until after you have created the profile the scripts will be found in:

install_root/profiles/profilename/dbscripts/CommonDB/dbType/dbName

The scripts are ready to execute, but you can edit them to include any specific requirements. If you try to start WebSphere Process Server before creating the database you will receive an error message.

The scripts perform the following steps:
  • Create a new database if asked (valid only for a local database), depending on your choices in the Database configuration panel in the Profile wizard. See Restrictions for details on database commands that are not supported by the Profile wizard.
  • Create a data source on the JDBC provider (also at the cell level).

Custom (managed) profile

The profile action scripts are located at the following directory after installation of WebSphere Process Server:

install_root/dbscripts/CommonDB/dbType

or if you defer creation of the database until after you have created the profile the scripts will be found in:

install_root/profiles/profilename/dbscripts/CommonDB/dbType/dbName

Note: You must select the same database type as the deployment manager profile. The data source is maintained only at the cell level.

SQL scripts

SQL scripts allow you to configure your database after profile creation. Tables are created with a deployment manager profile and so there are no SQL scripts executed as part of managed node creation.

SQL scripts for each Common database client can be found in the following locations:

install_root/dbscripts/CommonDB/dbType

or if you defer creation of the database until after you have created the profile the scripts will be found in:

install_root/profiles/profilename/dbscripts/CommonDB/dbType/dbName

The SQL script naming convention is:
  • For a component-specific script: createTable_componentName.sql. For example createTable_Recovery.sql.
  • For a component independent script: createTable.sql.

JDBC provider

If an appropriate JDBC provider does not exist one is created.

A data source is created with JNDI name jdbc/WPSDB.

Restrictions

There are several restrictions on the database commands that are available to the user during profile creation.

Create new database is disabled for the following database types:
  • DB2 Universal Database for z/OS and OS/390® V7.1
  • DB2 Universal Database for z/OS V8.1
  • Oracle OCI client
  • Oracle Thin

Tables

The Common database scripts create only static tables during profile creation. The following table gives a list of all the tables that are created by different components.
Table 2. Tables created by WebSphere Process Server components
Component Table names Scripts
Recovery FAILEDEVENTS FAILEDEVENTBOTYPES FAILEDEVENTMESSAGE createTable_Recovery.sql
Mediation MEDIATION_TICKETS createTable_mediation.sql
Relationship Dynamic table, created at runtime createTable_Relationship.sql
Application Scheduler WSCH_LMGR WSCH_LMPR WSCH_TASK WSCH_TREG createTable_AppScheduler.sql
Customization (selector/business rule group) BYTESTORE BYTESTOREOVERFLOW APPTIMESTAMP createTable_customization.sql
Common database SchemaVersionInfo createTable_CommonDB.sql
All the above SQL scripts are executed by commonDBUtility.ant from each component script, such as configRecovery > commonDBUtility > execute createTable_Recovery.sql.

Exported scripts

Database scripts are exported to the following folder:
install_root/profiles/profilename/dbscripts/CommonDB/dbType/dbName

Scripts are created for any option chosen on the Profile wizard panel used to configure the Common database (Create a new (local) database, Use an existing database, and Set up a new or existing database separately). The scripts contain only basic creation statements for databases, tables, and indexes. The database administrator must use database native commands to execute these scripts.

If the option Set up a new or existing database separately is selected, you can also create your database tables using the provided batch or shell file. The file invokes all the necessary scripts with the native database commands that are required to invoke them. The files are called configCommonDB.bat or configCommonDB.sh for Windows and UNIX-based operating systems, respectively. The file is created in the same directory as the scripts: install_root/profiles/profilename/dbscripts/CommonDB/dbType/dbName.

User ID privileges

The user credentials that you provide in the Profile wizard should have sufficient permissions to be able to create tablespaces, tables, indexes, and stored procedures. For the Create a new (local) database option, the user identity must have the necessary privileges to create a new database.


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)