HP NonStop G-Series - Manual (Page 18)

3. Configuring the Jolt System
This chapter explains how to configure Jolt 1.1 and describes the Jolt Internet Relay, Event Subscription, and
security features. Readers of this chapter are assumed to be system administrators and/or application developers
who have experience with the operating systems and workstation platforms on which they are going to
configure TUXEDO and Jolt.
This chapter includes the following sections:
Using the Jolt Server ●
Using the Jolt Repository ●
Event Subscription ●
Jolt Internet Relay ●
Using the Jolt Server
The Jolt Server consists of listeners and handlers.
Jolt Server Listener (JSL). The JSL is configured to support clients on an IP/port combination.The JSL works
with the Jolt Server Handler (JSH) to provide client connectivity to the backend of the Jolt system. The JSL is
administered by the same tools used to manage any resource within a NonStop TUXEDO environment.
Jolt Server Handler (JSH). The JSH is a program that runs on a TUXEDO server machine to provide a
network connection point for remote clients. The JSH works with the JSL to provide client connectivity
residing on the backend of the Jolt system.
The system administrator's responsibilities for the server components of Jolt include:
Determining server network addresses. ●
Determining the number of Jolt clients to be serviced by one JSH (for example, if there are 10 clients per
JSH and 10 JSHs, 100 clients can be connected). ●
Determining the minimum and maximum number of JSHs. ●
Jolt Internet Relay
The Jolt Internet Relay is a component that routes messages from a Jolt client to a JSL or JSH. This alleviates
the need for the JSL/JSH and TUXEDO to run on the same machine as the Web server. The Jolt Relay (JRLY)
is not required to be a TUXEDO server or a TUXEDO client. It is a stand-alone piece of software that routes
the Jolt messages to the JSL or JSH. Refer to the
Jolt Internet Relay in this chapter.
Security and Encryption
When you enable encryption support, Jolt uses DES encryption algorithms to encrypt authentication and key
exchange data that is transmitted between a Jolt client and a Jolt server. All subsequent exchanges are
encrypted using RC4 encryption.
If 128-bit encryption is enabled, a 128-bit RC4 session encryption key is generated at logon time, and this
session key is transmitted over the network in a message protected by 56-bit DES encryption. The temporary
session key is then used to encrypt the session's data. The overall security level achieved is equivalent to 56-bit