Database Connections for Integration Server and Hosted Products

You define JDBC database connection pools in Integration Server Administrator. Each pool defines the connection to a database server that hosts database components.

Integration Server Administrator provides functions that correspond to most database components (for example, IS Core Audit Log function that corresponds to the ISCoreAudit database component, a Cross Reference function that corresponds to the CrossReference database component, and so on). You direct each function to write to its database components by pointing the function at the appropriate connection pool.

During Integration Server installation, if you chose an external RDBMS for the Integration Server database components and supplied the database connection parameters, the installer automatically did the following:

Pointed the Cross Reference, Distributed Locking, Document History, IS Internal, IS Core Audit Log, Process Audit Log, and Process Engine functions at that pool.

Note:

If you created the MediatorEvents database component, you created it in the same schema or database as the IS Core Audit Log. Integration Server therefore writes to the MediatorEvents database component using the IS Core Audit Log function. Similarly, if you created the BusinessRules database component, you created it in the same schema or database as the Process Audit Log. Integration Server therefore writes to the BusinessRules database component using the Process Audit Log function. There is no separate function for the MediatorEvents or BusinessRules database component.

You can edit the default connection pool using the instructions in this section, or you can create separate pools and redirect individual functions to use them. At run time, Integration Server creates a separate instance of the appropriate connection pool for each database component.

During Trading Networks Server installation, you supplied the database connection parameters for the TradingNetworks database component. The installer created a connection pool from those parameters and pointed the Trading Networks function at that pool. You can edit the connection using Integration Server Administrator and the instructions below. The same is true for ActiveTransfer Server and Mobile Support.

If you created the CloudStreamsEvents database component, you must point that function at a connection pool. The same is true for the Archive, Staging, and Reporting database components.

Integration Server can authenticate clients using internally-defined user and group information, or it can use the My webMethods Server central user management feature. To use the latter, and to use the single sign on feature for My webMethods Server, Integration Server must have a connection pool that points to the My webMethods Server database component, and the CentralUsers function in Integration Server must point at that connection pool.

If you installed My webMethods Server in the same directory as Integration Server, the installer created a connection pool from the My webMethods Server database parameters you supplied and pointed the CentralUsers function at that pool. If you installed My webMethods Server in a different directory from Integration Server, you must create the connection pool and point the CentralUsers function at that pool using Integration Server Administrator and the instructions below.