Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy
	e-docs.beasys.com   |   Search   |   PDF Files   |   Contact   |   Glossary
Jolt Doc Home   |   Jolt Installation Guide   |   Previous Topic   |   Next Topic   |   Contents   |   Index

This chapter provides information on the preparations you need to make prior to installing BEA Jolt, hereafter designated as Jolt. The following topics are discussed in this chapter:

• What's New in Jolt

• What's Changed in Jolt

• Checking Your Package

• System Requirements

• Release Migration/Interoperability

• Jolt ASP Connectivity for TUXEDO

• Directory Structure

• Preinstallation Checklist

What's New in Jolt

The following features are new to Jolt:

• Compression-Allows application data that is sent between a Jolt client and a Jolt Server (JSH) to be compressed during transmission over the network at a very low cost (few CPU cycles). Compression is only supported for clients based on JDK 1.1.7 or 1.2.

• Diffie-Hellman (DH) Key Exchange-Replaces the DES key exchange mechanism. This allows Jolt to be classified as a true 128 bit secure environment (available to U. S. customers only).

• Two Session Keys per Jolt Session-Jolt uses two session keys for each user session. One key is used for encrypting and decrypting messages sent from the client to the server, the other for messages sent from the server to the client.

• Support for WebLogic Enterprise 4.2 (WLE)-WLE 4.2 provides advanced Java development services. It allows you to build distributed, mission-critical, CORBA-compliant applications in Java and C++.

• JRLY as an NT Service-The Jolt Relay (JRLY) in Jolt on the NT platform is provided as an NT service. As an NT service, this process can be started and stopped via the NT Service Control Manager (SCM).

• JRLY Connection to JRAD-The Jolt Relay (JRLY) in Jolt allows you to specify a list of IP addresses for JRADs. On startup, the JRLY tries to connect to each JRAD on the list, searching sequentially from the beginning. The first JRAD to respond successfully is used.

• Multiple JSL Addresses for JoltSessionAttributes-Jolt allows you to specify a list of IP port addresses from which the Jolt client randomly selects JSLs until a connection is established.

• ASP Connectivity for TUXEDO (formerly Jolt WAS for IIS)-Works with existing Microsoft Internet Information Server (IIS) to provide a gateway for HTML clients into a TUXEDO application environment. Interactions between the Web server and Jolt classes are through VBScript and VB inside ASPs.

• JSE Connectivity for TUXEDO (formerly Jolt WAS for Servlets)-Simplifies handling of HTTP requests to the TUXEDO application environment.

• Internationalization-Allows all informational and error messages that are generated by the Jolt client to be localized.

• Javadoc Format-The HTML and PDF versions of the Jolt class library are now in Javadoc format.

• Y2K Compliance-Any dates that are used or displayed by Jolt are in Y2K-compliant format. Specifically, the Jolt license file allows expiration dates beyond December 31, 1999 and all messages and timestamps that Jolt generates use a Y2K-compliant representation.

• Linux-Jolt now supports the Linux operating system.

• OS 400 and OS 390-Jolt now supports these operating systems.

What's Changed in Jolt

If you are migrating from Jolt 1.1 to Jolt 1.2, you should be aware of the following changes:

• TUXEDO/WLE Version-If you are currently running TUXEDO 6.1, 6.2, or 6.3 and are upgrading to Jolt 1.2, you must also upgrade your TUXEDO version to 6.4 or 6.5, or WLE 4.2. Jolt 1.2 only works with versions 6.4 and 6.5 of TUXEDO, or version 4.2 of WLE.

• Client/Server Interoperability-Jolt provides some client/server interoperability. While you must upgrade all server-side components together, you do not have to upgrade client components at the same time. A Jolt 1.1 client and Jolt 1.2 server interoperate, but the client has only 1.1 functionality; server components have additional functionality. However, a Jolt 1.2 client cannot operate with a Jolt 1.1 server.

