|
|
|
|
|
|
Deploying and Localizing Jolt Applets
Using the Jolt Class Library, you can build Java applications that execute from within a client Web browser. For these types of applications, perform the following application development tasks:
The following sections describe these application development considerations.
Deploying a Jolt Applet
When you deploy a Jolt applet, consider the following:
Information for configuring the BEA Tuxedo server and Jolt server to work with Jolt is available in Installing the BEA Tuxedo System. 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 an 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 is downloaded 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 CLASSPATH to include the jolt.jar file that contains all 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 requirement for the Jolt classes subdirectory is that the classes must be made available to the Web server.
The HTML file for the Jolt applet should refer the codebase to the jolt.jar file or the classes directory. For example:
/export/html/
|___ classes/
| |_____ bea/
| | |______ jolt/
| | |_____ JoltSessionAttributes.class
| | |_____ JoltRemoteServices.class
| | |_____ ...
| |_____ mycompany/
| |________ app.class
|___ ex1.html
|___ ex2.html
The webmaster may specify the "app" applet in ex1.html as:
<applet codebase="classes" code=mycompany.app.class width=400 height=200>
Localizing a Jolt Applet
If your Jolt application is intended for international use, you must address certain localization issues. Localization considerations apply to applications that execute from a client Web browser and applications that are designed to run outside a Web browser environment. Localization tasks can be divided into two categories:
For localization, the Jolt Class Library package relies on the conventions of the Java language and the BEA Tuxedo system. Jolt transfers Java 16-bit Unicode characters to the JSH. The JSH provides a mechanism to convert Unicode to the local character set.
For information about the Java implementation for Unicode and character escapes, refer to your Java Development Kit (JDK) documentation.
|
|
|
|
|
|
Copyright © 2000 BEA Systems, Inc. All rights reserved.
|