Oracle Jolt is a Java class library and API that provides an interface to Oracle Tuxedo from remote Java clients. Oracle Jolt consists of the following components for creating Java-based client programs that access Oracle Tuxedo services:

• Jolt Servers and Repository Servers—one or more Jolt servers listen for network connections from clients, translate Jolt messages, multiplex multiple clients into a single process, and submit and retrieve requests to and from Oracle Tuxedo-based applications running on one or more Oracle Tuxedo servers.
• Jolt Class Library—the Jolt class library is a Java package containing the class files that implement the Jolt API. These classes enable Java applications and applets to invoke Oracle Tuxedo services. The Jolt class library includes functionality to set, retrieve, manage, and invoke communication attributes, notifications, network connections, transactions, and services.
• JoltBeans—Oracle JoltBeans provides a JavaBeans-compliant interface to Oracle Jolt. JoltBeans are Beans components that you can use in JavaBeans-enabled integrated development environments (IDEs) to construct Oracle Jolt clients. Jolt Beans consists of two sets of Java Beans: JoltBeans toolkit (a JavaBeans-compliant interface to Oracle Jolt that includes the JoltServiceBean, JoltSessionBean, and JoltUserEventBean) and Jolt GUI beans, which consist of Jolt-aware Abstract Window Toolkit (AWT) and Swing-based beans.
• Jolt Internet Relay—the Jolt Internet Relay is a component that routes messages from a Jolt client to a Jolt Server Listener (JSL) or Jolt Server Handler (JSH). This component eliminates the need for the JSH and Oracle Tuxedo to run on the same machine as the Web server. The Jolt Internet Relay consists of the Jolt Relay (JRLY) and the Jolt Relay Adapter (JRAD).
• Jolt ECID —The Jolt call process is as follows: JOLT client --> JSL/JSH --> tuxedo server --> service.

1. Jolt Connection Pool supports ECID propagation between Weblogic and Oracle Tuxedo. ECID is propagated and inserted into a request message if java option "-Dtuxedo.ECID_ENABLE" or environment variable "ECID_ENABLE" is set to 'y'. Java option "-Dtuxedo.ECID_ENABLE" has higher priority than environment variable "ECID_ENABLE". ECID also can be sent back within a reply message from Oracle Tuxedo.
2. ECID relies on DMS (Dynamic Monitoring Service), ECID is not supported for standalone jolt client by default. If you want ECID to be created, DMS should be installed first.
3. Jolt ECID does not impact JRLY and JRAD. The format for ECID in jolt client trace is as follows:

   000915:30475@slc05are:1: ECID <0000KqPMc659XbHpIsT4if1LPfwR000001>: atmi: { JoltSession.send(len 132)