• ASP Connectivity for TUXEDO-The name of Jolt Web Application Server (WAS) has changed to ASP Connectivity for TUXEDO to emphasize the Microsoft ASP environment. Also, ASP Connectivity for TUXEDO is no longer an add-on; it is part of the Jolt Client Class Library.

• JSE Connectivity for TUXEDO-The name of Jolt WAS for Servlets is now JSE Connectivity for TUXEDO.

• JoltBeans-This feature is no longer an add-on; it is part of the Jolt Client Class Library.

• Security/Encryption-Diffie-Hellman (DH) key exchange replaces the DES key exchange mechanism (for U. S. customers only).

• Digital Alpha NT-Is no longer supported.

Checking Your Package

You should find the following contents when you open the Jolt box:

• Jolt CD (With either U.S. or International encryption)

• Jolt Documentation CD-Includes:

  • HTML and PDF versions of Jolt Installation and Configuration Guide

  • HTML and PDF versions of Jolt Developer's Guide

  • Jolt API Reference in Javadoc

• Jolt Release Notes-A hardcopy document that informs you of changes in the software that occurred after release.

• Jolt Installation and Configuration Guide (this document)-A hardcopy document (also in PDF on the Documentation CD) that provides instructions for installing and configuring Jolt.

The license is available in two formats:

• A 3.5-inch diskette that contains the product license may be taped outside the box

• A license file can be emailed to you directly.

System Requirements

The following hardware and software components are required before you can install Jolt.

BEA TUXEDO

If you are using Jolt with BEA TUXEDO, you must have TUXEDO 6.4 or 6.5 installed before you can install Jolt. TUXEDO versions prior to 6.4 are not supported by Jolt 1.2.

WebLogic Enterprise

If you plan to use Jolt with WebLogic Enterprise (WLE), you must have WLE 4.2 installed before you install Jolt.

Web Servers Supported

To provide HTTP/HTML-based access to enterprise applications, Jolt supports the Microsoft Internet Information Server (IIS) or Java Web Server.

Supported Platforms for Jolt Server

Jolt server platform support depends upon TUXEDO version support, as stated earlier in this chapter. The Jolt server also requires:

• CD-ROM access

• 500K of disk space

Table 1-1 shows the supported platforms for the Jolt server.

Table 1-1 Supported Platforms for Jolt Server

Operating System Vendor	Operating System	Operating System Version	TUXEDO Version Supported	WLE Version Supported
Digital Equipment Corporation (DEC)	Digital UNIX	4.0d	6.5 only
DEC	Digital UNIX	4.0e		4.2
Hewlett-Packard (HP)	HP-UX	10.20	6.4 and 6.5	4.2
HP	HP-UX	11.0	6.4 and 6.5	4.2
International Business Machines (IBM)	AIX	4.2.1 (RS/6000)	6.4 and 6.5
IBM	AIX	4.3.1 (RS/6000)	6.4 and 6.5
IBM	AIX	4.3.2		4.2
IBM	OS/390	V2R6	6.5 only
IBM	OS/400	4.1 (RISC)	6.5 only
Microsoft	Windows NT	4.0 (sp3)	6.4 and 6.5	4.2
Red Hat	Linux	5.2	6.5 only
Santa Cruz Operation (SCO)	Unixware	7.0	6.5 only
Sequent	Dynix/PTS	4.4.2	6.5 only	4.2
SGI (Silicon Graphics)	IRIX	6.4 -o32	6.4 and 6.5
SGI	IRIX	6.5 -n32	6.5 only	4.2
Sun	Solaris	2.5.1 (SPARC)	6.4 and 6.5
Sun	Solaris	2.5.1 (Intel)	6.4 and 6.5
Sun	Solaris	2.6 (SPARC)	6.4 and 6.5	4.2
Sun	Solaris	2.6 (Intel)	6.4 and 6.5
Sun	Solaris	2.7 (SPARC)	6.5 only	4.2
Sun	Solaris	2.7 (Intel)	6.5 only
Siemens Nixdorf (SNI)	Reliant UNIX	5.4.4b	6.5 only

