Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Configuring Database Sessions (ELUG)
This section describes the various components that you must configure in order to use database sessions.
Configurable Options for Database Session lists the configurable options for database sessions.
Introduction to Database Session Configuration
This table lists the configurable options for database sessions.
Configurable Options for Database Session
Option | Workbench |
Java |
---|---|---|
External connection pools (see Configuring External Connection Pools) |
||
Primary mapping project (see Configuring a Primary Mapping Project) |
||
Session login (see Configuring a Session Login) |
||
Logging (see Configuring Logging) |
||
Multiple mapping projects (see Configuring Multiple Mapping Projects) |
||
Performance profiler (see Configuring a Performance Profiler) |
||
Exception handler (see Configuring an Exception Handler) |
||
Session customizer class (see Configuring a Session Customizer Class) |
||
Server platform (see Configuring the Server Platform) |
||
Session event listeners (see Configuring Session Event Listeners) |
||
Coordinated cache (see Configuring a Coordinated Cache) |
||
Integrity checker (see Configuring the Integrity Checker) |
||
Named queries (see Configuring Named Queries at the Session Level) |
Configuring External Connection Pools
Unlike a server session, a database session does not provide internal connection pools. A database session only has a single database connection that it uses for its life cycle.
We recommend that you use a server and client session in a three-tier environment. Alternatively, you can use a database session with an external connection pool (see Configuring External Connection Pooling): in this case, you should allocate a new database session per user/thread or request.
WARNING: Do not allow the concurrent use of a database session by multiple users/threads. |
The usage of an external connection pool reduces the number of the database session login and logout attempts to acquire the database connection.