Overview
When you choose to use an external RDBMS while installing Integration Server, the installer asks you to supply the database connection. From this information, the installer creates a JDBC connection pool and configures Integration Server to write the following data to the external RDMS using that pool:
IS Internal
IS Core Audit Log
Cross Reference
Distributed Locking
Document History
Process Audit Log
Process Engine
To create additional JDBC connection pools or reconfigure Integration Server to write different types of data using different pools, you can do so using the Integration Server Administrator. The JDBC Pools screen enables you to specify the connection to a database server that hosts database components. The JDBC Pools screen enables you to manage the following:
Functional aliases
Pool aliases
Driver aliases
A
functional alias is a connection pool that corresponds to a specific database component (such as Scheduled Tasks and the
Trading Networks Audit Log). The functional alias directs auditing data and other information to a particular JDBC database. Functional aliases are predefined for the
Integration Server during installation. You cannot add or delete functional aliases, but you can change the JDBC connection pool to which a functional alias is assigned. For more information about changing the JDBC connection pool for functional aliases, see
Assigning Connection Pools to Functional Aliases.
You direct each function to write to its database components by pointing the function at the appropriate connection pool.
The
pool alias, also called a
connection pool alias, defines the location and connection parameters for the database.
Integration Server uses this information to interact with the database resource. When you create a pool alias definition, you must specify a
driver alias that identifies a database driver to
Integration Server.
Integration Server uses this database driver to connect to the defined database resource. For more information about pool aliases, see
Managing Pool Aliases. For more information about driver aliases, see
Managing Driver Aliases.