1. Using Oracle Jolt with Oracle Weblogic Server
  2. Configuring Jolt for WebLogic Server
  3. Configuring Jolt for WebLogic Server
  4. Jolt Startup Class and Connection Pool
  5. Jolt Connection Pool Attributes

2.2.1.1 Jolt Connection Pool Attributes

The Jolt connection pool attributes are defined as follows:

Attributes Description
Application Password (Optional) Tuxedo application password. This is required only if the Tuxedo authentication level is USER_AUTH or APP_PW.
MinimumPoolSize (Required) Specifies the initial session pool size when the session pool is created.
MaximumPoolSize (Required) Specifies the maximum session pool size. Each session within a pool can handle up to 50 outstanding requests at any one time.
Name (Optional) Defines a name for this session pool that should be unique from the names of other session pools. This is an optional argument, but it is recommended that you use it to avoid ambiguity.

The SessionPoolManager allows only one session pool to remain unnamed. You can access this unnamed session pool from your application by supplying null in place of the poolname string argument to the getSessionPool() method

Note:

We strongly recommend that you name every session pool.
PrimaryAddresses (Required) Defines a list of the addresses of the primary Jolt Server Listeners (JSLs) on the Tuxedo system. These are defined in the format: //hostname:port

where hostname is the name of the server where the JSL is running, and port is the port on which the JSL is configured to listen for requests. You can specify multiple addresses in a semicolon-separated (;) list

Note:

You must specify at least one primary JSL hostname:port address.
Failover Addresses (Optional) You can specify a list of failover Jolt Server Listeners in the same format used for appaddrlist above. Jolt attempts to use these failover JSL(s) if the primary JSLs listed above fail. These JSLs need not reside on the same host as the primary JSLs.
RecvTimeout (Required) Specifies the amount of time the client should wait to receive a response before timing out.
SecurityContext Enabled (Optional) Enables or disables the security context for this connection pool. This option should be enabled if you want to implement authentication propagation between WebLogic Server and Jolt. If identity propagation is desired, then the Jolt Service Handler (JSH) must be started with the -a option. If this option is not set, but SecurityContext is enabled, the JSH will not accept this request. If the SecurityContext attribute is enabled, then the Jolt client will pass the username of the caller to the JSH.

If 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.

Targets (Required) Specifies the target servers for the connection pool.
UserName (Optional) Tuxedo user name. This is required only if the Tuxedo authentication level is USER_AUTH.
UserPassword (Optional) Tuxedo user password. This is required only if the Tuxedo authentication level is USER_AUTH.
UserRole (Optional) Tuxedo user role. This is required only if the Tuxedo authentication level is USER_AUTH or APP_PW.

It is recommended that you configure one Jolt session pool for each application running on the WebLogic Server.

Parent topic: Jolt Startup Class and Connection Pool