Connecting Products to Database Components
This section explains how to connect Integration Server and hosted products to their database components. For information on connecting other products such as Optimize to their database components, see the product documentation.
You connect Integration Server to database components as follows:
Define
JDBC database connection pools that specify the connections to database servers that host database components.
Direct predefined
functions to write to their database components by pointing each function at the appropriate connection pool. For example, point the ISCoreAudit Log function to the connection pool for the ISCoreAudit database component, point the Xref function to the connection pool for the CrossReference database component, and so on. At run time,
Integration Server creates a separate instance of the connection pool for each database component.
Integration Server can connect to the ActiveTransfer and ActiveTransferArchive, APIGatewayEvents, Archive, BusinessRules, CloudStreamsEvents, CrossReference, DocumentHistory, ISInternal, ISCoreAudit, MywebMethodsServer, MobileSupport, ProcessAudit, ProcessEngine, and TradingNetworks and TradingNetworksArchive database components.
For instructions on creating connection pools and pointing functions at them, see webMethods Integration Server Administrator’s Guide and the points below.
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.
If you installed the
Integration Server and
Optimize database components in two different schemas, you will have two instances of the Process Audit Log database component. Configure
Integration Server and
Optimize to point to the same instance. You can then drop the other, redundant instance.