Proprietary & Confidential Java WebStart Created by Bob Hays

Proprietary & Confidential What is Java™ WebStart?  Deployment technology for Java Applications Libraries/Components  Implements JNLP – Java Network Launching Protocol, which was created via the Java Community Process (JSR-56)  Java™ WebStart supports: Multiple JREs Code-signing Sandboxing Versioning and incremental updates Desktop integration Offline operation Automatic installation of JREs and optional packages Application launcher  Java™ WebStart is currently at version 1.0.1_01 and can be found at

Proprietary & Confidential Why use Java WebStart and JNLP?  Java provides a rich graphical interface environment, but applets have problems  JNLP allows controlled and secure installation of remotely provided applications  Installation can be simplified and standardized  Installed files are cached locally and checked for update when the application is invoked  “The speed and responsiveness of the application does not depend on the connection speed” 1  “Applications work offline, for example, in a plane when traveling” 1  Maintenance of multiple applications can be handled remotely  Web browser independent 1 ”Java™ WebStart Architecture”,

Proprietary & Confidential JNLP depends upon standards  XML language to describe the installation  HTTP for transmission of executables  WAR file packaging  And Java, of course!

Proprietary & Confidential What are the steps to use Java WebStart?  Set up your web server for delivering WebStart content Configure the Web server so that all files with the.jnlp file extension are set to the application/x-java-jnlp-file MIME type  Pick an application and identify all the jar files required – everything delivered must be in one or more jar files  If the application will run in the sandbox: Use the getResource() method to obtaining information always from within jar files If an application is written to run in a secure sandbox, it must follow these restrictions: No access to local disk. All JAR files must be downloaded from the same host. Network connections are enabled only to the host from which the JAR files are downloaded. No security manager can be installed. No native libraries. Limited access to system properties. The application has read/write access to all system properties defined in the JNLP File, as well as read-only access to the same set of properties than an Applet has access to. An application is allowed to use the System.exit call.  Or if the application will have full access to the customer’s system: Sign all jar files with a common signature You can request full access to the system, and the customer will be prompted to accept this at installation time.

Proprietary & Confidential What are the steps to use Java WebStart? redux  Create a JNLP XML file to describe the installation  Create a web page to deliver the application via WebStart Launch My Application  JavaScript and VBScript is provided for identifying if WebStart is installed and going to an installation point at this URL:

Proprietary & Confidential An example JNLP file, part 1 TrackMyTime Aleph Naught and the Null Set Graphical tool to track time spent on work.

Proprietary & Confidential An example JNLP file, part 2

Proprietary & Confidential What happens when you use WebStart? 1 2 3

Proprietary & Confidential WebStart includes a launcher too

Proprietary & Confidential An example - TrackMyTime You can go to: to see WebStart in action and to download any of four applications: TrackMyTime – a simple time tracking application TrackMyTime Reports – reports for the time tracking tool TrackMyTime Time Editor – edit old and future time records FlatFileFields – a tool to graphically create an XML file to describe a flat file

Proprietary & Confidential Third parties are supporting JNLP and WebStart  OpenJNLP -  Deployment tools: VampHQ - Sitraka DeployDirector Bundler -

Proprietary & Confidential So, what are some of issues Bob has found?  You have to sign ALL jar files with the same signature if you want to play outside the sandbox You have to resign all the Sun extension jars, for example, with your signature  Using tools to build the jar files, handle signatures, and create the XML driver files is very useful I used DeployDirector Bundler and it worked well  When you move a WebStart application on the server, you need to change the JNLP file to contain the new self-pointer.

Proprietary & Confidential Any Questions? Bob Hays Neogration, Inc. (312) Please visit our web site at