BEA Logo BEA WebLogic Server Release 1.1

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

   Jolt for WebLogic Server User's Guide:   Previous topic   |   Next topic   |   Contents   |  Index


Configuring Jolt for WebLogic


Configuring a Jolt Session Pool connection between Tuxedo and WebLogic requires two procedures:

Configuring Jolt for Tuxedo

Refer to the Jolt User's Guide for instruction on setting up a Jolt Service Listener (JSL) within Tuxedo. In the Jolt User's Guide it is assumed that JSL services have already been configured within the Tuxedo domain. The guide only describes how to establish a session pool connection to these services from WebLogic.

Configuring Jolt for WebLogic

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 Properties

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



These example properties are already included in the default WebLogic properties file, but they are commented out. In order to make the properties take effect, you must find them, adjust them for your system configuration, and uncomment them. Then start (or restart) the WebLogic Server.

The first property in the preceding example (weblogic.system.startupClass.joltpool) instructs WebLogic to invoke the PoolManagerStartUp class when the WebLogic Server starts. The second property (weblogic.system.startupArgs.joltpool) specifies initialization arguments that are passed to the PoolManagerStartUp class. These arguments are defined as follows:


(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. It is the JSLs that service your servlet's Jolt requests. 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 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) 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.


(Optional) Tuxedo application password. 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 Properties

Configure WebLogic to disconnect the Jolt session pools from Tuxedo when it shuts down by adding the following lines to the WebLogic properties file (or uncommenting the appropriate lines if they already exist).


where myJoltPool is the name of the Jolt pool to be disconnected at shutdown.

The first property instructs WebLogic to invoke the PoolManagerShutDown class when the WebLogic Server shuts down. The second property describes arguments passed to the PoolManagerShutDown class, defining the poolname of the Jolt session pool to be closed. The second property is associated with the first through the virtual name binding-in this case, joltapp. The poolname will be specific to your application.

Displaying Jolt in the WebLogic Console

If you are connecting to a WebLogic Server that has Jolt correctly installed and configured, when you start the WebLogic Console you will see a managed object for the Jolt connection pool displayed in the WebLogic Console, as shown in Figure 2-1.

Figure 2-1 WebLogic Server Console with Jolt Connection Pool

For each Jolt connection pool there is an individual ManagedObject that displays the pool name, maximum connections, pool state, and statistics about the connection status.