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


Selector and business rules group database configurations

Use the Selector and business rules group database specifications to find information about supported database types; scripts and their locations; profile creation configuration actions; restrictions; table names; and user ID privileges.

When you install an application containing selector or business rule artifacts, the server stores these artifacts in database tables so that you can dynamically update them without changing the application. The selector and business rules group components use a database to hold the selector and business rule artifacts that are created in WebSphere® Integration Developer and installed on the server. If you make any changes to a selector through the administrative console or to business rules through the business rule manager, the database is updated with the latest information. The original artifacts in the EAR are not synchronized with any updates made after the application is installed.

Supported database types

The selector and business rules group 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.

When running the configuration script with the response file standAloneProfile.rsp, Derby is the database engineand a separate RepositoryDB is used.

Database Management Service (DBMS) instances

Only one database instance is available in a stand-alone configuration or network deployment configuration (server or cluster of servers). All selectors and business rules for the server in a stand-alone configuration or in a cell use the same repository. There is no support for using separate database instances for different selectors or business rules.

Database actions invoked by the product configuration script

Stand-alone configuration
  • If you are configuring WebSphere ESB for a stand-alone application server using the response file (standAloneProfile.rsp) with Derby the configDynamicArtifactRepository.ant script is invoked by the configuration script zWESBConfig.sh. This script calls the configDynamicArtifactRepository.jacl command to create the Derby JDBC provider at the node level for the RepositoryDB.
  • The RepositoryDB database is created in /configuration_root/app_server_root/derby/databases/RepositoryDB. The default profile for the server installation will use the same database. Multiple servers cannot be started and use rules, as Derby allows only one JVM to access the database at a time.
  • If you use a stand-alone with DB2 these database objects are generated in the scripts for the Common database.

Deployment manager configuration

If you are configuring WebSphere ESB for network deployment configuration using the response file DmgrDB2.rsp, the Common database for the cell is expected to be set up with the appropriate tables for selector and business rule group components. All selectors and business rules for the server in a deployment manager or managed node will use this database.

SQL scripts

For information about the SQL scripts that you can use to create tables see Scripts for configuring DB2 on a remote z/OS® server.

JDBC provider

The Selectors and Business Rules uses the Common database data source and JBDC provider:

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

Restrictions

When applications that contain selectors or business rules are uninstalled from the server or cell, the artifacts stored in the Common database or RepositoryDB databases are not removed. These must be removed manually following the instructions in the topic: "Removing business rule and selector data from the repository."

When you uninstall applications which contain Selectors or Business Rules from a server or cell, the artifacts stored in the Common database are not removed. These must be removed manually per the instructions in the Information Center: "Removing business rule and selector data from the repository."

Tables

For selectors and business rule groups, there are three tables which are used to hold the artifacts:
  • ByteStore
  • ByteStoreOverflow
  • AppTimestamp

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