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 standalone profile. |
Derby Network Server | Used as the default database type in network deployment environment. |
DB2 Universal | Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations. |
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. |
DB2 UDB for iSeries (Native) |
Used as a local database for standalone profile. |
DB2 UDB for iSeries (Toolbox) |
Used as a remote database for network deployment environment or as a local database for a standalone profile.Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations. |
DB2 Universal Runtime Client | Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations. |
Informix Dynamic Server | |
Microsoft SQL Server (Embedded) | |
Microsoft SQL Server (DataDirect) | |
Microsoft SQL Server (Microsoft) - Support for the Microsoft SQL Server JDBC Driver, version 1.2 was added in WebSphere Process Server, version 6.2.0.1 | |
Oracle 9i |
You need sysdba privilege to create the database, tables and schemas. Failure to have the correct sysdba privilege can result in errors creating and accessing the tables and schemas. |
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.
Stand-alone profile
During profile creation, the Common database uses createTable to create Business Rules and Selector tables. If you choose the default configuration, the default database is Derby Embedded. However, you cannot use multiple servers because Derby Embedded allows only one Java™ virtual machine to access the database at a time.
Deployment manager profile
For network deployment configuration, the Common database for the cell is 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.
See the Common database specifications for SQL script locations.
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."
The scripts are exported to the same location as the scripts for the Common database, except when using Derby Embedded, where no scripts are exported. See the "Common database specifications" for script locations.