Web Start
This section describes how to install the ELO Java Client as a Web Start for different operating systems.
Web StartInformation: If you make changes to the configuration file (EloClient.jnlp), you need to stop the Tomcat service and restart it after finishing the modifications.
Java Web Start technology enables you to start Java applications from a web browser with just a click. The required components are downloaded from the Internet as JAR files. The interaction of the required components is defined in the JNLP file. JNLP stands for Java Network Launching Protocol.
Requirements
The ELO Java Client requires Java Runtime Environment 8.0 (JRE 1.8.x) or newer.
Please note There is a 32-bit and a 64-bit version. The version you require depends on the version of the ELO Java Client you want to use (32-bit or 64-bit).
You can download the Java Runtime Environment (JRE) at the following URL:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
JNLP
The JNLP file includes the settings for the Web Start so you only need to modify the "ELOClient.jnlp" file.
Please note: The file EloClient.jnlp
is signed, which means that only placeholders designated as such may be edited.
Copy ELOclient files
1. Unzip the ZIP folder with the Web Start files.
2. Copy the ELOclient folder to a directory on your web server.
Information: You can copy the entire ELOclient folder to the webapps directory on one of the Apache Tomcat servers.
Set the start page
Start pages are provided for the two ELO product families. The files are called ELOprofessional.html and ELOenterprise.html.
1. Choose the file that matches your license.
2. Rename the file to index.html.
Information: You can modify the design of this page. Web Start only requires a link to the file EloClient.jnlp.
Entering codebase to JNLP files
The ELOClient.jnlp file is located in the ELOclient directory. The file must be adjusted.
1. Enter the URL for access to the ELOclient directory in every JNLP file as a value for codebase.
The URL has the following form:
http://[Servername]:[Port]/ELOclient
Example
The following excerpt shows the Eloclient.jnlp file. The texts in square brackets must be adjusted and replaced. Do not use the square brackets.
Entering a repository
To establish a connection to a repository, the client needs to have access to an Indexserver. The required settings are also made in the EloClient.jnlp file.
The entries to be changed are in square brackets in the following section: The square brackets disappear for the respective entry after making the changes to the file:
Please note: The placeholders must be retained in configuration areas that are not required (Repository 2, Repository 3, Kerberos). The Web Start now recognizes the non-configured areas by the content beginning with square brackets ("["). These entries may not be commented out or removed, as otherwise the file signature will no longer be recognized.
Repository profile
The name for the server connection is the same as the profile for the repository. The name is displayed during logon in the form of a repository selection and is used as the name in ELO link files.
URL to Indexserver
1. Open the JNLP file and enter the profile name and the URL of the Indexserver to the JNLP file.
Example
http://[server name]:[port]/ix-[repository name]/ix
Information: Determine the Indexserver URL with the help of the ELO Application Server Manager. Call the ELO Application Server Manager in your browser. Select the Indexserver to be used from the list of applications. You will find the associated repository name on the left.
Please note: You can also use HTTPS when the server is configured correctly.
Additional repositories
You can use additional entries in the configuration file to configure additional repositories.
Information: Only the settings are applied where the entries in square brackets have been replaced.
Example
Information: If the Indexserver is provided for the ELO Java Client in the registry, this information will be displayed in the Web Start dialog.
Start client
1. Open your browser.
2. Enter the URL that, for example, refers to the ELOclient server directory.
Example
http://ELODOKU:8080/ELOclient/
You will now see a website in the browser with the Start ELO Java Client button. Click this button to start the client.
3. Click the Start ELO Java Client button.
Java Web Start technology loads all required files into a local cache. This process is skipped when you start the client for the second time. The local cache is updated automatically when there is a new Client version on the server.
Please note: A security warning may appear when you run the program for the first time. This security warning shows the name of the provider (ELO Digital Office GmbH) and the server directory in use. You will need to confirm the security message.
Desktop shortcut
When you run the program for the first time, you will be asked if you want to create a desktop shortcut. The shortcut allows you to start the client without calling it up in the browser.
You can also add a desktop shortcut later on.
1. Open the Java configuration by clicking the Java (32-bit) entry in the Windows Control Panel.
The Java Control Panel appears.
2. Click General > Temporary Internet Files > View.
The Java Cache Viewer appears.
3. Select the ELO Java Client in the list.
4. Click the Install shortcuts (black arrow icon) button to create a shortcut on the desktop.
The shortcut to the ELO Java Client is created on the desktop.
Empty Web Start cache
On rare occasions, there may be issues with the Web Start cache. In this case, you should delete the Java cache. Make sure that the browser cache is deleted as well.
1. Open the Java configuration by clicking the Java (32-bit) entry in the Windows Control Panel.
The Java Control Panel appears.
2. Click General > Temporary Internet Files > View.
The Java Cache Viewer appears.
3. Choose the Resources entry in the Show drop-down menu.
A list of files is displayed. This includes the file ELOclient.jnlp.
4. Click the file in the list or select all entries in the list (keyboard shortcut CTRL+A).
5. Click the red cross button (Remove selected resources) to clear the cache.
The entries are deleted from the list. The cache is emptied.