WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Common database configurations

The Common database configurations contain information about supported database types; scripts and their locations; installation parameters; types of created tables and user ID privileges.

The Common database acts as a repository for various components. 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 configurations, create the database objects later by using the scripts that are generated during the configuration.

The WebSphere® ESB Common database is used by the following product components: You can either create the Common database when you run the product configuration script, or after you have configured WebSphere ESB by running the SQL that is generated as part of the configuration process. The SQL includes the database information that you provided in the response file.

If you prefer to use a single database for all the database objects that the node needs, you can run the createDB.sh script after configuring WebSphere ESB. The createDB.sh script creates and populates a single database with all the database objects required for WebSphere ESB. See "createDB.sh script" for more information.

If you prefer to use multiple databases for the database objects, you can create and populate the Common database manually using the SQL scripts that are supplied and generated. See "Creating the DB2 databases and storage groups using DButility,sh, SPUFI, or DSNTEP2" for more information.

You can optionally create the Common database before configuration but you cannot populate the Common database until after configuration because the SQL scripts are generated when you run the configuration script.

Supported database types

The Common database can use the following database products:
Table 1. Supported database products
Database Types Considerations
Derby Embedded Used as the default database type for a standalone server.

DB2 for z/OS v8
DB2 for z/OS v9

Important: When creating a profile for a server that uses DB2 for z/OS v9, the server must be able to connect to the DB2 database.
Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations.

User ID privileges

Generally the user credentials that you provide in the response file should be able to create table spaces, tables, indexes, and stored procedures. For Create new database option, the user identity should have the necessary privileges to create a new database.

Database Management Service instances

There is one set of common database tables per cell.

Database actions invoked by the product configuration script

After the SMP/E installation of WebSphere Process Server, the SQL scripts are located in the configuration file system of the node's profile directory. For example, for a stand-alone server configuration installed in the default location and using DB2 v8.1: /WebSphere/V6R1/AppServer/profiles/default/dbscripts/CommonDB/database_type/database_name

For a network deployment configuration installed in the default location and using DB2 v8.1: /WebSphere/V6R1/DeploymentManager/profiles/default/dbscripts/CommonDB/database_type/database_name

Where /WebSphere/V6R1 is the default location of the configuration file system, database_type is the version of the database that you are using to create the database, and database_name is the name of the database.

If you are configuring a stand-alone server using Derby, the database objects, including tables, are created by the configuration script (zWPSConfig.sh [filter for WESB to zWESBConfig.sh]) 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.

JDBC provider

A new JDBC provider is created depending on the database type. The provider is created in the node scope in a stand-alone profile and at cell level in network deployment environment. JDBC Provider refers to variable JDBC_DRIVER_PATH to locate local JDBC drivers. The variable is specified in cell level and each node level to point to correct local path.

Data source name:
  • WPS DataSource
Data source JNDI name:
  • jdbc/WPSDB

Tables

The following table gives a list of all the tables that are created by different components.
Table 2. Tables created by WebSphere ESB components
Component Table names Scripts
Relationship Dynamic table, created at runtime createTable_RelationshipMetadataTable.sql (create table space, for DB2 z/OS® only)
Common database SchemaVersionInfo createTable_CommonDB.sql
ESB Logger Mediation MSGLOG createTable_ESBLoggerMediation.sql
Note: In the ESB Logger Mediation component, you can configure each message logger primitive to use a different data source and a different database.

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