How Jolt ASP Connectivity for BEA Tuxedo Works


	BEA Home \| Events \| Solutions \| Partners \| Products \| Services \| Download \| Developer Center \| WebSUPPORT
	http://www.oracle.com/technology/documentation/index.html \| Site Map \| Search \| PDF Files \| Contact \| Glossary

Tuxedo Documentation \| Using BEA Jolt \| Local Topics \| Previous Topic \| Next Topic \| Contents \| Index

The Jolt ASP Connectivity for BEA Tuxedo architecture includes three main components: a session, a session pool, and a session pool manager. A session object represents a connection with the BEA Tuxedo system. A session pool represents many physical connections between the Web server and the BEA Tuxedo system. It also associates a session with an HTTP request.

The session pool manager is responsible for maintaining a set of session objects, each having a unique session identifier.

Jolt ASP Connectivity for BEA Tuxedo works as follows:

If the Web application has not been initialized, the Web application initializes the session pool manager, creates a session pool, and establishes sessions (also known as connections) with the Jolt Server.
When a service request arrives, the Web application gets a session pool object from the session pool manager. The session pool invokes the service call using the session that is the "least busy," based on the number of outstanding call requests on a given session.
If the selected session is terminated by the Jolt Server, the session pool object restarts a new session or reroutes the request to another session. If the session pool manager is unable to get any session, a null session object is returned.

A graphical representation of the ASP Connectivity for BEA Tuxedo architecture is shown in the following figure.

Jolt ASP Connectivity for BEA Tuxedo Architecture

Refer to the online BEA Jolt API Reference for additional information about the SessionPool class and SessionPoolManager class.