Jolt Connection Pools: Configuration: General
Configuration Options Related Tasks Related Topics
Use this page to define the general configuration of this Jolt connection pool.
Jolt uses connection pools to enable WebLogic Server clients to connect to BEA Tuxedo domains. WebLogic Server creates the Jolt connection pools at startup and assigns connections to WebLogic Server clients as needed.
Name Description Name
The name of this Jolt connection pool.
Minimum Pool Size
The minimum number of connections to be added to this Jolt connection pool when WebLogic Server starts.
Maximum Pool Size
The maximum number of connections that can be made from this Jolt connection pool.
The number of seconds the client waits to receive a response before timing out.
Security Context Enabled
Indicates whether this Jolt connection pool passes the connection pool's security context (user name, password and other information) from the WebLogic Server user to the Tuxedo domain.
If you enable the connection pool to pass the security context, you must start the Jolt Service Handler (JSH) with the
-aoption. When the JSH gets a message with the caller's identity, it calls
impersonate_user()to get the appkey for the user. JSH caches the appkey, so the next time the caller makes a request, the appkey is retrieved from the cache and the request is forwarded to the service. A cache is maintained by each JSH, which means that there will be a cache maintained for all the session pools connected to the same JSH.
You must enable Security Context if Tuxedo requires secured connections.
- Configure a user identity
- Configure Jolt addresses
- Target Jolt connection pools
- Reset Jolt connections
- Configure Jolt startup and shutdown classes