Using pools for control reasons
You can use pools for a number of control purposes.
For example, you could define them so as to:
- Restrict users and applications to particular targets or nodes, or restrict access to some targets to particular times of day.
- Force specific begin-session and end-session effects.
- Split resources among different types of back-end requests, according to (for example) priority, or to the department issuing the request. By doing this, you can ensure that there is always a set of connections to a target for time-sensitive requests, while other connections handle long-running requests that are not time-sensitive.
- Ration the use of connections, especially for long-running requests, so that each set of users has access to only a limited number of connections.
- Ease signon considerations.