Using the ODA Java interface, a developer can create an ODA driver that pools connections. For example, when a Factory process uses an ODA driver, the driver can create a connection to the data source. When the Factory process requests another connection to the data source, the ODA driver can return a new connection or reuse the previous connection instance. Connection pooling optimizes application performance and improves scalability.

You can use an application server, such as a J2EE application server, to implement a connection pool to a data source that supplies data to iHub. In a typical J2EE application server environment, the connection pool uses a data access object (DAO) to provide a common interface between iHub and the data storage system. A DAO separates the application logic from the data access logic to provide a re‑usable, persistent connection.

Figure 14‑2 shows a J2EE application server configuration that supports multiple Information Console client sessions. Each viewed document contains data extracted by an iHub from a data source using a shared connection.

You need the Deployment Kit option to enable connection pooling for Actuate Java Components.