Application deployment and localization, Deploying a jolt applet, Client considerations – HP NonStop G-Series User Manual
Page 94: Web server considerations
}
if ((failure = xfer.doxfer(51334, 40343, "$123.25")) != null)
System.err.println("Tranasaction failed: " + failure);
else
{
System.out.println("Transaction is done.");
System.out.println("From Acct Balance: "+xfer.fromBal);
System.out.println(" To Acct Balance: "+xfer.toBal);
}
}
}
Application Deployment and Localization
The Jolt Class Library allows you to build Java applications that execute from within a client Web browser. For these types of
applications, you need to address the following application development tasks:
Deploying your Jolt application in an HTML page
●
Localizing your Jolt application for different languages and character sets
●
The following sections describe these application development considerations.
Deploying a Jolt Applet
When you deploy a Jolt applet, you need to consider the three components that operate together to make the applet function in a Web
browser environment:
Requirements for the TUXEDO server and Jolt Server
●
Client-side execution of the applet
●
Requirements for the Web server that downloads the Java applet
●
Information for configuring the TUXEDO server and Jolt Server to work with Jolt is available in
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:
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:
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.