Difference: LaunchingAPPXDesktopClientFromWebPageViaJavaWebstart (60 vs. 61)

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 /]$

View topic | History: r73 < r72 < r71 < r70 | More topic actions...