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 the artifacts in database tables. You can then 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 Integration Designer and installed on the server. If you change a selector through the administrative console, or a business rule through the Business Rules Manager, the database is updated with the latest information. The original artifacts in the enterprise archive (EAR) are not synchronized with updates that are made after the application is installed.
| Database Types | Considerations |
|---|---|
| DB2® Express® | Used as the default database type for a stand-alone profile. |
| DB2 Universal | Used as the database in network deployment configurations. Optionally, can be used as the database in stand-alone server configurations. |
| DB2 Data Server | 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. |
| Microsoft SQL Server (Microsoft) | |
| Oracle | You need system database administrator privileges to create the database, tables, and schemas. If you do not have these privileges, you might receive errors when you create or access the tables and schemas. |
The user credentials that you provide in the Profile Management Tool must have the permissions necessary to create table spaces, tables, schemas, indexes, and stored procedures. For the Create new database option, the user ID must have the necessary privileges to create a database. If the user who is running the script has the authority to create tables, the script does not require an authentication ID within the script. For more information, see "Users and schemas for databases" and "Database privileges".
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.
See the common database specifications for SQL script locations.
The selector and business rules group database uses the common database data source and JBDC provider:
If you uninstall applications that contain selectors or business rules from the server or cell, artifacts stored in the common database or RepositoryDB databases are not removed. For information on how to manually remove the artifacts, see "Removing business rule and selector data from the repository."
If you uninstall applications that contain selectors or business rules from a server or cell, artifacts stored in the common database are not removed. For information on how to manually remove the artifacts, see "Removing business rule and selector data from the repository."
The scripts are exported to the same location as the scripts for the common database. For information on script locations, see "common database specifications".