Welcome to BEA Jolt, Version 1.1. This version of Jolt contains new features that add additional security, reliability and flexibility to your Jolt client application development. These Release Notes provide a brief overview of each new feature and contain essential information to get you up and running with BEA Jolt software.
Note: The BEA Jolt Release Notes present changes or updates to the standard documentation provided with your Jolt 1.1 product release. In all cases, these Release Notes contain the most up-to-date information for the Jolt 1.1 product.
Before you install BEA Jolt 1.1 software, read this document in conjunction with the installation section in the BEA Jolt User's Guide. You can browse the HTML version of the BEA Jolt User's Guide on your distribution medium and via the BEA Systems Web site at http://www.beasys.com/products/jolt/index.htm.
The following sections describe the new features added for the BEA Jolt 1.1 software release.
When you enable encryption support, Jolt 1.1 uses a combination of DES and RC4 encryption algorithms to encrypt all data that is transmitted between a Jolt client and a Jolt server. DES (56-bit) encryption is used for key exchange and authentication, and RC4 is used for all subsequent data exchanges. Jolt 1.1 features two versions of encryption support: one allows a 128-bit key for data encryption, the other allows a 40-bit key.
The 128-bit version generates a 128-bit RC4 session encryption key at logon time, and this session key is transmitted over the network in a message protected by 56-bit DES encryption. The temporary session key is then used to encrypt the session's data. The overall security level achieved is equivalent to 56-bit DES encryption, even though the data encryption is using a 128-bit key.
These two encryption versions of Jolt 1.1 (40-bit and 56/128-bit) are on separate CDs. All references in the BEA Jolt User's Guide to 128-bit encryption refer to the 56/128-bit capability as described in this paragraph.
Note: The 56/128-bit version of Jolt 1.1 cannot be used outside the United States without proper approval from the United States government.
The default for Jolt 1.1 is no encryption. The encryption feature can be turned on and off administratively using a Jolt Server Listener (JSL) command-line option in the UBBCONFIG
file.
The Jolt Internet Relay removes the need for the Jolt Servers to be installed on the same machine as the Web Server software. The Jolt Relay consists of two components, Jolt Relay (JRLY) and Jolt Relay Adapter (JRAD), that work as a pair and route client requests to the appropriate Jolt Server. The Jolt Relay is an optional component and is transparent to both the Jolt client and the Jolt Servers. The Jolt Server can concurrently have clients connected via a Jolt Relay and clients connected directly to the Server.
Jolt 1.1 clients can subscribe to TUXEDO events and to unsolicited notifications from TUXEDO servers or clients. Jolt clients cannot post events or generate unsolicited notifications, they can only receive them.
A new API class, JoltUserEvent, has been added to support events and unsolicited notifications. The JoltSession class has been enhanced to provide an onReply
method, which is invoked when events or notifications are received.
Jolt 1.1 allows for the use of strings containing 16-bit characters as parameters for TUXEDO services. The character conversion routine can be customized by application developers, using the dynamic library libjconv
. The Jolt default version of libjconv
supports 8-bit Latin-1 characters. To use 16-bit characters, you need a version of TUXEDO that supports 16-bit characters.
The Jolt repository contains service definitions that you can add using the GUI-based Repository Editor. However, loading large numbers of service definitions can be time-consuming. Therefore, Jolt 1.1 also includes a repository bulk loader. The Jolt 1.1 bulk loader utility takes its input from a text file and bulk loads multiple service definitions into the Jolt repository.
Jolt 1.1 works with TUXEDO 6.1, 6.2, and 6.3. All features of Jolt 1.1 are constant across all these releases of TUXEDO, except where new features have been added for TUXEDO 6.3. The new features of TUXEDO 6.3 supported by Jolt 1.1 are:
//hostname:port
, (e.g., //myserver:3000
). The TUXEDO 6.1 hexadecimal notation is also supported (i.e., 0x0002PPPPNNNNNNNN
).
The BEA Jolt User's Guide contains complete Jolt 1.1 installation instructions. This section highlights steps required to upgrade an existing installation of Jolt 1.0 or 1.0.1 to Jolt 1.1.
Before you start any upgrades, make a backup of any existing Jolt installation that you have on your system. Table 1 lists the files/directories where Jolt files are typically installed. If you have a previous Jolt installation at these locations, you should do a backup.
Jolt 1.1 is available for TUXEDO versions 6.1, 6.2, and 6.3. If you are upgrading both TUXEDO and Jolt: upgrade TUXEDO first; then, upgrade Jolt. For information about upgrading TUXEDO, refer to your BEA TUXEDO documentation.
The Jolt 1.1 release uses different default installation locations for some Jolt components than previous Jolt versions. Table 2 shows these changes.
After you have upgraded from a previous Jolt version to Jolt 1.1, locate and remove the Jolt directories shown in Table 2, Default Component Locations. The installation program on Windows NT systems should do this automatically, but the installation program on UNIX platforms will leave the original directories intact. The locations shown in the table are the default locations for these files-the actual location is dependent on the options selected when you installed your previous version of Jolt (E.A., 1.0, 1.0.1).
Note:
Leaving these directories intact does not necessarily impact the performance of Jolt 1.1. However, it could be confusing for application administrators to have access to redundant files. If these files are accidentally used in place of the Jolt 1.1 files, you may receive an error (e.g, using Jolt 1.0 client classes instead of Jolt 1.1 client classes will render the client unable to logon).
When installing Jolt 1.1 on UNIX platforms, the owner and group attributes of the installed files are set to the user ID and group ID of the current user (i.e., the user you are logged in as when you run the installation program). Since the default installation location for files is in When you have completed the pre-upgrade tasks, follow these steps to install Jolt 1.1:
Upgrading to BEA Jolt 1.1
Before You Start
Upgrading TUXEDO and Jolt
Removing Jolt 1.0 Files and Directories
File Ownership
$TUXDIR
, make sure that the current user has permission to write into this directory.
Upgrading to Jolt 1.1
tmshutdown
-
g <JOLT-SERVER-GROUP>
or tmshutdown
to shut down the complete application.
jrepository
).
unix
directory on the CD and run
install.sh
.
Note:
You may need to modify the UBBCONFIG
file to match the new jrepository path.
tmboot -g <JOLT-SERVER-GROUP>
or
tmboot
to boot the entire application.
Note:
If you are using the getOccurrenceCount()
method, you need to recompile.
Jolt 1.1 consists of several components that are available on various platforms. For the purpose of platform coverage the components are divided into:
The Jolt Server consists of the Jolt Server Listener (JSL), the Jolt Server Handler (JSH), the Jolt Repository Server (JREPSVR) and associated libraries ( The Jolt Server is available on the following platforms:
Jolt Server
libjnwi
and libjconv
).
The Jolt Relay consists of the Jolt Relay front-end (JRLY) and back-end (JRAD).
The JRAD is dependent on TUXEDO and is available on the same platforms as the Jolt Server (see the previous list).
The JRLY is not dependent on TUXEDO and is available on the following platforms:
Jolt Relay
The Jolt client classes are compiled using the Jolt Client Classes
javac
compiler from Java Developer's Kit (JDK) 1.0.2. These classes are available on all platforms that support JDK 1.0.2. The following considerations apply when using the Jolt class library:
When installing and using the Jolt 1.1 release, you may encounter some of the following issues that can make Jolt or a Jolt component inoperable.
Table 3 describes these issues and provides a workaround.
This section describes limitations in the current BEA Jolt 1.1 release and includes possible workarounds, where applicable.
Table 4 lists a CR (Change Request) number for each problem. Refer to this number to conveniently track the solution as the problems are resolved.
Please contact BEA Technical Support for assistance in tracking any unresolved problems. For contact information, see the section "Contacting BEA Technical Support."
For Windows NT systems, there is a TUXEDO system limit of 64 network sockets per process. When configuring a JSL server on Windows NT systems, there is a limit of 63 for the When you configure a JRAD server on Windows NT systems as part of a Jolt Internet Relay, there is also a limit of 64 active network connections per JRAD server. One connection is used to communicate with the JRLY process, and a maximum of 63 active network connections are available for carrying client communications to the corresponding JSL and JSH processes.
In the Jolt 1.1 release, we have fixed software problem that occurred in the Jolt 1.0 and Jolt 1.0.1 releases. Table 5 lists these fixes.
If you have any questions about this version of BEA Jolt, or if you have problems installing and running Jolt, contact BEA Technical Support at one of the following telephone numbers or use the email addresses:
North America Support Center European Support Center Asia Pacific Support Center Japan Support Center Miscellaneous Issues
Known Limitations
Known Platform Networking Limitations
-x
multiplexing value.
Software Problems Fixed in Jolt 1.1
Contacting BEA Technical Support
Sunnyvale, CA USA
M-F 5:00 am - 6:00 pm Pacific Time
1-888-232-7878
1-408-743-4070
1-408-743-4071 fax
email: support@beasys.com
Paris, France
M-F 9:00 am - 6:00 pm GMT +1
+33-1-41-45-7090
+33-1-41-45-7009 fax
email: support@beasys.fr
Brisbane, Australia
M-F 8:30 am - 5:30 pm
+61-7-3255-0506
+61-7-3255-0441 fax
email: support@beasys.com.au
Yokohama, Japan
M-F 9:00 am - 6:00 pm
+81-4-5224-1250
+81-4-5224-1251 fax
email: support@beasys.co.jp