Technical informations to use our Java applications
The following informations try to help the configuration of end-user desktops.
Feel free to contact
to get more support on these points.
What is required to run our Java applications
Our applications require Java 1.5 at least.
They are distributed using Java Web Start
or Java Applets. Distribution is made through http protocol and should work if you can read this page.
Each Java application is signed to allow the use of these applications as normal desktop ones.
Signed applications not only allow network connection with the server that hosts the WebStart or applet
but allow any other web access, local disk access...
However signed applications imply to trust us and tell security manager to authorize the application before running.
Most of the machines already have Java enabled and well configured (this is the case of MacOSX(Tiger) ).
In the other cases, please read next sections.
How to set up Java on your machine
You need to install the Java Runtime Environment (JRE) which allows end-users to run Java applications.
Installation Instructions
| ReadMe
| ReleaseNotes
| Sun License
| Third Party Licenses
How to set up Java applet mechanism
Your browser needs to get a java plugin. This plugin is distributed in the Java Runtime Environment (JRE) package.
How to set up Java WebStart mechanism
Your browser needs to associate the jnlp file extension with the javaws program (located into your Java Runtime Environment). You will find proper information in the WebStart installation guide.
The javaws command can also be used to launch a Java WebStart application.
How to get javaws command if it is not provided by JRE
You need to get netx.jar file from http://jnlp.sourceforge.net/netx/ and build a shell command that just run :
java -jar YOURPATH/netx.jar -jnlp $*
Then you can associate this command to jnlp file into your browser or type the command in a shell.
How to set up network configurations
Most of our applications use network to take advantage of distributed services. If all does not go straight forward, this requires to have a view on some special configuration points:
- does your network require the use of a proxy ?
- on your site, are some firewalls configured to drop outgoing connections ?
If you require to use one proxy
Java WebStart provides a setup-panel to control the proxy configuration. If you use a SUN implementation of Java just call javaws (javaws -viewer or ControlPanel) command and fill the network properties of the preference panel with the information given by your network administrator.
Java 1.5 also has configuration files to manage network configuration. General configuration should be done by modifying $JAVA_HOME/jre/lib/net.properties file.
Most of applications also handle following properties:
java -Dhttp.proxyHost=<HTTP_PROXY_HOST> -Dhttp.proxyPort=<HTTP_PROXY_PORT> <your.jar>
If you suspect some firewall configurations
The best thing you should do is to contact your local administrator and ask him his point of view. For information, one of the known problems which often occurs concerns some specific applications:
- ASPRO ports that are addressed on the jmmc servers onto tcp ports are included in range 50000-52500.
- SearchCal web service is still on a non standard port : tcp/8078
- LITpro GUI uses some application core web services on the common : tcp/80