Installing the Tuxedo System

 Previous Next Contents Index View as PDF  

BEA Jolt 8.1 Overview and Installation Information

The following sections provide an overview of BEA Jolt 8.1 and present the prerequisites and preparatory information for installing the BEA Jolt 8.1 software components:


About BEA Jolt

BEA Jolt is a Java class library and API that enables remote Java clients to access existing BEA Tuxedo ATMI services. As shown in the following figure, BEA Jolt extends the functionality of existing Tuxedo ATMI applications to include intranet- and Internet-wide availability.

Figure B-1 BEA Jolt Communication Architecture Using the Jolt Applet


The preceding figure shows one of five types of Jolt client personalities supported by BEA Jolt, all of which are briefly described in BEA Jolt Client Personalities.


BEA Jolt Licensing

BEA Jolt 8.1, which is included in the BEA Tuxedo 8.1 distribution, is controllable through the BEA Tuxedo 8.1 license. BEA Jolt remains a separately sold and licensed product.


BEA Jolt Components

BEA Jolt consists of the following components for enabling secure, reliable access to servers inside corporate firewalls, and for creating Java-based client programs that access Tuxedo ATMI services:

As shown in the following figure, the Jolt server implementation consists of one or more Jolt Server Handlers, one or more Jolt Server Listeners, and one and only one Jolt Repository Server, all running on the same BEA Tuxedo server machine.

Figure B-2 BEA Jolt Server Implementation


A Jolt server listens for network connections from Jolt clients, translates Jolt messages, multiplexes multiple Jolt clients into a single process, and submits and retrieves requests to and from a Tuxedo ATMI application. As with all Tuxedo system executables, the Jolt server components reside in the tux_prod_dir/bin directory, where tux_prod_dir represents the directory in which the BEA Tuxedo 8.1 distribution is installed.

Jolt Server Listener

A Jolt Server Listener (JSL) is a listening process, running on the Tuxedo server, that accepts connection requests from Jolt clients and assigns connections to a Jolt Server Handler also running on the Tuxedo server. It also manages the pool of Jolt Server Handler processes, starting them in response to load demands.

Jolt Server Handler

A Jolt Server Handler (JSH) is a gateway process, running on the Tuxedo server, that handles communications between Jolt clients and the Tuxedo ATMI server application. A JSH process resides within the administrative domain of the application and is registered in the local Tuxedo bulletin board as a client.

Each JSH process can manage multiple Jolt clients. A JSH multiplexes all requests and replies with a particular Jolt client over a single connection.

Jolt Repository Server

The Jolt Repository Server (JREPSVR), running on the Tuxedo server, retrieves Jolt service definitions from the Jolt Repository and returns the service definitions to the Jolt Server Handler. The Jolt Repository Server also provides user support for updating or adding Jolt service definitions to the Jolt Repository.

Jolt Repository

The Jolt Repository, located on the Tuxedo server, is a central repository that contains definitions of Tuxedo ATMI services. These Jolt repository definitions are used by Jolt at run time to access Tuxedo services. You can export services to a Jolt client application or unexport services by hiding the definitions from the Jolt client. Using the Repository Editor, you can test new and existing Tuxedo services independently of the client applications.

Jolt Internet Relay

Jolt Internet Relay routes messages from a Jolt client to a Jolt Server Listener (JSL) or Jolt Server Handler (JSH). It eliminates the need for the JSL, JSH, and Tuxedo application to run on the same machine as the Web server. The Jolt Internet Relay consists of the following components:

The following figure illustrates the Jolt Internet Relay connection path.

Figure B-3 BEA Jolt Internet Relay Connection Path


A Jolt server can connect directly to intranet Jolt clients and can connect indirectly to Internet Jolt clients through the Jolt Internet Relay, all at the same time. Jolt Internet Relay is transparent to Jolt servers and Jolt clients.

The JRLY executable (jrly) resides in the tux_prod_dir/udataobj/jolt/relay directory, whereas the JRAD executable resides in the tux_prod_dir/bin directory.

Jolt Class Library

The Jolt class library consists of Java class files that implement the Jolt API. These classes enable Java clients to invoke BEA Tuxedo ATMI services. The Jolt class library provides functions to set, retrieve, manage, and invoke communication attributes, notifications, network connections, transactions, and services.

The Jolt class library files reside in the tux_prod_dir/udataobj/jolt directory and are stored in the following JAR files:

To view the content of a Jolt JAR file, ensure that the path to the JDK 1.3 (or higher) software is included at the front of your PATH variable, go to the tux_prod_dir/udataobj/jolt directory, and enter the following command:

prompt> jar -tvf filename.jar

For example:

prompt> jar -tvf jolt.jar
     0 Thu Aug 08 07:19:02 EDT 2002 META-INF/
     68 Thu Aug 08 07:19:02 EDT 2002 META-INF/MANIFEST.MF
     547 Thu Aug 08 07:19:00 EDT 2002
     741 Thu Aug 08 07:19:00 EDT 2002 bea/jolt/BData.class
     951 Thu Aug 08 07:19:00 EDT 2002 bea/jolt/ByteArrayUtil.class


JoltBeans provides a JavaBeans-compliant interface to BEA Jolt. JoltBeans are Bean components that can be used in JavaBeans-enabled integrated development environments (IDEs) to construct Jolt clients.

