You define JDBC database connection pools in Integration Server Administrator. Each pool defines the connection to a database server that hosts database components.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, 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.Configured Integration Server to write to the external RDBMS.Created a default connection pool from the Integration Server database connection parameters you supplied.Pointed the Xref, DocumentHistory, ISInternal, ISCoreAudit, ProcessAudit, and ProcessEngine functions at that pool.Note: | If you created the MediatorEvents database component, you created it in the same schema or database as the ISCoreAudit database component. Integration Server therefore writes to the MediatorEvents database component using the ISCoreAudit function. Similarly, if you created the BusinessRules database component, you created it in the same schema or database as the ProcessAudit catabase component. Integration Server therefore writes to the BusinessRules database component using the ProcessAudit function. There is no separate function for the MediatorEvents or BusinessRules 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 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.You must point the Simulation function at the connection pool for the Reporting database component.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.