This chapter includes the following topics:
Java Web Start is an application-deployment technology that enables your users to launch full-featured applications with a single click from any web browser. Users can download and launch applications without going through complicated installation procedures.
With Java Web Start, your users launch applications by clicking a web page link. If the application is not present on their computer, Java Web Start automatically downloads all necessary files. It then caches the files on the computer so that the application is always ready to be relaunched anytime the user wants—either from an icon on the desktop or from the browser link. No matter which method is used to launch the application, the most current version of the application is always presented.
The technology underlying Java Web Start is the Java Network Launching Protocol & API (JNLP). This technology was developed through the Java Community Process (JCP). Java Web Start is the reference implementation (RI) for the JNLP specification. The JNLP technology defines, among other things, the JNLP file, which is a standard file format that describes how to launch an application. The JNLP specification is available at JSR 56: Java Network Launching Protocol and API.
From a technology standpoint, Java Web Start has a number of key benefits that make it an attractive platform to use for deploying applications.
The benefits include the following:
Java Web Start is built exclusively to launch applications written to the Java Platform, Standard Edition. Thus, a single application can be made available on a web server and then deployed on a wide variety of platforms, including Windows 7+, Linux, and macOS.
Java Web Start supports multiple revisions of the Java Platform, Standard Edition. Thus, an application can request a particular version of the platform it requires, such as Java SE 9. Several applications can run at the same time on different platform revisions without causing conflicts.
Java Web Start enables applications to be launched independently of a web browser. This can be used for off-line operation of an application, where launching the application through the browser is inconvenient or impossible. The application can also be launched through desktop shortcuts, making launching the web-deployed application similar to launching a native application.
Java Web Start takes advantage of security features of the Java Platform. Sandbox applications are run in a protective environment with restricted access to local disk and network resources. Users must also agree to run the application the first time it is launched.
Applications launched with Java Web Start are cached locally. Thus, an already-downloaded application is launched similar to a traditionally installed application.
Java Web Start is included in the Java Platform, Standard Edition development kit (JDK) and Java Runtime Environment (JRE), and includes the security features of the Java platform.
The JDK and JRE are available from the java.com website.
Java Web Start allows you to launch Java-technology-based applications directly from the Web. An application can be launched in three different ways:
From a web browser by clicking a link
From desktop icons or the Start Menu
From the Java Cache Viewer
Regardless of which way is used, Java Web Start will connect back to the web server each time an application is launched, to check whether an updated version of the application is available.
Point your web browser to a page with a link to a JNLP application, and click that link.
A security dialog box will pop up with information about the origin of the application based on who digitally signed the code, and the level of access requested. The application will run only if you decide to trust the vendor.
That is really all there is to using Java Web Start, but how does it work? The HTML links that launch the applications are, in fact, standard HTML links. However, instead of pointing to another web page, they link to a special configuration file called a JNLP file. The web browser examines the file extension or the MIME type of the file, and sees that it belongs to Java Web Start. It then launches Java Web Start with the downloaded JNLP file as an argument. Java Web Start proceeds with downloading, caching, and running the application as directed by the JNLP file.
Java Web Start technology can automatically create shortcuts for your application on the desktop and in the Start Menu for web-deployed applications developed with Java technology. You can use the Java Control Panel to control the shortcut settings. Shortcuts can also be added by using the Java Web Start Cache Viewer, using the install shortcut menu item.
Java Web Start software must be configured with the correct proxy settings in order to launch applications from outside your firewall. Java Web Start software automatically tries to detect the proxy settings from the default browser on your system (Internet Explorer or Mozilla browsers on Microsoft Windows, and Mozilla browsers on the Solaris Operating Environment and Linux). Java Web Start technology supports most web proxy auto-configuration scripts. It can detect proxy settings in almost all environments.
You can also use the Network Settings Tab in the Java Control Panel to view or edit the proxy configuration.
Applications can be deployed from any standard web server. Java Web Start leverages existing internet technology, such as the HTTP protocol and web servers, so existing infrastructure for deploying HTML-based content can be reused to deploy Java Technology-based applications using Java Web Start.
To deploy your application to client machines, ensure that all files that contain your application are accessible through a web server. This typically requires copying one or more JAR files and a JNLP file into the web server's directories. Enabling the website to support Java Web Start is similar to deploying HTML-based content. In addition, to use Java Web Start, the web server must be configured to support the
application/x-java-jnlp-file MIME type.
Many web servers come with the Java Web Start MIME type configured by default. If your web server does not, configure it so that all files with the
.jnlp file extension are set to the
application/x-java-jnlp-file MIME type.
Most web browsers use the MIME type returned with the contents from the web server to determine how to handle the particular content. The server must return the
application/x-java-jnlp-file MIME type for JNLP files in order for Java Web Start to be invoked.
Each web server has a specific way in which to add MIME types. For example, for the Apache web server, you add the following line to the
.mime.types configuration file:
Check the documentation for the specifics of your web server.
The easiest way to create this file is to modify an existing JNLP file with your requirements. A simple JNLP file is shown in the following example:
<?xml version="1.0" encoding="utf-8"?> <jnlp spec="9.0+" codebase="http://example.com/demos/helloworld" href="HelloWorld.jnlp"> <information> <title>HelloWorld</title> <description>HelloWorld demo application</description> </information> <resources> <j2se version="9"/> <jar href="HelloWorld.jar" size="47013" download="eager" /> </resources> <application-desc main-class="HelloWorld"/> </jnlp>
The syntax and format for the JNLP file is described in JNLP File Syntax.
Ensure that your application's JAR files and the JNLP file are accessible at the URLs listed in the JNLP file.
Create the web page and include one of the following options for starting a Java Web Start application:
Use a link to the JNLP file, as shown in the following examples:
<a href="/some/path/HelloWorld.jnlp">Launch HelloWorld demo</a> <a href="https://docs.oracle.com/javase/tutorialJWS/samples/deployment/dynamictree_webstartJWSProject/dynamictree_webstart.jnlp">Launch DynamicTree demo</a> <a href="http://docs.oracle.com/javase/tutorialJWS/samples/deployment/dynamictree_webstartJWSProject/dynamictree_webstart.jnlp">Launch DynamicTree demo</a>
<script src="https://www.java.com/js/deployJava.js"></script> <script> var url = "https://docs.oracle.com/javase/tutorialJWS/samples/deployment/dynamictree_webstartJWSProject/dynamictree_webstart.jnlp"; deployJava.createWebStartLaunchButton(url, '1.6.0'); </script>
Use a link with the
jnlp: schema, as shown in the following example:
<a href="jnlp:https://docs.oracle.com/javase/tutorialJWS/samples/deployment/dynamictree_webstartJWSProject/dynamictree_webstart.jnlp">Launch DynamicTree demo</a>
If you are using the Java Packager tool, see Create the Web Page.
Java Web Start includes a protocol handler to handle the custom URI schemes
jnlps:. Use these schemes as a direct way to start Java Web Start applications.
The protocol handler is automatically installed on Windows and macOS systems. It must be manually installed on Linux systems.
If you use the Chrome browser on Linux, manually install the protocol handler that enables you to start Java Web Start applications using the
xdg-opencommand is used to open a file or URL in the user's preferred application. To install the protocol handler, configure
xdg-opento use Java Web Start for URLs that include the
[Desktop Entry] Encoding=UTF-8 Name=Java(TM) Web Launcher Exec=jre-home/bin/javaws %U Terminal=false Type=Application MimeType=x-scheme-handler/jnlp;x-scheme-handler/jnlps
xdg-mime default javaws.desktop x-scheme-handler/jnlp xdg-mime default javaws.desktop x-scheme-handler/jnlps
jnlpsprotocol. For example, the following URL starts the Dynamic Tree sample from the Java Tutorials:
If you use the Firefox browser on Linux, manually install the protocol handler that enables you to start Java Web Start applications using the
jnlpsprotocol, you are prompted to choose the application to use to open the file. Select Java Web Start Launcher or browse to the