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.
Database Types | Considerations |
---|---|
Derby Embedded | Used as the default database type for a standalone server. |
DB2 for z/OS v8 |
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.
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.
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.
For information about the SQL scripts that you can use to create tables see Scripts for configuring DB2 on a remote z/OS® server.
The Selectors and Business Rules uses the Common database data source and JBDC provider:
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."