Difference: LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart (1 vs. 73)

Revision 732016-03-03 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="SystemAdministration"

APPX Desktop Client Launched via Java Web Start

Line: 6 to 6
 

Overview

Changed:
<
<
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.2.2 and higher. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. The size of the APPX Java Web Start bundle is about 18 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
>
>
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise. This document applies to APPX Desktop Client version 5.2.2 and higher.

These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. The size of the APPX Java Web Start bundle is about 18 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.

The first time a user connects to the URL, an icon will be added to their desktop. Subsequent connections can be made by just clicking the icon on the desktop.

 

Required software components

APPX Desktop Client Java Web Start Bundle

Line: 16 to 20
 You need a functioning web server configured with jnlp mime type support. Apache and IIS are two common servers.

Quick steps

  • Make sure your Web Server can process .jnlp files
Changed:
<
<
  • Unbundle the APPX Desktop Client Java Web Start Bundle files into a directory off of your web server's web root.
>
>
  • Unbundle the APPX Desktop Client Java Web Start Bundle files into a directory in your web server's web root.
 
  • Edit the .jnlp file and modify the codebase URL and any href tags to suit your APPX installation.

Detailed steps

Line: 33 to 37
  codebase="http://www.abc-company.com/appx/"
Changed:
<
<
At the bottom of the appx.jnlp file, notice the application-desc elements with argument attributes of -windowTitle, -remoteHost, etc. You can add any APPX Desktop Client startup parameter to this section. To see the allowed parameter names, look under 'File->Preferences' after you have logged on.
>
>
You may also want to customize the "<menu submenu="APPX via JWS">" line. This decription is used for the desktop icon that is automatically created, you can change this to something more meaningful for your installation.

At the bottom of the appx.jnlp file, notice the application-desc elements with argument attributes of -windowTitle, -remoteHost, etc. You can add any APPX Desktop Client startup parameter to this section. To see the allowed parameter names, look under 'File->Preferences' after you have logged on. Any changes you make will be used the next time anyone logs in.

 
Table of possible element / attribute available in a JNLP file.

Revision 722016-03-01 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="SystemAdministration"

APPX Desktop Client Launched via Java Web Start

Changed:
<
<
This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
>
>
This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
 

Overview

Changed:
<
<
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.2.2. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 18 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
>
>
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.2.2 and higher. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. The size of the APPX Java Web Start bundle is about 18 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
 

Required software components

APPX Desktop Client Java Web Start Bundle

You can get the APPX Desktop Client Java Web Start Bundle from the Desktop Downloads page.

Deleted:
<
<

APPX Server

You need a functioning APPX installation. Follow the installation instructions for the release to install APPX.

 

Web Server

You need a functioning web server configured with jnlp mime type support. Apache and IIS are two common servers.

Line: 18 to 14
 

Web Server

You need a functioning web server configured with jnlp mime type support. Apache and IIS are two common servers.

Deleted:
<
<
 

Quick steps

Changed:
<
<

APPX Desktop Client Java Web Start Bundle

>
>
  • Make sure your Web Server can process .jnlp files
 
  • Unbundle the APPX Desktop Client Java Web Start Bundle files into a directory off of your web server's web root.
Changed:
<
<
  • Configure the .html file to link to the .jnlp file.
  • Edit the .jnlp file and modify any href tags to fit your web server.
  • Web Server .jnlp mime type settings
    • Apache
      • /etc/mime.types

APPX Server

Install the APPX Server. No special configuration is needed in the APPX Server for APPX Desktop Client connectivity when launched via Java Web Start, just make sure you have an APPX Client Manager ( Unix or Linux or Windows) listening and accepting logins.

>
>
  • Edit the .jnlp file and modify the codebase URL and any href tags to suit your APPX installation.
 

Detailed steps

Here are the steps I used to load the APPX Desktop Client via Java Web Start. These instructions assume that you already have a working installation of APPX Server that is configured with a Client Manager ( Unix or Linux or Windows) and accepting logins. You must also have a web server installed and started.

Line: 38 to 24
 

Download and place the APPX Desktop Client Java Web Start Bundle.

For a Windows Web Server, download the Java Web Start Bundle and place the bundle in a directory off of your web server's web root. Extract the files using the appropriate command (tar or zip).

Changed:
<
<

appx32.gif

The appx32.gif file is the file used as an application runtime icon. It is referenced by the appx.jnlp file that we review later in this document.

appx32.png

The appx32.png file is the file used in a popup in the index.html file that we review later in this document.

appx.css

The appx.css contains css formatting and is referenced in the index.html file that we review later in this document.

README.txt

README.txt contains the following very brief instructions to the reader.

Place these files on your web server.

You need to change one item, replace appxjwsclient.example.com with the hostname and URL to the location of your files.

In appx.jnlp:
    codebase="http://appxjwsclient.example.com/" 

Please see our Wiki at http://wiki.appx.com/wiki/bin/view/Main/LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart for further documentation. 

appx.html

The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.

appx.html contents

[joe@webserver appx]$ *cat appx.html*

<HTML>
   <HEAD>
      <TITLE>APPX Desktop Client Web Start</TITLE>
      <body link="#333333" vlink="#444444" alink="#106D86"> 
   </HEAD>
   <BODY BGCOLOR=#146C86>
      <font face="Verdana, Arial, Helvetica, sans-serif" size="2">
      <font color=white>
      <center>
      
      <hr>
      <font veranda>
      <font style=bold>
      <font size=13pt>
      <font color=white>
APPX Desktop Client Web Start Demonstration
      
      <h3>
Clicking the icon below will attempt to detect if the correct Java JRE is installed, and if possible install it.  If the installer determines you need an updated JRE but it can't auto install a JRE, it will place you on Sun's download page for your platform.  After the JRE requirement is met, the APPX Desktop Client will be downloaded and launched.
      <hr>
      
      <h3>
      <!--<A HREF="http://www.example.com/appx/appx.jnlp">Click</a> To Launch the APPX Desktop Client Demonstration-->
      <!-- Start of Sun's deployJava.js script that attempts to detect if Java is installed and install it or updated -->
      <!-- as needed for Windows, Linux and Mac.  Sun encourages you to hotlink their version of the script -->
      <!-- because they update it as needed.  At the moment, the Windows platform has the best support for detection -->
      <!-- This deployJava.js script is meant to replace the A HREF line above, so we've left it commented out -->
      <script src="http://java.com/js/deployJava.js"></script>
      <script>
         var url = "http://www.example.com/appx/appx.jnlp";
         deployJava.launchButtonPNG = "http://www.example.com/appx/APPXLaunchButton.png";
         deployJava.createWebStartLaunchButton(url, '1.6+');
      </script>
      <BR>
      <hr>
      <h5>Please see our <a href=http://wiki.appx.com/wiki/bin/view/Main/LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart>Wiki</a> for further documentation. 
   </BODY>
</HTML>

[joe@webserver appx]$ 

appx.html modifications

You should change the following two URL values in your appx.html file to match your site.

         var url = " http://www.example.com/appx/appx.jnlp ";
         deployJava.launchButtonPNG = " http://www.example.com/appx/APPXLaunchButton.png ";

splash.gif

This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.

APPXLaunchButton.png

APPXLaunchButton.png is an image file that is displayed for the user to click to begin the JRE detection and ultimately start the APPX Desktop Client.

appx-nativelib.jar

The appx-nativelib.jar file contains platform specific files for the proper execution of the appx.jar file.

appx.jar

>
>

index.html

 
Changed:
<
<
The APPX Desktop Client in Java jar format.
>
>
The index.html file is a starter file that loads the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually. You can customize this file as desired. Alternatively, some browsers will open the .jnlp file directly.
 

appx.jnlp

Changed:
<
<
This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Now take a look at the appx.jnlp file.
appx.jnlp contents
>
>
This is an XML file that defines the environment for the APPX Desktop Client. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. The only change required is the URL of the appx.jnlp file. For example, if we installed the web start bundle in the 'appx' folder of our 'www.abc-company.com' web site, then we would change the 'codebase' line to:
 
Changed:
<
<
[joe@webserver appx]$ *cat appx.jnlp*
<?xml version="1.0" encoding="utf-8"?>
<!-- JNLP File for APPX Desktop Client -->
<jnlp
  spec="6.0+"
  codebase="http://appxjwsclient.example.com/"
  href="appx.jnlp">
  <information>
    <title>APPX</title>
    <vendor>APPX Software, Inc.</vendor>
    <homepage href="http://www.appx.com"/>
    <description>APPX</description>
    <description kind="short">APPX</description>
    <description kind="tooltip">APPX 5.2.2 via JWS</description>
    <icon href="appx32.gif"/>
    <icon kind="shortcut" href="appx32.gif" width="32" height="32"/>
    <icon href="splash.png" kind="splash"/>
    <icon href="appx32.gif" kind="default"/>
    <shortcut online="false">
        <desktop/>
            <menu submenu="APPX">
            </menu>
    </shortcut>
<!--    <offline-allowed/> -->
  </information>
  <security>
      <all-permissions/>
  </security>
  <resources os="Linux" arch="x86">
    <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se"/>
    <property name="swing.noxp" value="true"/>
    <jar href="appx.jar"/>
    <nativelib href="lib/appx-nativelib.jar"/>
    <jar href="lib/capsapi_classes.jar"/>
    <jar href="lib/ckeditor_linux.jar"/>
    <jar href="lib/DJNativeSwing.jar"/>
    <jar href="lib/DJNativeSwing-SWT.jar"/>
    <jar href="lib/js.jar"/>
    <jar href="lib/jsoup.jar"/>
    <jar href="lib/outldd.jar"/>
    <jar href="lib/swt_linux_32.jar"/>
    <jar href="lib/SyntaxHighlighter.jar"/>
  </resources>
  <resources os="Linux" arch="i686">
    <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se"/>
    <property name="swing.noxp" value="true"/>
    <jar href="appx.jar"/>
    <nativelib href="lib/appx-nativelib.jar"/>
    <jar href="lib/capsapi_classes.jar"/>
    <jar href="lib/ckeditor_linux.jar"/>
    <jar href="lib/DJNativeSwing.jar"/>
    <jar href="lib/DJNativeSwing-SWT.jar"/>
    <jar href="lib/js.jar"/>
    <jar href="lib/jsoup.jar"/>
    <jar href="lib/outldd.jar"/>
    <jar href="lib/swt_linux_32.jar"/>
    <jar href="lib/SyntaxHighlighter.jar"/>
  </resources>
  <resources os="Linux" arch="amd64">
    <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se"/>
    <property name="swing.noxp" value="true"/>
    <jar href="appx.jar"/>
    <nativelib href="lib/appx-nativelib.jar"/>
    <jar href="lib/capsapi_classes.jar"/>
    <jar href="lib/ckeditor_linux.jar"/>
    <jar href="lib/DJNativeSwing.jar"/>
    <jar href="lib/DJNativeSwing-SWT.jar"/>
    <jar href="lib/js.jar"/>
    <jar href="lib/jsoup.jar"/>
    <jar href="lib/outldd.jar"/>
    <jar href="lib/swt_linux_64.jar"/>
    <jar href="lib/SyntaxHighlighter.jar"/>
  </resources>
  <resources os="Linux" arch="x86_64">
    <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se"/>
    <property name="swing.noxp" value="true"/>
    <jar href="appx.jar"/>
    <nativelib href="lib/appx-nativelib.jar"/>
    <jar href="lib/capsapi_classes.jar"/>
    <jar href="lib/ckeditor_linux.jar"/>
    <jar href="lib/DJNativeSwing.jar"/>
    <jar href="lib/DJNativeSwing-SWT.jar"/>
    <jar href="lib/js.jar"/>
    <jar href="lib/jsoup.jar"/>
    <jar href="lib/outldd.jar"/>
    <jar href="lib/swt_linux_64.jar"/>
    <jar href="lib/SyntaxHighlighter.jar"/>
  </resources>
  <resources os="Windows" arch="x86">
    <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se"/>
    <property name="swing.noxp" value="true"/>
    <jar href="appx.jar"/>
    <nativelib href="lib/appx-nativelib.jar"/>
    <jar href="lib/capsapi_classes.jar"/>
    <jar href="lib/ckeditor_win.jar"/>
    <jar href="lib/DJNativeSwing.jar"/>
    <jar href="lib/DJNativeSwing-SWT.jar"/>
    <jar href="lib/js.jar"/>
    <jar href="lib/jsoup.jar"/>
    <jar href="lib/outldd.jar"/>
    <jar href="lib/swt_win_32.jar"/>
    <jar href="lib/SyntaxHighlighter.jar"/>
  </resources>
  <resources os="Windows" arch="amd64">
    <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se"/>
    <property name="swing.noxp" value="true"/>
    <jar href="appx.jar"/>
    <nativelib href="lib/appx-nativelib.jar"/>
    <jar href="lib/capsapi_classes.jar"/>
    <jar href="lib/ckeditor_win.jar"/>
    <jar href="lib/DJNativeSwing.jar"/>
    <jar href="lib/DJNativeSwing-SWT.jar"/>
    <jar href="lib/js.jar"/>
    <jar href="lib/jsoup.jar"/>
    <jar href="lib/outldd.jar"/>
    <jar href="lib/swt_win_64.jar"/>
    <jar href="lib/SyntaxHighlighter.jar"/>
  </resources>
  <resources os="Mac OS" arch="x86_64">
    <j2se version="1.6+" href="http://java.sun.com/products/autodl/j2se"/>
    <property name="swing.noxp" value="true"/>
    <jar href="appx.jar"/>
    <nativelib href="lib/appx-nativelib.jar"/>
    <jar href="lib/capsapi_classes.jar"/>
    <jar href="lib/ckeditor_osx.jar"/>
    <jar href="lib/DJNativeSwing.jar"/>
    <jar href="lib/DJNativeSwing-SWT.jar"/>
    <jar href="lib/js.jar"/>
    <jar href="lib/jsoup.jar"/>
    <jar href="lib/outldd.jar"/>
    <jar href="lib/swt_osx_64.jar"/>
    <jar href="lib/SyntaxHighlighter.jar"/>
  </resources>
  <application-desc main-class="start.Appx">
    <argument>-windowTitle=APPX Desktop JWS Client - $(host):$(port) PID:$(pid)</argument>
    <argument>-resizeMainWindowPane=true</argument>
    <!-- <argument>-screenRows=35</argument> -->
    <!-- <argument>-screenColumns=128</argument> -->
    <!-- <argument>-remotePort=1</argument> -->
    <!-- <argument>-remoteHost=www.example.com</argument> -->
    <!-- <argument>-rows=28</argument> -->
    <!-- <argument>-cols=110</argument> -->
    <!-- <argument>-useScrollNavBar=true</argument> -->
    <!-- <argument>-arrowScrollRegion=true</argument> -->
    <!-- <argument>-dockingScrollbar=false</argument> -->
  </application-desc> 
  <update check="always" policy="prompt-update"/>
</jnlp> 

[joe@webserver appx]$ 

appx.jnlp modifications

You should change the following URL value in your appx.jnlp file to match your site.

         
codebase="http://appxjwsclient.example.com/"
>
>
codebase="http://www.abc-company.com/appx/"
 
Changed:
<
<
Towards the end of the appx.jnlp file, notice the application-desc elements with argument attributes of -windowTitle, -remoteHost ... You can add any APPX Desktop Client startup parameter that you normally find when you select Options, Advanced upon initially starting the APPX Desktop Client.
>
>
At the bottom of the appx.jnlp file, notice the application-desc elements with argument attributes of -windowTitle, -remoteHost, etc. You can add any APPX Desktop Client startup parameter to this section. To see the allowed parameter names, look under 'File->Preferences' after you have logged on.
 
Changed:
<
<
Table of possible element / attribute available to you in a JNLP file.
>
>
Table of possible element / attribute available in a JNLP file.
 
Line: 1699 to 1437
 [joe@webserver /]$
Changed:
<
<
Or, if you wish to modify an .htaccess file in your http://www.example.com/appx/ directory, and your web server is configured to allow .htaccess modifications then try the following syntax which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
>
>
Or, if you wish to modify an .htaccess file in your http://www.example.com/appx/ directory, and your web server is configured to allow .htaccess modifications then try the following syntax which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
 
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess* 
[joe@webserver /]$ 

Line: 1743 to 1481
 
  • To clear the Web Start Cache
    • javaws -uninstall This will remove all cached applications.
  • Clear Browser's temporary files.
Changed:
<
<

Comments:

>
>

Comments:

  Read what other users have said about this page or add your own comments.
Deleted:
<
<
<--/commentPlugin-->
-- JoeOrtagus - 04 Mar 2009
 \ No newline at end of file
Added:
>
>
<--/commentPlugin-->
-- JoeOrtagus - 04 Mar 2009

Revision 712016-02-22 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="SystemAdministration"

APPX Desktop Client Launched via Java Web Start

Line: 38 to 38
 

Download and place the APPX Desktop Client Java Web Start Bundle.

For a Windows Web Server, download the Java Web Start Bundle and place the bundle in a directory off of your web server's web root. Extract the files using the appropriate command (tar or zip).

Deleted:
<
<
<span style="color: #630000; font-size: 17.29px; font-weight: bold; line-height: 1em; font-family: Verdana, Arial, Helvetica, sans-serif; background-color: transparent;">APPX Desktop Client Web Start Bundle Components</span>
 

appx32.gif

The appx32.gif file is the file used as an application runtime icon. It is referenced by the appx.jnlp file that we review later in this document.

Revision 702016-02-12 - JeanNeron

Line: 1 to 1
Changed:
<
<
META TOPICPARENT name="APPXAdministrator"
>
>
META TOPICPARENT name="SystemAdministration"
 

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.

Revision 692016-02-11 - JeanNeron

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 10 to 10
 

Required software components

APPX Desktop Client Java Web Start Bundle

Changed:
<
<
You can get the APPX Desktop Client Java Web Start Bundle from here for Unix or Linux or here for Windows.
>
>
You can get the APPX Desktop Client Java Web Start Bundle from the Desktop Downloads page.
 

APPX Server

Changed:
<
<
You need a functioning APPX installation. Follow instructions in this document to install APPX on Windows if you don't already have APPX installed.
>
>
You need a functioning APPX installation. Follow the installation instructions for the release to install APPX.
 

Web Server

You need a functioning web server configured with jnlp mime type support. Apache and IIS are two common servers.

Line: 30 to 30
 

APPX Server

Changed:
<
<
Install APPX Server. No special configuration is needed in the APPX Server for APPX Desktop Client connectivity when launched via Java Web Start, just make sure you have an APPX Client Manager ( Unix or Linux or Windows) listening and accepting logins.
>
>
Install the APPX Server. No special configuration is needed in the APPX Server for APPX Desktop Client connectivity when launched via Java Web Start, just make sure you have an APPX Client Manager ( Unix or Linux or Windows) listening and accepting logins.
 

Detailed steps

Changed:
<
<
Here are the steps I used to load the APPX Desktop Client via Java Web Start. These instructions assume that you already have a working installation of APPX Server that is configured with a Client Manager (Unix or Linux or Windows) and accepting logins. You must also have a web server installed and started.
>
>
Here are the steps I used to load the APPX Desktop Client via Java Web Start. These instructions assume that you already have a working installation of APPX Server that is configured with a Client Manager ( Unix or Linux or Windows) and accepting logins. You must also have a web server installed and started.
 

Download and place the APPX Desktop Client Java Web Start Bundle.

Changed:
<
<
For a Windows Web Server, download the Java Web Start Bundle from here. For my Linux/Unix server I downloaded version 5.0.4 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
>
>
For a Windows Web Server, download the Java Web Start Bundle and place the bundle in a directory off of your web server's web root. Extract the files using the appropriate command (tar or zip).
 
Changed:
<
<
  • I am going to use the command line tool wget to fetch the file bundle:

[joe@webserver /]$ *cd /var/www/html* 
[joe@webserver /]$ <strong>sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.2.2/java_web.tgz
</strong>[joe@webserver html]$ 

  • Now let's untar the files

[joe@webserver html]$ *sudo tar -xzvf java_web.tgz*

appx/
appx/appx.jar
appx/appx32.png
appx/downloadbutton.gif
appx/lib/
appx/lib/ckeditor_linux.jar
appx/lib/ckeditor_win.version
appx/lib/swt_linux_64.version
appx/lib/jsoup.jar
appx/lib/outldd.version
appx/lib/ckeditor_linux.version
appx/lib/ckeditor_win.jar
appx/lib/SyntaxHighlighter.version
appx/lib/capsapi_classes.jar
appx/lib/swt_linux_32.version
appx/lib/swt_linux_64.jar
appx/lib/swt_win_32.version
appx/lib/swt_linux_32.jar
appx/lib/swt_osx_64.version
appx/lib/swt_win_64.jar
appx/lib/DJNativeSwing.jar
appx/lib/swt_osx_64.jar
appx/lib/SyntaxHighlighter.jar
appx/lib/js.jar
appx/lib/swt_osx_32.version
appx/lib/jsoup.version
appx/lib/DJNativeSwing-SWT.jar
appx/lib/appx-nativelib.jar
appx/lib/outldd.jar
appx/lib/swt_osx_32.jar
appx/lib/ckeditor_osx.version
appx/lib/DJNativeSwing.version
appx/lib/swt_win_64.version
appx/lib/swt_win_32.jar
appx/lib/DJNativeSwing-SWT.version
appx/lib/ckeditor_osx.jar
appx/INSTALL.txt
appx/index.html
appx/appx.jnlp
appx/splash.png
appx/appx.css
appx/appx32.gif
appx/appx-small.png
appx/README.txt
appx/arrow.gif

[joe@webserver html]$ *ls -la*

total 1216
drwxr-xr-x  3 root root    4096 Mar  4 14:27 .
drwxr-xr-x 10 root root    4096 Jun 26  2007 ..
drwxr-xr-x 3 root root     4096 Feb 21 13:07 appx
-rw-r--r-- 1 root root 17038663 Feb 21 13:20 java_web.tgz

[joe@webserver html]$ *cd appx*
[joe@webserver appx]$ *ls*

