HP NonStop G-Series - Manual (Page 260)

walkthrough.
How the Jolt Web Application Services Works
The Jolt Web Application Services architecture includes three main components: a session, a
session pool, and a session pool manager. A session object represents a connection with the
TUXEDO system. A session pool represents many physical connections between the Web
server and the 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.
If the Web application has not be initialized the Web Application initializes the session
pool manager, creates a session pool, and establishes sessions (also known as
connections) with the Jolt Server. 1.
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. 2.
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. 3.
A graphical representation of the Web Application Services architecture is shown in Figure 1-1 .
As shown in the figure, the Web Application Services components reside on the web server.
The Jolt servers and the business application services (for example, services to support banking
transactions) reside on a host system such as a NonStop Kernel system running NonStop
TUXEDO.
Figure 1-1. Jolt Web Application Services Architecture