Preparing to Install BEA Jolt

 

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

• System Requirements

• Release Migration/Interoperability

• Jolt ASP Connectivity for BEA Tuxedo

• 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 5.1 -WebLogic Enterprise 5.1 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 BEA Tuxedo (formerly Jolt WAS for IIS)-Works with existing Microsoft Internet Information Server (IIS) to provide a gateway for HTML clients into a BEA Tuxedo application environment. Interactions between the Web server and Jolt classes are through VBScript and VB inside ASPs.

• JSE Connectivity for BEA Tuxedo (formerly Jolt WAS for Servlets)-Simplifies handling of HTTP requests to the BEA 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.

 

---

What's Changed in Jolt

• BEA Tuxedo/WebLogic Enterprise Version - Jolt 1.2 for WebLogic Enterprise 5.1 only works with WebLogic Enterprise 5.1.

• 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 BEA Tuxedo-The name of Jolt Web Application Server (WAS) has changed to ASP Connectivity for BEA Tuxedo to emphasize the Microsoft ASP environment. Also, ASP Connectivity for BEA Tuxedo is no longer an add-on; it is part of the Jolt Client Class Library.

• JSE Connectivity for BEA Tuxedo-The name of Jolt WAS for Servlets is now JSE Connectivity for BEA 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.

 

---

System Requirements

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

WebLogic Enterprise

If you plan to use Jolt with WebLogic Enterprise, you must have WebLogic Enterprise 5.1 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 BEA Tuxedo version support, as stated earlier in this chapter. The Jolt server also requires:

• CD-ROM access

• 500K of disk space

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

Table 14-1 Supported Platforms for Jolt Server

Operating System Vendor	Operating System	Operating System Version	BEA Tuxedo Version Supported	WebLogic Enterprise 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 (sp4)	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 14-2 shows the supported platforms for Jolt Relay:

Table 14-2 Supported Platforms for Jolt Relay

Operating System Vendor	Operating System	Operating System Version
DEC	Digital Tru64 UNIX	4.0f (Alpha)
HP	HP-UX	11.00
IBM	AIX	4.3.3
Microsoft	Windows NT	4.0 (Intel) (sp4)
Sun	Solaris	2.6 (SPARC)

Client Support

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

Table 14-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.7
Standalone Applications on a Desktop	Java	JDK 1.1.7, 1.2.2

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

Table 14-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 BEA Tuxedo	Supports VB or VBScript-based applications inside ASPs.
BEA WebXpress	WebLogic (WLX and/or WLS) 5.xx	Any	WebLogic Connectivity for BEA 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 BEA 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.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/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.2 on the following operating systems:

• Solaris 2.5.1, 2.6, and 2.7

• Windows NT 4.0

• Windows 95 and 98

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

Table 14-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.7	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 BEA Tuxedo

Requirements

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

• Windows NT Server 4.0 with NT Option Pack

• Microsoft IIS 4.0

• WebLogic Enterprise 5.1

Installation Instructions

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

To install Jolt ASP Connectivity for BEA 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.2 for WebLogic Enterprise 5.1 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 BEA 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 joltjsp.jar 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.

   wasreg.cmd file list

   @echo off

   REM
   REM This batch command file registers the necessary java
   REM classes as ActiveX components so that they are accessible
   REM from Active Server Pages or any other ActiveX client.
   REM The classes (or equivalent zip file) must exists
   REM in your java/Trustlib directory (normally C:\%WINDIR%\java\Trustlib.
   REM
   javareg /q /register /class:bea.jolt.pool.asp.UserInfo/progid:BEAWEB.UserInfo
   javareg /q/register/class:bea.jolt.pool.asp.SessionPoolManager/progid:BEAWEB.SessionPoolManager
   javareg /q /register /class:bea.jolt.pool.asp.Template/progid:BEAWEB.Template
   javareg /q /register /class:bea.jolt.pool.asp.TemplateData/progid:BEAWEB.TemplateData
   

   REM
   REM These are the new ActiveX component names.
   REM
   javareg /q /register /class:bea.jolt.pool.UserInfo/progid:BEAJOLTPOOL.AspUserInfo
   javareg /q /register /class:bea.jolt.pool.asp.AspPoolManagerConfig/progid:BEAJOLTPOOL.AspPoolManagerConfig
   javareg /q /register /class:bea.jolt.pool.asp.AspSessionPoolManager/progid:BEAJOLTPOOL.AspSessionPoolManager
   javareg /q /register /class:bea.jolt.pool.asp.AspTemplate/progid:BEAJOLTPOOL.AspTemplate
   javareg /q /register /class:bea.jolt.pool.asp.AspDataSet/progid:BEAJOLTPOOL.AspDataSet
   

   REM
   REM These are the new ActiveX component names.
   REM
   javareg /q /register /class:bea.jolt.pool.UserInfo/progid:BEAJOLTPOOL.AspUserInfo
   javareg /q /register /class:bea.jolt.pool.asp.AspPoolManagerConfig/progid:BEAJOLTPOOL.AspPoolManagerConfig
   javareg /q /register /class:bea.jolt.pool.asp.AspSessionPoolManager/progid:BEAJOLTPOOL.AspSessionPoolManager
   javareg /q /register /class:bea.jolt.pool.asp.AspTemplate/progid:BEAJOLTPOOL.AspTemplate
   javareg /q /register /class:bea.jolt.pool.asp.AspDataSet/progid:BEAJOLTPOOL.AspDataSet
   References

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

 

---

Preinstallation Checklist

Before you install Jolt, check the following:

• Back up your existing CATNAMES, 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 WebLogic Enterprise 5.1 installed, if applicable.

• Determine the location of the BEA 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.