Java Web Start (JWS) Installer

Oxygen XML Editor provides the tools to create your own JWS distribution that can be installed on a custom web server. Advantages of a JWS distribution include:

Oxygen XML Editor is run locally, not inside a web browser, overcoming many of the browser compatibility problems common to applets;
JWS ensures that the most current version of the application will be deployed, as well as the correct version of JRE;
applications launched with Java Web Start are cached locally. Thus, an already downloaded application is launched on par with a traditionally installed application;
you can preconfigure Oxygen XML Editor and the rest of your team will use the same preferences and frameworks.

Note: A code signing certificate is needed to sign the JWS distribution. The following procedure assumes that you already have such a certificate (for example Thawte™, or Verisign™, just to name a few).

The following schematics depicts the Oxygen XML Editor Java Web Start deployment procedure:

Java Web Start Deployment Procedure

The following steps describe the procedure of deploying a Oxygen XML Editor installation on a custom server.

Download the All Platforms Installation package from http://www.oxygenxml.com/InstData/Editor/All/oxygen.tar.gz to a local drive.
Expand the archive.
oxygen folder is created.
Optionally, you can customize the content of the frameworks folder, containing default template document files.
Edit the oxygen\tools\jwsPackager\packager.properties configuration file. The following properties need to be adjusted:
- codebase - represents the location of the future JWS distribution;
- keystore - keystore location path;
- storepass - password for keystore integrity;
- storetype - type of the certificate file, like PKCS12 or JKS;
- alias - keystore alias;
- optionsDir - points to the options directory that may be distributed with the JWS installer.
  Note: This property is optional and it is provided only if custom options need to be delivered to the end users.
The values of keystore, storepass, and alias properties are all provided by the code signing certificate. For more information, please check the documentation of the jarsigner tool.
Edit the JNLP oxygen\tools\jwsPackager\dist\javawebstart\oxygen\oxygen.jnlp template file to modify default settings. You can specify the list of files the application opens at startup by modifying the <argument> list. To pass system properties directly to the started Oxygen XML Editor application, you must add them the oxy prefix, like in the example:<property name="oxyPropertyName" value="testValue"/>. The system property is passed to the Oxygen XML Editor application with the prefix stripped.
Using a command-line console, run ant in the oxygen\tools\jwsPackager folder.
The ant process creates the oxygen\tools\jwsPackager\dist\InstData\oxygenJWS.zip archive that contains the actual remote JWS installer.
Copy the expanded content of the archive into the folder specified in the codebase property, previously set in the packager.properties file.
Using your favorite web browser, go to the address specified in the codebase property or to its parent folder and start the remote installer.