HP NonStop G-Series - Manual (Page 10)

such as INQUIRY, WITHDRAW, TRANSFER, and DEPOSIT. Typically, service requests are
implemented in C or COBOL as a sequence of calls to a program library. Accessing a library
from a native program means installing the library for the specific combination of CPU and
operating system release on the client machine, a situation Java was expressly designed to
avoid. The Jolt Server implementation acts as a proxy for the Jolt client, invoking the TUXEDO
service on behalf of the client. The Jolt Server accepts requests from the Jolt clients and maps
those requests into TUXEDO service requests.
Figure 1-1. Jolt Architecture
Figure 1-1 illustrates the end-to-end view of the Jolt architecture, as well as related TUXEDO
components and their interactions.
Jolt Servers
The Jolt Server has several components that act in concert to pass Jolt client transaction
processing requests to the TUXEDO application. The components are as follows:
Jolt Server Listener (JSL). The JSL handles the initial Jolt client connection, and is
responsible for assigning a Jolt Server Handler to the Jolt client. ●
Jolt Server Handler (JSH). The JSH manages network connectivity, executes service
requests on behalf of the client and translates TUXEDO buffer data into the Jolt buffer
and vice versa. ●
Jolt Repository Server (JREPSVR). The JREPSVR retrieves Jolt service definitions
from the Jolt Repository and returns the service definitions to the JSH. The JREPSVR ●