total 1372
drwxr-xr-x 3 root root    4096 Feb 21 13:07 .
drwxr-xr-x 3 root root    4096 Feb 21 13:20 ..
-r-xr-xr-x 1 root root     139 Jan  9 10:07 appx32.gif
-r-xr-xr-x 1 root root    3688 Jan 14 15:23 appx32.png
-r-xr-xr-x 1 root root    4342 Feb 21 12:41 appx.css
-r-xr-xr-x 1 root root 1314083 Jan 10 17:22 appx.jar
-r-xr-xr-x 1 root root    5732 Feb 21 13:04 appx.jnlp
-r-xr-xr-x 1 root root   16233 Jan  9 10:07 appx-small.png
-r-xr-xr-x 1 root root    2073 Jan 14 15:29 arrow.gif
-r-xr-xr-x 1 root root     708 Jan  9 10:07 downloadbutton.gif
-r-xr-xr-x 1 root root    3514 Feb 21 12:54 index.html
-r-xr-xr-x 1 root root      15 Jan  9 10:07 INSTALL.txt
dr-xr-xr-x 2 root root    4096 Feb 21 12:58 lib
-r-xr-xr-x 1 root root     369 Feb 21 13:07 README.txt
-r-xr-xr-x 1 root root   15402 Jan  9 10:07 splash.png

APPX Desktop Client Web Start Bundle Components

>
>
<span style="color: #630000; font-size: 17.29px; font-weight: bold; line-height: 1em; font-family: Verdana, Arial, Helvetica, sans-serif; background-color: transparent;">APPX Desktop Client Web Start Bundle Components</span>
 

appx32.gif

The appx32.gif file is the file used as an application runtime icon. It is referenced by the appx.jnlp file that we review later in this document.

Line: 145 to 53
  README.txt contains the following very brief instructions to the reader.
Changed:
<
<
>
>
 Place these files on your web server.

You need to change one item, replace appxjwsclient.example.com with the hostname and URL to the location of your files.

Line: 159 to 67
  The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.
appx.html contents
Changed:
<
<
[joe@webserver appx]$ *cat appx.html*

>
>
[joe@webserver appx]$ *cat appx.html*

 
Changed:
<
<
>
>
  APPX Desktop Client Web Start
Line: 202 to 111
 
Changed:
<
<
[joe@webserver appx]$
>
>
[joe@webserver appx]$
 
appx.html modifications

You should change the following two URL values in your appx.html file to match your site.

Changed:
<
<
         var url = " http://www.example.com/appx/appx.jnlp ";

>
>
         var url = " http://www.example.com/appx/appx.jnlp ";

  deployJava.launchButtonPNG = " APPXLaunchButton.png ";
Line: 230 to 138
  This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Now take a look at the appx.jnlp file.
appx.jnlp contents
Changed:
<
<
[joe@webserver appx]$ *cat appx.jnlp*
>
>
[joe@webserver appx]$ *cat appx.jnlp*
 
<-- JNLP File for APPX Desktop Client -->
<jnlp
Line: 380 to 289
 
Changed:
<
<
[joe@webserver appx]$
>
>
[joe@webserver appx]$
 
appx.jnlp modifications

You should change the following URL value in your appx.jnlp file to match your site.

Changed:
<
<
         
codebase="http://appxjwsclient.example.com/"
>
>
         
codebase="http://appxjwsclient.example.com/"
  Towards the end of the appx.jnlp file, notice the application-desc elements with argument attributes of -windowTitle, -remoteHost ... You can add any APPX Desktop Client startup parameter that you normally find when you select Options, Advanced upon initially starting the APPX Desktop Client.

Table of possible element / attribute available to you in a JNLP file.
Changed:
<
<
>
>
  Element
Line: 1788 to 1697
  If you wish to modify the Apache global TypesConfig file and the file exists in /etc/mime.types, then you might try syntax like the following which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
Changed:
<
<
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types*

>
>
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types*

 [joe@webserver /]$

Or, if you wish to modify an .htaccess file in your http://www.example.com/appx/ directory, and your web server is configured to allow .htaccess modifications then try the following syntax which will grep for the jnlp entry, and if not found will append an entry for jnlp support.

Changed:
<
<
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess* 

>
>
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess* 

 [joe@webserver /]$
Line: 1836 to 1745
 
  • To clear the Web Start Cache
    • javaws -uninstall This will remove all cached applications.
  • Clear Browser's temporary files.
Changed:
<
<

Bugs:

  1. Fixed - Bug Description 1.
  2. OPEN - Bug test - Test bug. Not valid.

Comments:

>
>

Comments:

  Read what other users have said about this page or add your own comments.
Deleted:
<
<
Is there a .zip version of java_web.tgz? Or something that Windows Vista knows how to uncompress?

-- RogerHuffman - 26 Mar 2009

You should be able to use WinRAR to unzip a tgz file on Windows. WinRAR is a free download, available at http://download.cnet.com/WinRAR/3000-2250_4-10007677.html, and other places as well. But your point is a good one, and we'll probably add a zip file version shortly.

-- AlKalter - 26 Mar 2009

The application cannot connect if the user’s browser has a proxy server configured. The browser downloads the “JAR” file without any problem, when I give the user name and password I cannot connect to APPX server. Is there any configuration that can solve this problem?

-- GerardoLopez - 01 Apr 2009

 
<--/commentPlugin-->
-- JoeOrtagus - 04 Mar 2009

Revision 682013-02-21 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 6 to 6
 

Overview

Changed:
<
<
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.0.4 and above. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 1.3 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
>
>
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.2.2. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 18 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
 

Required software components

APPX Desktop Client Java Web Start Bundle

Changed:
<
<
You can get the APPX Desktop Client Java Web Start Bundle from here for Unix or Linux or here for Windows.
>
>
You can get the APPX Desktop Client Java Web Start Bundle from here for Unix or Linux or here for Windows.
 

APPX Server

Line: 43 to 43
 
Changed:
<
<
[joe@webserver /]$ *cd /var/www/html* 
[joe@webserver /]$ *sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4/java_web.tgz*
[joe@webserver html]$ 

>
>
[joe@webserver /]$ *cd /var/www/html* 
[joe@webserver /]$ <strong>sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.2.2/java_web.tgz
</strong>[joe@webserver html]$ 
 

  • Now let's untar the files
Changed:
<
<
[joe@webserver html]$ *sudo tar xzvf java_web.tgz*

>
>
[joe@webserver html]$ *sudo tar -xzvf java_web.tgz*
 
Changed:
<
<
appx/
appx/appx32.gif
appx/README.txt
appx/INSTALL.txt
appx/appx.html
appx/splash.gif
appx/APPXLaunchButton.png
appx/appx-small.png
appx/appx-nativelib.jar
appx/appx.jar
appx/appx.jnlp
>
>
appx/
appx/appx.jar
appx/appx32.png
appx/downloadbutton.gif
appx/lib/
appx/lib/ckeditor_linux.jar
appx/lib/ckeditor_win.version
appx/lib/swt_linux_64.version
appx/lib/jsoup.jar
appx/lib/outldd.version
appx/lib/ckeditor_linux.version
appx/lib/ckeditor_win.jar
appx/lib/SyntaxHighlighter.version
appx/lib/capsapi_classes.jar
appx/lib/swt_linux_32.version
appx/lib/swt_linux_64.jar
appx/lib/swt_win_32.version
appx/lib/swt_linux_32.jar
appx/lib/swt_osx_64.version
appx/lib/swt_win_64.jar
appx/lib/DJNativeSwing.jar
appx/lib/swt_osx_64.jar
appx/lib/SyntaxHighlighter.jar
appx/lib/js.jar
appx/lib/swt_osx_32.version
appx/lib/jsoup.version
appx/lib/DJNativeSwing-SWT.jar
appx/lib/appx-nativelib.jar
appx/lib/outldd.jar
appx/lib/swt_osx_32.jar
appx/lib/ckeditor_osx.version
appx/lib/DJNativeSwing.version
appx/lib/swt_win_64.version
appx/lib/swt_win_32.jar
appx/lib/DJNativeSwing-SWT.version
appx/lib/ckeditor_osx.jar
appx/INSTALL.txt
appx/index.html
appx/appx.jnlp
appx/splash.png
appx/appx.css
appx/appx32.gif
appx/appx-small.png
appx/README.txt
appx/arrow.gif
 
Changed:
<
<
[joe@webserver html]$ *ls -la*

>
>
[joe@webserver html]$ *ls -la*
 
Changed:
<
<
total 1216

>
>
total 1216
 drwxr-xr-x 3 root root 4096 Mar 4 14:27 . drwxr-xr-x 10 root root 4096 Jun 26 2007 ..
Changed:
<
<
drwxrwxrwx 2 root root 4096 Mar 3 14:40 appx -rw-r--r-- 1 root root 1233805 Mar 4 14:27 java_web.tgz
>
>
drwxr-xr-x 3 root root 4096 Feb 21 13:07 appx -rw-r--r-- 1 root root 17038663 Feb 21 13:20 java_web.tgz
 
Changed:
<
<
[joe@webserver html]$ *cd appx*
[joe@webserver appx]$ *ls*

>
>
[joe@webserver html]$ *cd appx*
[joe@webserver appx]$ *ls*
 
Changed:
<
<
appx32.gif  appx.html  appx.jar  appx.jnlp  APPXLaunchButton.png appx-small.png appx-nativelib.jar  INSTALL.txt  README.txt  splash.gif

>
>
total 1372
drwxr-xr-x 3 root root    4096 Feb 21 13:07 .
drwxr-xr-x 3 root root    4096 Feb 21 13:20 ..
-r-xr-xr-x 1 root root     139 Jan  9 10:07 appx32.gif
-r-xr-xr-x 1 root root    3688 Jan 14 15:23 appx32.png
-r-xr-xr-x 1 root root    4342 Feb 21 12:41 appx.css
-r-xr-xr-x 1 root root 1314083 Jan 10 17:22 appx.jar
-r-xr-xr-x 1 root root    5732 Feb 21 13:04 appx.jnlp
-r-xr-xr-x 1 root root   16233 Jan  9 10:07 appx-small.png
-r-xr-xr-x 1 root root    2073 Jan 14 15:29 arrow.gif
-r-xr-xr-x 1 root root     708 Jan  9 10:07 downloadbutton.gif
-r-xr-xr-x 1 root root    3514 Feb 21 12:54 index.html
-r-xr-xr-x 1 root root      15 Jan  9 10:07 INSTALL.txt
dr-xr-xr-x 2 root root    4096 Feb 21 12:58 lib
-r-xr-xr-x 1 root root     369 Feb 21 13:07 README.txt
-r-xr-xr-x 1 root root   15402 Jan  9 10:07 splash.png
 

APPX Desktop Client Web Start Bundle Components

appx32.gif

The appx32.gif file is the file used as an application runtime icon. It is referenced by the appx.jnlp file that we review later in this document.

Added:
>
>

appx32.png

The appx32.png file is the file used in a popup in the index.html file that we review later in this document.

appx.css

The appx.css contains css formatting and is referenced in the index.html file that we review later in this document.

 

README.txt

README.txt contains the following very brief instructions to the reader.

Changed:
<
<
Place these files in a directory named /appx/ off your web server's webroot.

You need to change three items, all references to www.example.com to read your site URL:

In appx.html appx.html: ---> var url = "http://www.example.com/appx/appx.jnlp"; appx.html: ---> deployJava.launchButtonPNG = "http://www.example.com/appx/APPXLaunchButton.png";

>
>
Place these files on your web server.
 
Added:
>
>
You need to change one item, replace appxjwsclient.example.com with the hostname and URL to the location of your files.
  In appx.jnlp:
Changed:
<
<
appx.jnlp: --->

Please see our Wiki at http://wiki.appx.com/wiki/bin/view/Main/LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart for further documentation.

>
>
codebase="http://appxjwsclient.example.com/"
 
Changed:
<
<

INSTALL.txt

>
>
Please see our Wiki at http://wiki.appx.com/wiki/bin/view/Main/LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart for further documentation.
 
Deleted:
<
<
INSTALL.txt points the reader to README.txt
 

appx.html

The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.

Line: 188 to 233
 
[joe@webserver appx]$ *cat appx.jnlp*
<?xml version="1.0" encoding="utf-8"?>
Deleted:
<
<
<-- JNLP File for APPX Desktop Client 5.0.4 -->
 
<-- JNLP File for APPX Desktop Client  -->
Changed:
<
<
<-- example JNLP file that will launch the APPX Desktop Client 5.0.4 -->

<-- where the jnlp file lives on the web -->
>
>
<jnlp spec="6.0+" codebase="http://appxjwsclient.example.com/" href="appx.jnlp">
 
Changed:
<
<
APPX Desktop Client Java Web Start Demo Application
>
>
APPX
  APPX Software, Inc.
Changed:
<
<
APPX Desktop Client version 5.0.4. Connects to APPX Client Login Manager.
<-- hover help for this app.  -->
APPX Desktop Client 5.0.4
<-- This is the APPX Desktop Client application icon and splash screen. -->
<-- relative to codebase -->
>
>
APPX APPX APPX 5.2.2 via JWS
 
Changed:
<
<
<-- allow app to run without Internet access -->
<offline-allowed />
>
>
<--    <offline-allowed/> -->
 
Deleted:
<
<
<-- The APPX Desktop Client requires the all-permissions value for the security element -->
  <all-permissions />
Changed:
<
<
<-- Acceptable JVMs in preferred order, best first -->
<-- Sun JVM -->
>
>
 
Deleted:
<
<
<-- This swing.noxp value prevents a "look and feel" issue on Vista -->
 
Changed:
<
<
<-- application code, load before launch. JNLP 1.6 main="true" indicates jar with main class -->
>
>
 
Deleted:
<
<
<-- application class with main method -->
<-- This is the section where you would add startup parameters for the APPX -->
<-- Desktop Client.  Items such as TCP port number, initial window size etc -->
  <application-desc main-class="start.Appx">
Changed:
<
<
<-- command line arguments -->
-windowTitle=APPX - $(host):$(port) -remotePort=8064 -remoteUser=prospect -remoteHost=demo.appx.com -remotePassword=prospect -screenRows=28 -screenColumns=110 -SSLMode=disabled
>
>
-windowTitle=APPX Desktop JWS Client - $(host):$(port) PID:$(pid) -resizeMainWindowPane=true
<-- -screenRows=35 -->
<-- -screenColumns=128 -->
<-- -remotePort=1 -->
<-- -remoteHost=www.example.com -->
<-- -rows=28 -->
<-- -cols=110 -->
<-- -useScrollNavBar=true -->
<-- -arrowScrollRegion=true -->
<-- -dockingScrollbar=false -->
  </application-desc>
Added:
>
>
 

[joe@webserver appx]$

Line: 249 to 386
 
appx.jnlp modifications

You should change the following URL value in your appx.jnlp file to match your site.

Changed:
<
<
         codebase=" http://www.example.com/appx " href="appx.jnlp"
>
>
         
codebase="http://appxjwsclient.example.com/"
  Towards the end of the appx.jnlp file, notice the application-desc elements with argument attributes of -windowTitle, -remoteHost ... You can add any APPX Desktop Client startup parameter that you normally find when you select Options, Advanced upon initially starting the APPX Desktop Client.

Revision 672012-04-05 - BredaHennessy

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 352 to 352
 
Changed:
<
<
The information element contains other elements that describe the application and it's source.
>
>
The information element contains other elements that describe the application and its source.
 
Line: 628 to 628
 
Changed:
<
<
Can be used to indicate an application's preference for putting a shortcut on the users desktop.
>
>
Can be used to indicate an application's preference for putting a shortcut on the user's desktop.
 

1.5.0

Line: 1098 to 1098
 
Changed:
<
<
Specifies a JAR file that contains native libraries in it's root directory.
>
>
Specifies a JAR file that contains native libraries in its root directory.
 

1.0

Line: 1342 to 1342
 recursive
Changed:
<
<
Can be used to indicated that all package names beginning with the given name, can be found in the given part.
>
>
Can be used to indicate that all package names beginning with the given name, can be found in the given part.
 

1.0

Revision 662012-03-27 - ChrisBrower

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 43 to 43
 
