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.
For stand-alone profile creation where Cloudscape is selected, a separate RepositoryDB is used.
Only one database instance is available in a stand-alone profile or network deployment configuration (server or cluster of servers). All selectors and business rules for the server in a stand-alone profile 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 profile
For network deployment configuration, 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 custom profile will use this database.
The SQL scripts for table creation are available at install_root/dbscripts/CommonDB/dbType.
The Common database data source is used.
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.
The scripts are exported to the same location as the scripts for the Common database, except when using Cloudscape where no scripts are exported.
The user credentials that you provide must have sufficient permission to be able to create tablespaces, tables, indexes, and stored procedures.
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)