With Oracle Jolt, you can leverage existing Oracle Tuxedo services and extend your transaction environment to the corporate intranet or world-wide Internet. The key feature of Jolt architecture is its simplicity. You can build, deploy, and maintain robust, modular, and scalable electronic commerce systems that operate over the Internet.

Oracle Jolt includes the following features:

• Java-based API for simplified development — with its Java-based API, Oracle Jolt simplifies application design by providing well-designed object interfaces. Jolt supports the Java 2 Software Development Kit (SDK) and is fully compatible with Java threads. Jolt enables Java programmers to build graphical front-ends that use the Oracle Tuxedo application and transaction services without having to understand detailed transactional semantics or rewrite existing Oracle Tuxedo applications.
• Pure Java client development — using Jolt, you can build a pure Java client that runs in any Java-enabled browser. Jolt automatically converts from Java to native Oracle Tuxedo data types and buffers, and from Oracle Tuxedo back to Java. As a pure Java client, your applet or application does not need resident client-side libraries or installation; thus, you can download client applications from the network.
• Easy access to Oracle Tuxedo services through Oracle Tuxedo Service Metadata Repository — the Oracle Tuxedo Service Metadata Repository facilitates Java application development by managing and presenting Oracle Tuxedo service definitions that you can use in your Java client. A bulk loading utility lets you quickly integrate your existing Oracle Tuxedo services into the Jolt development environment. Jolt and Oracle Tuxedo simplify network and application scalability, while encouraging the reuse of application components. You can also use tmloadrepos to create or update the binary Tuxedo Service Metadata Repository file and load it with service parameter information. See tmloadrepos(1) for more information.
• GUI-Based maintenance and distribution of Oracle Tuxedo services— the GUI lets you manage Oracle Tuxedo service definitions such as service names, inputs and outputs. The GUI provides support for different input and output names for services defined in the Metadata Repository.
• Encryption for secure transaction processing — Oracle Jolt allows you to encrypt data transmitted between Jolt clients and the JSL/JSH. Jolt encryption helps ensure secure Internet transaction processing.
• Added security through Internet Relay —network administrators can use the Oracle Jolt Internet Relay component to separate their Web server and Oracle Tuxedo application server. Web servers are generally considered insecure because they often exist outside a corporate firewall. Using the Jolt Internet Relay, you can locate your Oracle Tuxedo server in a secure location or environment on your network, yet still handle transactions from Jolt clients on the Internet.
• Event Subscription Support —Jolt Event Subscription enables you to receive event notifications from Oracle Tuxedo services and Oracle Tuxedo clients. Jolt Event Subscription lets you subscribe to two types of Oracle Tuxedo application events:
  • Unsolicited Event Notifications—a Jolt client can receive these notifications when an Oracle Tuxedo client or service subscribes to unsolicited events and an Oracle Tuxedo client issues a broadcast or a directly targeted message.
  • Brokered Event Notifications—the Jolt client receives these notifications through the Oracle Tuxedo Event Broker. The Jolt client receives these notifications only when it subscribes to an event and any Oracle Tuxedo client or server posts an event.
• Jolt Trace —If java option -Dtuxedo.TMTRACE is set, JOLT client prints out trace as the trace format. JOLT trace format is the same as Oracle Tuxedo. Four trace categories, "atmi", "inet", "trace" and "*" are supported.

  atmi

  Trace points for explicit application calls to the ATMI and TX interfaces.

  inet

  Trace points related to network.

  trace

  Trace points related to the tracing feature itself, including message dyeing.

  *

  All trace points.

Listing Jolt Trace Category Example

-Dtuxedo.TMTRACE=trace_spec atmi/inet:jtrace
-Dtuxedo.JTRACEPATH=path_to_trace_file (optional, if not set, use
user.dir)
-Dtuxedo.ECID_ENABLE=y|n (optional)

Usage:
atmi+inet+trace:jtrace:dye
atmi+inet:jtrace:dye
*:jtrace:dye
atmi-inet:jtrace:undye

Output file name:
Jtrace.yyyymmdd