Supported Platforms for Jolt Relay

Table 1-2 shows the supported platforms for Jolt Relay:

Table 1-2 Supported Platforms for Jolt Relay

Operating System Vendor	Operating System	Operating System Version
DEC	Digital UNIX	4.0d (Alpha)
HP	HP-UX	10.20
HP	HP-UX	11.00
IBM	AIX	4.2.1 (RS/6000)
IBM	AIX	4.3, 4.3.1
Microsoft	Windows NT	4.0 (Intel) (sp4)
Sequent	Dynix/PTS	4.4.2
SNI	Reliant UNIX	5.4.4b
Sun	Solaris	2.5.1 (SPARC)
Sun	Solaris	2.6 (SPARC)

Client Support

Jolt 1.2 supports Java applets and standalone Java client applications for TUXEDO. The following table shows the client types supported by Jolt 1.2.

Table 1-3 Client Types Supported by Jolt 1.2

Client Type	Supports	Version Supported
Java Applet in a Browser	Microsoft Internet Explorer	Internet Explorer (IE) 4.0, 5.0
	Netscape	Netscape Communicator 4.5.1
Standalone Applications on a Desktop	Java	JDK 1.1.7, 1.2

The HTML-based Jolt Client Classes run inside a Web server. The following Web servers are certified with Jolt.

Table 1-4 Web Servers Certified With Jolt

Vendor	Web Server Version	OS Version	Jolt Client Personality	Comments
Microsoft	IIS 4.0x	Windows NT 4.0	ASP Connectivity for TUXEDO	Supports VB or VBScript-based applications inside ASPs.
BEA WebXpress	WebLogic (WLX and/or WLS) 4.xx	Any	WebLogic Connectivity for TUXEDO	Supports servlets. Backward-compatible only - You can have a Jolt 1.2 server with a Jolt 1.1 client.
Any	Java Servlet Engine (Any version)	Any OS running JDK 1.1.7	JSE Connectivity for TUXEDO	Supports servlets.

Jolt Client Requirements

Jolt has the following client requirements:

• 574K of disk space for client classes.

• 1364K of disk space for client API documentation.

• 190K of disk space for client examples.

• Java Developer's Kit (JDK) 1.1.7 or 1.2 is certified for Jolt 1.2 application development. Jolt 1.1 uses JDK 1.1.5 or 1.1.6. (http://java.sun.com:80/java.sun.com/products/JDK/index.html)

• Java-enabled browser (Internet Explorer) or Java Virtual Machine (JVM).

Jolt Client Class Library

Various implementations of Java tend to show minor differences in characteristics. Jolt 1.2 is based on the 1.1.7 JDK. The Jolt 1.2 class library is compatible with JDK versions 1.1.7 and 1.2 on the following operating systems:

• Solaris 2.5.1, 2.6, and 2.7

• Windows NT 4.0

• Windows 95 and 98

• OSR2

The Jolt class library is compatible with the browsers and JDK versions shown in Table 1-5.

Table 1-5 Jolt Class Library Compatibility

Vendor	Browser/Version	Java Virtual Machine (JVM)	OS Version
Microsoft	Internet Explorer 4.0.1 (sp1)	MS JVM 4.0	Windows NT 4.0 Service Pack 4
Microsoft	Internet Explorer 5.0	MS JVM 4.0	Windows NT 4.0 Service Pack 4
Netscape	Communicator 4.5, 4.6.1	JDK 1.1.5	Windows NT 4.0

Release Migration/Interoperability

If you have Jolt 1.1 installed, we recommend that you uninstall it before you install Jolt 1.2.

Jolt provides increased interoperability between versions. In the Jolt 1.2 release, however:

• You must upgrade all server-side components together.

• If you have Jolt 1.1 applications, only Jolt 1.1 functionality is available to the Jolt 1.1 client, even though the server-side components have additional functionality when they are upgraded to Jolt 1.2.

