A database component is a grouping of database objects that can be used by one or more modules. For example, Integration Servers write process status data to the Process Audit Log database component; My webMethods Server reads the data from the Process Audit Log database component and passes it to My webMethods to display. Each database component is named for the type of data that is written to it; for example, the database component for IS Core Audit Log data is called the ISCoreAudit database component.

Some modules use Java Database Connectivity (JDBC) to interact with their databases; specifically, to query and update data in database components.

All other modules use the DataDirect Connect JDBC 5.1 driver. The products come with the client component of this driver; it is a Type 5 JDBC native-protocol driver that does not have a server component. The products use the driver to convert JDBC requests from Java programs directly into the vendor-specific database protocol that each type of RDBMS can understand. The products execute DDL commands at install time and sometimes design time for each RDBMS with which they interact. For information about the DataDirect Connect JDBC driver, see DataDirect Connect for JDBC User's Guide and Reference 5.1, available in the same location as the rest of the webMethods product documentation.

To enable products to interact with a database component, you provide database connection parameters, usually during product installation, and the Software AG Installer uses the parameters to configure JDBC connection pools. After product installation and database component creation is complete, you set up the modules to use the appropriate connection pools.

For the list of RDBMSs supported by your products, see the webMethods and Intelligent Business Operations System Requirements.

For instructions to configure the databases, please refer to the Installing webMethods and Intelligent Business Platform document.