You can access session pools through the SessionPoolManager class. WebLogic Server uses a variation of the session pool called a servlet session pool. The servlet session pool provides extra functionality that is convenient for use inside an HTTP servlet.

When you configure a servlet session pool through the WebLogic Administration Console, the following information is added to the config.xml configuration file:

<StartupClass
   ClassName="bea.jolt.pool.servlet.weblogic.PoolManagerStartUp"
   FailureIsFatal="false"
   Name="MyStartup Class"
   Targets="myserver"
/>
<JoltConnectionPool
   ApplicationPassword="tuxedo"   
   MaximumPoolSize="5"
   MinimumPoolSize="3"
   Name="MyJolt Connection Pool"
   PrimaryAddresses="//TUXSERVER:6309"
   RecvTimeout="300"
   SecurityContextEnabled="true"
   Targets="myserver"
   UserName="joltuser"
   UserPassword="jolttest"
   UserRole="clt"
/>

When WebLogic is started (or restarted), it invokes the PoolManagerStartUp class and its associated startupArgs. On the first invocation, the PoolManagerStartUp class creates a ServletSessionPoolManager object, which contains every ServletSessionPool configured in the config.xml configuration file.

Subsequent calls add another ServletSessionPool to the same ServletSessionPoolManager. You must add an entry for each session pool, using a unique virtual name binding for each, as shown in the preceding example. The WebLogic Server creates a new ServletSessionPool as defined in the config.xml file.

For additional information about property settings and a list of definitions, see “Jolt Startup Class and Connection Pool”.

• Accessing a Servlet Session Pool