BEA Jolt is Java based interface to BEA Tuxedo System.

JOLT COMPONENTS

• Jolt Servers - One or more Servers listen for network connections from clients, translate Jolt messages, submit and retriew requests to and from Tuxedo Applications.
• Jolt Class Library for Java - A package of classes to enable Java Applications and Applets to invoke Tuxedo Services.
• Jolt Repository - A set of tools containing GUI based online administrative tools to give Java client application controlled access to Tuxedo servers and servers to update the Jolt Repository file.
• Jolt Internet Relay - A component consisting of Jolt Relay Server and Jolt Relay Adapter. This is used to eliminate the need for Tuxedo and the Web-Server to run on the same machine.


(Note: See enclosed Typical System Design diagram bellow for illustrations on how Jolt Relay, Jolt Servers and Tuxedo interact.)

JOLT SERVERS

• JSL - Jolt Server Listener handles Jolt client connection and is responsible for assigning a Jolt server Handler the Jolt Client.
• JSH - Jolt Server Handler  manages the network connectivity, executes service requests on behalf of client and translates Tuxedo buffer data into Jolt buffer and vice-versa.
• JREPSVR - Jolt Repository Server retrieves Jolt service definitions to JSH, updates or adds Jolt Service definitions.

JOLT INTERNET RELAY

• JRLY - Jolt Relay is is NOT a Tuxedo client or server. It is a stand-alone component that routes Jolt messages from a Jolt client to a JSL or JSH.
• JRAD - Jolt Relay Adapter is a Tuxedo aplication Server, but does not include Tuxedo services. JRAD receives client requests from JRLY and forwards the request to JSL/JSH. The responses received are forwarded back to JRLY.

Diagram Under Preparation

Typical System Design using JOLT-TUXEDO Middleware

JOLT CLASS LIBRARY

• One package only. Imported as: import bea.jolt.*;
• Some important classes are:
• JoltSessionAttributes - defines acceptable attributes for the JoltSession constructor.
• JoltSession - Represents the logon session object and is used to access Tuxedo Services.
• JoltRemoteService - Used to perform Request/Reply call.
• JoltRequestMessage - An abstract class inherited by JavaRemoteService.
• JoltTransaction - Used to indicate transaction timeout and the instance is passed as an attribute of JavaRemoteService.call().
• JoltEvent - A base class further inherited by class JoltUserEvent.
• JoltUserEvent - Extends JoltEvent. Used for subscription to an unsolicited notification or Event notification.
• JoltReply - JoltReply is a placeholder of the mesage for unsolicited messages or event notifications.
• Some important methods:
• JoltSessionAttributes.checkAuthenticationLevel()
• JoltSession.JoltSession() - Constructor implicititly attaches to client to Tuxedo. (Unlike JRS in BEA TopEnd Midleware which has separate method initialize()!)
• JoltSession.endSession()
• JoltRemoteService.call()(Transaction t)
• JoltRequestMessage - all get and set methods. Note that FML Field names match corrctly with that of /Tuxedo.
• JoltTransaction.commit(); JoltTransaction.rollback()
• JoltEvent.unsubscribe(); JoltEvent.subscribeAll()
• JoltUserEvent - Subscription to notification is done by the constructor.
• JoltReply.getMessage()

JOLT CONFIGURATION

Typical Configuration file for intgration Jolt with Tuxedo is given in the UBBCONFIG file.
 

EXAMPLES on JOLT
 

Examples Yet To Be Uploaded!!

REFERENCE

BEA Documentation on TUXEDO and JOLT.
 

<  BACK <