Changed:
<
<
[joe@webserver /]$ cd /var/www/html 
[joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4/java_web.tgz

>
>
[joe@webserver /]$ *cd /var/www/html* 
[joe@webserver /]$ *sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4/java_web.tgz*

 [joe@webserver html]$

  • Now let's untar the files
Changed:
<
<
[joe@webserver html]$ sudo tar xzvf java_web.tgz

>
>
[joe@webserver html]$ *sudo tar xzvf java_web.tgz*

 

appx/

Line: 66 to 66
 appx/appx.jnlp
Changed:
<
<
[joe@webserver html]$ ls -la

>
>
[joe@webserver html]$ *ls -la*

 

total 1216

Line: 76 to 76
 -rw-r--r-- 1 root root 1233805 Mar 4 14:27 java_web.tgz
Changed:
<
<
[joe@webserver html]$ cd appx
[joe@webserver appx]$ ls

>
>
[joe@webserver html]$ *cd appx*
[joe@webserver appx]$ *ls*

 

appx32.gif  appx.html  appx.jar  appx.jnlp  APPXLaunchButton.png appx-small.png appx-nativelib.jar  INSTALL.txt  README.txt  splash.gif

Line: 114 to 114
  The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.
appx.html contents
Changed:
<
<
[joe@webserver appx]$ cat appx.html

>
>
[joe@webserver appx]$ *cat appx.html*

 

Line: 171 to 171
  This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.
Changed:
<
<

APPXLaunchButton.png

>
>

APPXLaunchButton.png

 
Changed:
<
<
APPXLaunchButton.png is an image file that is displayed for the user to click to begin the JRE detection and ultimately start the APPX Desktop Client.
>
>
APPXLaunchButton.png is an image file that is displayed for the user to click to begin the JRE detection and ultimately start the APPX Desktop Client.
 

appx-nativelib.jar

The appx-nativelib.jar file contains platform specific files for the proper execution of the appx.jar file.

Line: 185 to 185
  This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Now take a look at the appx.jnlp file.
appx.jnlp contents
Changed:
<
<
[joe@webserver appx]$ cat appx.jnlp

>
>
[joe@webserver appx]$ *cat appx.jnlp*

 
<?xml version="1.0" encoding="utf-8"?>
<!-- JNLP File for APPX Desktop Client 5.0.4 -->
Line: 255 to 255
 Towards the end of the appx.jnlp file, notice the application-desc elements with argument attributes of -windowTitle, -remoteHost ... You can add any APPX Desktop Client startup parameter that you normally find when you select Options, Advanced upon initially starting the APPX Desktop Client.

Table of possible element / attribute available to you in a JNLP file.
Deleted:
<
<
 
Changed:
<
<

>
>
  Element

Attributes

Changed:
<
<

>
>
  Description
Line: 277 to 272
 

Required

Changed:
<
<

>
>
  jnlp
Changed:
<
<
>
>
 
Changed:
<
<

>
>
  This is the main xml element for a jnlp file. Everything is contained within the jnlp element.
Line: 301 to 290
 
Changed:
<
<

>
>
  spec

The spec attribute can be 1.0, 1.5.0, or 1.6.0 or can use the wildcards such as 1.0+ or 1.6+. It denoted the minimum version of the JNLP Specification that this jnlp file can work with.

Changed:
<
<

>
>
  1.0

Changed:
<
<

>
>
 

codebase

Changed:
<
<

>
>
  The codebase attribute specifies the base location for all relative URLs specified in href attributes in the JNLP file.
Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
 
Changed:
<
<
>
>
 

href

Changed:
<
<

>
>
  The href specifies the URL of the JNLP file itself.
Line: 356 to 329
 1.0
Changed:
<
<

>
>
 
Line: 383 to 354
  The information element contains other elements that describe the application and it's source.
Changed:
<
<

>
>
  1.0

yes

Changed:
<
<

>
>
 
Line: 410 to 375
 
Changed:
<
<

>
>
 
Changed:
<
<
>
>
  arch
Line: 430 to 391
 
Changed:
<
<

>
>
  platform

Specifies the platform for which this information element should be considered.

Changed:
<
<

>
>
  1.5.0
Changed:
<
<

>
>
 

locale

Changed:
<
<

>
>
  Specifies the locale for which this information element should be considered.
Line: 488 to 439
 

The vendor element specifies the provider of the application.

Changed:
<
<

>
>
  1.0

yes

Changed:
<
<

>
>
  homepage
Changed:
<
<

>
>
  The homepage of the application.
Line: 524 to 467
 

A URL pointing to where more information on this application can be found.

Changed:
<
<

>
>
  1.0

yes

Changed:
<
<

>
>
  description
Changed:
<
<

>
>
  A short statement describing the application.
Line: 558 to 495
 

An indicator as to what type of description this is, legal values are one-line, short, and tooltip.

Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
  icon
Changed:
<
<

>
>
  Describes an icon that can be used to identify the application to the user.
Line: 590 to 521
 

A URL pointing to the icon file, may be in one of the following formats: gif, jpg, png, ico.

Changed:
<
<

>
>
  1.0

yes

Changed:
<
<

>
>
 

kind

Changed:
<
<

>
>
  Indicates the suggested use of the icon, can be: default, selected, disabled, rollover, splash, or shortcut.
Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
 

width

Changed:
<
<

>
>
  Can be used to indicate the resolution of the image.
Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
 

height

Changed:
<
<

>
>
  Can be used to indicate the resolution of the image.
Line: 663 to 576
 

Can be used to indicate the resolution of the image.

Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
  offline-allowed
Changed:
<
<

>
>
  Indicates that this application can operate when the client system is disconnected from the network.
Line: 690 to 597
 

shortcut

Changed:
<
<

>
>
 
Line: 703 to 608
 
Changed:
<
<

>
>
 
Line: 713 to 616
 

Can be used to describe the application's preference for creating a shortcut to run online or offline.

Changed:
<
<

>
>
  1.5.0
Changed:
<
<

>
>
  desktop
Changed:
<
<

>
>
  Can be used to indicate an application's preference for putting a shortcut on the users desktop.
Line: 753 to 650
 
Changed:
<
<

>
>
 
Line: 764 to 659
 

Can be used to indicate an application's preference for where to place the menu item.

Changed:
<
<

>
>
  1.5.0
Changed:
<
<

>
>
 
Changed:
<
<
>
>
  association

Changed:
<
<

>
>
  Can be used to hint to the JNLP client that it wishes to be registered with the operating system as the primary handler of certain extensions and a certain mime-type.
Line: 792 to 679
 1.5.0
Changed:
<
<

>
>
 
Line: 807 to 692
  1.5.0
Changed:
<
<

>
>
 
Line: 820 to 703
  Contains the mime-type that the application requests it be registered to handle.
Changed:
<
<

>
>
  1.5.0
Changed:
<
<

>
>
  related-content
Changed:
<
<

>
>
  Describes an additional piece of related content that may be integrated with the application.

1.5.0

Changed:
<
<

>
>
 
Line: 864 to 737
 

yes

Changed:
<
<

>
>
 
Line: 876 to 747
 
Changed:
<
<

>
>
  update
Line: 895 to 762
 
Changed:
<
<

>
>
  check
Line: 910 to 775
 
Changed:
<
<

>
>
 
Line: 921 to 784
 

Indicates the preference for how the JNLP Client should handle an application update when it is known an update is available before the application is launched. It can be always, prompt-update, or prompt-run.

Changed:
<
<

>
>
  1.6.0

Changed:
<
<

>
>
 
Changed:
<
<

>
>
 
Line: 947 to 804
 

security

Changed:
<
<

>
>
 
Line: 960 to 815
 
Changed:
<
<

>
>
  all-permissions
Line: 976 to 829
 1.0
Changed:
<
<

>
>
  j2ee-application-client-permissions
Line: 989 to 840
 

1.0

Changed:
<
<

>
>
 
Line: 999 to 848
 
Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
  resources
Changed:
<
<

>
>
  Describes all the resources that are needed for an application.

1.0

Changed:
<
<

>
>
  yes
Line: 1038 to 877
 

Specifies the operating system for which the resources element should be considered.

Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
 
Changed:
<
<
>
>
  arch
Changed:
<
<

>
>
  Specifies the architecture for which the resources element should be considered.
Line: 1073 to 904
 

Specifies that the locales for which the resources element should be considered.

Changed:
<
<

>
>
 
Changed:
<
<

>
>
  java (or java se)
Changed:
<
<

>
>
  Specifies what version(s) of Java to run the application with.

1.6.0 (java)

Changed:
<
<

>
>
 
Changed:
<
<

>
>
  version
Line: 1116 to 937
 

yes

Changed:
<
<

>
>
 
Line: 1127 to 946
 

The URL denoting the supplier of this version of java, and where it may be downloaded from.

Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
 
Changed:
<
<
>
>
 

java-vm-args

Changed:
<
<

>
>
  Indicates an additional set of standard and non-standard virtual machine arguments that the application would prefer the JNLP
Line: 1178 to 989
  Indicates the maximum size of the Java heap.
Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
  jar
Changed:
<
<

>
>
  Specifies a JAR file that is part of the application's classpath.

1.0

Changed:
<
<

>
>
  yes
Line: 1217 to 1018
 

The URL of the jar file.

Changed:
<
<

>
>
  1.0

yes

Changed:
<
<

>
>
 
Changed:
<
<
>
>
  version
Changed:
<
<

>
>
  The requested version of the jar file. Requires using the version-based download protocol
Line: 1253 to 1046
 

Indicates if this jar contains the class containing the main method of the application.

Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
 

download

Changed:
<
<

>
>
  Can be used to indicate this jar may be downloaded lazily, or when needed.
Line: 1285 to 1072
 

Indicates the downloadable size of the jar file in bytes.

Changed:
<
<

>
>
  1.0

Changed:
<
<

>
>
 

part

Changed:
<
<

>
>
  Can be used to group resources together so they will be downloaded at the same time.
Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
  nativelib
Changed:
<
<

>
>
 
Changed:
<
<
>
>
  Specifies a JAR file that contains native libraries in it's root directory.
Line: 1331 to 1104
 1.0
Changed:
<
<

>
>
 
Line: 1357 to 1128
 

The requested version of the jar file. Requires using the version-based download protocol

Changed:
<
<

>
>
  1.0

Changed:
<
<

>
>
 

download

Changed:
<
<

>
>
  Can be used to indicate this jar may be downloaded lazily.
Line: 1383 to 1148
 1.0
Changed:
<
<

>
>
 
Line: 1398 to 1161
  1.0
Changed:
<
<

>
>
 
Line: 1410 to 1171
 

Can be used to group resources together so they will be downloaded at the same time.

Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
  extension
Changed:
<
<

>
>
  Contains pointer to an additional component-desc or installer-desc to be used with this application.
Line: 1450 to 1205
 

yes

Changed:
<
<

>
>
 
Line: 1461 to 1214
 

The version of the additional extension jnlp file.

Changed:
<
<

>
>
  1.0

Changed:
<
<

>
>
 

name

Changed:
<
<

>
>
  The name of the additional extension jnlp file
Line: 1487 to 1234
 1.0
Changed:
<
<

>
>
  ext-download
Line: 1501 to 1246
  1.0
Changed:
<
<

>
>
 
Line: 1513 to 1256
 

Describes the name of a part that can be expected to be found in the extension.

Changed:
<
<

>
>
  1.0

yes

Changed:
<
<

>
>
 

download

Changed:
<
<

>
>
  Can be used to indicate this extension may be downloaded eagerly or lazily.
Line: 1555 to 1290
 1.0
Changed:
<
<

>
>
  package
Changed:
<
<

>
>
 
Line: 1573 to 1304
 
Changed:
<
<

>
>
 
Line: 1591 to 1320
  yes
Changed:
<
<

>
>
 
Line: 1605 to 1332
 

1.0

Changed:
<
<

>
>
  yes
Changed:
<
<

>
>
  recursive

Can be used to indicated that all package names beginning with the given name, can be found in the given part.

Changed:
<
<

>
>
  1.0

Changed:
<
<

>
>
  property

Changed:
<
<

>
>
  Defines a system property that will be available through the System.getProperty and System.getProperties methods.
Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
 

name

Changed:
<
<

>
>
  Name of the system property.
Changed:
<
<

>
>
  1.0

yes

Changed:
<
<

>
>
 

value

Changed:
<
<

>
>
  Value it will be set to.
Line: 1690 to 1395
 yes
Changed:
<
<

>
>
 
Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
 
Line: 1735 to 1432
 

1.0

Changed:
<
<

>
>
 
Changed:
<
<
>
>
 
Line: 1753 to 1446
 

1.0

Changed:
<
<

>
>
  yes
Line: 1768 to 1459
  Each argument contains (in order) an additional argument to be passed to main.
Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
  applet-desc
Changed:
<
<

>
>
  Denotes this is the jnlp file for an applet.

1.0

Changed:
<
<

>
>
 
Changed:
<
<

>
>
  main-class
Line: 1814 to 1493
 

yes

Changed:
<
<

>
>
 
Line: 1825 to 1502
 

The document base for the Applet as a URL.

Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
 
Changed:
<
<
>
>
 

name

Changed:
<
<

>
>
  Name of the Applet.
Line: 1854 to 1523
  yes
Changed:
<
<

>
>
 
Line: 1868 to 1535
 

1.0

Changed:
<
<

>
>
  yes
Changed:
<
<

>
>
  height

The height of the applet in pixels

Changed:
<
<

>
>
  1.0

yes

Changed:
<
<

>
>
  param

Changed:
<
<

>
>
  A set of parameters that can be passed into the applet.
Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
 

name

Changed:
<
<

>
>
  The name of this parameter
Changed:
<
<

>
>
  1.0

yes

Changed:
<
<

>
>
 

value

Changed:
<
<

>
>
  The value of this parameter
Line: 1960 to 1605
 

Denotes this is the jnlp file for a component extension.

Changed:
<
<

>
>
  1.0

Changed:
<
<

>
>
  installer-desc

Changed:
<
<

>
>
  Denotes this is the jnlp file for an installed extension.
Changed:
<
<

>
>
  1.0
Changed:
<
<

>
>
 
Changed:
<
<
>
>
 

main-class

Changed:
<
<

>
>
  The name of the class containing the public static void main(String[]) method of the installer.
Line: 2010 to 1641
  yes
Changed:
<
<

>
>
 

Configure your web server's jnlp Mime type settings.

Line: 2023 to 1652
  If you wish to modify the Apache global TypesConfig file and the file exists in /etc/mime.types, then you might try syntax like the following which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
Changed:
<
<
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types

>
>
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types*

 [joe@webserver /]$

Or, if you wish to modify an .htaccess file in your http://www.example.com/appx/ directory, and your web server is configured to allow .htaccess modifications then try the following syntax which will grep for the jnlp entry, and if not found will append an entry for jnlp support.

Changed:
<
<
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess 

>
>
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess* 

 [joe@webserver /]$
Line: 2084 to 1712
  -- RogerHuffman - 26 Mar 2009
Changed:
<
<
You should be able to use WinRAR to unzip a tgz file on Windows. WinRAR is a free download, available at http://download.cnet.com/WinRAR/3000-2250_4-10007677.html, and other places as well. But your point is a good one, and we'll probably add a zip file version shortly.
>
>
You should be able to use WinRAR to unzip a tgz file on Windows. WinRAR is a free download, available at http://download.cnet.com/WinRAR/3000-2250_4-10007677.html, and other places as well. But your point is a good one, and we'll probably add a zip file version shortly.
  -- AlKalter - 26 Mar 2009

Revision 652012-02-23 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 6 to 6
 

Overview

Changed:
<
<
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.0.4b5 and above. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 1.3 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package ; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
>
>
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.0.4 and above. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 1.3 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package ; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
 

Required software components

APPX Desktop Client Java Web Start Bundle

Changed:
<
<
You can get the APPX Desktop Client Java Web Start Bundle from here for Unix or Linux or here for Windows.
>
>
You can get the APPX Desktop Client Java Web Start Bundle from here for Unix or Linux or here for Windows.
 

APPX Server

Line: 37 to 37
 

Download and place the APPX Desktop Client Java Web Start Bundle.

Changed:
<
<
For a Windows Web Server, download the Java Web Start Bundle from here. For my Linux/Unix server I downloaded version 5.0.4b5 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
>
>
For a Windows Web Server, download the Java Web Start Bundle from here. For my Linux/Unix server I downloaded version 5.0.4 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
 
  • I am going to use the command line tool wget to fetch the file bundle:

[joe@webserver /]$ cd /var/www/html 

Changed:
<
<
[joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta5/java_web.tgz
>
>
[joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4/java_web.tgz
 [joe@webserver html]$
Line: 60 to 60
 appx/appx.html appx/splash.gif appx/APPXLaunchButton.png
Added:
>
>
appx/appx-small.png
 appx/appx-nativelib.jar appx/appx.jar appx/appx.jnlp
Line: 79 to 80
 [joe@webserver appx]$ ls
Changed:
<
<
appx32.gif  appx.html  appx.jar  appx.jnlp  APPXLaunchButton.png  appx-nativelib.jar  INSTALL.txt  README.txt  splash.gif

>
>
appx32.gif  appx.html  appx.jar  appx.jnlp  APPXLaunchButton.png appx-small.png appx-nativelib.jar  INSTALL.txt  README.txt  splash.gif

 

APPX Desktop Client Web Start Bundle Components

Line: 101 to 102
 

In appx.jnlp:

Changed:
<
<
appx.jnlp: --->
>
>
appx.jnlp: --->
  Please see our Wiki at http://wiki.appx.com/wiki/bin/view/Main/LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart for further documentation.
Line: 187 to 188
 
[joe@webserver appx]$ cat appx.jnlp
<?xml version="1.0" encoding="utf-8"?>
Changed:
<
<
<-- JNLP File for APPX Desktop Client 5.0.4b5 -->
>
>
<-- JNLP File for APPX Desktop Client 5.0.4 -->
 
<-- JNLP File for APPX Desktop Client  -->
Changed:
<
<
<-- example JNLP file that will launch the APPX Desktop Client 5.0.4b5 -->
>
>
<-- example JNLP file that will launch the APPX Desktop Client 5.0.4 -->
 
<-- where the jnlp file lives on the web -->
Changed:
<
<
>
>
  APPX Desktop Client Java Web Start Demo Application APPX Software, Inc.
Changed:
<
<
APPX Desktop Client version 5.0.4b5.
>
>
APPX Desktop Client version 5.0.4.
  Connects to APPX Client Login Manager.
<-- hover help for this app.  -->
Changed:
<
<
APPX Desktop Client 5.0.4b5
>
>
APPX Desktop Client 5.0.4
 
<-- This is the APPX Desktop Client application icon and splash screen. -->
<-- relative to codebase -->

Revision 642012-01-24 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 6 to 6
 

Overview

Changed:
<
<
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.0.4b2 and above. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 1.3 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package ; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
>
>
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.0.4b5 and above. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 1.3 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package ; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
 

Required software components

APPX Desktop Client Java Web Start Bundle

Changed:
<
<
You can get the APPX Desktop Client Java Web Start Bundle from here for Unix or Linux or here for Windows.
>
>
You can get the APPX Desktop Client Java Web Start Bundle from here for Unix or Linux or here for Windows.
 

APPX Server

Line: 37 to 37
 

Download and place the APPX Desktop Client Java Web Start Bundle.

Changed:
<
<
For a Windows Web Server, download the Java Web Start Bundle from here. For my Linux/Unix server I downloaded version 5.0.4b2 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
>
>
For a Windows Web Server, download the Java Web Start Bundle from here. For my Linux/Unix server I downloaded version 5.0.4b5 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
 
  • I am going to use the command line tool wget to fetch the file bundle:

[joe@webserver /]$ cd /var/www/html 

Changed:
<
<
[joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta2/java_web.tgz
>
>
[joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta5/java_web.tgz
 [joe@webserver html]$
Line: 101 to 101
 

In appx.jnlp:

Changed:
<
<
appx.jnlp: --->
>
>
appx.jnlp: --->
  Please see our Wiki at http://wiki.appx.com/wiki/bin/view/Main/LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart for further documentation.
Line: 187 to 187
 
[joe@webserver appx]$ cat appx.jnlp
<?xml version="1.0" encoding="utf-8"?>
Changed:
<
<
<-- JNLP File for APPX Desktop Client 5.0.4b2 -->
>
>
<-- JNLP File for APPX Desktop Client 5.0.4b5 -->
 
<-- JNLP File for APPX Desktop Client  -->
Changed:
<
<
<-- example JNLP file that will launch the APPX Desktop Client 5.0.4b2 -->
>
>
<-- example JNLP file that will launch the APPX Desktop Client 5.0.4b5 -->
 
<-- where the jnlp file lives on the web -->
Changed:
<
<
>
>
  APPX Desktop Client Java Web Start Demo Application APPX Software, Inc.
Changed:
<
<
APPX Desktop Client version 5.0.4b2.
>
>
APPX Desktop Client version 5.0.4b5.
  Connects to APPX Client Login Manager.
<-- hover help for this app.  -->
Changed:
<
<
APPX Desktop Client 5.0.4b2
>
>
APPX Desktop Client 5.0.4b5
 
<-- This is the APPX Desktop Client application icon and splash screen. -->
<-- relative to codebase -->

Revision 632011-06-03 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 37 to 37
 

Download and place the APPX Desktop Client Java Web Start Bundle.

Changed:
<
<
For a Windows Web Server, download the Java Web Start Bundle from here For my Linux/Unix server I downloaded version 5.0.4b2 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
>
>
For a Windows Web Server, download the Java Web Start Bundle from here. For my Linux/Unix server I downloaded version 5.0.4b2 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
 
  • I am going to use the command line tool wget to fetch the file bundle:

Revision 622011-06-03 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 6 to 6
 

Overview

Changed:
<
<
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.0.4b1 and above. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 1.3 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package ; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
>
>
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.0.4b2 and above. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 1.3 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package ; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
 

Required software components

APPX Desktop Client Java Web Start Bundle

Changed:
<
<
You can get the APPX Desktop Client Java Web Start Bundle from here.
>
>
You can get the APPX Desktop Client Java Web Start Bundle from here for Unix or Linux or here for Windows.
 

APPX Server

Line: 37 to 37
 

Download and place the APPX Desktop Client Java Web Start Bundle.

Changed:
<
<
For a Windows Web Server, download the Java Web Start Bundle from here For my Linux/Unix server I downloaded version 5.0.4b1 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
>
>
For a Windows Web Server, download the Java Web Start Bundle from here For my Linux/Unix server I downloaded version 5.0.4b2 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
 
  • I am going to use the command line tool wget to fetch the file bundle:

[joe@webserver /]$ cd /var/www/html 

Changed:
<
<
[joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta1/java_web.tgz
>
>
[joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta2/java_web.tgz
 [joe@webserver html]$
Line: 101 to 101
 

In appx.jnlp:

Changed:
<
<
appx.jnlp: --->
>
>
appx.jnlp: --->
  Please see our Wiki at http://wiki.appx.com/wiki/bin/view/Main/LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart for further documentation.
Line: 187 to 187
 
[joe@webserver appx]$ cat appx.jnlp
<?xml version="1.0" encoding="utf-8"?>
Changed:
<
<
<-- JNLP File for APPX Desktop Client 5.0.4b1 -->
>
>
<-- JNLP File for APPX Desktop Client 5.0.4b2 -->
 
<-- JNLP File for APPX Desktop Client  -->
Changed:
<
<
<-- example JNLP file that will launch the APPX Desktop Client 5.0.4b1 -->
>
>
<-- example JNLP file that will launch the APPX Desktop Client 5.0.4b2 -->
 
<-- where the jnlp file lives on the web -->
Changed:
<
<
>
>
  APPX Desktop Client Java Web Start Demo Application APPX Software, Inc.
Changed:
<
<
APPX Desktop Client version 5.0.4b1.
>
>
APPX Desktop Client version 5.0.4b2.
  Connects to APPX Client Login Manager.
<-- hover help for this app.  -->
Changed:
<
<
APPX Desktop Client 5.0.4b1
>
>
APPX Desktop Client 5.0.4b2
 
<-- This is the APPX Desktop Client application icon and splash screen. -->
<-- relative to codebase -->

Revision 612011-03-08 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 43 to 43
 
Changed:
<
<
[joe@webserver /]$ *cd /var/www/html* 
[joe@webserver /]$ *sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta1/java_web.tgz*

>
>
[joe@webserver /]$ cd /var/www/html 
[joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta1/java_web.tgz

 [joe@webserver html]$

  • Now let's untar the files
Changed:
<
<
[joe@webserver html]$ *sudo tar xzvf java_web.tgz*

>
>
[joe@webserver html]$ sudo tar xzvf java_web.tgz

 

appx/

Line: 65 to 65
 appx/appx.jnlp
Changed:
<
<
[joe@webserver html]$ *ls -la*

>
>
[joe@webserver html]$ ls -la

 

total 1216

Line: 75 to 75
 -rw-r--r-- 1 root root 1233805 Mar 4 14:27 java_web.tgz
Changed:
<
<
[joe@webserver html]$ *cd appx*
[joe@webserver appx]$ *ls*

>
>
[joe@webserver html]$ cd appx
[joe@webserver appx]$ ls

 

appx32.gif  appx.html  appx.jar  appx.jnlp  APPXLaunchButton.png  appx-nativelib.jar  INSTALL.txt  README.txt  splash.gif

Line: 113 to 113
  The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.
appx.html contents
Changed:
<
<
[joe@webserver appx]$ *cat appx.html*

>
>
[joe@webserver appx]$ cat appx.html

 

Line: 184 to 184
  This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Now take a look at the appx.jnlp file.
appx.jnlp contents
Changed:
<
<
[joe@webserver appx]$ *cat appx.jnlp*

>
>
[joe@webserver appx]$ cat appx.jnlp

 
<?xml version="1.0" encoding="utf-8"?>
<!-- JNLP File for APPX Desktop Client 5.0.4b1 -->
Line: 2022 to 2022
  If you wish to modify the Apache global TypesConfig file and the file exists in /etc/mime.types, then you might try syntax like the following which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
Changed:
<
<
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types*

>
>
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types

 [joe@webserver /]$

Or, if you wish to modify an .htaccess file in your http://www.example.com/appx/ directory, and your web server is configured to allow .htaccess modifications then try the following syntax which will grep for the jnlp entry, and if not found will append an entry for jnlp support.

Changed:
<
<
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess* 

>
>
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess 

 [joe@webserver /]$

Revision 602011-03-08 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 37 to 37
 

Download and place the APPX Desktop Client Java Web Start Bundle.

Changed:
<
<
I downloaded version 5.0.4b1 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
>
>
For a Windows Web Server, download the Java Web Start Bundle from here For my Linux/Unix server I downloaded version 5.0.4b1 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
 
  • I am going to use the command line tool wget to fetch the file bundle:

Changed:
<
<
[joe@webserver /]$ cd /var/www/html 
[joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta1/java_web.tgz

>
>
[joe@webserver /]$ *cd /var/www/html* 
[joe@webserver /]$ *sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta1/java_web.tgz*

 [joe@webserver html]$

  • Now let's untar the files
Changed:
<
<
[joe@webserver html]$ sudo tar xzvf java_web.tgz

>
>
[joe@webserver html]$ *sudo tar xzvf java_web.tgz*

 

appx/

Line: 65 to 65
 appx/appx.jnlp
Changed:
<
<
[joe@webserver html]$ ls -la

>
>
[joe@webserver html]$ *ls -la*

 

total 1216

Line: 75 to 75
 -rw-r--r-- 1 root root 1233805 Mar 4 14:27 java_web.tgz
Changed:
<
<
[joe@webserver html]$ cd appx
[joe@webserver appx]$ ls

>
>
[joe@webserver html]$ *cd appx*
[joe@webserver appx]$ *ls*

 

appx32.gif  appx.html  appx.jar  appx.jnlp  APPXLaunchButton.png  appx-nativelib.jar  INSTALL.txt  README.txt  splash.gif

Line: 113 to 113
  The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.
appx.html contents
Changed:
<
<
[joe@webserver appx]$ cat appx.html

>
>
[joe@webserver appx]$ *cat appx.html*

 

Line: 126 to 126
 
Changed:
<
<

>
>
 
Line: 184 to 184
  This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Now take a look at the appx.jnlp file.
appx.jnlp contents
Changed:
<
<
[joe@webserver appx]$ cat appx.jnlp

>
>
[joe@webserver appx]$ *cat appx.jnlp*

 
<?xml version="1.0" encoding="utf-8"?>
<!-- JNLP File for APPX Desktop Client 5.0.4b1 -->
Line: 2022 to 2022
  If you wish to modify the Apache global TypesConfig file and the file exists in /etc/mime.types, then you might try syntax like the following which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
Changed:
<
<
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types

>
>
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types*

 [joe@webserver /]$

Revision 592011-03-08 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 113 to 113
  The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.
appx.html contents
Changed:
<
<
[joe@webserver appx]$ *cat appx.html*

>
>
[joe@webserver appx]$ cat appx.html

 

Line: 184 to 184
  This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Now take a look at the appx.jnlp file.
appx.jnlp contents
Changed:
<
<
[joe@webserver appx]$ *cat appx.jnlp*

>
>
[joe@webserver appx]$ cat appx.jnlp

 
<?xml version="1.0" encoding="utf-8"?>
<!-- JNLP File for APPX Desktop Client 5.0.4b1 -->
Line: 2022 to 2022
  If you wish to modify the Apache global TypesConfig file and the file exists in /etc/mime.types, then you might try syntax like the following which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
Changed:
<
<
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types*

>
>
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types

 [joe@webserver /]$

Revision 582011-03-08 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Line: 43 to 43
 
Changed:
<
<
[joe@webserver /]$ *cd /var/www/html* 
[joe@webserver /]$ *sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta1/java_web.tgz*

>
>
[joe@webserver /]$ cd /var/www/html 
[joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta1/java_web.tgz

 [joe@webserver html]$

  • Now let's untar the files
Changed:
<
<
[joe@webserver html]$ *sudo tar xzvf java_web.tgz*

>
>
[joe@webserver html]$ sudo tar xzvf java_web.tgz

 

appx/

Line: 65 to 65
 appx/appx.jnlp
Changed:
<
<
[joe@webserver html]$ *ls -la*

>
>
[joe@webserver html]$ ls -la

 

total 1216

Line: 75 to 75
 -rw-r--r-- 1 root root 1233805 Mar 4 14:27 java_web.tgz
Changed:
<
<
[joe@webserver html]$ *cd appx*
[joe@webserver appx]$ *ls*

>
>
[joe@webserver html]$ cd appx
[joe@webserver appx]$ ls

 

appx32.gif  appx.html  appx.jar  appx.jnlp  APPXLaunchButton.png  appx-nativelib.jar  INSTALL.txt  README.txt  splash.gif

Revision 572011-03-08 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

Added:
>
>
 This document will explain how to start the APPX Desktop Client via Java Web Start Technology.

Overview

Line: 4 to 5
 This document will explain how to start the APPX Desktop Client via Java Web Start Technology.

Overview

Changed:
<
<
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 4.2.a and above. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 1.3 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package ; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
>
>
When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 5.0.4b1 and above. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 1.3 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package ; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.
 

Required software components

APPX Desktop Client Java Web Start Bundle

Changed:
<
<
You can get the APPX Desktop Client Java Web Start Bundle from here.
>
>
You can get the APPX Desktop Client Java Web Start Bundle from here.
 

APPX Server

Added:
>
>
 You need a functioning APPX installation. Follow instructions in this document to install APPX on Windows if you don't already have APPX installed.

Web Server

Added:
>
>
 You need a functioning web server configured with jnlp mime type support. Apache and IIS are two common servers.

Quick steps

Line: 30 to 37
 

Download and place the APPX Desktop Client Java Web Start Bundle.

Changed:
<
<
I downloaded version 4.2.a from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
>
>
I downloaded version 5.0.4b1 from here. Place the bundle in a directory off of your web server's web root and follow the steps below to install and configure.
 
  • I am going to use the command line tool wget to fetch the file bundle:

Changed:
<
<
[joe@webserver /]$ cd /var/www/html 
[joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/4.2.a/java_web.tgz

>
>
[joe@webserver /]$ *cd /var/www/html* 
[joe@webserver /]$ *sudo wget http://www.appx.com/ftp/appx/products/appx/client/5.0.4.beta1/java_web.tgz*

 [joe@webserver html]$
Changed:
<
<
>
>
 
  • Now let's untar the files
Changed:
<
<
[joe@webserver html]$ sudo tar xzvf java_web.tgz
>
>
[joe@webserver html]$ *sudo tar xzvf java_web.tgz*
 
Changed:
<
<
appx/

>
>
appx/

 appx/appx32.gif appx/README.txt appx/INSTALL.txt
Line: 63 to 63
 appx/appx-nativelib.jar appx/appx.jar appx/appx.jnlp
Changed:
<
<
>
>
 
Changed:
<
<
[joe@webserver html]$ ls -la
>
>
[joe@webserver html]$ *ls -la*
 
Changed:
<
<
total 1216

>
>
total 1216

 drwxr-xr-x 3 root root 4096 Mar 4 14:27 . drwxr-xr-x 10 root root 4096 Jun 26 2007 .. drwxrwxrwx 2 root root 4096 Mar 3 14:40 appx -rw-r--r-- 1 root root 1233805 Mar 4 14:27 java_web.tgz
Changed:
<
<
>
>
 
Changed:
<
<
[joe@webserver html]$ cd appx
[joe@webserver appx]$ ls
>
>
[joe@webserver html]$ *cd appx*
[joe@webserver appx]$ *ls*
 
Changed:
<
<
appx32.gif  appx.html  appx.jar  appx.jnlp  APPXLaunchButton.png  appx-nativelib.jar  INSTALL.txt  README.txt  splash.gif
>
>
appx32.gif  appx.html  appx.jar  appx.jnlp  APPXLaunchButton.png  appx-nativelib.jar  INSTALL.txt  README.txt  splash.gif
 

APPX Desktop Client Web Start Bundle Components

appx32.gif

Line: 97 to 84
 

APPX Desktop Client Web Start Bundle Components

appx32.gif

Added:
>
>
 The appx32.gif file is the file used as an application runtime icon. It is referenced by the appx.jnlp file that we review later in this document.

README.txt

Added:
>
>
 README.txt contains the following very brief instructions to the reader.
Changed:
<
<
>
>
 Place these files in a directory named /appx/ off your web server's webroot.

You need to change three items, all references to www.example.com to read your site URL:

Line: 116 to 104
 appx.jnlp: --->

Please see our Wiki at http://wiki.appx.com/wiki/bin/view/Main/LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart for further documentation.

Changed:
<
<
>
>
 

INSTALL.txt

Added:
>
>
 INSTALL.txt points the reader to README.txt

appx.html

Added:
>
>
 The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.
appx.html contents
Changed:
<
<
[joe@webserver appx]$ cat appx.html
>
>
[joe@webserver appx]$ *cat appx.html*
 
Changed:
<
<
>
>
  APPX Desktop Client Web Start
Line: 140 to 126
 
Changed:
<
<



>
>

 
APPX Desktop Client Web Start Demonstration
Changed:
<
<

>
>
 

Clicking the icon below will attempt to detect if the correct Java JRE is installed, and if possible install it. If the installer determines you need an updated JRE but it can't auto install a JRE, it will place you on Sun's download page for your platform. After the JRE requirement is met, the APPX Desktop Client will be downloaded and launched.

Changed:
<
<


>
>
 

<--Click To Launch the APPX Desktop Client Demonstration-->
<-- Start of Sun's deployJava.js script that attempts to detect if Java is installed and install it or updated -->

Line: 171 to 157
 

[joe@webserver appx]$

Changed:
<
<
>
>
 
appx.html modifications
Added:
>
>
 You should change the following two URL values in your appx.html file to match your site.
Changed:
<
<
         var url = " http://www.example.com/appx/appx.jnlp ";

>
>
         var url = " http://www.example.com/appx/appx.jnlp ";

  deployJava.launchButtonPNG = " APPXLaunchButton.png ";
Changed:
<
<
>
>
 

splash.gif

Added:
>
>
 This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.

APPXLaunchButton.png

Line: 191 to 178
 The appx-nativelib.jar file contains platform specific files for the proper execution of the appx.jar file.

appx.jar

Added:
>
>
 The APPX Desktop Client in Java jar format.

appx.jnlp

Added:
>
>
 This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Now take a look at the appx.jnlp file.
appx.jnlp contents
Changed:
<
<
[joe@webserver appx]$ cat appx.jnlp
>
>
[joe@webserver appx]$ *cat appx.jnlp*
 
Changed:
<
<
<-- JNLP File for APPX Desktop Client 5.0.0.a9 -->
>
>
<-- JNLP File for APPX Desktop Client 5.0.4b1 -->
 
<-- JNLP File for APPX Desktop Client  -->
Changed:
<
<
<-- example JNLP file that will launch the APPX Desktop Client 5.0.0.a9 -->
>
>
<-- example JNLP file that will launch the APPX Desktop Client 5.0.4b1 -->
 
<-- where the jnlp file lives on the web -->
Line: 214 to 198
  APPX Desktop Client Java Web Start Demo Application APPX Software, Inc.
Changed:
<
<
APPX Desktop Client version 4.2.a.
>
>
APPX Desktop Client version 5.0.4b1.
  Connects to APPX Client Login Manager.
<-- hover help for this app.  -->
Changed:
<
<
APPX Desktop Client 5.0.0.a9
>
>
APPX Desktop Client 5.0.4b1
 
<-- This is the APPX Desktop Client application icon and splash screen. -->
<-- relative to codebase -->
Line: 259 to 243
 

[joe@webserver appx]$

Changed:
<
<
>
>
 
appx.jnlp modifications
Added:
>
>
 You should change the following URL value in your appx.jnlp file to match your site.
Changed:
<
<
         codebase=" http://www.example.com/appx " href="appx.jnlp"
>
>
         codebase=" http://www.example.com/appx " href="appx.jnlp"
 Towards the end of the appx.jnlp file, notice the application-desc elements with argument attributes of -windowTitle, -remoteHost ... You can add any APPX Desktop Client startup parameter that you normally find when you select Options, Advanced upon initially starting the APPX Desktop Client.

Table of possible element / attribute available to you in a JNLP file.
Changed:
<
<
Elements and Attributes of a JNLP file
>
>
 

Changed:
<
<

Element

Attributes

>
>
Element

Attributes

 

Deleted:
<
<

Description

 
Changed:
<
<

Since

>
>
Description
 
Changed:
<
<

Required

>
>
 
Added:
>
>
Since
 
Added:
>
>
Required
 
Added:
>
>
 
Changed:
<
<

jnlp

>
>
jnlp
 

Changed:
<
<


>
>
 

Deleted:
<
<

This is the main xml element for a jnlp file. Everything is contained within the jnlp element.

 
Changed:
<
<

1.0

>
>
This is the main xml element for a jnlp file. Everything is contained within the jnlp element.
 
Changed:
<
<

yes

>
>

1.0

yes

 
Deleted:
<
<


 

Changed:
<
<

spec

The spec attribute can be 1.0, 1.5.0, or 1.6.0 or can use the wildcards such as 1.0+ or 1.6+. It denoted the minimum version of the JNLP Specification that this jnlp file can work with.

>
>
spec

The spec attribute can be 1.0, 1.5.0, or 1.6.0 or can use the wildcards such as 1.0+ or 1.6+. It denoted the minimum version of the JNLP Specification that this jnlp file can work with.

 

Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0
 
Changed:
<
<


>
>
 
Changed:
<
<

codebase

>
>

codebase

 

Changed:
<
<

The codebase attribute specifies the base location for all relative URLs specified in href attributes in the JNLP file.

>
>
The codebase attribute specifies the base location for all relative URLs specified in href attributes in the JNLP file.
 

Changed:
<
<

1.0

>
>
1.0
 

Deleted:
<
<


 
Changed:
<
<


>
>
 
Changed:
<
<

href

>
>

href

 

Deleted:
<
<

The href specifies the URL of the JNLP file itself.

 
Changed:
<
<

1.0


>
>
The href specifies the URL of the JNLP file itself.
 
Changed:
<
<

>
>

1.0

 
Deleted:
<
<


 
Deleted:
<
<
 
Changed:
<
<

version

>
>
 
Changed:
<
<

The version of the application being launched, as well as the version of the JNLP file itself.

1.0

>
>
 
Changed:
<
<


>
>
version
 
Changed:
<
<

information

>
>
 
Changed:
<
<


The information element contains other elements that describe the application and it's source.

>
>
The version of the application being launched, as well as the version of the JNLP file itself.

1.0

information

The information element contains other elements that describe the application and it's source.

 

Changed:
<
<

1.0

yes

>
>
1.0

yes

 
Changed:
<
<
>
>
 
Deleted:
<
<


os

 
Changed:
<
<
>
>
 
Changed:
<
<

Specifies the operating system for which this information element should be considered.

1.5.0

>
>
os
 
Changed:
<
<

>
>
 
Changed:
<
<


>
>
Specifies the operating system for which this information element should be considered.

1.5.0

 
Changed:
<
<


>
>
 

Deleted:
<
<

arch

 
Changed:
<
<

Specifies the architecture for which this information element should be considered

1.5.0

>
>
arch
 
Changed:
<
<


>
>
Specifies the architecture for which this information element should be considered
 
Changed:
<
<


>
>
1.5.0

 
Deleted:
<
<

 

Deleted:
<
<

platform

Specifies the platform for which this information element should be considered.

 
Changed:
<
<
>
>
platform
 
Changed:
<
<

1.5.0

>
>
Specifies the platform for which this information element should be considered.
 
Changed:
<
<


>
>

1.5.0

 

Changed:
<
<


locale

>
>

locale

 

Changed:
<
<

Specifies the locale for which this information element should be considered.

1.5.0


>
>
Specifies the locale for which this information element should be considered.
 
Changed:
<
<

title

>
>
1.5.0
 
Changed:
<
<


The title element specifies the title of the application.

>
>

title

The title element specifies the title of the application.

1.0

yes

vendor

The vendor element specifies the provider of the application.

 
Added:
>
>
 
Deleted:
<
<

1.0

 
Changed:
<
<

yes

>
>
1.0

yes

 
Added:
>
>
 
Changed:
<
<

vendor

>
>
homepage
 
Changed:
<
<


>
>
 
Changed:
<
<

The vendor element specifies the provider of the application.

>
>
The homepage of the application.

1.0

href

A URL pointing to where more information on this application can be found.

 

Deleted:
<
<

1.0

yes

 
Changed:
<
<
>
>
1.0

yes

description

 
Deleted:
<
<

homepage


 

Changed:
<
<

The homepage of the application.

>
>
A short statement describing the application.

1.0

kind

An indicator as to what type of description this is, legal values are one-line, short, and tooltip.

 
Added:
>
>
 
Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0
 
Changed:
<
<


>
>
 
Changed:
<
<

href

>
>

icon

 
Added:
>
>
 
Changed:
<
<

A URL pointing to where more information on this application can be found.

>
>
Describes an icon that can be used to identify the application to the user.

1.0

href

A URL pointing to the icon file, may be in one of the following formats: gif, jpg, png, ico.

 

Deleted:
<
<

1.0

 
Changed:
<
<

yes

>
>
1.0
 
Changed:
<
<

description

>
>

yes

 
Changed:
<
<


>
>
kind
 

Changed:
<
<

A short statement describing the application.

>
>
Indicates the suggested use of the icon, can be: default, selected, disabled, rollover, splash, or shortcut.
 
Added:
>
>
 
Deleted:
<
<

1.0

 
Changed:
<
<
>
>
1.0
 
Changed:
<
<



>
>
 
Changed:
<
<

>
>
 
Added:
>
>

width

 
Changed:
<
<

kind

>
>
 
Changed:
<
<

An indicator as to what type of description this is, legal values are one-line, short, and tooltip.

>
>
Can be used to indicate the resolution of the image.
 

Deleted:
<
<

1.0


 
Changed:
<
<

icon


>
>
1.0
 
Changed:
<
<

Describes an icon that can be used to identify the application to the user.

1.0

>
>
 
Changed:
<
<


>
>
 
Changed:
<
<


>
>
 
Added:
>
>
height
 
Deleted:
<
<
 
Deleted:
<
<

href

 
Deleted:
<
<

A URL pointing to the icon file, may be in one of the following formats: gif, jpg, png, ico.

 
Changed:
<
<

1.0

>
>
Can be used to indicate the resolution of the image.
 
Changed:
<
<

yes

>
>
1.0
 
Changed:
<
<


>
>
 
Changed:
<
<

kind

>
>
 
Changed:
<
<

Indicates the suggested use of the icon, can be: default, selected, disabled, rollover, splash, or shortcut.

>
>

depth

Can be used to indicate the resolution of the image.

 

Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0
 
Changed:
<
<


>
>

offline-allowed

 
Deleted:
<
<

width

 

Deleted:
<
<

Can be used to indicate the resolution of the image.

 
Changed:
<
<

1.0


>
>
Indicates that this application can operate when the client system is disconnected from the network.
 
Changed:
<
<

>
>
1.0
 
Changed:
<
<


>
>
 
Changed:
<
<

height

>
>
shortcut
 
Changed:
<
<

Can be used to indicate the resolution of the image.

1.0

>
>
 
Changed:
<
<
>
>
 
Changed:
<
<



>
>
The shortcut element can be used to indicate an application's preferences for desktop integration.
 
Changed:
<
<

>
>
1.5.0
 
Changed:
<
<

depth

Can be used to indicate the resolution of the image.

>
>
 
Changed:
<
<

1.0


>
>
 
Deleted:
<
<
 
Deleted:
<
<

offline-allowed


 
Changed:
<
<

Indicates that this application can operate when the client system is disconnected from the network.

>
>

online

Can be used to describe the application's preference for creating a shortcut to run online or offline.

 
Added:
>
>
 
Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.5.0
 
Changed:
<
<

shortcut

>
>
 
Changed:
<
<
>
>

desktop

 
Deleted:
<
<


 
Added:
>
>
 
Deleted:
<
<

The shortcut element can be used to indicate an application's preferences for desktop integration.

 
Changed:
<
<

1.5.0

>
>
Can be used to indicate an application's preference for putting a shortcut on the users desktop.
 
Changed:
<
<


>
>
1.5.0
 
Changed:
<
<


>
>
 
Changed:
<
<

online

>
>
 
Changed:
<
<

Can be used to describe the application's preference for creating a shortcut to run online or offline.

>
>
menu
 
Changed:
<
<

1.5.0


>
>
 
Changed:
<
<

>
>
Can be used to indicate an application's preference for putting a menu item in the users start menus.
 
Changed:
<
<

desktop

>
>
 
Changed:
<
<


>
>
1.5.0
 
Changed:
<
<

Can be used to indicate an application's preference for putting a shortcut on the users desktop.

1.5.0

>
>
 
Deleted:
<
<


 
Changed:
<
<

>
>
 
Changed:
<
<

menu

>
>
 
Changed:
<
<


Can be used to indicate an application's preference for putting a menu item in the users start menus.

>
>
sub-menu

 
Added:
>
>
Can be used to indicate an application's preference for where to place the menu item.
 
Deleted:
<
<

1.5.0

 
Added:
>
>

1.5.0

 
Added:
>
>
 
Deleted:
<
<


 
Changed:
<
<


>
>
 
Changed:
<
<

sub-menu

>
>

association

 
Added:
>
>
 
Deleted:
<
<

Can be used to indicate an application's preference for where to place the menu item.

 
Changed:
<
<

1.5.0

>
>
Can be used to hint to the JNLP client that it wishes to be registered with the operating system as the primary handler of certain extensions and a certain mime-type.
 
Changed:
<
<


>
>
 
Changed:
<
<

association

>
>
1.5.0
 
Deleted:
<
<


 
Changed:
<
<

Can be used to hint to the JNLP client that it wishes to be registered with the operating system as the primary handler of certain extensions and a certain mime-type.

>
>
 
Changed:
<
<

1.5.0


>
>
 
Changed:
<
<

>
>
extensions
 
Changed:
<
<


>
>
 
Changed:
<
<

extensions

>
>
Contains a list of file extensions (separated by spaces) that the application requests it be registered to handle.
 
Changed:
<
<

Contains a list of file extensions (separated by spaces) that the application requests it be registered to handle.

1.5.0

>
>
1.5.0
 

Deleted:
<
<



 
Changed:
<
<

mime-type

Contains the mime-type that the application requests it be registered to handle.

>
>
 
Changed:
<
<
>
>

mime-type

Contains the mime-type that the application requests it be registered to handle.

 
Deleted:
<
<

1.5.0

 
Changed:
<
<


>
>

1.5.0

 

Changed:
<
<

related-content


>
>

related-content

 

Changed:
<
<

Describes an additional piece of related content that may be integrated with the application.

1.5.0

>
>
Describes an additional piece of related content that may be integrated with the application.

1.5.0

 

Deleted:
<
<


 
Changed:
<
<


>
>
 
Changed:
<
<

>
>
 
Changed:
<
<

href

A URL pointing to the related content.

>
>
href
 
Changed:
<
<

1.5.0

>
>
A URL pointing to the related content.
 
Changed:
<
<

yes

>
>
 
Changed:
<
<


>
>
1.5.0
 
Changed:
<
<


>
>
 
Changed:
<
<

>
>
yes
 
Deleted:
<
<


 
Changed:
<
<


>
>
 
Changed:
<
<


>
>
 
Changed:
<
<
>
>
 
Changed:
<
<

update


>
>
 
Changed:
<
<
>
>
 
Deleted:
<
<

The update element is used to indicate the preferences for how application updates should be handled by the JNLP Client.

1.6.0

 
Deleted:
<
<
 
Changed:
<
<


>
>
 
Deleted:
<
<


 
Changed:
<
<
>
>
update
 
Changed:
<
<

check

Indicates the preference for when the JNLP Client should check for updates. It can be always, timeout, or background..

>
>
 
Changed:
<
<

1.6.0

>
>
The update element is used to indicate the preferences for how application updates should be handled by the JNLP Client.
 
Changed:
<
<


>
>
1.6.0
 
Changed:
<
<


>
>
 
Deleted:
<
<

 
Added:
>
>
 
Deleted:
<
<

policy

 
Changed:
<
<

Indicates the preference for how the JNLP Client should handle an application update when it is known an update is available before the application is launched. It can be always, prompt-update, or prompt-run.

>
>
check
 
Changed:
<
<

1.6.0

>
>
Indicates the preference for when the JNLP Client should check for updates. It can be always, timeout, or background..
 
Changed:
<
<


>
>
 
Changed:
<
<
>
>
1.6.0

 
Deleted:
<
<



 
Changed:
<
<
>
>
 
Changed:
<
<


>
>

policy

Indicates the preference for how the JNLP Client should handle an application update when it is known an update is available before the application is launched. It can be always, prompt-update, or prompt-run.

 
Added:
>
>
 
Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.6.0
 
Changed:
<
<

security

>
>
 
Changed:
<
<
>
>

 
Deleted:
<
<


 
Added:
>
>
 
Deleted:
<
<

This element can be used to request enhanced permissions.

 
Changed:
<
<

1.0

>
>
 
Changed:
<
<


>
>
1.0
 
Changed:
<
<
>
>
 
Changed:
<
<

all-permissions

>
>
security
 
Added:
>
>
 
Deleted:
<
<


 
Changed:
<
<

Requests that the application be run with all permissions.

>
>
 
Changed:
<
<

1.0


>
>
This element can be used to request enhanced permissions.
 
Changed:
<
<
>
>
1.0

 
Deleted:
<
<
 
Deleted:
<
<

j2ee-application-client-permissions


 
Changed:
<
<

>
>
all-permissions
 
Changed:
<
<

Requests that the application be run with a permission set that meets the security specifications of the J2EE Application Client environment.

1.0

>
>
 
Changed:
<
<



>
>
Requests that the application be run with all permissions.
 
Changed:
<
<



>
>
 
Changed:
<
<
>
>
1.0
 
Deleted:
<
<

1.0


 
Changed:
<
<
>
>
 
Changed:
<
<

resources


>
>
j2ee-application-client-permissions
 
Changed:
<
<
>
>
 
Changed:
<
<

Describes all the resources that are needed for an application.

1.0

>
>
Requests that the application be run with a permission set that meets the security specifications of the J2EE Application Client environment.

1.0

 

Deleted:
<
<

yes

 
Changed:
<
<


>
>
 
Changed:
<
<

os

>
>

 
Deleted:
<
<

Specifies the operating system for which the resources element should be considered.

 

Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0
 
Added:
>
>
 
Changed:
<
<


>
>

resources

 
Deleted:
<
<

arch

 

Deleted:
<
<

Specifies the architecture for which the resources element should be considered.

1.0

 
Added:
>
>
Describes all the resources that are needed for an application.

1.0

 
Added:
>
>
 
Changed:
<
<



>
>
yes
 
Changed:
<
<

>
>
 
Changed:
<
<

locale

Specifies that the locales for which the resources element should be considered.

>
>
 
Changed:
<
<



>
>
os
 
Changed:
<
<

java (or java se)


>
>
 
Changed:
<
<

Specifies what version(s) of Java to run the application with.

>
>
Specifies the operating system for which the resources element should be considered.
 
Added:
>
>
 
Deleted:
<
<

1.6.0 (java)

 
Changed:
<
<
>
>
1.0
 
Changed:
<
<



>
>

 
Deleted:
<
<

 

Changed:
<
<

version

>
>
arch
 
Added:
>
>
 
Deleted:
<
<

Describes an ordered list of version ranges to use.

 
Changed:
<
<

1.0

>
>
Specifies the architecture for which the resources element should be considered.
 
Changed:
<
<

yes

>
>
1.0
 
Changed:
<
<


>
>
 
Changed:
<
<

href

>
>
 
Changed:
<
<

The URL denoting the supplier of this version of java, and where it may be downloaded from.

>
>

locale

Specifies that the locales for which the resources element should be considered.

 

Deleted:
<
<

1.0

 
Changed:
<
<


>
>
 
Changed:
<
<


>
>

java (or java se)

 
Deleted:
<
<

java-vm-args

 

Deleted:
<
<

Indicates an additional set of standard and non-standard virtual machine arguments that the application would prefer the JNLP

 
Changed:
<
<
Client to use when launching Java.

1.0

>
>
Specifies what version(s) of Java to run the application with.

1.6.0 (java)

 
Added:
>
>
 
Deleted:
<
<


 
Changed:
<
<

>
>
 
Changed:
<
<


>
>
 
Changed:
<
<

initial-heap-size

Indicates the initial size of the Java heap.

1.0

>
>
version
 
Changed:
<
<


>
>
Describes an ordered list of version ranges to use.
 
Changed:
<
<


>
>
 
Changed:
<
<

max-heap-size

Indicates the maximum size of the Java heap.

>
>
1.0
 
Changed:
<
<
>
>
 
Changed:
<
<

1.0


>
>
yes
 
Changed:
<
<
>
>
 
Changed:
<
<

jar


>
>
 
Changed:
<
<
>
>
href
 
Changed:
<
<

Specifies a JAR file that is part of the application's classpath.

>
>

The URL denoting the supplier of this version of java, and where it may be downloaded from.

 
Added:
>
>
 
Changed:
<
<

1.0

>
>
1.0
 

Deleted:
<
<

yes

 
Changed:
<
<


>
>
 
Changed:
<
<

href

>
>
 
Added:
>
>

java-vm-args

 
Added:
>
>
 
Deleted:
<
<

The URL of the jar file.

 
Changed:
<
<

1.0

>
>
Indicates an additional set of standard and non-standard virtual machine arguments that the application would prefer the JNLP
 
Changed:
<
<

yes

>
>
Client to use when launching Java.
 
Changed:
<
<


>
>
1.0
 
Changed:
<
<

version

>
>
 
Changed:
<
<

The requested version of the jar file. Requires using the version-based download protocol

1.0

>
>
 
Changed:
<
<
>
>
initial-heap-size
 
Changed:
<
<



>
>
Indicates the initial size of the Java heap.
 
Changed:
<
<

>
>
1.0
 
Changed:
<
<

main

Indicates if this jar contains the class containing the main method of the application.

>
>
 
Changed:
<
<

1.0


>
>
 
Changed:
<
<


download

>
>

max-heap-size

Indicates the maximum size of the Java heap.

 
Deleted:
<
<

Can be used to indicate this jar may be downloaded lazily, or when needed.

 
Added:
>
>
 
Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0
 
Deleted:
<
<

 
Added:
>
>
 
Deleted:
<
<


 
Changed:
<
<
>
>

jar

 
Deleted:
<
<

size

 
Added:
>
>
 
Deleted:
<
<

Indicates the downloadable size of the jar file in bytes.

 
Changed:
<
<

1.0

>
>
Specifies a JAR file that is part of the application's classpath.
 
Added:
>
>
1.0
 
Added:
>
>
 
Deleted:
<
<


 
Changed:
<
<


>
>
yes
 
Changed:
<
<

part

>
>
 
Changed:
<
<

Can be used to group resources together so they will be downloaded at the same time.

>
>

href

The URL of the jar file.

 

Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0

yes

 
Deleted:
<
<

nativelib

 

Changed:
<
<


>
>
version
 

Deleted:
<
<

Specifies a JAR file that contains native libraries in it's root directory.

 
Changed:
<
<

1.0


>
>
The requested version of the jar file. Requires using the version-based download protocol
 
Changed:
<
<

>
>
1.0
 
Changed:
<
<


>
>
 
Changed:
<
<

href

>
>

 
Changed:
<
<

The URL of the jar file.

>
>
main

Indicates if this jar contains the class containing the main method of the application.

 
Added:
>
>
 
Deleted:
<
<

1.0

 
Changed:
<
<

yes

>
>
1.0
 
Changed:
<
<


>
>
 
Changed:
<
<

>
>
 
Changed:
<
<

version

>
>

download

 
Added:
>
>
 
Deleted:
<
<

The requested version of the jar file. Requires using the version-based download protocol

 
Changed:
<
<

1.0

>
>
Can be used to indicate this jar may be downloaded lazily, or when needed.
 
Changed:
<
<


>
>
1.0
 
Changed:
<
<
>
>
 
Changed:
<
<


download

>
>
 
Changed:
<
<

Can be used to indicate this jar may be downloaded lazily.

>
>
size
 
Added:
>
>
Indicates the downloadable size of the jar file in bytes.
 
Added:
>
>
 
Deleted:
<
<

1.0


 
Changed:
<
<

>
>
1.0
 
Changed:
<
<


>
>
 
Changed:
<
<

size

>
>
 
Changed:
<
<

Indicates the downloadable size of the jar file in bytes.

1.0

>
>
 
Changed:
<
<
>
>
 
Changed:
<
<


>
>
part
 
Deleted:
<
<


 
Deleted:
<
<

part

 
Changed:
<
<

Can be used to group resources together so they will be downloaded at the same time.

>
>
Can be used to group resources together so they will be downloaded at the same time.
 

Deleted:
<
<

1.0


 
Changed:
<
<

extension


>
>
1.0
 
Changed:
<
<

Contains pointer to an additional component-desc or installer-desc to be used with this application.

1.0

>
>
 
Changed:
<
<


>
>
 
Changed:
<
<

>
>
nativelib
 
Deleted:
<
<


 
Deleted:
<
<
 
Deleted:
<
<

href

 
Added:
>
>
 
Deleted:
<
<

The URL to the additional extension jnlp file.

 
Changed:
<
<

1.0

>
>
Specifies a JAR file that contains native libraries in it's root directory.
 
Changed:
<
<

yes

>
>
1.0

 
Deleted:
<
<
 
Deleted:
<
<


 
Changed:
<
<

version

>
>
 
Changed:
<
<

The version of the additional extension jnlp file.

>
>
href
 
Changed:
<
<

1.0

>
>
The URL of the jar file.
 
Changed:
<
<


>
>
1.0
 
Changed:
<
<
>
>
 
Changed:
<
<


name

>
>
yes
 
Changed:
<
<

The name of the additional extension jnlp file

>
>

 
Added:
>
>
version

The requested version of the jar file. Requires using the version-based download protocol

 
Added:
>
>
 
Deleted:
<
<

1.0


 
Changed:
<
<

>
>
1.0
 
Changed:
<
<

ext-download

>
>
 
Changed:
<
<


>
>
 
Changed:
<
<

Can be used in an extension element to denote the parts contained in a component-extension.

1.0

>
>
 
Changed:
<
<
>
>
 
Changed:
<
<


>
>
download
 
Deleted:
<
<


 
Deleted:
<
<

ext-part

 
Deleted:
<
<

Describes the name of a part that can be expected to be found in the extension.

 
Changed:
<
<

1.0

yes

>
>
Can be used to indicate this jar may be downloaded lazily.
 
Changed:
<
<
>
>

1.0

 
Deleted:
<
<


download

 
Changed:
<
<
>
>

size

Indicates the downloadable size of the jar file in bytes.

1.0

 
Deleted:
<
<

Can be used to indicate this extension may be downloaded eagerly or lazily.

1.0

 
Added:
>
>
 
Changed:
<
<


>
>
 
Changed:
<
<


>
>
 
Changed:
<
<

part

>
>
part
 
Added:
>
>
Can be used to group resources together so they will be downloaded at the same time.
 
Deleted:
<
<

Denotes the name of a part in this jnlp file to include the extension in.

 
Deleted:
<
<
 
Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0
 
Changed:
<
<

package

>
>
 
Changed:
<
<


>
>

extension

 
Added:
>
>
 
Deleted:
<
<

Can be used to indicate to the JNLP Client which packages are implemented in which JAR files.

 
Changed:
<
<

1.0

>
>
Contains pointer to an additional component-desc or installer-desc to be used with this application.
 
Changed:
<
<


>
>
1.0
 
Changed:
<
<
>
>
 
Changed:
<
<


name

>
>

href

The URL to the additional extension jnlp file.

1.0

yes

 
Deleted:
<
<
 
Changed:
<
<

Package name contained in the jar files of the given part.

>
>

version

 
Added:
>
>
The version of the additional extension jnlp file.
 
Added:
>
>
 
Deleted:
<
<

1.0

yes

 
Changed:
<
<
>
>
1.0
 
Changed:
<
<


part

>
>

 
Added:
>
>
name
 
Added:
>
>
 
Changed:
<
<

Part name containing the jar files that include the given package name.

>
>
The name of the additional extension jnlp file

1.0

 
Changed:
<
<

1.0

>
>

ext-download

Can be used in an extension element to denote the parts contained in a component-extension.

1.0

 

Changed:
<
<

yes


>
>
 
Changed:
<
<
>
>
 
Changed:
<
<

recursive

Can be used to indicated that all package names beginning with the given name, can be found in the given part.

>
>
ext-part

Describes the name of a part that can be expected to be found in the extension.

 

Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0

yes

 
Added:
>
>
 
Deleted:
<
<

property

 
Changed:
<
<


>
>

download

 

Deleted:
<
<

Defines a system property that will be available through the System.getProperty and System.getProperties methods.

 
Changed:
<
<

1.0

>
>
Can be used to indicate this extension may be downloaded eagerly or lazily.

1.0

part

Denotes the name of a part in this jnlp file to include the extension in.

1.0

 
Deleted:
<
<


 
Deleted:
<
<
 
Changed:
<
<


>
>
 
Added:
>
>
package
 
Added:
>
>
 
Deleted:
<
<

name

 
Changed:
<
<

Name of the system property.

>
>
 
Changed:
<
<

1.0

yes

>
>
Can be used to indicate to the JNLP Client which packages are implemented in which JAR files.
 
Changed:
<
<
>
>
1.0

 
Deleted:
<
<
 
Changed:
<
<


>
>

name

Package name contained in the jar files of the given part.

1.0

yes

 
Deleted:
<
<

value

 
Changed:
<
<
>
>

part

 
Changed:
<
<

Value it will be set to.

1.0

>
>

Part name containing the jar files that include the given package name.

1.0

 
Added:
>
>
 
Changed:
<
<

yes


>
>
yes
 

Changed:
<
<



>
>
recursive

Can be used to indicated that all package names beginning with the given name, can be found in the given part.

 

Changed:
<
<

1.0


>
>
1.0
 
Changed:
<
<
>
>
 
Changed:
<
<



>
>

property

 
Added:
>
>
 
Changed:
<
<

Note: A jnlp file must contain one of application-desc, applet-desc, component-desc, or installer-desc

>
>
Defines a system property that will be available through the System.getProperty and System.getProperties methods.
 
Added:
>
>
 
Deleted:
<
<

1.0

 
Changed:
<
<

yes

>
>
1.0
 
Changed:
<
<

applicaation-desc

>
>
 
Changed:
<
<


>
>

 
Changed:
<
<

>
>
name
 
Added:
>
>
 
Deleted:
<
<

Denotes this is the jnlp file for an application.

 
Added:
>
>
Name of the system property.
 
Added:
>
>
 
Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0
 
Changed:
<
<


>
>
yes
 
Changed:
<
<

main-class

>
>

value

 
Added:
>
>
 
Deleted:
<
<

The name of the class containing the public static void main(String[]) method of the application.

 
Changed:
<
<

1.0

>
>
Value it will be set to.
 
Changed:
<
<

yes

>
>
1.0
 
Changed:
<
<

argument

>
>
yes
 
Added:
>
>
 
Changed:
<
<


Each argument contains (in order) an additional argument to be passed to main.

>
>
 

Deleted:
<
<

1.0


 
Changed:
<
<
>
>
1.0

 
Added:
>
>
 
Deleted:
<
<

applet-desc


 
Changed:
<
<
>
>
 
Changed:
<
<

Denotes this is the jnlp file for an applet.

1.0

>
>

Note: A jnlp file must contain one of application-desc, applet-desc, component-desc, or installer-desc

1.0

yes

applicaation-desc

Denotes this is the jnlp file for an application.

1.0

 

Deleted:
<
<


 
Deleted:
<
<


 
Changed:
<
<

>
>
 
Changed:
<
<

main-class

This is the name of the main Applet class.

>
>
 
Changed:
<
<

1.0

>
>
main-class
 
Added:
>
>

The name of the class containing the public static void main(String[]) method of the application.

1.0

 
Added:
>
>
 
Deleted:
<
<

yes

 
Changed:
<
<


>
>
yes
 
Changed:
<
<

documentbase

>
>
argument

Each argument contains (in order) an additional argument to be passed to main.

 
Deleted:
<
<

The document base for the Applet as a URL.

 

Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0
 
Added:
>
>
 
Changed:
<
<


>
>

applet-desc

 
Deleted:
<
<

name

 

Deleted:
<
<

Name of the Applet.

 
Added:
>
>
Denotes this is the jnlp file for an applet.

1.0

 
Changed:
<
<

1.0

>
>
 
Deleted:
<
<

yes

 
Changed:
<
<
>
>
 
Deleted:
<
<


 
Added:
>
>
 
Deleted:
<
<

width

 
Added:
>
>
main-class

This is the name of the main Applet class.

1.0

yes

 
Changed:
<
<

The width of the applet in pixels.

>
>

documentbase

The document base for the Applet as a URL.

 
Added:
>
>
 
Changed:
<
<

1.0

>
>
1.0
 

Changed:
<
<

yes


>
>
 
Changed:
<
<
>
>
 
Changed:
<
<

height

>
>

name

 
Added:
>
>
 
Changed:
<
<

The height of the applet in pixels

>
>
Name of the Applet.

1.0

yes

 
Changed:
<
<

1.0

>
>

 
Added:
>
>
width

The width of the applet in pixels.

1.0

 
Added:
>
>
 
Deleted:
<
<

yes

 
Changed:
<
<

param

>
>
yes
 
Added:
>
>
 
Deleted:
<
<


 
Changed:
<
<

A set of parameters that can be passed into the applet.

>
>
height

The height of the applet in pixels

 

Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0
 
Changed:
<
<


>
>

yes

param

 
Deleted:
<
<

name

 

Changed:
<
<

The name of this parameter

>
>
A set of parameters that can be passed into the applet.
 

Deleted:
<
<

1.0

yes

 
Changed:
<
<
>
>
1.0
 
Changed:
<
<


value

>
>
 
Changed:
<
<
>
>
 
Changed:
<
<

The value of this parameter

1.0

>
>
 
Changed:
<
<

yes

component-desc

>
>
name
 
Deleted:
<
<
 
Deleted:
<
<


 
Changed:
<
<

Denotes this is the jnlp file for a component extension.

>
>
The name of this parameter
 

Deleted:
<
<

1.0

 
Changed:
<
<


>
>
1.0
 
Changed:
<
<

installer-desc

>
>
yes

value

 
Deleted:
<
<


 

Deleted:
<
<

Denotes this is the jnlp file for an installed extension.

 
Changed:
<
<

1.0

>
>
The value of this parameter
 
Changed:
<
<


>
>
1.0
 
Added:
>
>
yes
 
Added:
>
>
component-desc
 
Added:
>
>
 
Added:
>
>
Denotes this is the jnlp file for a component extension.
 
Added:
>
>
 
Added:
>
>
1.0
 
Added:
>
>
 
Added:
>
>
 
Changed:
<
<


>
>

installer-desc

 
Deleted:
<
<

main-class

 

Deleted:
<
<

The name of the class containing the public static void main(String[]) method of the installer.

 
Added:
>
>
Denotes this is the jnlp file for an installed extension.
 
Added:
>
>
 
Changed:
<
<

1.0

>
>
1.0
 
Added:
>
>
 
Deleted:
<
<

yes

 
Added:
>
>

main-class

 
Changed:
<
<
>
>

The name of the class containing the public static void main(String[]) method of the installer.

1.0

yes

 

Configure your web server's jnlp Mime type settings.

Line: 2646 to 2022
  If you wish to modify the Apache global TypesConfig file and the file exists in /etc/mime.types, then you might try syntax like the following which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
Changed:
<
<
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types

>
>
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types*

 [joe@webserver /]$
Changed:
<
<
>
>
 Or, if you wish to modify an .htaccess file in your http://www.example.com/appx/ directory, and your web server is configured to allow .htaccess modifications then try the following syntax which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
Changed:
<
<
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess 

>
>
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess* 

 [joe@webserver /]$
Changed:
<
<
>
>
 

Microsoft IIS web server Mime type settings

Windows 2000 IIS Server
Added:
>
>
 Start the IIS Management Console and perform the following steps:
  • Right-click server computer in left pane, then select Properties from the drop-down menu.
  • In the 'Computer MIME Map,' click the [Edit] button.
Line: 2693 to 2069
 That's all there is to publishing APPX Desktop Client utilizing Java Web Start technology.

Troubleshooting tips

  • To clear the Web Start Cache
Changed:
<
<
    • javaws -uninstall This will remove all cached applications.
>
>
    • javaws -uninstall This will remove all cached applications.
 
  • Clear Browser's temporary files.

Bugs:

Changed:
<
<
  1. Fixed - Bug Description 1.
  2. OPEN - Bug test - Test bug. Not valid.
>
>
  1. Fixed - Bug Description 1.
  2. OPEN - Bug test - Test bug. Not valid.
 

Comments:

Added:
>
>
 Read what other users have said about this page or add your own comments.
Line: 2712 to 2087
  -- AlKalter - 26 Mar 2009
Changed:
<
<
The application cannot connect if the user’s browser has a proxy server configured. The browser downloads the “JAR” file without any problem, when I give the user name and password I cannot connect to APPX server. Is there any configuration that can solve this problem?
>
>
The application cannot connect if the user’s browser has a proxy server configured. The browser downloads the “JAR” file without any problem, when I give the user name and password I cannot connect to APPX server. Is there any configuration that can solve this problem?
  -- GerardoLopez - 01 Apr 2009
Deleted:
<
<
<--/commentPlugin-->
-- JoeOrtagus - 04 Mar 2009
 \ No newline at end of file
Added:
>
>
<--/commentPlugin-->
-- JoeOrtagus - 04 Mar 2009
 \ No newline at end of file

Revision 562009-04-01 - GerardoLopez

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2711 to 2711
 You should be able to use WinRAR to unzip a tgz file on Windows. WinRAR is a free download, available at http://download.cnet.com/WinRAR/3000-2250_4-10007677.html, and other places as well. But your point is a good one, and we'll probably add a zip file version shortly.

-- AlKalter - 26 Mar 2009

Added:
>
>

The application cannot connect if the user’s browser has a proxy server configured. The browser downloads the “JAR” file without any problem, when I give the user name and password I cannot connect to APPX server. Is there any configuration that can solve this problem?

-- GerardoLopez - 01 Apr 2009

 
<--/commentPlugin-->
-- JoeOrtagus - 04 Mar 2009 \ No newline at end of file

Revision 552009-03-26 - AlKalter

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2706 to 2706
 Is there a .zip version of java_web.tgz? Or something that Windows Vista knows how to uncompress?

-- RogerHuffman - 26 Mar 2009

Added:
>
>

You should be able to use WinRAR to unzip a tgz file on Windows. WinRAR is a free download, available at http://download.cnet.com/WinRAR/3000-2250_4-10007677.html, and other places as well. But your point is a good one, and we'll probably add a zip file version shortly.

-- AlKalter - 26 Mar 2009

 
<--/commentPlugin-->
-- JoeOrtagus - 04 Mar 2009 \ No newline at end of file

Revision 542009-03-26 - RogerHuffman

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2701 to 2701
 

Comments:

Read what other users have said about this page or add your own comments.
Added:
>
>

Is there a .zip version of java_web.tgz? Or something that Windows Vista knows how to uncompress?

-- RogerHuffman - 26 Mar 2009

 
<--/commentPlugin-->
-- JoeOrtagus - 04 Mar 2009 \ No newline at end of file

Revision 532009-03-20 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 68 to 68
 

Changed:
<
<
[joe@webserver html]$ ls -la
>
>
[joe@webserver html]$ ls -la
 
Line: 84 to 84
 

Changed:
<
<
[joe@webserver html]$ cd appx [joe@webserver appx]$ ls
>
>
[joe@webserver html]$ cd appx [joe@webserver appx]$ ls
 
Line: 125 to 125
 
appx.html contents

Changed:
<
<
[joe@webserver appx]$ cat appx.html
>
>
[joe@webserver appx]$ cat appx.html
 
Line: 197 to 197
 
appx.jnlp contents

Changed:
<
<
[joe@webserver appx]$ cat appx.jnlp
>
>
[joe@webserver appx]$ cat appx.jnlp
 
Line: 2648 to 2648
 

Changed:
<
<
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types
>
>
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types
 [joe@webserver /]$

Revision 522009-03-20 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 37 to 37
 


Changed:
<
<
[joe@webserver /]$ cd /var/www/html [joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/4.2.a/java_web.tgz
>
>
[joe@webserver /]$ cd /var/www/html [joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/4.2.a/java_web.tgz
 [joe@webserver html]$
Line: 47 to 47
 

Changed:
<
<
[joe@webserver html]$ sudo tar xzvf java_web.tgz
>
>
[joe@webserver html]$ sudo tar xzvf java_web.tgz
 
Line: 2656 to 2656
 

Changed:
<
<
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess
>
>
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess
 [joe@webserver /]$
Line: 2693 to 2693
 That's all there is to publishing APPX Desktop Client utilizing Java Web Start technology.

Troubleshooting tips

  • To clear the Web Start Cache
Changed:
<
<
    • javaws -uninstall This will remove all cached applications.
>
>
    • javaws -uninstall This will remove all cached applications.
 
  • Clear Browser's temporary files.

Bugs:

  1. Fixed - Bug Description 1.

Revision 512009-03-20 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 273 to 273
 
Table of possible element / attribute available to you in a JNLP file.
Added:
>
>

Elements and Attributes of a JNLP file

Element

Attributes

Description

Since

Required

jnlp


This is the main xml element for a jnlp file. Everything is contained within the jnlp element.

1.0

yes


spec

The spec attribute can be 1.0, 1.5.0, or 1.6.0 or can use the wildcards such as 1.0+ or 1.6+. It denoted the minimum version of the JNLP Specification that this jnlp file can work with.

 
Added:
>
>

1.0

 
Added:
>
>



codebase

The codebase attribute specifies the base location for all relative URLs specified in href attributes in the JNLP file.

1.0



href

The href specifies the URL of the JNLP file itself.

1.0



version

The version of the application being launched, as well as the version of the JNLP file itself.

1.0


information


The information element contains other elements that describe the application and it's source.

1.0

yes


os

Specifies the operating system for which this information element should be considered.

1.5.0

 
Added:
>
>



arch

Specifies the architecture for which this information element should be considered

1.5.0



platform

Specifies the platform for which this information element should be considered.

1.5.0



locale

Specifies the locale for which this information element should be considered.

1.5.0


title


The title element specifies the title of the application.

1.0

yes

vendor


The vendor element specifies the provider of the application.

1.0

yes

homepage


The homepage of the application.

1.0



href

A URL pointing to where more information on this application can be found.

1.0

yes

description


A short statement describing the application.

1.0



kind

An indicator as to what type of description this is, legal values are one-line, short, and tooltip.

1.0


icon


Describes an icon that can be used to identify the application to the user.

1.0



href

A URL pointing to the icon file, may be in one of the following formats: gif, jpg, png, ico.

1.0

yes


kind

Indicates the suggested use of the icon, can be: default, selected, disabled, rollover, splash, or shortcut.

1.0



width

Can be used to indicate the resolution of the image.

1.0



height

Can be used to indicate the resolution of the image.

1.0



depth

Can be used to indicate the resolution of the image.

1.0


offline-allowed


Indicates that this application can operate when the client system is disconnected from the network.

1.0


shortcut


The shortcut element can be used to indicate an application's preferences for desktop integration.

1.5.0



online

Can be used to describe the application's preference for creating a shortcut to run online or offline.

1.5.0


desktop


Can be used to indicate an application's preference for putting a shortcut on the users desktop.

1.5.0


menu


Can be used to indicate an application's preference for putting a menu item in the users start menus.

1.5.0



sub-menu

Can be used to indicate an application's preference for where to place the menu item.

1.5.0


association


 
Added:
>
>

Can be used to hint to the JNLP client that it wishes to be registered with the operating system as the primary handler of certain extensions and a certain mime-type.

 
Added:
>
>

1.5.0



extensions

Contains a list of file extensions (separated by spaces) that the application requests it be registered to handle.

1.5.0



mime-type

Contains the mime-type that the application requests it be registered to handle.

1.5.0


related-content


Describes an additional piece of related content that may be integrated with the application.

1.5.0



href

A URL pointing to the related content.

1.5.0

yes






update


The update element is used to indicate the preferences for how application updates should be handled by the JNLP Client.

1.6.0



check

Indicates the preference for when the JNLP Client should check for updates. It can be always, timeout, or background..

1.6.0



policy

Indicates the preference for how the JNLP Client should handle an application update when it is known an update is available before the application is launched. It can be always, prompt-update, or prompt-run.

 
Added:
>
>

1.6.0

 
Added:
>
>





1.0


security


This element can be used to request enhanced permissions.

1.0


all-permissions


Requests that the application be run with all permissions.

1.0


j2ee-application-client-permissions


Requests that the application be run with a permission set that meets the security specifications of the J2EE Application Client environment.

1.0





1.0


resources


Describes all the resources that are needed for an application.

1.0

yes


os

Specifies the operating system for which the resources element should be considered.

1.0



arch

Specifies the architecture for which the resources element should be considered.

1.0



locale

Specifies that the locales for which the resources element should be considered.



java (or java se)


Specifies what version(s) of Java to run the application with.

1.6.0 (java)



version

Describes an ordered list of version ranges to use.

1.0

yes


href

The URL denoting the supplier of this version of java, and where it may be downloaded from.

1.0



java-vm-args

 
Added:
>
>

Indicates an additional set of standard and non-standard virtual machine arguments that the application would prefer the JNLP

 
Added:
>
>
Client to use when launching Java.

1.0



initial-heap-size

Indicates the initial size of the Java heap.

1.0



max-heap-size

Indicates the maximum size of the Java heap.

1.0


jar


Specifies a JAR file that is part of the application's classpath.

1.0

yes


href

The URL of the jar file.

1.0

yes


version

The requested version of the jar file. Requires using the version-based download protocol

1.0



main

Indicates if this jar contains the class containing the main method of the application.

1.0



download

Can be used to indicate this jar may be downloaded lazily, or when needed.

1.0



size

Indicates the downloadable size of the jar file in bytes.

1.0



part

Can be used to group resources together so they will be downloaded at the same time.

1.0


nativelib


Specifies a JAR file that contains native libraries in it's root directory.

1.0



href

The URL of the jar file.

1.0

yes


version

The requested version of the jar file. Requires using the version-based download protocol

1.0



download

Can be used to indicate this jar may be downloaded lazily.

1.0



size

Indicates the downloadable size of the jar file in bytes.

1.0



part

Can be used to group resources together so they will be downloaded at the same time.

1.0


extension


Contains pointer to an additional component-desc or installer-desc to be used with this application.

1.0



href

The URL to the additional extension jnlp file.

1.0

yes


version

The version of the additional extension jnlp file.

1.0



name

The name of the additional extension jnlp file

1.0


ext-download


Can be used in an extension element to denote the parts contained in a component-extension.

1.0



ext-part

Describes the name of a part that can be expected to be found in the extension.

1.0

yes


download

Can be used to indicate this extension may be downloaded eagerly or lazily.

1.0



part

Denotes the name of a part in this jnlp file to include the extension in.

1.0


package


Can be used to indicate to the JNLP Client which packages are implemented in which JAR files.

1.0



name

Package name contained in the jar files of the given part.

1.0

yes


part

Part name containing the jar files that include the given package name.

1.0

yes


recursive

Can be used to indicated that all package names beginning with the given name, can be found in the given part.

1.0


property


Defines a system property that will be available through the System.getProperty and System.getProperties methods.

1.0



name

Name of the system property.

1.0

yes


value

Value it will be set to.

1.0

yes




1.0




Note: A jnlp file must contain one of application-desc, applet-desc, component-desc, or installer-desc

1.0

yes

applicaation-desc


Denotes this is the jnlp file for an application.

1.0



main-class

The name of the class containing the public static void main(String[]) method of the application.

1.0

yes

argument


Each argument contains (in order) an additional argument to be passed to main.

1.0


applet-desc


Denotes this is the jnlp file for an applet.

1.0



main-class

This is the name of the main Applet class.

1.0

yes


documentbase

The document base for the Applet as a URL.

1.0



name

Name of the Applet.

1.0

yes


width

The width of the applet in pixels.

1.0

yes


height

The height of the applet in pixels

1.0

yes

param


A set of parameters that can be passed into the applet.

1.0



name

The name of this parameter

1.0

yes


value

The value of this parameter

1.0

yes

component-desc


Denotes this is the jnlp file for a component extension.

1.0


installer-desc


Denotes this is the jnlp file for an installed extension.

1.0



main-class

The name of the class containing the public static void main(String[]) method of the installer.

1.0

yes

 
Added:
>
>
 
Changed:
<
<

Element

Attributes

Description

Since

Required

jnlp

This is the main xml element for a jnlp file. Everything is contained within the jnlp element.

1.0

yes

spec

The spec attribute can be 1.0, 1.5.0, or 1.6.0 or can use the wildcards such as 1.0+ or 1.6+. It denoted the minimum version of the JNLP Specification that this jnlp file can work with.

1.0

codebase

The codebase attribute specifies the base location for all relative URLs specified in href attributes in the JNLP file.

1.0

href

The href specifies the URL of the JNLP file itself.

1.0

version

The version of the application being launched, as well as the version of the JNLP file itself.

1.0

information

The information element contains other elements that describe the application and it's source.

1.0

yes

os

Specifies the operating system for which this information element should be considered.

1.5.0

arch

Specifies the architecture for which this information element should be considered

1.5.0

platform

Specifies the platform for which this information element should be considered.

1.5.0

locale

Specifies the locale for which this information element should be considered.

1.5.0

title

The title element specifies the title of the application.

1.0

yes

vendor

The vendor element specifies the provider of the application.

1.0

yes

homepage

The homepage of the application.

1.0

href

A URL pointing to where more information on this application can be found.

1.0

yes

description

A short statement describing the application.

1.0

kind

An indicator as to what type of description this is, legal values are one-line, short, and tooltip.

1.0

icon

Describes an icon that can be used to identify the application to the user.

1.0

href

A URL pointing to the icon file, may be in one of the following formats: gif, jpg, png, ico.

1.0

yes

kind

Indicates the suggested use of the icon, can be: default, selected, disabled, rollover, splash, or shortcut.

1.0

width

Can be used to indicate the resolution of the image.

1.0

height

Can be used to indicate the resolution of the image.

1.0

depth

Can be used to indicate the resolution of the image.

1.0

offline-allowed

Indicates that this application can operate when the client system is disconnected from the network.

1.0

shortcut

The shortcut element can be used to indicate an application's preferences for desktop integration.

1.5.0

online

Can be used to describe the application's preference for creating a shortcut to run online or offline.

1.5.0

desktop

Can be used to indicate an application's preference for putting a shortcut on the users desktop.

1.5.0

menu

Can be used to indicate an application's preference for putting a menu item in the users start menus.

1.5.0

sub-menu

Can be used to indicate an application's preference for where to place the menu item.

1.5.0

association

Can be used to hint to the JNLP client that it wishes to be registered with the operating system as the primary handler of certain extensions and a certain mime-type.

1.5.0

extensions

Contains a list of file extensions (separated by spaces) that the application requests it be registered to handle.

1.5.0

mime-type

Contains the mime-type that the application requests it be registered to handle.

1.5.0

related-content

Describes an additional piece of related content that may be integrated with the application.

1.5.0

href

A URL pointing to the related content.

1.5.0

yes

update

The update element is used to indicate the preferences for how application updates should be handled by the JNLP Client.

1.6.0

check

Indicates the preference for when the JNLP Client should check for updates. It can be always, timeout, or background..

1.6.0

policy

Indicates the preference for how the JNLP Client should handle an application update when it is known an update is available before the application is launched. It can be always, prompt-update, or prompt-run.

1.6.0

1.0

security

This element can be used to request enhanced permissions.

1.0

all-permissions

Requests that the application be run with all permissions.

1.0

j2ee-application-client-permissions

Requests that the application be run with a permission set that meets the security specifications of the J2EE Application Client environment.

1.0

1.0

resources

Describes all the resources that are needed for an application.

1.0

yes

os

Specifies the operating system for which the resources element should be considered.

1.0

arch

Specifies the architecture for which the resources element should be considered.

1.0

locale

Specifies that the locales for which the resources element should be considered.

java (or java se)

Specifies what version(s) of Java to run the application with.

1.6.0 (java)

version

Describes an ordered list of version ranges to use.

1.0

yes

href

The URL denoting the supplier of this version of java, and where it may be downloaded from.

1.0

java-vm-args

Indicates an additional set of standard and non-standard virtual machine arguments that the application would prefer the JNLP

Client to use when launching Java.

1.0

initial-heap-size

Indicates the initial size of the Java heap.

1.0

max-heap-size

Indicates the maximum size of the Java heap.

1.0

jar

Specifies a JAR file that is part of the application's classpath.

1.0

yes

href

The URL of the jar file.

1.0

yes

version

The requested version of the jar file. Requires using the version-based download protocol

1.0

main

Indicates if this jar contains the class containing the main method of the application.

1.0

download

Can be used to indicate this jar may be downloaded lazily, or when needed.

1.0

size

Indicates the downloadable size of the jar file in bytes.

1.0

part

Can be used to group resources together so they will be downloaded at the same time.

1.0

nativelib

Specifies a JAR file that contains native libraries in it's root directory.

1.0

href

The URL of the jar file.

1.0

yes

version

The requested version of the jar file. Requires using the version-based download protocol

1.0

download

Can be used to indicate this jar may be downloaded lazily.

1.0

size

Indicates the downloadable size of the jar file in bytes.

1.0

part

Can be used to group resources together so they will be downloaded at the same time.

1.0

extension

Contains pointer to an additional component-desc or installer-desc to be used with this application.

1.0

href

The URL to the additional extension jnlp file.

1.0

yes

version

The version of the additional extension jnlp file.

1.0

name

The name of the additional extension jnlp file

1.0

ext-download

Can be used in an extension element to denote the parts contained in a component-extension.

1.0

ext-part

Describes the name of a part that can be expected to be found in the extension.

1.0

yes

download

Can be used to indicate this extension may be downloaded eagerly or lazily.

1.0

part

Denotes the name of a part in this jnlp file to include the extension in.

1.0

package

Can be used to indicate to the JNLP Client which packages are implemented in which JAR files.

1.0

name

Package name contained in the jar files of the given part.

1.0

yes

part

Part name containing the jar files that include the given package name.

1.0

yes

recursive

Can be used to indicated that all package names beginning with the given name, can be found in the given part.

1.0

property

Defines a system property that will be available through the System.getProperty and System.getProperties methods.

1.0

name

Name of the system property.

1.0

yes

value

Value it will be set to.

1.0

yes

1.0

Note: A jnlp file must contain one of application-desc, applet-desc, component-desc, or installer-desc

1.0

yes

applicaation-desc

Denotes this is the jnlp file for an application.

1.0

main-class

The name of the class containing the public static void main(String[]) method of the application.

1.0

yes

argument

Each argument contains (in order) an additional argument to be passed to main.

1.0

applet-desc

Denotes this is the jnlp file for an applet.

1.0

main-class

This is the name of the main Applet class.

1.0

yes

documentbase

The document base for the Applet as a URL.

1.0

name

Name of the Applet.

1.0

yes

width

The width of the applet in pixels.

1.0

yes

height

The height of the applet in pixels

1.0

yes

param

A set of parameters that can be passed into the applet.

1.0

name

The name of this parameter

1.0

yes

value

The value of this parameter

1.0

yes

component-desc

Denotes this is the jnlp file for a component extension.

1.0

installer-desc

Denotes this is the jnlp file for an installed extension.

1.0

main-class

The name of the class containing the public static void main(String[]) method of the installer.

1.0

yes

Elements and Attributes of a JNLP file
>
>
 

Configure your web server's jnlp Mime type settings.

Revision 502009-03-20 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"
Deleted:
<
<
 

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 236 to 235
 
<-- Acceptable JVMs in preferred order, best first -->
<-- Sun JVM -->
Added:
>
>
<-- This swing.noxp value prevents a "look and feel" issue on Vista -->
 
<-- application code, load before launch. JNLP 1.6 main="true" indicates jar with main class -->

Revision 492009-03-19 - AlKalter

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"
Added:
>
>
 

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 37 to 38
 


Changed:
<
<
[joe@webserver /]$ cd /var/www/html [joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/4.2.a/java_web.tgz
>
>
[joe@webserver /]$ cd /var/www/html [joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/4.2.a/java_web.tgz
 [joe@webserver html]$
Line: 47 to 48
 

Changed:
<
<
[joe@webserver html]$ sudo tar xzvf java_web.tgz
>
>
[joe@webserver html]$ sudo tar xzvf java_web.tgz
 
Line: 68 to 69
 

Changed:
<
<
[joe@webserver html]$ ls -la
>
>
[joe@webserver html]$ ls -la
 
Line: 84 to 85
 

Changed:
<
<
[joe@webserver html]$ cd appx [joe@webserver appx]$ ls
>
>
[joe@webserver html]$ cd appx [joe@webserver appx]$ ls
 
Line: 125 to 126
 
appx.html contents

Changed:
<
<
[joe@webserver appx]$ cat appx.html
>
>
[joe@webserver appx]$ cat appx.html
 
Line: 179 to 180
 
         var url = "http://www.example.com/appx/appx.jnlp";
         deployJava.launchButtonPNG = "http://www.example.com/appx/APPXLaunchButton.png";

Deleted:
<
<
 
Added:
>
>
 

splash.gif

This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.
Line: 197 to 198
 
appx.jnlp contents

Changed:
<
<
[joe@webserver appx]$ cat appx.jnlp
>
>
[joe@webserver appx]$ cat appx.jnlp
 
Line: 250 to 251
  -remoteUser=prospect -remoteHost=demo.appx.com -remotePassword=prospect
Added:
>
>
-screenRows=28 -screenColumns=110
  -SSLMode=disabled </application-desc>
Line: 269 to 272
 
Table of possible element / attribute available to you in a JNLP file.
Deleted:
<
<

Elements and Attributes of a JNLP file

Element

Attributes

Description

Since

Required

jnlp


This is the main xml element for a jnlp file. Everything is contained within the jnlp element.

1.0

yes


spec

The spec attribute can be 1.0, 1.5.0, or 1.6.0 or can use the wildcards such as 1.0+ or 1.6+. It denoted the minimum version of the JNLP Specification that this jnlp file can work with.

 
Deleted:
<
<

1.0

 
Deleted:
<
<



codebase

The codebase attribute specifies the base location for all relative URLs specified in href attributes in the JNLP file.

1.0



href

The href specifies the URL of the JNLP file itself.

1.0



version

The version of the application being launched, as well as the version of the JNLP file itself.

1.0


information


The information element contains other elements that describe the application and it's source.

1.0

yes


os

Specifies the operating system for which this information element should be considered.

1.5.0

 
Deleted:
<
<



arch

Specifies the architecture for which this information element should be considered

1.5.0



platform

Specifies the platform for which this information element should be considered.

1.5.0



locale

Specifies the locale for which this information element should be considered.

1.5.0


title


The title element specifies the title of the application.

1.0

yes

vendor


The vendor element specifies the provider of the application.

1.0

yes

homepage


The homepage of the application.

1.0



href

A URL pointing to where more information on this application can be found.

1.0

yes

description


A short statement describing the application.

1.0



kind

An indicator as to what type of description this is, legal values are one-line, short, and tooltip.

1.0


icon


Describes an icon that can be used to identify the application to the user.

1.0



href

A URL pointing to the icon file, may be in one of the following formats: gif, jpg, png, ico.

1.0

yes


kind

Indicates the suggested use of the icon, can be: default, selected, disabled, rollover, splash, or shortcut.

1.0



width

Can be used to indicate the resolution of the image.

1.0



height

Can be used to indicate the resolution of the image.

1.0



depth

Can be used to indicate the resolution of the image.

1.0


offline-allowed


Indicates that this application can operate when the client system is disconnected from the network.

1.0


shortcut


The shortcut element can be used to indicate an application's preferences for desktop integration.

1.5.0



online

Can be used to describe the application's preference for creating a shortcut to run online or offline.

1.5.0


desktop


Can be used to indicate an application's preference for putting a shortcut on the users desktop.

1.5.0


menu


Can be used to indicate an application's preference for putting a menu item in the users start menus.

1.5.0



sub-menu

Can be used to indicate an application's preference for where to place the menu item.

1.5.0


association


 
Deleted:
<
<

Can be used to hint to the JNLP client that it wishes to be registered with the operating system as the primary handler of certain extensions and a certain mime-type.

 
Deleted:
<
<

1.5.0



extensions

Contains a list of file extensions (separated by spaces) that the application requests it be registered to handle.

1.5.0



mime-type

Contains the mime-type that the application requests it be registered to handle.

1.5.0


related-content


Describes an additional piece of related content that may be integrated with the application.

1.5.0



href

A URL pointing to the related content.

1.5.0

yes






update


The update element is used to indicate the preferences for how application updates should be handled by the JNLP Client.

1.6.0



check

Indicates the preference for when the JNLP Client should check for updates. It can be always, timeout, or background..

1.6.0



policy

Indicates the preference for how the JNLP Client should handle an application update when it is known an update is available before the application is launched. It can be always, prompt-update, or prompt-run.

 
Deleted:
<
<

1.6.0

 
Deleted:
<
<





1.0


security


This element can be used to request enhanced permissions.

1.0


all-permissions


Requests that the application be run with all permissions.

1.0


j2ee-application-client-permissions


Requests that the application be run with a permission set that meets the security specifications of the J2EE Application Client environment.

1.0





1.0


resources


Describes all the resources that are needed for an application.

1.0

yes


os

Specifies the operating system for which the resources element should be considered.

1.0



arch

Specifies the architecture for which the resources element should be considered.

1.0



locale

Specifies that the locales for which the resources element should be considered.



java (or java se)


Specifies what version(s) of Java to run the application with.

1.6.0 (java)



version

Describes an ordered list of version ranges to use.

1.0

yes


href

The URL denoting the supplier of this version of java, and where it may be downloaded from.

1.0



java-vm-args

 
Deleted:
<
<

Indicates an additional set of standard and non-standard virtual machine arguments that the application would prefer the JNLP

 
Deleted:
<
<
Client to use when launching Java.

1.0



initial-heap-size

Indicates the initial size of the Java heap.

1.0



max-heap-size

Indicates the maximum size of the Java heap.

1.0


jar


Specifies a JAR file that is part of the application's classpath.

1.0

yes


href

The URL of the jar file.

1.0

yes


version

The requested version of the jar file. Requires using the version-based download protocol

1.0



main

Indicates if this jar contains the class containing the main method of the application.

1.0



download

Can be used to indicate this jar may be downloaded lazily, or when needed.

1.0



size

Indicates the downloadable size of the jar file in bytes.

1.0



part

Can be used to group resources together so they will be downloaded at the same time.

1.0


nativelib


Specifies a JAR file that contains native libraries in it's root directory.

1.0



href

The URL of the jar file.

1.0

yes


version

The requested version of the jar file. Requires using the version-based download protocol

1.0



download

Can be used to indicate this jar may be downloaded lazily.

1.0



size

Indicates the downloadable size of the jar file in bytes.

1.0



part

Can be used to group resources together so they will be downloaded at the same time.

1.0


extension


Contains pointer to an additional component-desc or installer-desc to be used with this application.

1.0



href

The URL to the additional extension jnlp file.

1.0

yes


version

The version of the additional extension jnlp file.

1.0



name

The name of the additional extension jnlp file

1.0


ext-download


Can be used in an extension element to denote the parts contained in a component-extension.

1.0



ext-part

Describes the name of a part that can be expected to be found in the extension.

1.0

yes


download

Can be used to indicate this extension may be downloaded eagerly or lazily.

1.0



part

Denotes the name of a part in this jnlp file to include the extension in.

1.0


package


Can be used to indicate to the JNLP Client which packages are implemented in which JAR files.

1.0



name

Package name contained in the jar files of the given part.

1.0

yes


part

Part name containing the jar files that include the given package name.

1.0

yes


recursive

Can be used to indicated that all package names beginning with the given name, can be found in the given part.

1.0


property


Defines a system property that will be available through the System.getProperty and System.getProperties methods.

1.0



name

Name of the system property.

1.0

yes


value

Value it will be set to.

1.0

yes




1.0




Note: A jnlp file must contain one of application-desc, applet-desc, component-desc, or installer-desc

1.0

yes

applicaation-desc


Denotes this is the jnlp file for an application.

1.0



main-class

The name of the class containing the public static void main(String[]) method of the application.

1.0

yes

argument


Each argument contains (in order) an additional argument to be passed to main.

1.0


applet-desc


Denotes this is the jnlp file for an applet.

1.0



main-class

This is the name of the main Applet class.

1.0

yes


documentbase

The document base for the Applet as a URL.

1.0



name

Name of the Applet.

1.0

yes


width

The width of the applet in pixels.

1.0

yes


height

The height of the applet in pixels

1.0

yes

param


A set of parameters that can be passed into the applet.

1.0



name

The name of this parameter

1.0

yes


value

The value of this parameter

1.0

yes

component-desc


Denotes this is the jnlp file for a component extension.

1.0


installer-desc


Denotes this is the jnlp file for an installed extension.

1.0



main-class

The name of the class containing the public static void main(String[]) method of the installer.

1.0

yes

 
Deleted:
<
<
 
Changed:
<
<
>
>

Element

Attributes

Description

Since

Required

jnlp

This is the main xml element for a jnlp file. Everything is contained within the jnlp element.

1.0

yes

spec

The spec attribute can be 1.0, 1.5.0, or 1.6.0 or can use the wildcards such as 1.0+ or 1.6+. It denoted the minimum version of the JNLP Specification that this jnlp file can work with.

1.0

codebase

The codebase attribute specifies the base location for all relative URLs specified in href attributes in the JNLP file.

1.0

href

The href specifies the URL of the JNLP file itself.

1.0

version

The version of the application being launched, as well as the version of the JNLP file itself.

1.0

information

The information element contains other elements that describe the application and it's source.

1.0

yes

os

Specifies the operating system for which this information element should be considered.

1.5.0

arch

Specifies the architecture for which this information element should be considered

1.5.0

platform

Specifies the platform for which this information element should be considered.

1.5.0

locale

Specifies the locale for which this information element should be considered.

1.5.0

title

The title element specifies the title of the application.

1.0

yes

vendor

The vendor element specifies the provider of the application.

1.0

yes

homepage

The homepage of the application.

1.0

href

A URL pointing to where more information on this application can be found.

1.0

yes

description

A short statement describing the application.

1.0

kind

An indicator as to what type of description this is, legal values are one-line, short, and tooltip.

1.0

icon

Describes an icon that can be used to identify the application to the user.

1.0

href

A URL pointing to the icon file, may be in one of the following formats: gif, jpg, png, ico.

1.0

yes

kind

Indicates the suggested use of the icon, can be: default, selected, disabled, rollover, splash, or shortcut.

1.0

width

Can be used to indicate the resolution of the image.

1.0

height

Can be used to indicate the resolution of the image.

1.0

depth

Can be used to indicate the resolution of the image.

1.0

offline-allowed

Indicates that this application can operate when the client system is disconnected from the network.

1.0

shortcut

The shortcut element can be used to indicate an application's preferences for desktop integration.

1.5.0

online

Can be used to describe the application's preference for creating a shortcut to run online or offline.

1.5.0

desktop

Can be used to indicate an application's preference for putting a shortcut on the users desktop.

1.5.0

menu

Can be used to indicate an application's preference for putting a menu item in the users start menus.

1.5.0

sub-menu

Can be used to indicate an application's preference for where to place the menu item.

1.5.0

association

Can be used to hint to the JNLP client that it wishes to be registered with the operating system as the primary handler of certain extensions and a certain mime-type.

1.5.0

extensions

Contains a list of file extensions (separated by spaces) that the application requests it be registered to handle.

1.5.0

mime-type

Contains the mime-type that the application requests it be registered to handle.

1.5.0

related-content

Describes an additional piece of related content that may be integrated with the application.

1.5.0

href

A URL pointing to the related content.

1.5.0

yes

update

The update element is used to indicate the preferences for how application updates should be handled by the JNLP Client.

1.6.0

check

Indicates the preference for when the JNLP Client should check for updates. It can be always, timeout, or background..

1.6.0

policy

Indicates the preference for how the JNLP Client should handle an application update when it is known an update is available before the application is launched. It can be always, prompt-update, or prompt-run.

1.6.0

1.0

security

This element can be used to request enhanced permissions.

1.0

all-permissions

Requests that the application be run with all permissions.

1.0

j2ee-application-client-permissions

Requests that the application be run with a permission set that meets the security specifications of the J2EE Application Client environment.

1.0

1.0

resources

Describes all the resources that are needed for an application.

1.0

yes

os

Specifies the operating system for which the resources element should be considered.

1.0

arch

Specifies the architecture for which the resources element should be considered.

1.0

locale

Specifies that the locales for which the resources element should be considered.

java (or java se)

Specifies what version(s) of Java to run the application with.

1.6.0 (java)

version

Describes an ordered list of version ranges to use.

1.0

yes

href

The URL denoting the supplier of this version of java, and where it may be downloaded from.

1.0

java-vm-args

Indicates an additional set of standard and non-standard virtual machine arguments that the application would prefer the JNLP

Client to use when launching Java.

1.0

initial-heap-size

Indicates the initial size of the Java heap.

1.0

max-heap-size

Indicates the maximum size of the Java heap.

1.0

jar

Specifies a JAR file that is part of the application's classpath.

1.0

yes

href

The URL of the jar file.

1.0

yes

version

The requested version of the jar file. Requires using the version-based download protocol

1.0

main

Indicates if this jar contains the class containing the main method of the application.

1.0

download

Can be used to indicate this jar may be downloaded lazily, or when needed.

1.0

size

Indicates the downloadable size of the jar file in bytes.

1.0

part

Can be used to group resources together so they will be downloaded at the same time.

1.0

nativelib

Specifies a JAR file that contains native libraries in it's root directory.

1.0

href

The URL of the jar file.

1.0

yes

version

The requested version of the jar file. Requires using the version-based download protocol

1.0

download

Can be used to indicate this jar may be downloaded lazily.

1.0

size

Indicates the downloadable size of the jar file in bytes.

1.0

part

Can be used to group resources together so they will be downloaded at the same time.

1.0

extension

Contains pointer to an additional component-desc or installer-desc to be used with this application.

1.0

href

The URL to the additional extension jnlp file.

1.0

yes

version

The version of the additional extension jnlp file.

1.0

name

The name of the additional extension jnlp file

1.0

ext-download

Can be used in an extension element to denote the parts contained in a component-extension.

1.0

ext-part

Describes the name of a part that can be expected to be found in the extension.

1.0

yes

download

Can be used to indicate this extension may be downloaded eagerly or lazily.

1.0

part

Denotes the name of a part in this jnlp file to include the extension in.

1.0

package

Can be used to indicate to the JNLP Client which packages are implemented in which JAR files.

1.0

name

Package name contained in the jar files of the given part.

1.0

yes

part

Part name containing the jar files that include the given package name.

1.0

yes

recursive

Can be used to indicated that all package names beginning with the given name, can be found in the given part.

1.0

property

Defines a system property that will be available through the System.getProperty and System.getProperties methods.

1.0

name

Name of the system property.

1.0

yes

value

Value it will be set to.

1.0

yes

1.0

Note: A jnlp file must contain one of application-desc, applet-desc, component-desc, or installer-desc

1.0

yes

applicaation-desc

Denotes this is the jnlp file for an application.

1.0

main-class

The name of the class containing the public static void main(String[]) method of the application.

1.0

yes

argument

Each argument contains (in order) an additional argument to be passed to main.

1.0

applet-desc

Denotes this is the jnlp file for an applet.

1.0

main-class

This is the name of the main Applet class.

1.0

yes

documentbase

The document base for the Applet as a URL.

1.0

name

Name of the Applet.

1.0

yes

width

The width of the applet in pixels.

1.0

yes

height

The height of the applet in pixels

1.0

yes

param

A set of parameters that can be passed into the applet.

1.0

name

The name of this parameter

1.0

yes

value

The value of this parameter

1.0

yes

component-desc

Denotes this is the jnlp file for a component extension.

1.0

installer-desc

Denotes this is the jnlp file for an installed extension.

1.0

main-class

The name of the class containing the public static void main(String[]) method of the installer.

1.0

yes

Elements and Attributes of a JNLP file
 

Configure your web server's jnlp Mime type settings.

Line: 2644 to 3388
 

Changed:
<
<
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types
>
>
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types
 [joe@webserver /]$
Line: 2652 to 3396
 

Changed:
<
<
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess
>
>
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess
 [joe@webserver /]$
Line: 2689 to 3433
 That's all there is to publishing APPX Desktop Client utilizing Java Web Start technology.

Troubleshooting tips

  • To clear the Web Start Cache
Changed:
<
<
    • javaws -uninstall This will remove all cached applications.
>
>
    • javaws -uninstall This will remove all cached applications.
 
  • Clear Browser's temporary files.

Bugs:

  1. Fixed - Bug Description 1.

Revision 482009-03-16 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 148 to 148
  APPX Desktop Client Web Start Demonstration
Changed:
<
<

Clicking the icon below will attempt to detect if the correct Java JRE is installed, and if possible install it. If the installer determines you need an updated JRE but it can't auto install a JRE, it will place you on Sun's download page for your platform. After the JRE requirement is met, the APPX Desktop Client will be downloaded and launched.

>
>

Clicking the icon below will attempt to detect if the correct Java JRE is installed, and if possible install it. If the installer determines you need an updated JRE but it can't auto install a JRE, it will place you on Sun's download page for your platform. After the JRE requirement is met, the APPX Desktop Client will be downloaded and launched.

 


Line: 240 to 241
 

<-- application class with main method -->
Added:
>
>
<-- This is the section where you would add startup parameters for the APPX -->
<-- Desktop Client.  Items such as TCP port number, initial window size etc -->
  <application-desc main-class="start.Appx">
<-- command line arguments -->
-windowTitle=APPX - $(host):$(port)

Revision 472009-03-16 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 98 to 98
 

APPX Desktop Client Web Start Bundle Components

appx32.gif

The appx32.gif file is the file used as an application runtime icon. It is referenced by the appx.jnlp file that we review later in this document.
Added:
>
>

README.txt

README.txt contains the following very brief instructions to the reader.

Place these files in a directory named /appx/ off your web server's webroot.

You need to change three items, all references to www.example.com to read your site URL:

In appx.html
appx.html: ---> var url = "http://www.example.com/appx/appx.jnlp";
appx.html: ---> deployJava.launchButtonPNG = "http://www.example.com/appx/APPXLaunchButton.png";


In appx.jnlp:
appx.jnlp: ---> <jnlp spec="1.5+" codebase="http://www.example.com/appx" href="appx.jnlp" version ="5.0.0.a9"> 

Please see our Wiki at http://wiki.appx.com/wiki/bin/view/Main/LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart for further documentation. 

INSTALL.txt

INSTALL.txt points the reader to README.txt
 

appx.html

The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.
appx.html contents
Line: 159 to 181
 
Added:
>
>

splash.gif

This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.

APPXLaunchButton.png

APPXLaunchButton.png is an image file that is displayed for the user to click to begin the JRE detection and ultimately start the APPX Desktop Client.

appx-nativelib.jar

The appx-nativelib.jar file contains platform specific files for the proper execution of the appx.jar file.
 

appx.jar

The APPX Desktop Client in Java jar format.

appx.jnlp

Line: 2601 to 2631
 
Deleted:
<
<

APPXLaunchButton.png

APPXLaunchButton.png is an image file that is displayed for the user to click to begin the JRE detection and ultimately start the APPX Desktop Client.

appx-nativelib.jar

The appx-nativelib.jar file contains platform specific files for the proper execution of the appx.jar file.

INSTALL.txt

INSTALL.txt points the reader to README.txt

README.txt

README.txt contains the following very brief instructions to the reader.

Place these files in a directory named /appx/ off your web server's webroot.

You need to change three items, all references to www.example.com to read your site URL:

In appx.html
appx.html: ---> var url = "http://www.example.com/appx/appx.jnlp";
appx.html: ---> deployJava.launchButtonPNG = "http://www.example.com/appx/APPXLaunchButton.png";


In appx.jnlp:
appx.jnlp: ---> <jnlp spec="1.5+" codebase="http://www.example.com/appx" href="appx.jnlp" version ="5.0.0.a9"> 

Please see our Wiki at http://wiki.appx.com/wiki/bin/view/Main/LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart for further documentation. 

splash.gif

This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.
 

Configure your web server's jnlp Mime type settings.

Your webserver needs to support the .jnlp mime type. There are too many web servers and web server version that each configure via different actions, syntax or configuration file location that it is beyond the scope of this document to cover mime type configuration fully. However, this might be enough to get you on the right track if your server is not already configured for jnlp mime type support.

Revision 462009-03-16 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 78 to 78
 drwxr-xr-x 3 root root 4096 Mar 4 14:27 . drwxr-xr-x 10 root root 4096 Jun 26 2007 .. drwxrwxrwx 2 root root 4096 Mar 3 14:40 appx
Changed:
<
<
-rw-r--r-- 1 root root 1233717 Mar 4 14:27 java_web.tgz
>
>
-rw-r--r-- 1 root root 1233805 Mar 4 14:27 java_web.tgz
 
Line: 217 to 217
  -remoteUser=prospect -remoteHost=demo.appx.com -remotePassword=prospect
Added:
>
>
-SSLMode=disabled
  </application-desc>
Line: 231 to 232
  codebase="http://www.example.com/appx" href="appx.jnlp"
Added:
>
>
Towards the end of the appx.jnlp file, notice the application-desc elements with argument attributes of -windowTitle, -remoteHost ... You can add any APPX Desktop Client startup parameter that you normally find when you select Options, Advanced upon initially starting the APPX Desktop Client.
 
Table of possible element / attribute available to you in a JNLP file.

Revision 452009-03-16 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 203 to 203
 
<-- Acceptable JVMs in preferred order, best first -->
<-- Sun JVM -->
Changed:
<
<
>
>
 
<-- application code, load before launch. JNLP 1.6 main="true" indicates jar with main class -->
Line: 300 to 300
 

The spec attribute can be 1.0, 1.5.0, or 1.6.0 or can use

Changed:
<
<
the wildcards such as 1.0+. It denoted the minimum version of the JNLP
>
>
the wildcards such as 1.0+ or 1.6+. It denoted the minimum version of the JNLP
 Specification that this jnlp file can work with.

Revision 442009-03-16 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2628 to 2628
 

splash.gif

This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.
Deleted:
<
<

appx.html

The appx.html file is the web document that a web browser can view. This document contains a link to a Java Web Start file (appx.jnlp). When this link is clicked, the JRE environment is installed if it doesn't exist on the client desktop, and then the APPX Desktop Client application will load. Subsequent clicks will only download updates.
 

Configure your web server's jnlp Mime type settings.

Revision 432009-03-16 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 7 to 7
 When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 4.2.a and above. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 1.3 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package ; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.

Required software components

APPX Desktop Client Java Web Start Bundle

Changed:
<
<
You can get the APPX Desktop Client Java Web Start Bundle from here coming soon!.
>
>
You can get the APPX Desktop Client Java Web Start Bundle from here.
 

APPX Server

You need a functioning APPX installation. Follow instructions in this document to install APPX on Windows if you don't already have APPX installed.
Line: 47 to 47
 

Changed:
<
<
[joe@webserver html]$ sudo tar xzvpf appx.tgz
>
>
[joe@webserver html]$ sudo tar xzvf java_web.tgz
 
Line: 55 to 55
 
appx/
appx/appx32.gif

Added:
>
>
appx/README.txt appx/INSTALL.txt
 appx/appx.html appx/splash.gif
Added:
>
>
appx/APPXLaunchButton.png
 appx/appx-nativelib.jar appx/appx.jar appx/appx.jnlp
Line: 75 to 78
 drwxr-xr-x 3 root root 4096 Mar 4 14:27 . drwxr-xr-x 10 root root 4096 Jun 26 2007 .. drwxrwxrwx 2 root root 4096 Mar 3 14:40 appx
Changed:
<
<
-rw-r--r-- 1 root root 1212317 Mar 4 14:27 appx.tgz
>
>
-rw-r--r-- 1 root root 1233717 Mar 4 14:27 java_web.tgz
 
Line: 88 to 91
 

Changed:
<
<
appx32.gif appx.html appx.jar appx.jnlp appx-nativelib.jar splash.gif
>
>
appx32.gif appx.html appx.jar appx.jnlp APPXLaunchButton.png appx-nativelib.jar INSTALL.txt README.txt splash.gif
 

APPX Desktop Client Web Start Bundle Components

appx32.gif

The appx32.gif file is the file used as an application runtime icon. It is referenced by the appx.jnlp file that we review later in this document.
Deleted:
<
<

appx.jar

The APPX Desktop Client in Java jar format.

appx.jpg

appx-nativelib.jar

The appx-nativelib.jar file contains platform specific files for the proper execution of the appx.jar file.
 

appx.html

The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.
appx.html contents
Line: 120 to 118
 
Deleted:
<
<
 



Line: 162 to 159
 
Added:
>
>

appx.jar

The APPX Desktop Client in Java jar format.
 

appx.jnlp

This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Now take a look at the appx.jnlp file.
appx.jnlp contents
Line: 2600 to 2599
 
Added:
>
>

APPXLaunchButton.png

APPXLaunchButton.png is an image file that is displayed for the user to click to begin the JRE detection and ultimately start the APPX Desktop Client.

appx-nativelib.jar

The appx-nativelib.jar file contains platform specific files for the proper execution of the appx.jar file.

INSTALL.txt

INSTALL.txt points the reader to README.txt

README.txt

README.txt contains the following very brief instructions to the reader.

Place these files in a directory named /appx/ off your web server's webroot.

You need to change three items, all references to www.example.com to read your site URL:

In appx.html
appx.html: ---> var url = "http://www.example.com/appx/appx.jnlp";
appx.html: ---> deployJava.launchButtonPNG = "http://www.example.com/appx/APPXLaunchButton.png";


In appx.jnlp:
appx.jnlp: ---> <jnlp spec="1.5+" codebase="http://www.example.com/appx" href="appx.jnlp" version ="5.0.0.a9"> 

Please see our Wiki at http://wiki.appx.com/wiki/bin/view/Main/LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart for further documentation. 
 

splash.gif

This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.

appx.html

Revision 422009-03-16 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 228 to 228
 
appx.jnlp modifications
You should change the following URL value in your appx.jnlp file to match your site.
Changed:
<
<
         <jnlp spec="1.5+" codebase="http://www.example.com/appx" href="appx.jnlp" version ="5.0.0.a9">
>
>
         codebase="http://www.example.com/appx" href="appx.jnlp"
 
Deleted:
<
<
 
Table of possible element / attribute available to you in a JNLP file.

Revision 412009-03-16 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 228 to 228
 
appx.jnlp modifications
You should change the following URL value in your appx.jnlp file to match your site.
Changed:
<
<

>
>
 
Changed:
<
<
>
>
 
Table of possible element / attribute available to you in a JNLP file.

Revision 402009-03-16 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 154 to 154
 
appx.html modifications
Changed:
<
<
You should change the URL values in the following two locations to match your site.
>
>
You should change the following two URL values in your appx.html file to match your site.
 
         var url = "http://www.example.com/appx/appx.jnlp";

Line: 226 to 225
 
Added:
>
>
appx.jnlp modifications
You should change the following URL value in your appx.jnlp file to match your site.
         
 
Table of possible element / attribute available to you in a JNLP file.

Revision 392009-03-16 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 153 to 153
 [joe@webserver appx]$
Changed:
<
<
>
>
appx.html modifications
You should change the URL values in the following two locations to match your site.
         var url = "http://www.example.com/appx/appx.jnlp";
         deployJava.launchButtonPNG = "http://www.example.com/appx/APPXLaunchButton.png";
 

appx.jnlp

This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Now take a look at the appx.jnlp file.

Revision 382009-03-16 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 102 to 102
 The appx-nativelib.jar file contains platform specific files for the proper execution of the appx.jar file.

appx.html

The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.
Changed:
<
<
>
>
appx.html contents
 
[joe@webserver appx]$ cat appx.html

Line: 127 to 127
 
Changed:
<
<
APPX Desktop Client Demonstration
>
>
APPX Desktop Client Web Start Demonstration

Clicking the icon below will attempt to detect if the correct Java JRE is installed, and if possible install it. If the installer determines you need an updated JRE but it can't auto install a JRE, it will place you on Sun's download page for your platform. After the JRE requirement is met, the APPX Desktop Client will be downloaded and launched.

 


Line: 139 to 141
 
Added:
>
>

Please see our Wiki for further documentation.
 

Revision 372009-03-13 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 179 to 179
  APPX Desktop Client 5.0.0.a9
<-- This is the APPX Desktop Client application icon and splash screen. -->
<-- relative to codebase -->
Changed:
<
<
>
>
 
<-- allow app to run without Internet access -->
<offline-allowed />

Revision 362009-03-13 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 162 to 162
 
<?xml version="1.0" encoding="utf-8"?>
Changed:
<
<
<-- JNLP File for APPX Desktop Client 4.2.a Application -->
>
>
<-- JNLP File for APPX Desktop Client 5.0.0.a9 -->
 
Changed:
<
<
<-- JNLP File for APPX Desktop Client 4.2.a Application -->
<-- example JNLP file that will launch the APPX Desktop Client -->
>
>
<-- JNLP File for APPX Desktop Client  -->
<-- example JNLP file that will launch the APPX Desktop Client 5.0.0.a9 -->
 
<-- where the jnlp file lives on the web -->
Changed:
<
<
>
>
 
Changed:
<
<
APPX Desktop Client 4.2.a Java Web Start Demo Application
>
>
APPX Desktop Client Java Web Start Demo Application
  APPX Software, Inc. APPX Desktop Client version 4.2.a. Connects to APPX Client Login Manager.
<-- hover help for this app.  -->
Changed:
<
<
APPX Desktop Client 4.2.a
>
>
APPX Desktop Client 5.0.0.a9
 
<-- This is the APPX Desktop Client application icon and splash screen. -->
<-- relative to codebase -->
Line: 196 to 196
 
<-- application code, load before launch. JNLP 1.6 main="true" indicates jar with main class -->
Deleted:
<
<

<-- JNI native Sun .so code -->
<-- relative to codebase -->

<-- JNI native Windows .dll code -->
<-- relative to codebase -->

<-- JNI native Linux .so code -->
<-- relative to codebase -->

<-- JNI native Mac OS X 64bit .so code -->
<-- relative to codebase -->

<-- JNI native Mac OS X 32bit .so code -->
<-- relative to codebase -->

<-- JNI native Mac OS X ppc .so code -->
<-- relative to codebase -->
 

Revision 352009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 7 to 7
 When you publish the APPX Desktop Client using Java Web Start technology you ensure the most current version of the application will be deployed, as well as the correct version of the Java Runtime Environment (JRE). Since the APPX Desktop Client will only be configured on the web server, you will not need to install the client on each desktop in your enterprise, just have the user base run the application for a published URL. This document applies to APPX Desktop Client version 4.2.a and above. These instructions do not require any APPX server configuration other than an APPX Login Manager configured to accept logins. APPX server on any platform may be connected to via the client when launched with Java Web Start. The size of the APPX Java Web Start bundle is about 1.3 MB. When the APPX Desktop Client is run for the first time, Java Web Start will download the entire package ; the next time it will check only for modified jar files (an upgrade) and download them. If this is not the case, the application will start immediately.

Required software components

APPX Desktop Client Java Web Start Bundle

Changed:
<
<
You can get the APPX Desktop Client Java Web Start Bundle from here.
>
>
You can get the APPX Desktop Client Java Web Start Bundle from here coming soon!.
 

APPX Server

You need a functioning APPX installation. Follow instructions in this document to install APPX on Windows if you don't already have APPX installed.

Revision 342009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2678 to 2678
 

Troubleshooting tips

  • To clear the Web Start Cache
    • javaws -uninstall This will remove all cached applications.
Added:
>
>
  • Clear Browser's temporary files.
 

Bugs:

  1. Fixed - Bug Description 1.
  2. OPEN - Bug test - Test bug. Not valid.

Revision 332009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2675 to 2675
 
    • Application/x-java-jnlp-file jnlp
  • Click [OK] to close the MIME Type window. Restart the IIS Admin Service.
That's all there is to publishing APPX Desktop Client utilizing Java Web Start technology.
Changed:
<
<
>
>

Troubleshooting tips

  • To clear the Web Start Cache
    • javaws -uninstall This will remove all cached applications.
 

Bugs:

  1. Fixed - Bug Description 1.
  2. OPEN - Bug test - Test bug. Not valid.

Revision 322009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2622 to 2622
 

appx.html

The appx.html file is the web document that a web browser can view. This document contains a link to a Java Web Start file (appx.jnlp). When this link is clicked, the JRE environment is installed if it doesn't exist on the client desktop, and then the APPX Desktop Client application will load. Subsequent clicks will only download updates.
Changed:
<
<

Configure your web server

>
>

Configure your web server's jnlp Mime type settings.

  Your webserver needs to support the .jnlp mime type. There are too many web servers and web server version that each configure via different actions, syntax or configuration file location that it is beyond the scope of this document to cover mime type configuration fully. However, this might be enough to get you on the right track if your server is not already configured for jnlp mime type support.
Changed:
<
<

Apache web server

>
>

Apache web server Mime type settings

 You need to add a mime type entry for jnlp. You can either use the Apache AddType directive inside the Apache httpd.conf file or the .htaccess file, or modify the Apache web server global mime.types file. The location of this mime.types file is specified by the TypesConfig Apache directive. Apache recommends that you use the AddType directive.

If you wish to modify the Apache global TypesConfig file and the file exists in /etc/mime.types, then you might try syntax like the following which will grep for the jnlp entry, and if not found will append an entry for jnlp support.

Line: 2644 to 2644
 [joe@webserver /]$
Changed:
<
<

Microsoft IIS web server

>
>

Microsoft IIS web server Mime type settings

 
Windows 2000 IIS Server
Start the IIS Management Console and perform the following steps:
  • Right-click server computer in left pane, then select Properties from the drop-down menu.

Revision 312009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2645 to 2645
 

Microsoft IIS web server

Changed:
<
<
APPX-Desktop-Client-Java-Web-Start-002.gif

Apache /etc/ files.

APPX-Desktop-Client-Java-Web-Start-003.gif

IIS .jnlp mime entry.

>
>
Windows 2000 IIS Server
Start the IIS Management Console and perform the following steps:
  • Right-click server computer in left pane, then select Properties from the drop-down menu.
  • In the 'Computer MIME Map,' click the [Edit] button.
  • The File Types window is displayed. Click New Type.
  • In the File Type box, enter the following in the Associated Extension edit box:
    • jnlp
  • In the Content Type (MIME) box, enter:
    • Application/x-java-jnlp-file jnlp
  • Click [Ok] to close the File Type box. Click [Ok] again to close the File Types Window. Click [Ok] in the Server properties window to save the changes. Restart the IIS Admin Service.
Windows Server 2003 and XP IIS Server
Start the IIS Management Console and perform the following steps:
  • Right-click server computer in left pane, then select Properties from the drop-down menu.
  • In the HTTP Headers tab, click [MIME Types].
  • The MIME Types window displays. Click [New].
  • In the MIME Type box, enter the following in the Extension edit box:
    • jnlp
  • In the MIME type box, enter:
    • Application/x-java-jnlp-file jnlp
  • Click [OK] to close the MIME Type box. Click [OK] again to close the MIME Types Window. Click [OK] in the Server properties window to save the changes. Restart the IIS Admin Service.
Windows Vista IIS Server
Start the IIS Management Console and perform the following steps:
  • Double-click the MIME Types module.
  • The MIME Types window displays. Click [Add] in the Action panel.
  • The Add MIME Type window displays. Enter the following in the File Name Extension box:
    • jnlp
  • In the MIME Type box, enter:
    • Application/x-java-jnlp-file jnlp
  • Click [OK] to close the MIME Type window. Restart the IIS Admin Service.
 That's all there is to publishing APPX Desktop Client utilizing Java Web Start technology.

Bugs:

Revision 302009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 37 to 37
 


Changed:
<
<
[joe@webserver /]$ cd /var/www/html [joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/4.2.a/java_web.tgz
>
>
[joe@webserver /]$ cd /var/www/html [joe@webserver /]$ sudo wget http://www.appx.com/ftp/appx/products/appx/client/4.2.a/java_web.tgz
 [joe@webserver html]$
Line: 47 to 47
 

Changed:
<
<
[joe@webserver html]$ sudo tar xzvpf appx.tgz
>
>
[joe@webserver html]$ sudo tar xzvpf appx.tgz
 
Line: 65 to 65
 

Changed:
<
<
[joe@webserver html]$ ls -la
>
>
[joe@webserver html]$ ls -la
 
Line: 81 to 81
 

Changed:
<
<
[joe@webserver html]$ cd appx [joe@webserver appx]$ ls
>
>
[joe@webserver html]$ cd appx [joe@webserver appx]$ ls
 
Line: 105 to 105
 

Changed:
<
<
[joe@webserver appx]$ cat appx.html
>
>
[joe@webserver appx]$ cat appx.html
 
Line: 156 to 156
 
appx.jnlp contents

Changed:
<
<
[joe@webserver appx]$ cat appx.jnlp
>
>
[joe@webserver appx]$ cat appx.jnlp
 
Line: 2632 to 2632
 

Changed:
<
<
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types
>
>
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types
 [joe@webserver /]$
Line: 2640 to 2640
 

Changed:
<
<
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess
>
>
[joe@webserver /]$ grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess
 [joe@webserver /]$

Revision 292009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2624 to 2624
 

Configure your web server

Changed:
<
<
Your webserver needs to support the .jnlp mime type. There are too many web servers and web server version that each configure via different actions, syntax or configuration file location that it is beyond the scope of this document to cover mime type configuration fully. However, this might be enough to get you on the right track is your server is not already configured for jnlp mime type support.
>
>
Your webserver needs to support the .jnlp mime type. There are too many web servers and web server version that each configure via different actions, syntax or configuration file location that it is beyond the scope of this document to cover mime type configuration fully. However, this might be enough to get you on the right track if your server is not already configured for jnlp mime type support.
 

Apache web server

Changed:
<
<
You need to add a mime type entry for jnlp. You can either use the Apache AddType directive inside the Apache httpd.conf file or the .htaccess file, or modify the Apache web server global mime.types file. The location of this mime.types file is specified by the TypesConfig Apache directive. Apache recommends that you use the AddType directive.
>
>
You need to add a mime type entry for jnlp. You can either use the Apache AddType directive inside the Apache httpd.conf file or the .htaccess file, or modify the Apache web server global mime.types file. The location of this mime.types file is specified by the TypesConfig Apache directive. Apache recommends that you use the AddType directive.
  If you wish to modify the Apache global TypesConfig file and the file exists in /etc/mime.types, then you might try syntax like the following which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
Deleted:
<
<
grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types
 
Changed:
<
<
Or, if you wish to modify an .htaccess file in your http://www.example.com/appx/ directory, and your web server is configured to allow .htaccess modificatioons then try the following syntax which will grep for the jnlp entry, and if not found will append an entry for jnlp support. grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess
>
>
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types* 
[joe@webserver /]$ 
Or, if you wish to modify an .htaccess file in your http://www.example.com/appx/ directory, and your web server is configured to allow .htaccess modifications then try the following syntax which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
 
Added:
>
>
[joe@webserver /]$ *grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess* 
[joe@webserver /]$ 
 

Microsoft IIS web server

APPX-Desktop-Client-Java-Web-Start-002.gif

Revision 282009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2626 to 2626
  Your webserver needs to support the .jnlp mime type. There are too many web servers and web server version that each configure via different actions, syntax or configuration file location that it is beyond the scope of this document to cover mime type configuration fully. However, this might be enough to get you on the right track is your server is not already configured for jnlp mime type support.

Apache web server

Changed:
<
<
You need to add a mime type entry for jnlp. You can either use the Apache AddType directive inside the Apache httpd.conf file or the .htaccess file, or modify the Apache web server global mime.types file. The location of this mime.types file is specified by the TypesConfig Apache directive. Apache recommends that you use the AddType directive.
>
>
You need to add a mime type entry for jnlp. You can either use the Apache AddType directive inside the Apache httpd.conf file or the .htaccess file, or modify the Apache web server global mime.types file. The location of this mime.types file is specified by the TypesConfig Apache directive. Apache recommends that you use the AddType directive.
 
Changed:
<
<
If you wish to modify the Apache global TypesConfig file and the file exists in /etc/mime.types, then you might try syntax like the following which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
>
>
If you wish to modify the Apache global TypesConfig file and the file exists in /etc/mime.types, then you might try syntax like the following which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
 grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types
Changed:
<
<
Or, if you wish to modify an .htaccess file in your http://www.example.com/appx/ directory, and your web server is configured to allow .htaccess modificatioons then try the following syntax which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
>
>
Or, if you wish to modify an .htaccess file in your http://www.example.com/appx/ directory, and your web server is configured to allow .htaccess modificatioons then try the following syntax which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
 grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess

Microsoft IIS web server

Revision 272009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2626 to 2626
  Your webserver needs to support the .jnlp mime type. There are too many web servers and web server version that each configure via different actions, syntax or configuration file location that it is beyond the scope of this document to cover mime type configuration fully. However, this might be enough to get you on the right track is your server is not already configured for jnlp mime type support.

Apache web server

Changed:
<
<
You need to add a mime type entry for jnlp. You can either use the Apache AddType directive inside the Apache httpd.conf file or the .htaccess file, or modify the Apache web server global mime.types file. The location of this mime.types file is specified by the TypesConfig Apache directive. Apache [[http://httpd.apache.org/docs/2.0/mod/mod_mime.html#addtype][recommends] that you use the AddType directive.
>
>
You need to add a mime type entry for jnlp. You can either use the Apache AddType directive inside the Apache httpd.conf file or the .htaccess file, or modify the Apache web server global mime.types file. The location of this mime.types file is specified by the TypesConfig Apache directive. Apache recommends that you use the AddType directive.
 
Added:
>
>
If you wish to modify the Apache global TypesConfig file and the file exists in /etc/mime.types, then you might try syntax like the following which will grep for the jnlp entry, and if not found will append an entry for jnlp support.
 grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types
Changed:
<
<
or grep -qs 'application/x-java-jnlp-file' .htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> .htaccess
>
>
Or, if you wish to modify an .htaccess file in your http://www.example.com/appx/ directory, and your web server is configured to allow .htaccess modificatioons then try the following syntax which will grep for the jnlp entry, and if not found will append an entry for jnlp support. grep -qs 'application/x-java-jnlp-file' /var/www/html/appx/.htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> /var/www/html/appx/.htaccess
 

Microsoft IIS web server

Revision 262009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 2620 to 2620
 

splash.gif

This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.

appx.html

Changed:
<
<
The appx.html file is the web document that a web browser can view. This document contains a link to a Java Web Start file (appx.jnlp). When this link is clicked, the JRE environment is installed if it doesn't exist on the client desktop, and then the APPX Desktop Client application will load. Subsequent clicks will only download updates. Modify
>
>
The appx.html file is the web document that a web browser can view. This document contains a link to a Java Web Start file (appx.jnlp). When this link is clicked, the JRE environment is installed if it doesn't exist on the client desktop, and then the APPX Desktop Client application will load. Subsequent clicks will only download updates.
 

Configure your web server

Your webserver needs to support the .jnlp mime type. There are too many web servers and web server version that each configure via different actions, syntax or configuration file location that it is beyond the scope of this document to cover mime type configuration fully. However, this might be enough to get you on the right track is your server is not already configured for jnlp mime type support.

Apache web server

Added:
>
>
You need to add a mime type entry for jnlp. You can either use the Apache AddType directive inside the Apache httpd.conf file or the .htaccess file, or modify the Apache web server global mime.types file. The location of this mime.types file is specified by the TypesConfig Apache directive. Apache [[http://httpd.apache.org/docs/2.0/mod/mod_mime.html#addtype][recommends] that you use the AddType directive.

grep -qs 'application/x-java-jnlp-file' /etc/mime.types || echo 'application/x-java-jnlp-file jnlp' >> /etc/mime.types or grep -qs 'application/x-java-jnlp-file' .htaccess || echo 'AddType application/x-java-jnlp-file jnlp' >> .htaccess

 

Microsoft IIS web server

APPX-Desktop-Client-Java-Web-Start-002.gif

Revision 252009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 94 to 94
 

APPX Desktop Client Web Start Bundle Components

appx32.gif

Changed:
<
<
The appx32.gif file is the file used as an application runtime icon. It is referenced by the appx.jnlp file that we review later in this document.
>
>
The appx32.gif file is the file used as an application runtime icon. It is referenced by the appx.jnlp file that we review later in this document.
 

appx.jar

The APPX Desktop Client in Java jar format.

appx.jpg

Line: 153 to 153
 

appx.jnlp

This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Now take a look at the appx.jnlp file.
Changed:
<
<
>
>
appx.jnlp contents
 
[joe@webserver appx]$ *cat appx.jnlp*

Line: 250 to 250
 
Added:
>
>
Table of possible element / attribute available to you in a JNLP file.
 
Elements and Attributes of a JNLP file
Line: 2616 to 2618
 

splash.gif

Changed:
<
<
This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.
>
>
This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.
 

appx.html

Changed:
<
<
The appx.html file is the web document that a web browser can view. This document contains a link to a Java Web Start file ( appx.jnlp). When this link is clicked, the JRE environment is installed if it doesn't exist on the client desktop, and then the APPX Desktop Client application will load. Subsequent clicks will only download updates. Modify
>
>
The appx.html file is the web document that a web browser can view. This document contains a link to a Java Web Start file (appx.jnlp). When this link is clicked, the JRE environment is installed if it doesn't exist on the client desktop, and then the APPX Desktop Client application will load. Subsequent clicks will only download updates. Modify
 

Configure your web server

Revision 242009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 92 to 92
 
Changed:
<
<

The appx.html file.

  • Take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file.:
>
>

APPX Desktop Client Web Start Bundle Components

appx32.gif

The appx32.gif file is the file used as an application runtime icon. It is referenced by the appx.jnlp file that we review later in this document.

appx.jar

The APPX Desktop Client in Java jar format.

appx.jpg

appx-nativelib.jar

The appx-nativelib.jar file contains platform specific files for the proper execution of the appx.jar file.

appx.html

The appx.html file exists only to provide the user with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file. Let's take a look at the appx.html file. This file is just a starter file that you can use to load the .jnlp file. There is a bit of javascript code that attempts to detect if a JRE is installed on the user's desktop for the Java Web Start launch. If the JRE needs to be installed or updated the script will either attempt to update the JRE or present the user with the appropriate link to download the software manually.
 

Line: 142 to 150
 
Changed:
<
<

The appx.jnlp file.

  • Now take a look at the appx.jnlp file. This file is an XML file that contains the information needed by Java Web Start to load the APPX Desktop Client jar file:
>
>

appx.jnlp

This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Now take a look at the appx.jnlp file.
 

Line: 2606 to 2615
 
Deleted:
<
<

APPX Desktop Client Web Start Bundle Components

appx32.gif

The appx32.gif file is the file used as an application runtime icon. It is referenced by the appx.jnlp file that we review later in this document.

appx.jar

The APPX Desktop Client in Java jar format.

appx.jpg

appx-nativelib.jar

The appx-nativelib.jar file contains platform specific files for the proper execution of the appx.jar file.

appx.html

The appx.html file exists only to provide someone with a link to click the appx.jnlp file. It is not technically needed because if someone entered the path to the jnlp file the application would launch just the same as if the jnlp file had been clicked from a link in the html file.

appx.jnlp

This is an XML file that defines the environment that the APPX Desktop Client will run it. The file is made up of elements, element values, element stanzas and comments. The file is documented with comments. Let's review a few of the key elements of the appx.jnlp file.
  • The Codebase is the location of the appx.jar file.
  • The Information section contains the data displayed to the user when the application starts, such as a splash screen image, application icon, and title bar text.
  • The Security element grants the APPX Desktop Client required permissions to run properly on the user's desktop.
  • The Resource element defines a minimum operating environment for the APPX Desktop Client. Here we've specified a JRE version of 1.6 and we can also load optional files based on the client's operating system and hardware platform.
 

splash.gif

This is the initial image displayed while the APPX Desktop Client is loading, it is referenced by name in the appx.jnlp file.

appx.html

Revision 232009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 123 to 123
 


Changed:
<
<
Click To Launch the APPX Desktop Client Demonstration
>
>
<--Click To Launch the APPX Desktop Client Demonstration-->
<-- Start of Sun's deployJava.js script that attempts to detect if Java is installed and install it or updated -->
<-- as needed for Windows, Linux and Mac.  Sun encourages you to hotlink their version of the script -->
<-- because they update it as needed.  At the moment, the Windows platform has the best support for detection -->
<-- This deployJava.js script is meant to replace the A HREF line above, so we've left it commented out -->

 

Revision 222009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 944 to 944
 

Changed:
<
<

Can be used to hint to the JNLP client that it wishes to

>
>

Can be used to hint to the JNLP client that it wishes to

 be registered with the operating system as the primary handler of
Changed:
<
<
certain extensions and a certain mime-type.

>
>
certain extensions and a certain mime-type.

 
Line: 1865 to 1865
 

href

Changed:
<
<

The URL to the additional extension jnlp file.

>
>

The URL to the additional extension jnlp file.

 

Revision 212009-03-12 - JoeOrtagus

Line: 1 to 1
 
META TOPICPARENT name="APPXAdministrator"

APPX Desktop Client Launched via Java Web Start

This document will explain how to start the APPX Desktop Client via Java Web Start Technology.
Line: 231 to 231
 

Changed:
<
<
Elements and Attributes of a JNLP file
>
>
Elements and Attributes of a JNLP file
 
Line: 270 to 270
 

Changed:
<
<

This is the main xml element for a jnlp file. Everything is contained within the jnlp element.

>
>

This is the main xml element for a jnlp file. Everything is contained within the jnlp element.

 
Line: 296 to 296
 

The spec attribute can be 1.0, 1.5.0, or 1.6.0 or can use

Changed:
<
<
the wildcards such as 1.0+. It denoted the minimum version of the JNLP Specification that this jnlp file can work with.

>
>
the wildcards such as 1.0+. It denoted the minimum version of the JNLP Specification that this jnlp file can work with.

 

Line: 322 to 322
 

The codebase attribute specifies the base location for all

Changed:
<
<
relative URLs specified in href attributes in the JNLP file.

>
>
relative URLs specified in href attributes in the JNLP file.

 

Line: 346 to 346
 

Changed:
<
<

The href specifies the URL of the JNLP file itself.

>
>

The href specifies the URL of the JNLP file itself.

 
Line: 371 to 371
 

The version of the application being launched, as well as

Ch