• A Jolt 1.2 client cannot operate with a Jolt 1.1 server.

Jolt ASP Connectivity for TUXEDO

Before you install Jolt ASP Connectivity for TUXEDO, you must have the following software installed:

• Windows NT Server 4.0 with NT Option Pack

• Microsoft IIS 4.0

• TUXEDO 6.x

Installation Instructions

Note: These instructions are documented from the Microsoft standard. Check the Microsoft documentation for updates.

To install Jolt ASP Connectivity for TUXEDO:

1. Remove any files that you copied when you installed the Jolt 1.1 WAS package.

2. Install the Microsoft Java Component Framework from the IIS 4.0 SDK (if it is not already installed).

3. Create a new directory, aspcomp in the java\Trustlib directory. (This is most typically found in %windir%\java\TrustLib ).

   Since the framework files have been created in a package called aspcomp , the Java Virtual Machine (JVM) expects to find them there.

   The Microsoft Java Component Framework files are typically found in: C:\InetPub\iissamples\sdk\components\java\Framework

4. Copy the framework class files to the newly created

   java\TrustLib\aspcomp directory.

   (You only need to copy the *.class files.)

5. Install the latest Jolt 1.2 classes in the Windows NT server java\Trustlib directory.

   Contact BEA Customer Support for the latest Jolt 1.2 patch files.

6. Copy the class subdirectories and files (or unzip jolt.zip) from the Jolt 1.1 Patch 5 client distribution into your java\lib directory. The Jolt 1.2 classes have been created in packages beginning with "bea" so the JVM expects to find them in the java\lib\bea\... subdirectories.

   Install the corresponding Jolt 1.2 patch files on your Tuxedo server if you have not already done so.

7. Install the Web Application Services classes in the Windows NT server

   java\Trustlib directory.

8. Unzip webiis.zip to create the class files in your java\trustlib directory.

   Make sure you expand the files using the subdirectory folders in the zip archive.

   The Web Application Services classes are created in packages beginning with "bea" so the JVM will expect to find them in the java\Trustlib\bea\... subdirectories.

9. Register the Web Application Service classes as ActiveX components.

   Run the wasreg.cmd command file to register the BEA Web Application Services java classes as BEAWEB ActiveX components. This enables the BEAWEB components to be accessible from the Microsoft ASP scripts.

Refer to the online Microsoft NT Option Pack Product Documentation, especially the Microsoft Internet Information Server (IIS) chapters.

Directory Structure

The following sections show the CD directory structures for UNIX and NT systems.

UNIX Directory Structure on Jolt CD

Table 1-6 shows you directory paths for components of specified platforms on the Jolt CD.

Table 1-6 Examples of Directory Paths for UNIX Platforms

