The fundamental object types that maintain the communications connection from the WebLogic Java HTTP servlet to the Jolt Server and from the Jolt Server to Tuxedo, are as follows:

• Session

  A session object represents a physical connection with the Tuxedo system.

• SessionPool

  A session pool contains one or more sessions. The sessions in the session pool are reused for efficiency. Your WebLogic servlet uses sessions to invoke services in Tuxedo through the methods of a session pool. Session pools are initialized by the WebLogic server at startup and configured by attributes in the config.xml file.

  Note:

  For Oracle WebLogic Server 6.0 or later, the xml-based config.xml configuration file has replaced the weblogic.properties file. For more information about the config.xml file, refer to the Oracle WebLogic Server Administration Guide.
• SessionPoolManager

  Use the session pool manager to get a reference to a session pool and to create, administer, and remove session pools. The session pool manager is created just before the WebLogic Server initializes the first session pool.

The following figure shows the architecture for Oracle Jolt for Oracle WebLogic Server.

Figure 1-1 Oracle Jolt for Oracle WebLogic Server Architecture