Skip Headers

# Configuring External Connection Pooling

Previous

Next

For non-J2EE applications, you typically use internal connection pools provided by TopLink (see "Internal Connection Pools"). In this case, you can use TopLink Workbench to configure connection pool options and to create a sequence connection pool and application-specific (named) connection pools.

For J2EE applications, you typically use external connection pools provided by a JDBC driver or J2EE container (see "External Connection Pools"). Optionally, you can configure a read connection pool to use a nontransactional login, and you can configure a sequence connection pool to use a separate (preferably nontransactional) login of its own.

Because JTA external transaction controllers are dependent upon the external transaction service that the application server provides, you must configure TopLink to use external connection pools if you are using an external transaction controller (see "Integrating the Unit of Work With an External Transaction Service").

External connection pools enable your TopLink application to do the following:

- Integrate into a J2EE-enabled system.

- Integrate with JTA transactions (JTA transactions require a JTA-enabled data source).

- Leverage a shared connection pool in which multiple applications use the same data source.

- Use a data source configured and managed directly on the server.

For more information about connection pools, see "Connection Pools".