Platform	Directory Path
UNIX installation program	/unix/ install.sh
Alpha
Jolt with TUXEDO 6.5 on Alpha dux40	/unix/alpha/dux40/TUX6.5/jolt
Jolt with WLE 4.2 on Alpha dux40	/unix/alpha/dux40/WLE4.2/jolt
HP
Jolt with TUXEDO 6.4 or 6.5 on HP hpux1020	/unix/hp/hpux1020/TUX6.4_6.5 /jolt
Jolt with TUXEDO 6.4 or 6.5 on HP hpux11	/unix/hp/hpux11/TUX6.4_6.5/jolt
Jolt with WLE 4.2 on HP hpux1020	/unix/hp/hpux1020/WLE4.2/jolt
Jolt with WLE 4.2 on HP hpux11	/unix/hp/hpux11/WLE4.2/jolt
IBM
Jolt with TUXEDO 6.4 or 6.5 on IBM aix42	/unix/ibm/aix42/TUX6.4_6.5/jolt
Jolt with TUXEDO 6.4 or 6.5 on IBM aix43	/unix/ibm/aix43/TUX6.4_6.5/jolt
Jolt with WLE 4.2 on IBM aix42	/unix/ibm/aix43/WLE4.2/jolt
Linux
Jolt with TUXEDO 6.4 or 6.5 on Linux inlnx52	/unix/linux/inlnx52/TUX6.4_6.5 /jolt
Sequent
Jolt with TUXEDO 6.5 on Sequent dynix 442	/unix/seq/dynix442/TUX6.5/jolt
Jolt with WLE 4.2 on Sequent dynix 442	/unix/seq/dynix442/WLE4.2/jolt
SGI
Jolt with TUXEDO 6.4 or 6.5 on SGI irix64	/unix/sgi/irix64/TUX6.4_6.5/jolt
Jolt with TUXEDO 6.5 on SGI irix65	/unix/sgi/irix65/TUX6.5/jolt
Jolt with WLE 4.2 on SGI irix65	/unix/sgi/irix65/WLE4.2/jolt
SNI
Jolt with TUXEDO 6.5 on SNI rel544	/unix/sni/rel544/TUX6.5/jolt
Sun
Jolt with TUXEDO 6.4 or 6.5 on Sun SPARC Solaris 2.5.1	/unix/ sun5x/sol251/TUX6.4_6.5/jolt
Jolt with TUXEDO 6.4 or 6.5 on Sun SPARC Solaris 2.6	/unix/ sun5x/sol26/TUX6.4_6.5/jolt
Jolt with WLE 4.2 on Sun SPARC Solaris 2.6	/unix/ sun5x/sol26/WLE4.2/jolt
Jolt with TUXEDO 6.5 on Sun SPARC Solaris 2.7	/unix/ sun5x/sol27/TUX6.5/jolt
Jolt with WLE 4.2 on Sun SPARC Solaris 2.7	/unix/ sun5x/sol27/WLE4.2/jolt
Jolt with TUXEDO 6.4 or 6.5 on Sun Intel Solaris 2.5.1	/unix/ sun5x/isol251/TUX6.4_6.5/jolt
Jolt with TUXEDO 6.4 or 6.5 on Sun Intel Solaris 2.6	/unix/ sun5x/isol26/TUX6.4_6.5/jolt
Jolt with TUXEDO 6.5 on Sun Intel Solaris 2.7	/unix/ sun5x/isol27/TUX6.5/jolt
UW
Jolt with TUXEDO 6.5 on UnixWare uw70	/unix/uw/uw70/TUX6.5/jolt

NT Directory Structure on Jolt CD

Table 1-7 shows the Jolt CD directory structure for NT platforms. On NT Intel, the installation is automatically launched when you insert the CD.

Table 1-7 Examples of Directory Path for NT Platform

Platform	Directory Path
Jolt on Windows NT 4.0 (Intel)	jolt1.2/inwnt40/setup.exe

IBM Mainframe Directory Structure on Jolt CD

Table 1-8 shows the Jolt CD directory structure for IBM OS 400 and OS 390 platforms.

Table 1-8 Examples of Directory Paths for IBM Mainframes

Platform	Directory Path
Jolt on OS400	jolt1.2/as400/us/AS400/V4R1/README.txt
Jolt on OS390	jolt1.2/os390/os390.tar

Preinstallation Checklist

Before you install Jolt, check the following:

• Back up your existing jrepository and jrly.config files.

• Uninstall previous version of Jolt, if applicable. Note that you can install all Jolt 1.2 components at once or separately, in the same or different directories. However, a single uninstall removes everything: files, directories and registry entries.

• Verify that you have TUXEDO version 6.4 or 6.5 or WLE 4.2 installed, if applicable.

• Determine the location of the TUXEDO directory where the Jolt server is to be installed.

• Determine the location of the directory where the Jolt documentation is to be installed.

• Determine the Web server location where the Jolt client components are to be installed.

• Verify the user ID and group ID assigned to Jolt server files (on UNIX).

• Verify the user ID and group ID to be assigned to Jolt client files (on UNIX).

• Review the BEA Jolt Release Notes and the Jolt Product Page (http://www.beasys.com) for any new information .

  Caution: Jolt 1.2 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.