Table of Contents
Abstract
[ http://java.sun.com/products/javawebstart/ ] Java Web Start (JWS) is a means for deploying rich Java-based applications over networks. It is designed to supplant the older "applet" technology and as such, bears some similarities to its predecessor as well as some important differences. This document provides an overview of what you need to do to make sure you can use JWS-based applications launched from your web browser.
Launching a Web Start application through your web browser requires that you have a recent (1.4 or later) version of the Java Runtime Environment (JRE) from Sun Microsystems installed, and that your web browser is configured to recognize Java Network Launch Protocol (JNLP) files. Once these parts are in place, launching a JWS application is as easy as clicking on the link to a JNLP file.
Computers purchased through the CCI have Sun's JRE, including the JWS component, preinstalled. If, however, your machine was not purchased through the CCI, you are using a browser you installed after purchasing your computer, or your installed JRE predates version 1.4, you may need to install or upgrade the JRE in order to set your system up to run JWS applications. The latest version of the JRE is available at [ http://java.com/en/index.jsp ] Sun's download site. Simply follow the "Get it Now!" link and follow the instructions there to get the JRE for your computer.
Note
If you are running Microsoft Windows, the JRE installer will also configure Internet Explorer and any Mozilla-based browser (Netscape 6+, Mozilla, Mozilla Firefox) you may have installed to recognize JWS files.
As noted above, launching a JWS application can be as simple as following a link. Understanding how JWS works can help you to track down any problems you may have launching a JWS application. The steps are:
Web Start Application Launch Sequence
-
The browser receives the JNLP file.
-
The browser recognizes that the JNLP file should be handled by JWS.
-
A new JWS (Java) process is launched (a small splash screen that says "Loading Java" should show up).
-
The JWS process checks to see if it has a local copy of the application already; if it has no copy, or an outdated copy, it downloads the application from the web server.
-
The JWS process starts the application.
Java is designed to be highly secure; it is rather paranoid (as it should be!) about running applications downloaded over the network. A malicious application could do all sorts of damage once it is running on your machine. To help reduce the risk of malicious code, Java by default does not allow an application to do "dangerous" things such as read or write files to the drives on your machine, alter various settings, or open network connections. For those situations where JWS application authors may need to do these things, it is possible to sign the application code to verify the identity of the code's distributor. An application which is signed prompts Java to show the user a dialog asking if she wants to allow the application permission to do "dangerous" things. Signed code can't be guaranteed to be safe, but at least the user can evaluate whether the signature belongs to a responsible party. Responsible application developers who distribute applications that require access to "unsafe" operations will typically sign their applications to indicate that they stand behind their application. If a security dialog pops up while you are launching or running a JWS application and you trust whoever signed the code, select "Yes" to allow the code to run with full permissions once, or select "Always" to have Java remember your decision to trust the code.


