Web archive

The ELO Web Client consists of a web archive (.war) that is deployed on an Apache Tomcat Server.

The ELO Web Client must be installed individually for each repository that is managed through a separate Indexserver.

ELO Server/Tomcat

To enable parameter transfer with special characters, the /conf/server.xml file of the ELO Server/Tomcat must have the entry URIEncoding=“UTF-8“ in the Connector section.

Example

<Connector port="8080" protocol="HTTP/1.1" connectionTimeout="20000" redirectPort="8443" URIEncoding="UTF-8" />

Browser

The ELO Web Client runs as a web application in a browser. As an HTML5 application, the ELO Web Client requires a current browser. The browser must support the latest HTML5, CSS, and JavaScript standards.

Information: Configure the browser to allow cookies and so JavaScript is activated.

The document System Requirements contains information about which browsers are currently supported.

Though the ELO Web Client is generally supported by older browser versions, we recommended using the latest versions for better performance.

Information: When using Internet Explorer, icons may not be loaded correctly so the default icons are displayed instead. This phenomenon occurs for all versions of Internet Explorer.

Indexserver access

The Indexserver must be available directly for the browser (see section ELO Web Client Internet Access).

Single sign-on

The single sign-on (SSO) function is run automatically via the Indexserver. You do not need to configure this in the ELO Web Client.

Installation

The ELO Web Client is installed via the server setup. Refer to the Server manual for information on the installation.

ELO Web Client Internet Access

To work with the ELO Web Client both locally via the intranet as well as via the Internet, a specific configuration of the ELO Web Client Internet Access is necessary.

Refer to the separate developer documentation on the SupportWeb for detailed information on the configuration of the ELO Web Client.