# Default configuration

To make the ELO installation process as easy as possible, the ELO server setup makes several settings automatically. This section provides information about the default configuration of the ELO server after installation. If you change any of these settings before installation, the installed ELO server will have a correspondingly different configuration.

# Apache Tomcats

The standard installation mode installs four instances of Apache Tomcat for the different ELO server modules and the ELO iSearch module. The default settings on each Tomcat are described below.

# General settings

Several settings apply for all Apache Tomcats installed by the ELO server setup. The following is a list of the most important settings that apply for all Tomcats:

  • Tomcat administrator
  • Name: admin (can be changed in custom installation mode)
  • Roles: admin-gui, manager-gui

# Custom settings

The different settings for each Tomcat instance are as follows:

Tomcat 1: Named ELO-<computer name>-1. Contains ELO Indexserver (including ELO Access Manager and ELO Document Manager) and ELO Forms Services. Maximum memory 2048 MB, HTTP port 9090.

Tomcat 2: Named ELO-<computer name>-2. Contains ELO Administration Console, ELO Textreader and OCR. Maximum memory 2048 MB, HTTP port 9080.

Tomcat 3: Named ELO-<computer name>-3. Contains ELO Automation Services. Maximum memory 1024 MB, HTTP port 9070.

Information

All of the information listed above for Tomcat 1-3 can be changed before you install custom installation mode.

Tomcat 4: Named ELO iSearch. Contains the ELO iSearch/Elasticsearch module. Maximum memory 4096 MB, HTTP port 9200.

Please note

ELO recommends keeping the default value for memory here. Experience has shown that assigning additional RAM here can result in various problems, while not appreciably increasing performance.

# Ports used

The Tomcat servers named above can use the following ports for communication. To check whether a port is currently in use, you can enter the following in the command line:

netstat -aon | find "<port>"

Replace <port> with the port number you are currently testing.

The ELO server setup automatically opens ports in the Windows firewall for communication with client applications. However, none of the ports named below should be used by other programs.

Information

The ports specified here are the values for a standard installation. They can vary depending on the configuration.

# Tomcat 1

  • 9090: HTTP
  • 9091: JMX
  • 9093: HTTPS/redirect (optional)
  • 9094: AJP
  • 9095: Shutdown
  • 9096: Replication (optional)

Information

Use port 9090 to connect to the ELO server from client applications with standard settings (ELO Indexserver address).

# Tomcat 2

  • 9080: HTTP
  • 9081: JMX
  • 9083: HTTPS/redirect (optional)
  • 9084: AJP
  • 9085: Shutdown
  • 9086: Replication (optional)

# Tomcat 3

  • 9070: HTTP
  • 9071: JMX
  • 9073: HTTPS/redirect (optional)
  • 9074: AJP
  • 9075: Shutdown
  • 9076: Replication (optional)

# Tomcat 4 (ELO iSearch)

  • 9200: HTTP (REST)
  • 9201: JMX
  • 9204: TCP

Please note

Port 9204 is used for communication between the ELO Indexserver and the search module in the Indexserver options. This setting is applied automatically during setup.

# Analytics

  • 9300: RMI
  • + 10: for each additional repository

# OCR workers

  • Highest assigned port +10. +2 for each additional worker.

# Example

The highest port in the system is 9200 and there are two OCR workers. Ports 9210 to 9212 are occupied by the OCR workers.

  • 9060: Recommended if installing on a separate Apache Tomcat

# ELO Connectivity Pack for SAP® ERP

  • 3300: RFC (port number increases by 1 for each instance)
  • 3600: If using the SAP Message Server (port number increases by 1 for each instance; the start port may be different)

# Standard storage locations

The following information will help you manage your ELO repository and shows you where important files related to your servers are installed.

In the following, your ELO installation directory (e. g. C:\ELOprofessional) is referred to as <ELO>.

Repository: The default storage path for repository documents is <ELO>\repository\<repository name>. The two default storage paths, basis and elosys, are created here.

Configurations: Configuration files for the ELO web applications (config.xml and logback.xml) are stored in <ELO>\config\<application name>\<server name>.

Additional important configuration files are stored in the servers directory (see below).

Java: The ELO server stores a 64-bit version of OpenJDK in this directory. All Tomcat servers installed by the ELO server setup use this version of Java.

ELO server modules: All ELO server modules (web applications/WAR files) are stored in <ELO>\prog\webapps. These files are extracted to directories on the corresponding Tomcat server at startup.

Log files: The log files for the ELO web applications and ELO iSearch are stored in the directory <ELO>\logs\<server name>\. Tomcat-specific log files (catalina.log, manager.log, etc.) are stored under <ELO>\servers\<server name>\logs.

Servers: The ELO Tomcat servers and ELO iSearch are installed by default to <ELO>\servers.

Extracted WAR files: Extracted WAR files are stored for each ELO server module in <ELO>/servers/<server name>/webapps.

Last updated: June 14, 2024 at 1:23 PM