Jolt 1.2 Developer's Guide
Table Of Contents
- Jolt for NonStop(TM) TUXEDO Developer's Guide
- Jolt for NonStop(TM) TUXEDO Developer's Guide
- About This Guide
- 1. Introducing Jolt
- 2. Installing Jolt
- 3. Configuring the Jolt System
- 4. Bulk Loading NonStopTM TUXEDO Services
- 5. Using the Jolt Repository Editor
- 6. Using the Jolt Class Library
- 7. Using JoltBeans
- 8. Using Servlet Connectivity for NonStopTM TUXEDO
- 9. Using Jolt 1.2 ASP Connectivity for NonStopTM TUXEDO
- A. NonStopTM TUXEDO Errors
- B. System Messages
- Index
Requirements for the NonStop
TM
TUXEDO server and Jolt Server●
Client-side execution of the applet●
Requirements for the Web server that downloads the Java applet●
The following sections describe common client and Web server considerations for deploying Jolt applets.
Client Considerations
When you write a Java applet that incorporates Jolt classes, the applet works just as any other Java applet in an HTML page. A Jolt applet can be
embedded in a HTML page using the HTML applet tag:
<applet code="applet_name.class"> </applet>
If the Jolt applet is embedded in an HTML page, the applet downloads when the HTML page loads. You can code the applet to run immediately
after it is downloaded, or you can include code that sets the applet to run based upon a user action, a timeout, or a set interval. You can also create
an applet that downloads in the HTML page, but opens in another window or, for instance, simply plays a series of sounds or musical tunes at
intervals. The programmer has a large degree of freedom in coding the applet initialization procedure.
Note
If the user loads a new HTML page into the browser, the applet execution is stopped.
Web Server Considerations
When you use the Jolt classes in a Java applet, the Jolt Server must run on the same machine as the Web server that downloads the Java applet
unless you install Jolt Relay on the Web server.
When a webmaster sets up a Web server, a directory is specified to store all the HTML files. Within that directory, a subdirectory named "classes"
must be created to contain all Java class files and packages. For example:
<html-dir>/classes/bea/jolt
Or, you can set the class path to include the jolt.jar file that contains all of the Jolt classes.
Note
You can place the Jolt classes subdirectory anywhere. For convenient access, you may want to place it in the same directory
as the HTML files. The only requirements for the Jolt classes subdirectory are that they must be made available to the Web
server.
The HTML file for the Jolt applet should refer the codebase to the "classes" directory. For example: