BEA Logo BEA Tuxedo Release 8.0

  BEA Home  |  Events  |  Solutions  |  Partners  |  Products  |  Services  |  Download  |  Developer Center  |  WebSUPPORT


   Tuxedo Documentation   |   Using BEA Jolt with BEA WebLogic Server   |   Local Topics   |   Previous Topic   |   Next Topic   |   Contents


Configuring Jolt for WebLogic Server

This section describes how to set up a BEA Jolt connection pool between the WebLogic Server and the JSL in the Tuxedo domain. Your WebLogic Server must have access to the host running the JSL.

Jolt Startup Class and Connection Pool

You must instruct WebLogic Server to invoke the PoolManagerStartUp class whenever the WebLogic Server is started or restarted. This invocation establishes the pool connection to Tuxedo from the config.xml file, as shown in the following example.

Note: For WebLogic Server 6.0 or later, Jolt startup classes and connection pool attributes are configured via the configuration MBeans in the Administration Console. For more information about configuration and run-time MBeans, refer to the BEA WebLogic Server Administration Guide.

Name="MyStartup Class"
Name="MyJolt Connection Pool"

The startup class in the preceeding example instructs WebLogic Server to invoke the PoolManagerStartUp class when the WebLogic Server starts. The JoltConnectionPool specifies initialization arguments that are passed to the PoolManagerStartUp class.

Jolt Connection Pool Attributes

The Jolt connection pool attributes are defined as follows:


(Optional) Tuxedo application password. This is required only if the Tuxedo authentication level is USER_AUTH or APP_PW.


(Required) Specifies the initial session pool size when the session pool is created.


(Required) Specifies the maximum session pool size. Each session within a pool can handle up to 50 outstanding requests at any one time.


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


(Required) Defines a list of the addresses of the primary Jolt Server Listeners (JSLs) on the Tuxedo system. These are defined in the format:
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.


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


(Required) Specifies the amount of time the client should wait to receive a response before timing out.


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


(Required) Specifies the target servers for the connection pool.


(Optional) Tuxedo user name. This is required only if the Tuxedo authentication level is USER_AUTH.


(Optional) Tuxedo user password. This is required only if the Tuxedo authentication level is USER_AUTH.


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

Jolt Shutdown Class

To configure WebLogic Server to disconnect the Jolt session pools from Tuxedo when it shuts down, add the following lines to the WebLogic Server config.xml file:

ClassName="bea.jolt.pool.servlet.weblogic.PoolManager ShutDown."

The shutdown class instructs WebLogic Server to invoke the PoolManagerShutDown class when the WebLogic Server shuts down.


back to top previous page next page