Database Connections for Integration Server and Hosted Products or Microservices Container

You use Integration Server Administrator or Microservices Container Administrator to connect Integration Server or Microservices Container to database components, as follows:

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

Integration Server Administrator and Microservices Container Administrator provide functions that correspond to most database components (for example, an ISCoreAudit Log function that corresponds to the ISCoreAudit database component, an Xref 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 or Microservices Container installation, if you chose an external RDBMS for the product database components and supplied the database connection parameters, the installer automatically did the following:

Created a default connection pool from the database connection parameters you supplied. The pool is named based on the value you supplied in the Connection name field on the installer panel.

Pointed the Xref, DocumentHistory, ISInternal, ISCoreAudit, ProcessAudit, and ProcessEngine functions at that pool.

Note:

If you created the BusinessRules database component, you created it in the same schema or database as the ProcessAudit database component. Integration Server therefore writes to the BusinessRules database component using the ProcessAudit function. There is no separate function for the 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 or Microservices Container creates a separate instance of the appropriate connection pool for each database component.

In the case of Integration Server, you also use Integration Server Administrator to connect other products to database components, as follows:

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 TN 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 or Microservices Container can authenticate clients using internally-defined user and group information, or 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 or Microservices Container must have a connection pool that points to the My webMethods Server database component, and the CentralUsers function in Integration Server or Microservices Container must point at that connection pool.

If you installed My webMethods Server in the same directory as Integration Server or Microservices Container, 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 or Microservices Container, you must create the connection pool and point the CentralUsers function at that pool using Integration Server Administrator or Microservices Container Administrator and the instructions below.