JoltBeans consists of two sets of Java Beans: JoltBeans toolkit (a JavaBeans-compliant interface to BEA 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. The separation of BEA Jolt into these components permits the transactional and Internet components of client/server applications to be implemented separately with the security and scalability required for large-scale Internet and intranet services.


BEA Jolt Client Personalities

In addition to using BEA Jolt to build client applets and applications that remotely invoke existing and new Tuxedo applications, Java programmers can use BEA Jolt to build HTTP servlets or Microsoft Active Server Pages (ASPs) to perform server-side Java tasks in response to HTTP requests. This latter type of Jolt connectivity enables simple Web clients to access Tuxedo application services through any Web application server that supports generic servlets or ASPs.

BEA Jolt supports the following types of Java client personalities:


BEA Jolt Capabilities


Running as a Java applet or as a standalone Java client application, BEA Jolt supports the following capabilities:

To accommodate the BEA Jolt 8.1 server (JSL, JSH, JREPSVR) and Jolt Internet Relay (JRLY, JRAD) components, your environment must provide 2 MB of disk space. For BEA Jolt 8.1 system requirements, including supported platforms, see BEA Tuxedo 8.1 Platform Data Sheets.


BEA Jolt Client Support

As stated in BEA Jolt Client Personalities, BEA Jolt 8.1 supports the following five client types:

The following table lists the requirements for the Jolt 8.1 applet and application client types.


Table B-1 Requirements for BEA Jolt 8.1 Applet and Application Client Types

This client type . . .

Is supported on . . .

Java applet running in a browser

Microsoft Internet Explorer (IE) 6.0 or higher

Netscape Communicator 7.0 or higher

Jolt application—standalone application—running in a desktop environment

Java Development Kit (JDK) 1.3.1


The following table lists the requirements for the remaining three Jolt client types, all of which are implemented by HTML-based Jolt client classes running inside a Web server. The Web servers certified with BEA Jolt 8.1 are listed in the table.

Table B-2 Requirements for Web-Server based BEA Jolt 8.1 Client Types


Web Server Version

OS Version

BEA Jolt Client Personality


Any vendor

Java Servlet Engine

(Any version)

Any OS running JDK 1.3.1

JSE Connectivity for BEA Tuxedo

For a description, see the first note after this table.

BEA Systems, Inc.

BEA WebLogic Enterprise 5.1 or BEA WebLogic Server 6.0 or higher


WebLogic Connectivity for BEA Tuxedo (also known as "BEA Jolt for BEA WebLogic Server")

For example installation instructions, see Installing BEA Jolt 8.1 with BEA WebLogic Server.


IIS 4.0 or higher

Windows 2000

ASP Connectivity for BEA Tuxedo

For a description, see the second note after this table.


Note: JSE Connectivity for BEA Tuxedo is the name of the Jolt Web application server that simplifies the handling of servlets in a BEA Tuxedo application environment. JSE is short for Java Servlet Engine.

Note: ASP Connectivity for BEA Tuxedo is the name of the Jolt Web application server that works with the existing Microsoft Internet Information Server (IIS) to provide a gateway for HTML clients into a BEA Tuxedo application environment. ASP, short for Active Server Pages, is an open, compile-free application environment in which Visual Basic programmers can combine HTML, scripts, and reusable ActiveX server components to create dynamic Web pages. Interactions between the Web server and Jolt classes are performed through VBScript and VB inside ASP.

BEA Jolt Client Requirements

BEA Jolt has the following client requirements:

BEA Jolt Client Class Library

Various implementations of Java tend to show minor differences in characteristics. BEA Jolt 8.1 is based on JDK 1.3.1.

The BEA Jolt class library is compatible with the browsers and JDK versions shown in the following table.

Table B-3 BEA Jolt Class Library Compatibility


Browser Version

Java Virtual Machine (JVM)

OS Version


Internet Explorer 6.0

MS JVM 4.0

Windows 2000


Communicator 7.0

JDK 1.3.1

Windows 2000



BEA Jolt Release Interoperability

A BEA Jolt 8.1 client can interoperate with a BEA Jolt 1.2, 1.2.1, or 8.0 server implementation, but the client cannot use the new features available with BEA Jolt 8.1.

A BEA Jolt 1.2, 1.2.1, or 8.0 client can interoperate with a BEA Jolt 8.1 server implementation, but only the BEA Jolt 1.2, 1.2.1, or 8.0 functionality is available to the BEA Jolt client, even though new functionality is added to the BEA Jolt server-side components when they are upgraded to BEA Jolt 8.1.


ASP Connectivity Prerequisites

The following components are required before you can install BEA Jolt 8.1 ASP Connectivity for the BEA Tuxedo system:

For details about the Microsoft products listed here, see the online Microsoft 2000 Option Pack product documentation, specifically the documentation about Microsoft Internet Information Server.


BEA Jolt Pre-Installation Checklist

On Windows systems, BEA Jolt 8.1 automatically installs two Microsoft dynamic link libraries (DLLs), MSVCRT.DLL and MFC42U.DLL, and overwrites older versions of these libraries. Before you begin installation, check whether older versions of these dynamic link libraries already exist. If they do exist and you do not want them to be overwritten, back them up.


BEA Jolt Documentation

For more information about BEA Jolt, see the following documentation:


Back to Top Previous Next
Contact e-docsContact BEAwebmasterprivacy