En Elo Server 9

ELO
Document Management and Archiving Software
SERVER
June 2014
ELO Digital Office GmbH
http://www.elo.com
Copyright 2014 ELO Digital Office GmbH
All rights reserved
E090-HBSB-EN
[02.06.2014-09:52 - en - 9.0]
Table of Contents
Preface........................................................................................... 5
Welcome......................................................................................................... 7
Conventions....................................................................................................8
ELO server structure................................................................... 9

The ELO environment............................................................................... 10
Microserver architecture.......................................................................... 12
Installation preparation...........................................................17
ELO installation software......................................................................... 20
Installation checklist.................................................................................. 21
Microsoft SQL Server................................................................22

ELOprofessional 9 server......................................................... 45
Post-installation server adjustments.....................................................69
Updating ELOprofessional 9 server.......................................................72
ELOenterprise 9 Server............................................................ 90
Apache Tomcat Installation.................................................................... 97
Tomcat memory adjustment................................................................109
ELO OCR Service installation................................................................ 112
ELOenterprise server installation.........................................................117
ELO Access Manager and Document Manager................ 119

ELO Indexserver...................................................................... 137
Post-installation adjustments............................................................... 153
ELO iSearch and Search Indexer..........................................156

ELO Fulltext.............................................................................. 171
The Fulltext indexing process.............................................................. 172
Fulltext module installation..................................................................176
ELO Textreader........................................................................ 192

ELO XML Importer..................................................................203
ELO Automation Services......................................................216
Installing multiple Automation Services........................................... 226
ELO Workflow......................................................................... 230

ELO Web Client....................................................................... 241
Administration Console.........................................................252
Table of Contents
Updating ELOenterprise........................................................259
ELO Viewer............................................................................. 274
ELO Windows Client.............................................................. 277
Standard Client Installation.................................................................. 279
Automatic Client Installation................................................................286
ELO Java Client........................................................................ 291

ELO Java Client (Windows) MSI Installation.....................................292
ELO Java Client web start......................................................................298
ELO Java Client with additional components.................................. 301
Java Client registry entries.................................................................... 307
Appendix.................................................................................. 309
Additional Installation Information....................................................310
Directory Access Rights.......................................................................... 311
Parameters in config.xml.......................................................................313
Log Files......................................................................................................317
Third-Party Licenses................................................................................ 319
Further references................................................................................... 320
Index.......................................................................................... 321
Table of Contents
Preface
Important Information
This manual is intended to be used by system administrators. It

contains specific information which is intended for use by the
administrator during program installation, system administration,
and system security administration. The manual is not intended
for end users of the software. Use of the software is covered in detail in the ELO client manuals.
There are also areas in ELO where access for end users should be
restricted due to system security considerations. The main areas
where this applies are the ELO script manager, document paths,
and the system security settings. These subjects are covered in detail in the server manual, but are only briefly covered in the client
manuals. The administrator should consult both the client and the
server manuals for support.
Copyright Notices
ELO Digital Office GmbH is the copyright holder for this program,
manual, and all other relevant documentation. These products
may only be used and copied in accordance with the License
Agreements.
It is illegal to wholly or partly copy, reproduce, or distribute ELO
server software as a full version.
No part of this manual may be reproduced, transmitted, translated or otherwise duplicated without the prior written consent of
ELO Digital Office GmbH. The contents of this manual in no way
represent an entitlement on the part of the purchaser. The contents of this manual have been diligently prepared, however the
accuracy of the content cannot be guaranteed. ELO Digital Office
GmbH accepts no liability for any damages resulting from the use
of this product or documentation. The details of this product are
subject to change without notice.
Preface
Trademarks
ELOenterprise 9 Server and ELOprofessional 9 Server are registered trademarks of ELO Digital Office GmbH.
Microsoft Windows, Microsoft Word and Microsoft Excel are
registered trademarks of Microsoft Corporation. All other product names are protected by copyright and are registered trademarks/brand names of their respective owners. The use of trademarks, brand names and product names in this manual does not
imply that such names are not protected by copyright
Disclaimer
Every effort has been made to ensure that this product is as accurate as possible. However, as we are continuously developing ELO
SERVER and are undertaking development on several parallel versions, the program is subject to change without notice. In certain
circumstances minor errors or inaccuracies may, therefore, occur
in the content of this manual. We would like to apologize in advance for any inconvenience this may cause. Visit the ELO website
to find the latest versions of ELO documentation.
Preface
Welcome
ELO - the leader in
document management software
Whether documents are to be archived, searched for, forwarded

or copied, ELO offers all of these options through fast and easy to
use functions. This helps you reduce or eliminate large amounts
of paper documents in the office. However, ELO is more than just
an electronic reproduction of a filing and archive system on the
computer. The major advantages of an electronic document management and archive system lie in the additional possibilities for
storage and processing provided by the medium.
What to expect from

this guide
This document describes in detail how to install and run the standard ELO server software components and associated modules.
Both the installation of ELOenterprise and ELOprofessional are described in the following. This document also includes notes on
updating server applications that are already installed. Additional
components that require the purchase of supplemental licenses,
such as ELO DocXtractor or ELO for Sharepoint, are not included
in this guidebook. For notes on how to maintain and optimize the
server applications, please consult the other ELO documentation,
the ELO Support Forum, or the ELO Support Department.
Preface
Conventions
The manual contains numerous notes, instructions and suggestions for program dialog boxes, menu items and tips. The following conventions are followed in this documentation:
Notes
When especially important information needs to be conveyed by

the text, it is shown in a grey box with a special icon next to it. The
following types of note are used in this guide:
Information: This is a piece of additional information that can
make it easier to use ELO.
Please note: This information should be noted to ensure the program runs without problems.
Warning: This information must be noted, as otherwise program

functions may be impacted significantly.
Italics
The names of menus, options, dialog boxes, folders, references to

chapters, paths and file extensions are printed in italics.
Example: Click the ELO button > Configuration > Mail/signature
and select a keywording form.
Upper case
Keyboard shortcuts are printed in UPPER CASE. A plus sign (+) between the key descriptions means the keys should be pressed simultaneously. Keys that should be pressed in sequence are designated by a comma (,). Example: CTRL + C
Bold
Notes and titles are highlighted in bold in this guide, as well as

alternative and optional methods and the names of examples.
Courier
Program code, program input and output, and scripts are shown
in Courier font. Example: MsgBox "Hello world!"
Preface
ELO server structure
This chapter discusses the ELO server components in a general

sense and how they interact with each other. Use this chapter to
plan what components to use in ELO - particularly if you are installing ELOenterprise. This chapter also helps explain what components must be running properly in order for specific functions
to be available.
The ELO server components have been developed using Java
servlet technology. The Apache Tomcat server architecture is used
as a basis for the ELO Application Server, which works as a container for the individual ELO modules or servlets. If your server environment has very specific requirements, other servlet containers
can be used, but the config.xml file must be installed and configured manually. This file is described in more detail in the appendix.
The ELO environment

ELO server and clients
The image above shows the ELO server and clients along with the
protocols used to communicate among them. Though the image
may seem intimidating at first glance, it can be very helpful in understanding the ELO system as a whole.
ELO server fundamentals
10
The ELO system requires a webserver and a database to run at minimum. The supported database types are Microsoft SQL Server, Oracle, and IBM DB2. Most of the time, you will not need to interact with the database directly after it is installed, so these databases are described more specifically in a later chapter. For the webserver, ELO uses Apache Tomcat to manage and deliver archive
services to the clients. The four main components of the Tomcat
server engine are the ELO Indexserver, Access Manager, Document
Manager, and Fulltext module.
ELO Document Manager
The ELO Document Manager controls the documents (and their

metadata) contained in your archive. It communicates directly
with the ELO Windows Client to serve documents, the Access
Manager to provide access control, and the Indexserver to serve
documents to the other ELO clients. Each archive has its own Document Manager.
ELO Access Manager
The ELO Access Manager is the gatekeeper to all users and pieces
of information in ELO. The ELO Windows Client accesses the Access Manager directly for user authentication, but all other clients
log on via the Indexserver, which forwards such requests to the
Access Manager.
ELO Fulltext module
The ELO Fulltext module is a servlet that controls an additional

database used only for searches with ELO. Along with the ELO Textreader, it stores information contained within documents in the
ELO archives, and in combination with ELO iSearch is able to deliver information contained both in document contents and document metadata (keywording).
ELO Indexserver
The ELO Indexserver is the point of contact to the ELO server applications for most ELO clients. The ELO Administration Console,
Java Client, Web Client, ELO for Mobile Devices, and other applications log on via the Indexserver and perform requests through
the proprietary Indexserver interface. Hence if the Indexserver is
not running properly, most ELO clients will fail to function as well.
The ELO Windows Client, which is based on somewhat older technology, will not be significantly affected - only a few components
like iSearch will be disabled.
11
Microserver architecture
Architecture
Fig. Server Component Architecture
Logging on
12
The Access Manager is responsible for the central administration

of the user list, the users currently logged on, the user rights and
permissions, and the key lists. Each client and each server process
registers with the Access Manager at startup. The Access Manager
then provides a ticket which identifies the client and is required
for communication with the ELO server processes.
Fig. Client logon
Document storage
An individual Document Manager is required for each archive. The

Document Manager is responsible for saving, managing, and providing each document upon request. When using Microsoft SQL,
a separate database is created for each archive. When using Oracle SQL, an independant user with the same name as the archive
is created for each archive.
The backup service and the EMC centera interface are also run by
the Document Manager, if these additional modules have been
purchased.
13
Fig. Archiving documents
Fulltext
14
An optional Fulltext module can be installed for each archive (Document Manager). If the Fulltext module is required for more than
one archive, it must be installed once for each of the archives. The
multiple instances can be installed on a single central computer
or can be distributed between a number of computers. Each Fulltext module also requires an individual textreader instance. The
Textreader instance or instances can also be installed on a central
computer or distributed between a number of computers. In order to provide this modularity, the Fulltext and Textreader modules must be installed separately.
Fig. Full text indexing
Scalability
The ELOenterprise services are scalable. Nearly all of the services

can be installed on a single computer or they can each be installed
on dedicated individual computers.
The location of the various services can be freely defined and any
combination of the services, with a few exceptions that will be
mentioned in their specific installation chapters, can be installed
on different computers as required and depending upon the actual system requirements.
15
Fig. ELOenterprise scalability
16
Installation
preparation
Operating system information
The following installation guide is based upon the Microsoft

Windows operating system. Although there are some differences when installing to a Linux or Solaris operating system,
the installation procedure is in principle the same. Detailed information about installation on these operating systems is provided in the respective readme files: readme.linux.txt and
readme.solaris.txt.
Differences in the installation processes between operating systems are noted in these installation instructions when they occur.
System requirements
Please see the document titled System Requirements on the ELO

SupportWeb for information on the current hardware and software requirements for running ELO.
User accounts
It is recommended to run both Tomcat and the database services

under a user account with restricted privileges to increase flexibility and security. A new user is set up in the system's user manager.
In Windows Server 2012, a user can be created with the system's
Computer Management application. Navigate to Local Users and
Groups and right-click the Users folder to create a new user from
the context menu.
Installation preparation
17
Fig. Creating a new user
The New User dialog box appears. Enter a name for the service
user (for example, "EloService") and a password. Clear the checkbox for User must change password at next logon and select the
box for Password never expires. Create the new user with OK.
18
Fig. New User dialog box
If the option of User must change password at next logon is selected for a service account, you must log on with that account manually and change the account password before it can be used. If this
is not done, services associated with that account will not start.
19
ELO installation software

Place the ELO installation media into your DVD drive. If it does not
start the installer automatically, navigate to the drive in a file explorer and double-click Start.exe. This opens the installer menu
in the browser.
Use the installer menu to install the ELO server and client components. The DVD also contains a number of other documents on
using and managing the ELO programs, as well as links to the ELO
SupportWeb and other helpful websites. If you cannot find a module or document on the ELO DVD, please visit the ELO SupportWeb
or contact ELO Support.
The following chapters will guide you through the installation and
operation of the ELO server software in its most common configurations.
Please note: The ELO server must be set up in the proper order for
it to function correctly. The next few sections describe the steps
you need to take, in the order you need to take them, to insure
your installation runs smoothly. The following is a list of the general steps you need to take to set up ELO on a server:
Steps in installing ELO
to the server
Step
1
2
3
4
5
6
20
Instructions
Create your installation checklist.
Install an SQL server.
Install Java.
Notes
Only on ELOenterprise
Install Apache Tom- Only on ELOentercat.
prise
Install ELO OCR Ser- Only on ELOentervice.
prise (optional)
Install ELO server.
Installation checklist
Before you install ELO, create a checklist of information required
by the system to function. Keep this information secure and decide
on the settings before starting the installation process. You may
not need all of the information listed below for your installation use it as a general guide.
Accounts
Windows accounts: (name and password)
Database service
ELO Server Engine/Tomcat
Database accounts:
Database administrator (default: sa)
ELO database user (default: elodb)
ELO accounts:
Administrator
Service account (default: ELO Service)
Tomcat accounts:
Administrator (manager-gui)
Database
Tomcat
Script user (manager-script)
Computer name
Database type (MSSQL/Oracle/DB2)
Database port
Database storage location
Miscellaneous: instance name, authentication mode,

database name/schema, etc.
Computer name (names for ELOenterprise)
Port
Version
21
Microsoft SQL Server
A database must be running before the ELO server components

can be installed. ELOprofessional and ELOenterprise 9 support Microsoft SQL Server, IBM DB2, and Oracle database products for the
database. See the separate System Requirements documentation for more information on the supported versions of each product. The following instructions detail how to set up Microsoft SQL
Server 2012 for use with ELO.
Preparation
Microsoft SQL Server 2012 is one of the supported database types

for the ELO server. There are various versions available for purchase on the Microsoft website, along with the Express edition,
which is free to use and supports up to 10 GB per database. However, please consult with the ELO sales department and examine
the details of the various versions to determine which edition is
right for you. Microsoft SQL Server 2012 requires Internet Explorer version 7 and higher, the .NET Framework version 4.0, and Microsoft PowerShell version 2.0 for installation. Please see the Microsoft website for more details on the system requirements.
Installation prerequisites
Before installing SQL Server 2012, the Microsoft .Net Framework

4.0 must be installed and the Windows Installer must be up to
date. If an update of these components is needed, the setup routine will automatically download and install the required components. Click OK for the setup to take care of this automatically, or
click Cancel to close the installer and install the components manually.
Please ensure that your computer has enough free storage space
before starting the installation. Microsoft SQL Server 2012 requires approximately 6 GB free disk space.
22
The SQL server 2012 installation starts automatically. The first

screen you will see after double-clicking setup.exe is the SQL Server
Installation Center.
Fig. SQL Server Installation Center
23
Fig. Installation of a new SQL server
Click Installation to select the required installation type. Choose

New installation.
24
Fig. Completed check
After selecting the installation type, the Setup Support Rules

screen appears. The installer first checks whether all conditions are
met for installing SQL Server 2012. If any failures are reported, they
must be corrected before proceeding with the installation.
25
Fig. Entry of the product key
Once the support rules have been successfully fulfilled, click OK to

enter the Product Key. A valid product key needs to be entered in
the space provided before clicking Next.
26
Fig. Microsoft license terms
The next screen lists Microsoft's license terms. Accept them and
click Next.
27
Fig. Product updates
The next screen shows you whether Product Updates have been
found, which can be installed automatically with the server. If you
choose to install the updates with the server, the installer will
download the files after clicking Next. Click Next to continue.
28
Fig. SQL Server installation preparation
In the final screen of this step, the setup program prepares the
installation files along with any updates chosen in the previous screen. It continues automatically to the Setup Support Rules
screen without further user input.
29
Fig. Select the SQL Server Feature Installation
Please note: Before configuring the SQL server, it is recommended to create a separate user account in Windows for running the
SQL Server service. Instructions for doing this can be found at the
beginning of the chapter under User accounts.
The setup initially checks the system and displays the Setup Support Rules again. Click Next and continue through the Product Key
and License Terms screens to the Setup Role screen. ELOenterprise
only requires certain server features to be installed. Select SQL
Server Feature Installation and click Next.
30
Fig. Selection of SQL server features
On the Feature Selection screen, the installation paths can be modified and the specific SQL server components can be individually
selected. ELOenterprise server and ELOprofessional server requires
the installation of both the Database Engine Services and the Management Tools - Complete. The analysis and reporting services can
be additionally installed if desired. Click Next to proceed.
31
Fig. Testing the selected configuration
The Installation Rules screen indicates that the setup has checked
whether the desired features can be installed on the system. If the
tests on this screen all show Passed, the database should install
properly. Click Next to continue.
32
Fig. Instance Configuration screen
On the Instance Configuration screen, use the default values, or

enter the instance name of the SQL server, the instance ID, and the
instance root directory. Click Next to continue.
33
Fig. Disk Space Requirements
The next window shows the amount of disk space required for
installation. If the server has sufficient free disk space, click Next
to continue.
34
Fig. Configuring service accounts of the SQL server
On the Server Configuration screen, enter the account names and

passwords for the services required by the SQL server. As already
noted, it is recommended to use non-administrator accounts for
these services. On the Collation tab, you can change the collation
settings for the database. These settings control the types of data
used by the database and how they are sorted. After entering the
required information, click Next to continue.
Please note: Please keep the default SQL server setting of case
insensitive (CI) collation here. Changing the collation after the SQL
server is installed may require significant administrative effort.
35
Fig. Configuring database authentication
The following dialog is the Database Engine Configuration. The

Mixed Mode (SQL Server authentication and Windows authentication) should be selected for the Authentication Mode. It is also necessary to specify the administrator and the corresponding password for managing the SQL server.
36
Fig. Server instance data directories
You can specify the default directories for this SQL server instance
on the Data Directories tab. The directories include the Data Root
Directory, System Database Directory, User Database Directory, User
Database Log Directory, Temp DB Directory, Temp DB Log Directory, and Backup Directory. You can keep the default settings if you
wish.
Please check whether the data directories exist and are correct.
Create the correct directories as needed.
The next tab of the Database Engine Configuration is the
FILESTREAM. FILESTREAM can be enabled if needed. Consult the
Microsoft documentation for more information on this topic.
After configuring the database engine, click Next to continue.
37
If Analysis and Reporting Services were selected as features to

be installed, the next windows request you to specify their installation directories and corresponding authentication information.
Microsoft also offers an opportunity to participate in automatic
error reporting (optional). Click Next to continue.
Fig. Final requirements check
At this point, the setup checks whether all conditions for successful installation have been met. Assuming all tests show Passed,
click Next to continue.
38
Click Next to open the Ready to Install screen, which shows all
details of the SQL server to be installed. Click Install to install Microsoft SQL Server 2012.
39
Fig. Installation progress
Click Next. Use the Installation Progress page of the SQL 2012 server installation wizard to monitor the status of the SQL Server Setup.
40
Fig. Completed SQL server setup
On the Complete page, review the location of the SQL server summary upgrade log file and additional items. Click Close to finalize
the installation.
Please note: At this point the SQL server is fully installed. The following section, "Creating database user elodb", only needs to be
followed if you are installing ELOenterprise. If you are installing
ELOprofessional, you can skip the following section and continue
to the ELOprofessional installation chapter. The elodb user can be
created automatically when ELOprofessional is installed.
Creating database
user elodb
After installing Microsoft SQL Server, you must create a database

user that ELO uses to manage its archives. Start the Microsoft SQL
Server Management Studio and log on.
41
Fig. Creating database user elodb
In the Object Explorer, navigate to <database> > Security > Logins

and select New Login.
42
Fig. Login information for elodb
A window to create a new database user opens. Enter elodb

as the login name. Select SQL Server authentication and enter
the password and password confirmation from your installation
checklist. Make sure that Enforce password expiration is not selected. You may select Enforce password policy if you wish to apply the
computer's password rules to the database user.
The database user does not need to be named elodb. If you
choose a different name for the database user here, make sure the
installation of the ELO server and ELO Windows Client are adjusted accordingly.
43
Fig. Assigning the server role dbcreator
Switch to the Server Roles page and activate the server role dbcreator. Click OK to create the elodb database user.
Close the SQL Management Console to begin installing the ELO
server components.
44
ELOprofessional 9
server
ELOprofessional 9
server installation
This chapter describes how to install and update the ELOprofessional 9 server. Instructions for installing additional components
can be found on the ELO DVD or ELO SupportWeb.
Place the ELOprofessional DVD in your DVD drive. If the start program does not start automatically, navigate to the DVD and run
Start.exe.
Start.exe opens a browser menu, showing you the following
screen. Select the entry for Basic Installation:
Fig. ELOprofessional 9 DVD
From there, click the entry for Server Installer for Windows.
ELOprofessional 9 server
45
Fig. Start the 'Server Installer for Windows'
Run Setup.exe.
Fig. Installing ELOprofessional 9 server
46
After starting the server setup, a welcome dialog appears. Click

Next to proceed with the installation.
Fig. License agreement
The license agreement must be accepted before proceeding. Click

Yes to accept.
47
Fig. Installation directory
Choose the installation directory. If you need to use a different directory than the default directory, click Browse... to select another
location. Click Next to continue.
48
Fig. Port configuration
Either accept the default ports for the Application Server or enter
different ones. Click Next to continue.
You can check whether the default ports are open on your computer by entering netstat -aon | find "9090" to the Windows command line. Check ports 9091 and 9092 in the same way.
49
Fig. Enabling port 9090 in firewall
Firewall Configuration provides an opportunity to open port 9090

during setup. Click Next to proceed.
If you open port 9090 with the setup routine, the port will only be
open for the local domain. If your network does not use a domain
or has other requirements, you may need to adjust this setting in
the Windows Firewall later.
50
Fig. Authentication for server administrator
In the User Configuration window, enter the name and password

for the ELO server administrator.
This information is stored to <Tomcat installation directory>\conf\tomcat-users.xml. An additional administrative user named "adminscript" is created there automatically
during ELOprofessional installation. Note that the user names and
passwords for these Tomcat users are stored in plaintext - make
sure the directory can only be accessed by administrators.
Click Next to continue.
51
Fig. Setting recognition languages
Select the languages to be recognized by the OCR component.

52
Fig. ELO OCR service installer
The installer for the server-based OCR service starts. Click Next to
continue.
53
Fig. Select OCR service install directory
Select the directory in which you want to install the ELO OCR service. Click Next to continue.
54
Fig. OCR service - ready to install
Click Install to install the ELO OCR service. This will take a few minutes to complete.
55
Fig. OCR service installation complete
After the OCR service has successfully installed, the above screen
appears. Click Finish to continue installing ELOprofessional.
Fig. Directory for Tomcat
56
The installation routine now takes a few minutes to install files before opening a new window. Select the directory where Tomcat
will be installed, which is the basis for the ELO Application Server. The default path is recommended, but it can be changed with
Browse... if desired. Click Next to continue.
Fig. Language setting for database
Select the language for database entries. The setting chosen here
affects:
The names of default users (such as Administrator) and

groups
The names of ELO font colors
The names of ELO projects and activities
The name of the "System keys"
The names of the ELO keywording forms
Click next to continue.
57
Fig. Database type
Choose the database type already installed on the server. Click

Next to continue.
Fig. ELOprofessional serial number
Enter the serial number for the licensed copy of ELOprofessional

9 server. Click Next to continue.
58
Enter the authentication information for the database account

to be used by ELO. It is standard to use elodb for this account's
name.
Fig. Database settings - Microsoft SQL Server
It may also be useful to use an alias name for the database server
rather than the computer name of the SQL server on the network.
Alias names are managed from the domain controller and can
significantly reduce downtimes and administrative effort when
changing servers, for example.
If you are installing ELO to a database instance rather than
the main database account, enter the server name, followed
by a backslash, followed by the instance name. For example:
SQLSERVER\ELOSQL01.
If you did not create a database user for ELO previously, you can
use the setup program to do this for you now. This will create a
user automatically that has all the required rights for ELO. Click
Create database account to create the ELO database user.
59
Fig. Authentication settings for creating new database user
A dialog box opens to verify the password for the new database
user. It is also necessary to enter the authentication for the administrator account established when the SQL server was installed.
Click OK to close this dialog box, then click Next to continue.
60
Oracle
Fig. Database settings - Oracle
Enter the database settings for Oracle and the password for the
database account. Click Next to proceed.
IBM DB2
Fig. Database settings - IBM DB2
61
Enter the database settings for DB2 and the password for the
database account. Click Next to proceed.
All database types
Fig. Default or custom application settings
Next, enter a name for the new archive in the Settings Window.
Before clicking Next to continue, select whether you want to keep
the default application settings or use custom settings.
If Custom application settings was chosen in the previous dialog,
two additional dialog windows are shown.
62
Fig. Custom settings (1)
In the first, enter the paths to the data root directory, the archive,
and the search index. Next you can define the name of the ELO
service user with administrator rights. Please note the information
below regarding the "Administrator" account. Underneath you
can change the settings for the number of simultaneous database
connections for ELOam, ELOdm, and ELOix. The default number
of database connections will work in most environments, but may
provide insufficient speed if a large number of ELO users are anticipated.
As a rule of thumb, you should set the number of simultaneous
database connections for ELOam and ELOdm to 1-3% of the expected simultaneous users of ELO. Note that any number less than
3 will result in significantly reduced ELO performance. Increasing
the number of database connections will also result in increased
static RAM usage, so this setting may need to be adjusted to find
the setting that guarantees optimum performance.
63
An additional note on performance: In environments where the

ELO Windows Client is used, a connection to the ELO database is
established for each running ELO client. For all other ELO clients,
only the Indexserver connects to the database. Therefore, in environments with several hundred concurrent users, the ELO Java
Client guarantees noticeably better performance.
Fig. Custom settings (2)
The second Custom Settings window allows you define an alias

name for the ELO server if you are working within a domain. Using an alias reduces administrative effort when changing servers
later. The default entry is the local computer name. You can also
adjust the maximum file sizes for the Fulltext and Textreader components. Note that the files in the archive may take up significantly more space in server RAM when they are opened for analysis.
However, these settings can also be changed later, so it is usually
a good idea to keep the default settings here and change them
later if they cause problems.
64
The words used when the Textreader is unable to interpret a file

may also be changed here. It is also possible to choose whether
the XML import should delete files after importing their contents
into the archive and whether the import should be initiated by a
signal file.
Fig. Web Client installation
You may install the ELO Web Client along with ELOprofessional if
you wish. Depending on your license, the type of Web Client installed may be limited to access via mobile devices, or it may support ELO access via any modern browser. However, installing the
ELO Web Client means the server will require more memory to run.
See the ELO Web Client manual for more information.
65
Fig. Password for ELO administrator
Next, enter a password for the ELO administrator.

A note on the Administrator account: Some care needs to be
taken when entering administrator information here. Though the
window requests the logon credentials for the ELO administrator,
the same password will be used automatically to create the ELO
Service user. It is quite easy to change the password for the administrator, but changing the password for ELO Service also requires
data in several ELO module configuration files to be changed as
well. Therefore, please enter the password for the ELO Service
user here, then change the administrator password after installation is complete.
66
When Input Complete appears, click Next to start installing ELOprofessional.
Fig. Installation finished
67
A status window appears. When the status message Installation

finished appears, ELOprofessional 9 server has been installed. Click
Finish to open the final installation note.
The final window of the installation routine notifies you that the
service user was created and that the iSearch search indexer will
only start to run after 24 hours have passed. This delay allows you
to perform additional administrative tasks before this automated
task starts working. If you need the indexer to start immediately,
please see the chapter below on installing ELO iSearch to see how
to manually re-index the iSearch database.
You can now install and configure additional ELO components as
needed.
68
Post-installation server adjustments

Enable Create external
link
A new function called Create external link was added to the ELO
Java Client in ELOprofessional 9. This function shares documents
within an ELO archive with persons who do not have an ELO user
account. When the ELOprofessional server is first installed, however, these "external" links only work with computers that are located within the same network or domain as the ELO server. In order to share ELO documents via this function with all computers
with an Internet connection, proceed as follows.
1. Assign a fixed IP address to the computer on which the ELOprofessional server is running. Depending on your network settings,
you may need to change various settings on your network controller and/or firewall to make sure the ELO server can be reached
by the Internet.
2. Open the ELOprofessional Application Server Manager and click
the entry for the Indexserver to open its status page:
Fig. ELO Application Server status page
3. Click the entry for the Indexserver to open its status page. The
entry is highlighted in red in the image above.
69
4. The Indexserver status page opens in a new tab. Click Configure

Options at the top of the window, then re-enter the user name
and password for the ELO server administrator. The status page
changes to the following:
Fig. ixUrlBase in the Indexserver options
5. The ELOprofessional setup program normally sets the ixUrlBase option for the Indexserver to the following format: http://
<computer name>:<server port>/ix-<archive name>/
ix. Replace the computer name with the fixed IP assigned to the
ELO server. Click Save, then Reload to save the change and then
apply it to the server.
70
If ixUrlBase has not been set for your Indexserver, you can add it
to the list via the drop-down menu in the last line of the table. Enter the value as described above, then click Add to add the option
to the list. Click Save and Reload afterwards to apply the setting.
Fig. Sample ixUrlBase entry
Document links created by Create external link will now direct

users to the correct document.
Exposing a computer to the Internet requires elevated security settings to protect your network from intrusions. Please ensure the
required security measures are in effect before enabling the Create external link feature.
The value for ixUrlBase can also be changed to a website if your
network rules have been correctly set to redirect requests to the
Indexserver and/or port. For example:
Fig. Website redirect to IX ixUrlBase
Fig. Resulting sample link to document
71
Updating ELOprofessional 9 server

ELO provides updates to ELOprofessional server applications on a
regular basis. There are several ways to apply these updates:
Use the newest release DVD of ELOprofessional. This updates Java, Tomcat, and the ELOprofessional server all at
the same time.
Download and run the newest server setup update from

the ELO SupportWeb. New server setups are published
more frequently than DVD releases.
Update individual ELO server applications manually. This

is more complicated than the other options, but it ensures that you have the most current version of the application.
All of these update options are described in the following.

Update from DVD or
Server Setup
The easiest way to update the ELOprofessional server files is to run

the server setup program. This can also be used to update from
ELOprofessional 2011 to ELOprofessional 9.
When you perform an update in this way, the ELO server will be
stopped for a short time. Make sure that no users are using the
archive at this time.
1. Back up your existing copy of ELOprofessional. It is easiest to
back up the entire ELOprofessional install directory (such as C:
\ELOprofessional) and all child directories. Also back up the databases for the Access Manager and all archives.
Update from DVD
2. Place the ELOprofessional DVD in the ELO server's DVD drive and
run Start.exe.
3. Navigate to the Basic Installation tab and click Server Installer
for Windows. If the server is running a 32-bit version of Windows,
open a command window and enter the following command:
<drive letter>\Start\Server\Basis\Install\Server_Windows
\setup.exe -X86
72
Update from Server

Setup
3. Download the newest version of the ELOprofessional Server Setup files from the ELO SupportWeb. Extract the ZIP file to the following directory:
<ELOprofessional>/prog/serversetup/
Navigate to the serversetup directory and run setup.exe.
4. The ELOprofessional Server Setup program starts. Click Next to

continue.
73
5. Read through the license agreement and click Yes to confirm.
74
6. Select the directory in which you installed the ELOprofessional.

7. A confirmation dialog box appears if you select the correct directory. This confirmation notifies you that the installer has found
an existing ELO installation and asks to overwrite the existing files
there. Click Yes to confirm.
75
8. The installer asks which languages should be detected by the

OCR process. German, English, and French are selected by default.
Select the languages you want and click Next to continue. You can
change this setting later by editing the OCR configuration file.
76
9. The installation program takes a few minutes to update the

ELO Application Server and Java, then copies the files for the ELO
applications to a local directory. Afterwards, the installer for the
ELO OCR service starts. Installing the ELO OCR service enables server-side OCR for the Web Client, Webstart Java Client, and so on.
77
10. Select an installation directory for the OCR service and click
Next.
78
11. Click Install to install the OCR service. After it completes, the
ELO server update continues.
12. Select the ELO Application Server directory, then click Next to
continue.
79
13. A selection screen appears with Update all applications selected by default. Click Next to continue.
14. An update notice appears. If you have proceeded with the update according to the instructions here, you do not need to perform any additional steps. Click Next to continue.
80
15. Select the language for database entries. This must be the
same language used when the server was first installed. The correct entry should be selected by default. Click Next to continue.
16. Select the type of database already in use by ELO. The correct
entry should be selected by default. Click Next to continue.
81
17. A summary page appears, notifying you of the applications

that the update program has recognized and is able to update. If
not all of your applications are detected, you may need to update
them manually. Click Next to continue.
82
18. A dialog box appears in which you can update the ELOprofessional serial number. If you are upgrading to a new full version of
ELO (such as from ELOprofessional 2011 to 9), it is necessary to
update the serial number. Click Next to continue.
19. The update program gives you the ability to install some new
programs if they are not installed already. Click Next to continue.
If you are not installing any additional applications, you can skip
to step 23 now.
83
20. Enter the search index directory for ELOis, followed by the ELO
server name. An alias can be used for the server name. Click Next
to continue.
21. Enter the user name and password for an existing ELO user. It is
recommended to use the ELO service user. Click Next to continue.
84
22. Enter the data directory used by ELOprofessional. Click Next to

continue.
23. The Input Complete screen appears. You can go back and
change your input for steps 12-22 by clicking Back now. Click Next
to install the updates.
85
24. The update is performed and shows the progress of the update
as it occurs. If any errors occur, attempt to correct them and then
run the update program again. Click Next to continue.
If errors occur and you need to repeat the update, you do not need
to run it from the DVD. You can run it from the serversetup directory (see following section), which skips the Java and ELO Application Server update.
86
25. Any final notes regarding the installation are shown on this
screen. Read through these notes to see if any additional steps are
required. Click Finish to close the ELOprofessional Server Setup.
Manual application
update
There are several ways to update ELOprofessional server applications. In ELOprofessional 2011 and earlier, the applications
were extracted to separate directories, complicating the update
process. Starting with ELOprofessional 9, the WAR files that contain the ELO applications are loaded dynamically to Tomcat at runtime. To update ELOprofessional 9 server applications, proceed as
follows:
The ELO Application Server does not need to be stopped to perform an update in this way. However, increased server RAM will
be required until the ELO server is restarted. It is recommended to
perform a server restart after performing an ELO application update as soon as it is convenient to do so.
1. Download the new ELO application from the ELO SupportWeb.
See the included documentation for any dependencies between
the application and other ELO server applications or client programs. Also check whether the configuration files for the application need to be changed.
2. Navigate to the directory:
87
<ELOprofessional>/prog/webapps/
Check to see that the application you want to update already exists in this directory. Each ELO application uses a special abbreviation (such as dm.war for the ELO Document Manager, ix.war for
the Indexserver, and so on.
If the updated application is not located in this directory, use the
update method following this one titled Manual update with
transfer directory.
3. Extract the updated ELO application to your hard drive and rename it (if necessary) so it has the same name as the old ELO application.
4. Copy the updated ELO server application to the prog/webapps
directory so that it overwrites the old application.
5. Tomcat will automatically load the updated application to
memory. Check the status page of the updated application in your
browser in the ELOprofessional Server Manager. If the application
has a status of Running and no errors are displayed, the application has updated successfully.
Manual update with
transfer directory
If you are running ELOprofessional 2011 or your server application

is not stored in the prog/webapps directory, use the following
method to update your ELO server applications:
1. Create a directory on the server where the updated application
files will be stored. This is called the transfer directory.
2. Copy the servlet configuration file from the server into the transfer directory. This configuration file is located in <ELO server installation directory>\server\conf\Catalina\localhost. It is an .XML
file with the same name as the web application, such as trArchive1.xml.
3. Copy the new web application (a .WAR file) into the transfer
directory, then give it the same name (without extension) as the
configuration file, such as tr-Archive1.war.
4. Open the ELO Server Manager and locate the application you
want to update, then click Undeploy:
88
This deletes the old version of the application and configuration

file, though the data associated with it (such as the archive, iSearch
database and so on) is retained.
5. At the bottom of the ELO Server Manager, enter the information
for the updated application:
Context Path: The name of the old application with a forward
slash in front, such as /tr-Archive1.
XML Configuration file URL: The UNC path to the XML file in the
transfer directory, such as C:\transfer\tr-Archive1.xml.
WAR or Directory URL: The same directory as the path above, but
with .war instead of .xml. For example: C:\transfer\tr-Archive1.war.
6. Click Deploy. You will normally not have to restart ELO or Tomcat. You can delete the files in the transfer directory now if you
wish.
89
ELOenterprise 9 Server
General note
The following chapters provide installation notes for ELOenterprise. If you installed ELOprofessional in the previous chapter, you
can skip the following chapters, since the ELOprofessional setup
program installs Java, Tomcat, and the ELO server components automatically.
Java installation
If the required JRE or JDK is already installed on the system, you do

not need to install it again. To check whether the correct version
of Java is installed, open the command line and enter:
java -version
The currently installed Java type and version will be displayed. The
JRE is sufficient for running ELOenterprise. The JDK does not need
to be installed unless it is required by other applications.
Consult the current system requirements document on the ELO
SupportWeb to see the version of Java required for your version of
ELO. If either Java is not yet installed or a newer version is required,
the ELO DVD contains a JRE installer compatible with current versions of the software. The JRE/JDK can also be downloaded from
Oracle's Java website at http://www.java.com.
The Java installation

program
90
This section details how to install the Java Runtime Environment

for ELO. When you run the Java installer, you first have the option
to use the default installation folder or to change it if you wish.
ELO recommends using the default installation directory.
Fig. Java installation start screen
Click Install to proceed. The Java installation will now begin.

After the installation has completed successfully, the dialog box
changes to the following figure. Click Close to complete the installation.
91
Fig. Java installation complete
Depending on your operating system, a message box may appear,

informing you that you need to restart the computer. After restarting, set the JAVA_HOME environment variable.
The JAVA_HOME Variable
92
The JAVA_HOME variable must be set for ELO to recognize where

Java has been installed. On most versions of Windows, click the
Windows button > Control Panel > System. If your Control Panel is
grouped by category, open the Control Panel > System and Security
> System. Click the Advanced system settings.
Fig. Opening advanced system settings
Go to the Advanced tab and click Environment Variables.
93
Fig. Opening "Environment Variables" in the system settings
The JAVA_HOME variable can be added to either the user or

system variables. However, since you will likely not be running
ELO under an administrator account, add JAVA_HOME to the system variables to make it available to all users. Click New, enter
JAVA_HOME as the variable name, and enter the full path to the
folder in which you installed Java. If you did not change the install
folder during installation, this is C:\Program Files\Java\jre7. Confirm your entries by clicking OK.
94
Fig. Adding JAVA_HOME as an environment variable
As described at the beginning of this section, the success of the

Java installation can now be tested by entering java -version
to the command line. If the correct version number is displayed,
the installation was successful.
Linux
If a sufficiently modern version of Java is not installed on the

server, download and install a version that fulfills the system requirements. Make sure that the JAVA_HOME environment variable points to the correct version if you do this.
95
Solaris
If Java is already installed, it can normally be found in the /usr

directory. An environment variable named java also exists and
points to the installed version. Check the installed version of Java
by entering java -version to the console. Download and install
a new version of Java if required, and afterwards make sure the
java variable has updated.
If you are installing ELO to Linux or Solaris, consult the Readme
files in their respective installation packages before starting the
installation.
96
Apache Tomcat Installation

Tomcat can be installed from the ELOenterprise installation DVD,
or you can download the installation file from the Apache homepage at http://tomcat.apache.org.
Windows
Before installing Tomcat, it is important to first check whether

Tomcat is already installed on the system and, if so, whether it is
a supported version.
Tomcat ports
Tomcat requires three unused ports on the server to function

properly. Make sure they are not in use before installing Tomcat.
Port 8080 is the standard port used by Tomcat for communication, and port 8005 is used as the shutdown port. Port 8009 is the
AJP/1.3 connector port. To check whether these ports are available, open the command line and enter netstat -n.
Fig. Displaying ports in use
97
netstat -n returns a list of all ports that are currently in use by

the computer. Note that some programs may not show up in this
list because they use the port only occasionally. Now enter telnet localhost 8080 to make sure the computer does not already accept connections on this port.
Fig. Tomcat ports free for use
Oracle 9 and later uses port 8080 for XML access. This can be
changed in the Oracle Enterprise Manager Console.
Starting the Tomcat
Installation
The following instructions for installing Tomcat are based on the

version from the ELO DVD. However, the steps should not be significantly different if you have downloaded Tomcat from the Internet.
If you have downloaded Tomcat from the Internet, it is recommended to install a version designated as stable. Alpha or beta
versions of Tomcat are not guaranteed to run properly with ELO.
Start installation by clicking the link to Apache Tomcat in the
browser.
98
Fig. Tomcat installation start screen
Click Next to continue to the License Agreement.
99
Fig. License agreement
You must accept the terms and conditions in the License Agreement by clicking I Agree to continue. You can now select the components you want to install.
The Service Startup and Manager components are required and
must be selected. Clear the option for Native operation. If you are
installing for a productive system, clear the option for Examples as
well to ensure secure and stable operation. The other components
are optional. The selection of non-default components automatically switches the installation type to Custom.
100
Fig. Choosing Tomcat components
Selecting the Service components installs Tomcat as a service and

not as an application. This is the recommended method.
Once the appropriate components have been selected, click Next
to enter the Tomcat configuration options.
101
Fig. Configuring port and login options
The server shutdown port is used to shut down the ELO Application Server remotely. Its default value is 8005. If you observe that
your ELO server does not appear to start normally, double-check
to see that the server shutdown port is not in use by another application.
The HTTP/1.1 connector port is the port used to connect to the
ELO Application Server applications. The default value for the port
is 8080, but this can be changed as needed.
The AJP/1.3 connector port is primarily relevant to environments
where the Tomcat Java web applications are integrated into a web
interface that also contains static content. It is not used by ELO
and therefore does not necessarily need to be free for ELO to work
properly. Consult the Apache Tomcat documentation for more information on this feature.
Any name can be chosen as the Windows service name. It can be
seen in Windows Services by clicking the start menu in Windows
and entering services.msc. Use a name like ELOenterprise here to
more easily distinguish it from other running services.
102
At the bottom, enter a user name and password for the administrator and make sure that this information is also on your installation checklist. After entering this data, click Next to continue to
the Java Virtual Machine window.
The Tomcat users and passwords are stored in plaintext in <Tomcat install directory>\conf\tomcat-users.xml. This
is useful if you lose the paper copy of this information and need to
regain access to the Tomcat Manager interface, but it also increases your security requirements. Make sure that the directory is not
shared on the network, and especially that it cannot be reached
on the Internet.
Fig. Path to Java Virtual Machine
Enter the path to your locally installed Java Runtime Environment.

If the JRE was installed to the standard path, the default entry is
correct here as well. If you installed Java to another directory, enter
it here. Click Next to select the Install Location for Tomcat. Keep the
default directory or enter an alternative location.
103
Fig. Tomcat installation directory
Please note: The increased attention paid to security in newer versions of Windows (after XP) complicates the administration of ELO
and Tomcat if they are installed to the Program Files directory. For
this reason, we recommend installing Tomcat outside of the default Program Files directory.
After entering all necessary information, start installing Tomcat by
clicking Install.
104
Fig. Installation progress
After installation has completed, ensure Run Apache Tomcat is selected in the final dialog box before clicking Finish.
105
Fig. Completed Tomcat installation
Once Tomcat has started, its icon should appear in the notification
area of the taskbar. A green arrow indicates that the service is running. If the icon is red, this means that the service is not running.
If the icon remains red, right-click the icon and select Start service
from the context menu.
Fig. Tomcat taskbar indicator: service stopped (left), service started (right)
After the Installation
Once installed and running, Tomcat can now be tested by opening

the Tomcat Manager in the browser. Enter the following address
to a web browser:
http://localhost:8080/
(Adjust the port number at the end if you selected a different HTTP
port during installation.)
If Tomcat is running, you will see the following image:
106
Fig. Tomcat start page in the browser
After successfully installing Tomcat, it will use the local system account by default. This is not optimal for security purposes. Rightclick the Tomcat icon on the desktop and select Configure..., then
go to the Log On tab. Enter the logon details for a non-administrator user (ideally created specifically for Tomcat) to This account.
Tomcat - Linux installation
Tomcat is automatically installed with some distributions of Linux.

If this is not the case, Tomcat for Linux can be installed from binaries downloaded from the Apache homepage. There are several
methods for installing Tomcat. If a tar.gz file is used, follow the
instructions in the provided readme files. The following instructions were tested with SUSE Linux.
Extract the binaries with gtar into the desired folder, such as /opt.
There are two methods of starting and stopping Tomcat in Linux.
As a daemon with the root user:
The commands tomcat start and tomcat stop can be executed by the root user. Check whether the Tomcat script is located in the /etc/init.d folder. This is not the case with every version of Linux. If it is not present, the start script must be manually
changed to the corresponding directory. A new start script can also be created by hand.
107
As user tomcat:
Enter the command su tomcat and navigate to the bin folder
in the terminal. Run startup.sh or shutdown.sh.
When starting Tomcat as a daemon, you can set start error messages to be written to the log file. In SUSE Linux, the log file is
found at:
/usr/share/tomcat/logs
The installation log file produced by Tomcat can also be found in
the /logs folder.
To test whether the installation has been successful, open a web
browser and enter the following to the address bar:
http://localhost:8080/
If Tomcat was installed correctly, you will see the Tomcat start
screen.
Please note: in order to start the Tomcat Manager with Tomcat
7.0 or later, a user with the role manager-gui must be present in
<Tomcat install directory>\conf\tomcat-users.xml.
This user is created automatically when Tomcat is installed in Windows, but you may need to create it manually in Linux. Use the
following syntax to create the user:
<user
username="admin"
roles="manager-gui"/>
Solaris
108
password="password"
The first step is to check whether a version of Tomcat has already

been installed and enabled. Solaris 9 includes an older version of
Tomcat with the Apache package, but it is not enabled by default.
When using an older Tomcat version, it can be started with the
start script located at /etc/init.d/apache. However, it is recommended to install a newer version of Tomcat.
Tomcat memory adjustment

The amount of system memory allocated to Tomcat after installation is insufficient to run an ELO archive. Before installing the ELO
server installations, the amount of RAM allocated to Tomcat must
be adjusted as follows.
The memory settings listed here will work for many ELO environments, but are not optimal for all. If you are just running a few ELO
applications per server, you may reduce the amount of RAM given
to Tomcat accordingly. Similarly, if you are running multiple ELO
archives on the same server or have a large number of ELO users,
you may need to increase the amounts above those listed here.
A definite indication of insufficient memory assigned to Tomcat is
the appearance of errors in the Apache log file stdout.log that
look like: java.lang.OutOfMemoryError: PermGen space
The two most important memory settings for Tomcat are Maximum memory pool and MaxPermSize. You must increase these
amounts from the default values to the following:
Maximum memory pool = 1000 MB
MaxPermSize = 350 MB
If you continue to see PermGen errors in your log files, you can increase the values further. For optimal performance, MaxPermSize
should be about one-third of the Maximum memory pool.
Windows
There are two ways to adjust these values in Windows: via the
Tomcat server properties and via the registry.
To open the Tomcat properties, right-click the Tomcat tray icon
and select Configure or run Configure Tomcat from the start menu.
The Apache Tomcat Properties window opens. Navigate to the Java tab.
109
Fig. Corrected memory settings for Tomcat
In the Java Options field, enter the following line at the end of the
options:
-XX:MaxPermSize=350m
Then enter a value of 1000 to the Maximum memory pool field.

These settings can also be changed in the registry. This makes it
possible to, for example, use scripts to speed up server deployment. The memory settings are stored under:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software
Foundation\Procrun 2.0\<Tomcat service name>\Parameters\Java
If you are running a 32-bit server, leave out the Wow6432Node portion of the path.
110
The setting for the Maximum memory pool is stored in hexidecimal format to the JvmMx parameter.
The MaxPermSize is stored as a multi-string value to the Options
parameter.
Linux and Solaris
In Linux and Solaris operating systems, change the memory settings for Tomcat by modifying the CATALINA_OPTS system variable. To modify this variable in SUSE Linux Enterprise Server
11, add a line like the following to the tomcat7 file in /etc/
sysconfig:
CATALINA_OPTS="-Xms1000m -Xmx1000m -XX:MaxPermSize=350m"
Tomcat must be restarted to apply any new or changed memory

settings.
111
ELO OCR Service installation

The ELO OCR Service is an optional component used to perform
server-side OCR on image documents (such as scanned documents). The ELO OCR Service can only be installed to a computer
running the Windows operating system. You can also install the
ELO OCR Service after installing the ELO server.
If you are updating your version of ELOenterprise from a previous
version, you must deactivate or uninstall the earlier version of the
OCR service, which uses a different architecture.
To install the ELO OCR Service, proceed as follows:
1. Run start.exe on the ELOenterprise DVD. The ELOenterprise installer menu opens in your browser.
2. Navigate to the ELO OCR and ELO Barcode tab on the left.
3. Run ELO OCR Service for ELO Server and ELO Java Client.
112
4. The ELO OCR Service installer starts. Click Next to continue.
113
5. Choose a location where the OCR service will be installed. Click

Next to continue.
114
6. Click Install to install the ELO OCR Service.
115
7. Click Finish to close the installer. See the ELO OCR Service documentation for additional information on using the ELO OCR Service and any additional settings you may need to enter.
116
ELOenterprise server installation

To start the ELOenterprise server installation, navigate to the ELO
DVD menu and select Basic Installation in the upper left. This
opens the menu to install the ELO server components. Choose between Server Installer for Windows (for Windows-based servers)
and Server Installer for Linux and Solaris (all other server operating
systems).
The ELOenterprise serial number is required during setup and
should be available before the installation process is started.
Windows
Click Server Installer for Windows from the DVD menu to open the
following installer:
Fig. Server installer setup
117
Select a local directory to save the installation files. The extractor

can create the directory if it does not already exist. Select Start the
server installation at the end to run the ELOenterprise server setup
immediately afterwards.
Click Start extracting to begin.
If the option to automatically start the server installer is not selected, or if you need to run the installer multiple times, go to the
directory selected above, then navigate to the subfolder /prog/
serversetup. Run setup.exe. The program must be given administrator privileges to install correctly.
Linux and Solaris
In Linux and Solaris, start the installation by running the script

setup.sh in the console.
Installation
After copying the server setup files to the computer and starting
the ELOenterprise Server Setup program, the following screen appears. Select Install a new application, then click Next.
When you are installing ELOenterprise for the first time, you must
install the Access Manager and Document Manager before installing other ELO applications. The following chapter describes
how to do this. Subsequent chapters describe how to install additional ELO server components.
118
ELO Access Manager

and Document
Manager
Installation
Before installing the Document Manager and Access Manager,

stop the Tomcat service.
If you have just run the ELOenterprise server setup extractor, the
following screen opens automatically. Otherwise, run setup.exe
(setup.sh in Linux or Solaris environments). These files are located
in the /prog/serversetup/ directory.
ELO Access Manager and Document Manager
119
Fig. Select installation type
Select Install a new application and click Next.
Fig. Application selection
120
On the next screen, select Access Manager and Document Manager. The components can be installed separately (they are the next
two items in the list, respectively), but it is easier to install them at
the same time.
Note: A separate Document Manager must be installed for each
archive.
Fig. Language selection
Next, select the language for database entries. The language

selected here affects the default font color names, keywording
forms, names of projects and activities, system keys, and the default users and groups in ELO. It does not affect the languages in
the ELO client interface.
121
Fig. Database Type
Now select the database type in use. ELOenterprise supports Microsoft SQL Server, Oracle, and DB2 databases. The database must
already be installed when the ELOenterprise setup is run, but it
does not need to be installed to the same computer as the ELO
server.
122
Fig. Tomcat directory
Now enter the location on the computer where Tomcat was installed. If the default value is not correct, click Browse... to navigate
to the Tomcat directory.
Fig. Tomcat log directory
123
Next, enter the location where ELO will store its log files. The default location is a subdirectory of Tomcat and can generally be accepted.
Fig. Directory settings
On the next screen, enter the ELOam data directory and the
ELOdm archive directory.
ELOam data directory: This is the directory for Access Manager
data. A variety of configuration data is stored here.
ELOdm archive directory: This is where the physical documents
in the archive are stored. Make sure that sufficient disk space is
available there and that the directory is backed up regularly.
When installing on a Windows system, UNC paths can be used. If
you are working with UNC paths, please ensure that the Tomcat
service user has access to the directories. Neither of the directories
specified here should be used to store other documents.
124
Fig. General settings - Microsoft SQL Server
Next, enter the database settings. The options provided here depend on the type of database in use.
Microsoft SQL values
Database server name: Name or IP address for the database server on the network. This can also be the local computer. If multiple
instances of Microsoft SQL Server are in use, place a backslash (\)
after the server name, followed by the instance name.
Port: The database port. 1433 is the default value for the Microsoft
SQL server and this does not need to be changed in most cases.
Existing database account: An existing account, (e.g. elodb) with
the right to create databases. This account is used by the setup
program, Access Manager and the Document Manager. The standard account name is elodb.
Password: Password for the database account.
New Database for ELOam: The database name for the Access
Manager could be eloam. Alternative names should only be used
when an access manager already exists on the current SQL server,
such as in multi-client operation or for development and testing
environments.
125
New database for ELOdm (archive name): The Document Manager database name and the name of the archive. The default
name is elo, but it is recommended to change this to a name that
informs the users of the archive in use (in this example the name is
Archive01). The name cannot contain spaces, non-alphanumeric
characters, or accents.
Oracle values
The following values are required in the General Settings when using an Oracle database.
Fig. General settings - Oracle
Database server name: Name or IP address for the database server in the network. This can also be the local computer.
Database name (SID): Name of the existing database instance.
The Oracle SID (system identifier) should be entered here and
not the global database name. An entry in the Oracle file
tnsnames.ora is not required. This name can be freely assigned
and is not restricted.
Port: Port for the database. The value in the text field is the standard value from Oracle for databases. Check whether this entry is
correct and change it as needed.
126
Existing database account (with role DBA): This account must

already exist and is used by the setup program to administer the
accounts with the appropriate tables. The separate document
ELO_Oracle.pdf should be consulted when setting up this user.
The document is supplied with the installation DVD and explains
the various rights that the user requires.
New database account for ELOam: The database name for the
Access Manager should be eloam. Alternative names should only
be used when an Access Manager already exists on the current
SQL server, such as in multi-client operation or in development and
test environments.
New database account for ELOdm (archive name): The database for the document manager will be named after this value,
which will be the archive name. The standard value elo can be
altered as required. The name should consist only of alphanumeric characters. Special characters should not be used in the archive
name.
Passwords for these accounts: The passwords must be the same
because the passwords of the ELOdm account should be identical
to the password of the account to be used by the ELO client.
After clicking Next, the Access Manager name is checked against
existing databases. If the name already exists, an error message
will be displayed and a new name must be entered. Use unique
and easily identifiable names for the databases and the archives.
IBM DB2 values
The following values are required in the General Settings when using IBM DB2.
127
Fig. DB2 database settings
Database name: Name of the existing database instance. The DB2
should be entered here and not the global database name.
Port: Database port. The value in the text field is the standard value from DB2 for databases. Check whether this entry is correct and
change it if needed.
Existing database account: This account must already exist and
is used by the setup program to administer the accounts with the
appropriate tables.
New schema for ELOam: The database name for the Access Manager should be eloam. Alternative names should only be used
when an Access Manager already exists on the current server (for
example multi-client operation or development and test environments).
New schema for ELOdm (archive name): This is the account
which should be created for ELOdm.
All database types
128
Now enter the number of database connections for the modules.

Fig. Database connections
Number of database connections for ELOam and Number of

database connections for ELOdm: The numbers entered here determine the number of database connections permanently used
in the connection pool by the Access Manager and Document
Manager respectively.
The server establishes multiple connections to the databases in order to ensure optimal multithreaded performance with the SQL
server. As a general guide for the number of connections, approximately 1 to 3% of the number of expected parallel users should
be used. A value of less than 3 is not recommended.
The number of connections should not exceed the maximum
number of connections available from the SQL server.
129
Oracle
Database setup: This screen only shows up when installing

ELOenterprise for Oracle environments. Enter names for the tablespace and index tablespace for both the Access Manager and Document Manager. The default values can usually be kept. Click Next
to continue.
130
All database types
Fig. Enter serial number
In the following window, enter the serial number, the Access Manager server name and the Access Manager Tomcat port.
The serial number must be a valid ELOenterprise number. ELOprofessional serial numbers cannot be used.
The password for the ELO administrator must be entered next. This
is the password used by the administrator when logging on to
ELO.
A note on the Administrator account: Some care needs to be
taken when entering administrator information here. Though the
window requests the logon credentials for the ELO administrator,
the same password will be used automatically to create the ELO
Service user. It is quite easy to change the password for the administrator, but changing the password for ELO Service also requires
data in several ELO module configuration files to be changed as
well. Therefore, please enter the password for the ELO Service
user here, then change the administrator password after installation is complete.
131
Fig. Administrator password
The next dialog indicates that all entries necessary for the installation have been successfully made. Before clicking Next, double-check that Tomcat is stopped in order for files to be copied to
its installation directory.
132
Fig. ELOam and ELOdm - Input Complete
If successfully installed, the following dialog appears, indicating

that the first part of the installation is complete.
Fig. Completed first part of installation
133
Before proceeding with the next part of the installation, a connection test is required. Start Tomcat, then click Next.
Fig. Connection test
The setup is now ready to finish the installation process. Click Next
to proceed.
134
Fig. Prepared to finish installation
Assuming no errors occur, the installation progress log will end

with Installation finished. Click Next, then Finish to close the dialog
box.
Fig. Second part of installation complete
135
Check installation
Check that the new web applications have been successfully installed by opening a browser to the following address
to log on to the Tomcat Application Manager: http://localhost:8080/manager. Enter the Tomcat administrator user
name and password (as entered during the Tomcat installation).
The browser should display a list of installed web applications, including the ELO Access Manager and the ELO Document Manager.
Fig. ELOam and ELOdm in Tomcat's Application Manager
If errors occur, check the logs in Tomcat's log directory. If the problem cannot be readily determined (for example if a log indicates
an incorrect database password or invalid serial number), contact
the ELO support department.
136
ELO Indexserver
The Indexserver
The ELO Indexserver can be understood as a kind of server-based

version of the ELO Windows Client. Other clients connect to the
Indexserver and send it requests, which the Indexserver interprets
and forwards to other ELO components for processing, then the
Indexserver returns the results to the clients. In addition, the Indexserver performs iSearch functions for all clients (including the
Windows Client).
The Indexserver is accessed via HTTP/HTTPS via a standardized
SOAP interface and a proprietary Indexserver interface. Please
consult the Indexserver documentation on the ELO SupportWeb
for more information on developing custom solutions for the Indexserver.
Start the server setup program as described above.
ELO Indexserver
137
Fig. Indexserver installation
Select Install a new application and click Next to proceed.
Fig. Select application
Under Select Application, choose Additional applications (requires

a Document Manager) and click Next.
138
ELO Indexserver
Fig. Select the Indexserver
Under Additional Applications, select Indexserver (requires a Document Manager) and click Next to continue.
Fig. Select database language
ELO Indexserver
139
Select the language installed with the Document Manager and

click Next.
Fig. Select database type
Under Database, select the database type in use and click Next.
Fig. Tomcat directory path
140
ELO Indexserver
Select the Tomcat installation path on the Directory Setting screen.

If the displayed path is incorrect, use Browse... to find the correct
location. Click Next to continue.
Fig. Setting the log directory
The default location for the Indexserver's log directory is the Tomcat log directory. If another location is desired, use Browse... to
change the path setting. Click Next to continue.
ELO Indexserver
141
Fig. Set ELO data directory
Next you must select the Indexserver data directory. Click Next to
continue.
Fig. General Settings - Microsoft SQL
142
ELO Indexserver
If Microsoft SQL Server is used for the database, the following settings need to be entered:
Database server name: Name or IP address of the database server
on the network. This can also be the local computer (localhost) or
an alias name. If a non-standard version of Microsoft SQL Server
is in use, enter the server name, followed by a backslash (\), then
the instance name.
Port: The port used to access the database. The default value of
1433 is the standard port used by the Microsoft SQL Server.
Database account: An existing account with the "database creator" right. This account is used by the setup program and new
web applications. Use the same account used during the Access
Manager and Document Manager installation. The standard account name is elodb.
Password: The database account password.
Database of ELOam: The name of the database used by the previously installed Access Manager.
Database of ELOdm: The name of the database used by the Document Manager, which is also the archive name. The database and
all of the database tables must already exist.
ELO Indexserver
143
Fig. Database Connections - Microsoft
If you are using Microsoft SQL Server, you now need to enter the
maximum number of database connections. This is the number of
database connections which will be permanently used by the Indexserver in its connection pool. As a general rule, you should enter between one and ten percent of the total number of simultaneous users. The default value is 100. If the number entered here
is too low, there will be a performance penalty, while entering a
larger number here will increase the amount of required server
RAM. Click Next to continue.
144
ELO Indexserver
Oracle
Fig. General Settings - Oracle
If an Oracle database is in use, enter the following settings:

on the network. This can also be the local computer or an alias.
The Oracle SID (system identifier) should be entered here and not
the global database name. It is not necessary to make an entry to
the Oracle file tnsnames.ora. This name can be freely assigned
Port: The port used by the database. The value in the text field is
the default value for Oracle databases.
Database account (with role DBA): This account must already exist and is used by the setup program to administer the accounts
with the corresponding tables. Please see the separate document
on installing ELO with an Oracle database for help in setting up
this user. It explains the various permissions which are required for
the user. The document can be found on the ELO SupportWeb.
Database account of ELOam: The database name for the previously installed Access Manager.
Database account of ELOdm: The existing database account
used by the previously installed Document Manager.
ELO Indexserver
145
Password for these accounts: Password for each of the existing

database accounts.
Click Next to advance to an additional setup dialog for Oracle, in
which the following entries are made:
Fig. Database setup - Oracle
ELOix maximum number of database connections: The number of database connections which will be permanently used by
the Indexserver in its connection pool. The number of connections
must be restricted. As a general rule one to ten percent of the total
number of simultaneous users should be used. The default value
is 100.
ELOdm tablespace: The predefined table of the Document Manager. This tablespace must already exist.
ELOdm index tablespace: The predefined table of the Document
Manager's index. This tablespace must already exist.
146
ELO Indexserver
IBM DB2
Fig. General settings - DB2
If DB2 is being used for the database, the following settings need
to be entered:
Database server name: Name or IP address for the database server on the network. This can also be the local computer.
Database name: Name of the existing database instance.
Port: Port for the database. The value in the text field is the standard value from DB2 for databases. Check whether this entry is
Database account: This account must already exist and is used by
the setup program to administer the accounts with the appropriate tables.
Schema of ELOam: The database name for the previously installed Access Manager.
Schema of ELOdm: The existing database account used by the
Document Manager.
Click Next to advance to an additional setup dialog for DB2.
ELO Indexserver
147
Fig. Database Connections - Microsoft
Now enter the maximum number of connections permitted from

the Indexserver to the DB2 database. This number of database
connections will be permanently used by the Indexserver in its
connection pool. The number of connections must be restricted.
As a general rule, one to ten percent of the total number of simultaneous users should be used. The default value is 100. Click Next
to continue.
148
ELO Indexserver
All database types
Fig. Server names and ports for ELOam and ELOix
On the Server Setup screen, enter the server names and port numbers for the ELO Application Manager, Indexserver, and iSearch.
Continue with Next.
Fig. Tomcat connection test
ELO Indexserver
149
A connection test is now necessary before installing. Be sure Tomcat is running before clicking Next.
Fig. User authentication for the Indexserver
In the next step, enter the ELO service user name and password.
The default name for this user is ELO Service. The Indexserver uses this user for certain functions, but usually the Indexserver performs actions using a ticket from client applications. Click Next to
continue.
150
ELO Indexserver
Fig. Authentication for ELO administrator
Under ELO Administrator User, enter the user name and password
of a user with administrator rights. This user is usually named "Administrator". Click Next to continue.
Fig. Input complete - ready to install Indexserver
ELO Indexserver
151
The Indexserver will now be installed after clicking Next. The

progress will be displayed on screen.
Fig. Installation complete
Once the Installation dialog has reached 100 percent, click Finish
to close the dialog box.
Open the ELO Server Manager to verify that the Indexserver is installed and running.
Fig. Indexserver in Tomcat Application Manager
152
ELO Indexserver
Post-installation adjustments
Enable Create external
link
A new function called Create external link was added to the ELO Java Client in ELOenterprise 9. This function shares documents within an ELO archive with persons who do not have an ELO user account. When the ELOenterprise server is first installed, however,
these "external" links only work with computers that are located
within the same network or domain as the ELO server. In order to
share ELO documents via this function with all computers with an
Internet connection, proceed as follows.
1. Assign a fixed IP address to the computer on which the Indexserver is running. Depending on your network settings, you
may need to change various settings on your network controller
and/or firewall to make sure the Indexserver can be reached by
the Internet.
2. Open the Tomcat Server Manager and click the entry for the
Indexserver to open its status page:
Fig. ELO Application Server status page
3. Click the entry for the Indexserver to open its status page. The
entry is highlighted in red in the image above.
ELO Indexserver
153
4. The Indexserver status page opens in a new tab. Click Configure

Options at the top of the window, then re-enter the user name
and password for the ELO server administrator. The status page
changes to the following:
Fig. ixUrlBase in the Indexserver options
5. The ELOenterprise setup program normally sets the ixUrlBase option for the Indexserver to the following format: http://
<computer name>:<server port>/ix-<archive name>/
ix. Replace the computer name with the fixed IP assigned to the
ELO server. Click Save, then Reload to save the change and then
apply it to the server.
If ixUrlBase has not been set for your Indexserver, you can add it
to the list via the drop-down menu in the last line of the table. Enter the value as described above, then click Add to add the option
to the list. Click Save and Reload afterwards to apply the setting.
154
ELO Indexserver
Fig. Sample ixUrlBase entry
Document links created by Create external link will now direct

users to the correct document.
Exposing a computer to the Internet requires elevated security settings to protect your network from intrusions. Please ensure the
required security measures are in effect before enabling the Create external link feature.
The value for ixUrlBase can also be changed to a website if your
network rules have been correctly set to redirect requests to the
Indexserver and/or port. For example:
Fig. Website redirect to IX ixUrlBase
Fig. Resulting sample link to document
ELO Indexserver
155
ELO iSearch and

Search Indexer
Please note: The instructions for the installation of this component only apply to ELOenterprise. Additional notes are available
at the end of the chapter for all ELO server environments.
iSearch and Search Indexer
ELO iSearch is an ELO server application that allows searches of

both document contents and document metadata. iSearch requires both the main iSearch application and the ELO Search Indexer to run.
iSearch performs search requests via the Indexserver. An Indexserver, Access Manager, and Document Manager must be running either locally or remotely for iSearch to work.
iSearch installation
156
Run the server setup program as described above. Select Install a

new application. Click Next to proceed.
ELO iSearch and Search Indexer
Fig. Installing iSearch
Under Select Application, select Additional applications (requires a

Document Manager) and click Next to continue.
Fig. Additional applications
157
Under Additional Applications, select ELO iSearch and ELO Search

Indexer (requires an Indexserver) and click Next to continue.
Fig. Selection of iSearch and Search Indexer
Select the language used by the ELO database and click Next to
continue.
158
Fig. Selection of database language
Under Database, select the database type in use and click Next to
continue.
Fig. Selection of database type
159
Under Directory Setting, enter the path to the Tomcat server. If the
displayed path is incorrect, use Browse... to find the correct location. Click Next to continue.
The default location for iSearch's log directory is the Tomcat log
directory. If you wish to use another location, click Browse... to
change the path. Click Next to continue.
160
Fig. Select log directory
The next step is to select the data directory for the iSearch. The
data directories for the iSearch will then be created under this directory. Click Next to continue.
Fig. Select data directory
161
If Microsoft SQL Server is being used for the database, the following settings need to be entered:
Fig. Database settings - SQL Server

an alias name. If a non-standard version of Microsoft SQL Server
is in use, enter the server name, followed by a backslash (\), then
the instance name.
Port: The port used by the database. 1433 is the default port used
by the Microsoft SQL Server.
Database account: An existing database account with the "database creator" right. This account is used by the setup program and
new web applications. The account used when installing the Access Manager and Document Manager should be used. The default entry is elodb.
Database of ELOam: The name of the database used by the previously installed Access Manager.
Database of ELOdm: The name of the database used by the Document Manager, which is the same as the archive name. The database and all of the database tables must already exist.
162
Oracle
If an Oracle database is in use, the following settings need to be

entered:
Fig. Database settings - Oracle
Database server name: Name or IP address for the database server on the network. This can also be the local computer.
not the global database name. An entry in the Oracle file
Port: Port for the database. The value in the text field is the standard value from Oracle for databases. Check whether this entry is
Database account (with role DBA): This account must already
exist and is used by the setup program to administer the accounts with the appropriate tables. The separate document
ELO_oracle.pdf should be consulted when setting up this user.
It explains the various permissions which are required for the user.
The document can be found on the installation medium.
163

used by the Document Manager.
Password for these accounts: Password for the existing database
accounts.
IBM DB2
If DB2 is being used for the database, the following settings need
to be entered:
Fig. Database settings - DB2
the setup program to administer the accounts with the appropriate tables.
164

Document Manager.
All database types
Under Server Setup, enter the server names and port numbers
for both the ELO Access Manager and Indexserver. Continue with
Next.
Fig. Server settings
A connection test is now necessary before installing. Ensure Tomcat is running before clicking Next.
165
Enter the user name and password for the ELO service user. Click
Next to continue.
Fig. ELO user for iSearch
166
Click Next to install iSearch. The progress will be displayed on

screen.
Fig. Input complete
Once the Installation dialog has reached 100 percent, iSearch is

installed. Click Next to continue to the final installation message.
167
The final message advises you to check the status page of the
Tomcat Application Manager to make sure that the connection to
iSearch is working.
The note at the bottom shows that the iSearch indexer will not
start to catalog archive entries until 24 hours have passed. Indexing can be started manually on the iSearch Indexer status page
(see below).
168
Fig. Installation note
Open the Tomcat Application Manager to check whether ELO

iSearch and ELO iSearch Indexer appear in the list of installed applications.
Fig. iSearch and iSearch Indexer in Tomcat Application Manager
iSearch re-indexing
Immediately after installing iSearch, the iSearch functions will become visible in the ELO clients. However, performing a search at
this point will not return any results. This is because the iSearch
Indexer does not start work for a 24-hour period after installation.
169
To start using the iSearch immediately, click the ELO iSearch Indexer on the Tomcat Application Manager to open its status page.
Click Edit in the upper right-hand corner of the status page and reenter the Tomcat administrator credentials. In the Re-indexer area
of the status page, you will now see an additional button on the
right-hand side of the Status line:
Click RE-INDEX NOW to start the indexer. iSearch will now work as
expected.
Possible iSearch Error
When the Indexserver is first installed, it will attempt to connect

to the iSearch. Since the iSearch is not installed at this point, an
error will appear on the Indexserver status page in the Application
Manager. The error will look like the following:
Fig. Connection failure in ELOix's status report (Tomcat)
To resolve this issue, restart either the Indexserver or Tomcat. The

ELOix status report should now no longer display an error.
Fig. Starting/stopping IndexServer in Tomcat
170
ELO Fulltext
Basics
One of the most important aspects of the ELO system is the powerful range of search functions. The server-side processes supporting
these functions consist of the Fulltext module, the ELO Textreader,
the OCR components, and ELO iSearch. The following section describes the installation of the Fulltext module in ELOenterprise.
The ELO Fulltext module is an optional module which can be used
with the ELOprofessional and ELOenterprise systems. It is installed
automatically by the ELOprofessional setup routine. When the
Fulltext module is installed, a second database is created for full
text information alongside the standard ELO database. This full
text database is used to find information with iSearch.
The ELO Fulltext module indexes the textual content of documents for iSearch.
The Fulltext module runs as a server-based process installed to the
archive server. The archived documents are indexed for the Fulltext database automatically at regular intervals. Since the process
runs on the server, it does not reduce client application performance. This indexing process transfers the textual contents of documents into the Fulltext database. Each word within a document
is assigned an index value. The index values are internally structured in such a way to optimize search times for each term.
ELO Fulltext
171
The Fulltext indexing process

The process for indexing documents in the Fulltext database varies
depending upon the type of document being processed. Two
types of documents can be processed. The first is made up of individual characters which can be read directly by the computer,
while the second consists of graphical information which cannot
be read directly by the computer. Computer-readable documents
contain so-called coded information (CI). Graphical files contain
non-coded information (NCI), which cannot be interpreted immediately by the computer.
Coded information
The process for entering documents consisting of coded information into the Fulltext database is relatively straightforward. The
Fulltext module copies the documents into one of a number of
folders, depending upon the type of document. For example, Microsoft Word files are copied into the .doc folder. The Textreader then collects the documents from these folders and translates
the documents into pure text documents, which are then saved in
a .txt folder designated for text files. The Fulltext module then
transfers the contents of the text files into the Fulltext database
and indexes the detected terms.
Non-coded information
The process that creates Fulltext indexes for documents consisting

of non-coded information is different from that of CI documents.
NCI documents require Optical Character Recognition (OCR) software to translate documents into a format that can be stored in
the database. OCR software is able to interpret text within image
files, such as scanned documents, which can then be stored in the
Fulltext database.
Graphical documents are processed similarly to text documents.
The documents are transferred to a corresponding folder, such as
the .tiff folder. The OCR Textreader software extracts the text
content of the files here and saves the text to the .txt folder. The
Fulltext module then transfers the contents of the text file into the
Fulltext database and builds the corresponding indexes.
172
ELO Fulltext
Fig. Fulltext Indexing with OCR
OCR analysis
Two processes are used by the OCR analysis: pattern matching and
feature recognition.
Pattern matching: The white space around individual

graphical elements is defined and then theses elements
are compared against existing pixel patterns corresponding to individual text characters. This makes the identification of any text characters possible and the graphical
patterns can be transformed into text characters.
Feature recognition: Significant characteristics of the actual pixel patterns, as opposed to the white space around
the patterns, are used to search for unmistakable properties which allow the identification of characters.
ELO Fulltext uses a combination of these two processes for OCR.

Feature recognition is used at the start of the process to convert
the graphical NCI data into CI data. Any remaining graphical data that was not identified during feature recognition is then analyzed by the pattern matching process in order that the remaining
NCI data is converted into CI data.
ELO Fulltext
173
OCR analysis is not used on documents that only contain machine-readable text, such as Microsoft Word documents.
The overall recognition rate is dependant upon the following factors:
The (visual) quality of the original document
Scanner resolution during scanning process
The specific font used for the text
The size of the text characters
The number and type of special characters present
The spacing of the characters
The spacing of the words
The spacing between the lines
The background of the original document
The character set and font used in documents can significantly

improve or decrease the reliability of the OCR process. Please see
the documentation on specialized OCR character sets published
by the various OCR standards institutes for more information on
improving the results of the OCR process.
Keywording and indexes
The Fulltext module ensures that full text information can be

searched in the same way as keywording information (metadata)
for documents in ELO. When using iSearch, keywording and full
text data are searched simultaneously.
Not all of the words contained in the documents are stored in
the full text database. Certain words are not stored in the Fulltext
database because they reduce the quality of the search results. For
example, short and common words like and, of, the, in, on and so
on are not indexed. Since nearly all documents would return a result for these words, including them in the database would reduce
search performance while not helping to find specific documents.
Usage example
174
A keywording form is created for the job applications received by a

company. The documents receive manual keywording data upon
being archived in the ELO archive. The keywording attributes include the following attributes: last name, first name, address, and
so on.
ELO Fulltext
In addition, the complete applications are entered into the Fulltext database via the OCR. When searching for the documents, the
user now has two possibilities. Either the manually entered keywording or the Fulltext data can be used to search for a relevant
word or term.
Fig. Database Index Information
Some strategy should be used when deciding what documents

are and are not added to the full text database. If too much text
information is added to the full text database, performance will
decrease. For this reason, it may be useful to only add the first few
pages of each document to the full text database, to exclude certain types of documents, and so on.
Proper use of the full text database may also include using other
methods to help users find documents as appropriate. Users may
not need to use full text information if the archive is structured
usefully and if keywording information is used optimally.
ELO Fulltext
175
Fulltext module installation

ELO Fulltext (ELOft) runs on the server and is responsible for transferring documents to be added to the Fulltext database into
the appropriate folders (export). Once the documents have been
translated into text files by the Textreader (installed separately),
the Fulltext module processes the text files from the text folder
and adds them to the full text database while compiling the corresponding indexes (import).
The import and export components are provided by the Fulltext
module. The Textreader component is installed separately and is
covered in the ELO Textreader chapter.
Installation
To install the Fulltext module, start the server setup program. It is

usually located in the directory <ELOenterprise>/prog/serversetup/setup.exe in Windows. The <ELOenterprise> directory is specified when the installer extraction program was first
run from the ELO DVD.
Fig. Select installation type
176
ELO Fulltext
The first screen to appear allows you to Select Installation Type.

Fig. Installing additional applications
Under Select Application, select Additional applications (requires a

Document Manager) and click Next.
ELO Fulltext
177
Fig. Select the Fulltext application
Under Additional Applications, select Fulltext (requires a Document

Manager). If you are using multiple archives/Document Managers, a separate Fulltext module must be installed for each. Click
Next to continue.
178
ELO Fulltext
Fig. ELOdm database entries
Under Language for Database Entries, select the language used by

the Document Manager and click Next.
Fig. Selecting the database type
Under Database, select the database type in use and click Next.
ELO Fulltext
179
Fig. Location of Tomcat directory
The directory of the installed instance of Tomcat should be shown

under Directory Setting. If the displayed path is not correct, use
Browse... to locate the Tomcat installation. Click Next to continue.
Fig. Log directory
180
ELO Fulltext
Under Log Directory, enter the location where ELOft will store its
log files. The default entry is the standard Tomcat log directory,
but it can be changed by clicking Browse.... Click Next to continue.
Fig. Full text data directory
Select a location where the Fulltext module will store its data in
the Directory Setting dialog. Click Next to continue.
Note: The Fulltext data directory may grow quite large if a large
number of documents are contained in the archive. This folder
can also grow quickly if a Fulltext module is added to an existing
archive, or a large data import occurs. Please ensure sufficient disk
space is made available to this folder.
ELO Fulltext
181
Fig. Text file size
The Maximum Text File Size dialog box is displayed next.

The Fulltext service imports the contents of files into the database
when the size of the text file does not exceed the value entered
here. Files in other formats, such as PDFs, are translated beforehand into text files by the textreader (when installed). This value
does not normally need to be increased and applies only to text
files. It is set to ensure that sufficient memory is available for the
Fulltext process.
It is also recommended to increase the maximum amount of RAM
available to Tomcat when the Fulltext module is installed, particularly if multiple Fulltext modules are installed to the same server.
182
ELO Fulltext
Fig. Database settings for Microsoft SQL Server
The General Settings for the Access Manager and Fulltext service
are required next.
an alias. When using a non-standard installation of Microsoft SQL
Server, enter the instance name as well, separated from the server
name by a \.
Port: Port used by the database. The existing value in the text field
is the default port used by Microsoft SQL Server.
web applications. The account used for the Access Manager and
Document Manager installation should be used. The standard account name is elodb.
Database of ELOam: The name of the database used by the Access Manager, which is usually eloam.
ELO Fulltext
183
Database of ELOdm: Name of the database used by the Document Manager, which is the same as the archive name. The database and all of the database tables must already exist. This is the
archive associated with the Fulltext module.
Oracle
Fig. General settings under Oracle
not the global database name. An entry in the oracle file
Port: Port for the database. The value in the text field is the standard value from Oracle for databases. Check whether the entry is
Database account (with role DBA): This account must already exist and is used by the setup program to manage accounts and their
corresponding tables. The separate document ELO_oracle.pdf
should be consulted when setting up this user. The file is supplied
with the installation DVD and explains the various rights that the
user requires.
184
ELO Fulltext
Database account of ELOam: the database name for the previously installed Access Manager.
Database account of ELOdm: the existing database account used
by the previously installed Document Manager.
Password for these accounts: password for the existing database
accounts.
IBM DB2
Fig. General settings under DB2
Database name: Name of the installed database instance.
Database account: This account must already exist. It is used by
the setup program to manage the accounts and corresponding
tables.
Schema of ELOam: the database name for the previously installed
Access Manager.
ELO Fulltext
185
Schema of ELOdm: the database account used by the previously

installed Document Manager.
All database types
Fig. Server setup
The Server Setup details have to be entered next. Enter the server name and access port for the Access Manager and Document
Manager. These applications do not need to be installed on the
same computer. Alias names or localhost can be entered here.
186
ELO Fulltext
Fig. Connection test to Tomcat
A connection test is carried out, and then the ELO User dialog box
is displayed.
Fig. ELO full text user
ELO Fulltext
187
Enter an existing ELO user and password. This entry is required for
the Fulltext module to read documents, as the service needs to
access the Access Manager to do so. The Administrator account
should not be used. You can change the Fulltext user account at
any time in the ELO Windows Client.
Fig. Input complete - ready to install
A progress bar and installation information is shown in a progress

dialog box.
188
ELO Fulltext
Fig. Completed installation
Click Next to display a list of directories that have been created and
registered in the database in order for the Fulltext module to run.
Fig. List of full text directories
ELO Fulltext
189
Fig. ELOft directories by document type
Fig. ELO full text in the Tomcat Application Manager
190
ELO Fulltext
Additional Document
Types
ELO Fulltext
Folders for the common document types are created automatically in the data directory. The folders are created for the document types supported by the Java Textreader. If further document
types need to be added to the Fulltext database, additional text interpreter software must generally be installed. These are not provided by or supported by ELO. Create corresponding folders for
these file types in the data directory and enter the file types to the
Fulltext configuration. Restart the Fulltext web application afterwards.
191
ELO Textreader
Please note: The instructions for the installation of this component only apply to ELOenterprise.
Installation
The textreader is used to convert CI (text-based) documents into

text files. After the conversion, the document contents are made
available to the Fulltext module for indexing.
Before installing the ELO Textreader, an archive (Document Manager), Access Manager, and Fulltext module must already be installed.
Fig. Installing the Textreader
192
ELO Textreader
Run the server setup program as described previously. Select Install

a new application and click Next.
Fig. Additional applications
Select Additional applications (requires a Document Manager).
Fig. Textreader option
ELO Textreader
193
In the Additional Applications dialog box, select the option for Textreader (requires Fulltext and an Indexserver).
Select the language used in the database for the archive. If you
have run the program on this computer already, the correct language should be selected by default.
194
ELO Textreader
Fig. Database selection
The type of database must then be selected.
ELO Textreader
195
The Tomcat directory must be provided next. You can generally

keep the default value. If the displayed directory is incorrect, click
Browse... to locate the correct directory.
Fig. Log directory
Next, enter the location where ELOtr will store its log files.
196
ELO Textreader
Fig. Full text data directory
In the next screen, enter the Fulltext module's data directory. This
must be the directory selected during the Fulltext setup.
Fig. Maximum file size for Textreader
ELO Textreader
197
Next, enter the maximum file size for documents. If you increase
this value above 25 MB, a warning message appears, notifying you
that the amount of memory allocated to Tomcat may need to be
increased as well.
Fig. General database settings
Next, enter the General Settings for the ELO Textreader.

Database of ELOam: Enter the Access Manager's database name.
This is usually eloam.
Database of ELOdm: The name of the archive (database) that will
be used with the Textreader.
Words used when not converted: If the Textreader cannot convert a file for whatever reason (due to an invalid format, an error
in the file, and so on), a text file is created containing the text entered here. This file is then imported by the Fulltext module and
can be used to search for documents that could not correctly be
interpreted.
If you enter a | (pipe) and a second word, that word will be used for
certain subordinate documents that cannot be converted, such as
in e-mail attachments. This entry is optional.
198
ELO Textreader
Now enter connection data for the Access Manager and Indexserver. If you have already installed ELO server applications to
this computer, the correct entries should be entered by default.
ELOam server name: The computer name or IP address of the ELO
Access Manager.
ELOam server port: The Tomcat port used by the Access Manager.
ELOix server name: The computer name or IP address of the Indexserver.
ELOix server port: The Tomcat port used by the Indexserver.
ELO Textreader
199
Next, the connection to the Tomcat server is tested. Click Next to

continue.
Enter the authentication data for an ELO user. The ELO service user
should usually be used here. Click Next to continue.
200
ELO Textreader
Fig. Input complete - ready to install Textreader
After reaching the Input Complete screen, click Next to install the
Textreader.
Click Finish to close the installer.
ELO Textreader
201
Open the Tomcat Application Manager to see that the Textreader

is installed and running.
Fig. Textreader in Tomcat Application Manager
202
ELO Textreader
ELO XML Importer
The ELO XML Importer is an ELO application used to import documents automatically into an ELO archive based on an XML control file. The XML Importer monitors a specific directory at regular intervals to initiate an import process. Please see the ELO XML
Importer documentation for more information on how to use the
XML Importer.
The XML Importer requires a running Indexserver, Access Manager, and Document Manager to work.
To install the ELO XML Importer in ELOenterprise environments,
proceed as follows:
Navigate to the directory containing the ELOenterprise setup files (normally <ELOenterprise>\prog\serversetup\,
where <ELOenterprise> is a directory you specify when the setup extractor is run). Run setup.exe. The following screen appears:
ELO XML Importer
203
Click Additional applications (requires a Document Manager) and

then click Next.
204
ELO XML Importer
Select XML Importer (requires an Indexserver) and click Next.
Select the language used by ELO in the database and click Next.
This must be the setting chosen when the Access Manager and
Document Manager were first installed.
ELO XML Importer
205
Select the database type in use and click Next.
Select the directory in which Tomcat was installed locally, then

click Next.
206
ELO XML Importer
Select the directory in which you want to store log files produced
by the XML Importer, then click Next.
Select a directory where the XML Importer will store its data and
click Next.
ELO XML Importer
207
Enter the database names for the Access Manager (usually eloam)
and Document Manager (the name of the archive). Click Next to
continue.
Oracle
208
ELO XML Importer
Enter the database account names for the Access Manager (usually eloam and the Document Manager (the name of the archive).
IBM DB2
Enter the schema names for the Access Manager (usually eloam
and the Document Manager (the name of the archive). Click Next
to continue.
ELO XML Importer
209
All database types
On the following screen, select what should occur to documents

after they have been imported using the XML Importer. The default option to Delete documents after import can be used in most
cases. If an import fails without importing documents, the Importer will try again and no documents will be deleted automatically. However, you can also select the option to Move documents
to another directory after import for added security or other reasons. This option can also be changed after installation. Click Next
to continue.
210
ELO XML Importer
Now you must select an import directory for the XML Importer.
This is the directory the Importer monitors for documents to import. Click Next to continue.
Enter connection data for the ELO Access Manager and Indexserver.
ELO XML Importer
211
ELOam server name: The computer name or IP address of the Access Manager.
ELOam server port: The Tomcat port used by the Access Manager.
ELOix server name: The computer name or IP address of the Indexserver.
ELOix server port: The Tomcat port used by the Indexserver.
On the Signal File screen, you must specify whether the XML Importer uses a signal file for imports. If this option is selected, a .SIG
file must be present in the import directory in order to initiate an
import. Click Next to continue.
212
ELO XML Importer
Make sure the ELO Tomcat server is running locally, then click Next.
Enter the authentication data for an existing ELO user. The ELO
service user should usually be used here. Click Next to continue.
ELO XML Importer
213
Click Next to install the XML Importer.
The final screen shows the progress of the XML Importer installation. Wait for the progress bar to reach 100 percent and then click
Finish to close the installer.
214
ELO XML Importer
If errors occur, try to correct them and then run the XML Importer
installation again.
After closing the installer, go to the Tomcat Manager status page
and check that the XML Importer is installed and running:
Fig. Tomcat status page with running XML Importer
ELO XML Importer
215
ELO Automation
Services
ELOas was named ELO Mover in earlier versions of the software.
The ELO Automation Services provide administrators to automate

nearly any task in the archive. ELO Automation Services (or ELOas
in short) is initiated either via an http request, or more commonly,
in time intervals. When an ELOas process is initiated, it performs
JavaScript commands on the ELO server by communicating directly with the Indexserver. Common uses of ELOas include:
Moving entries with certain keywording attributes within

the archive
Automatically performing functions in workflows, such

as assigning users
Notifying users when specific criteria in the archive are

fulfilled
Various backup and maintenance tasks
Consult the ELO Indexserver Programming Guide from ELOpress

and the ELO Automation Services documentation for more information about the capabilities of this module.
Install ELOas by starting the server setup program.
216
ELO Automation Services
Select Additional applications and click Next.
217
Select Automation Services (requires an Indexserver) and click Next.
Select the language selected previously for the database and click
Next.
218
Select the database type and click Next.
Select the directory in which the ELO Application Server (Tomcat)

is installed and click Next.
219
Select the location where ELOas will store its logs and click Next.
Enter the name of the databases used by the Access Manager

(default: eloam) and Document Manager (archive name). If you
wish to use ELOas with multiple archives, you must install multiple
ELOas instances. Click Next to continue.
220
Oracle
Enter the database account names for the Access Manager (usually eloam and the Document Manager (the name of the archive).
IBM DB2
221
Enter the schema names for the Access Manager (usually eloam
and the Document Manager (the name of the archive). Click Next
to continue.
Enter the computer name and ELO port for the Access Manager
and Indexserver, then click Next.
222
Start the ELO Application Server if it is not already running, then

click Next.
Enter the user name and password for the ELO service user (ELO
Service by default). Click Next to continue.
In principle, any user can be used by ELOas, as long as the user option to force a password change has not been set. However, since
ELOas performs all functions within this user context, a user with
administrator rights is recommended.
223
Click Next to install ELO Automation Services.
Once the screen above appears, click Finish to close the setup program.
224
Check the Tomcat Host Manager to make sure that ELO Automation Services is running.
225
Installing multiple Automation Services

Multiple instances of ELO Automation Services may be installed
for the same archive (Document Manager) in ELOenterprise environments. However, since ELOas is designed to use a fixed GUID
for its ruleset folder in the archive, the normal server setup program cannot be used to install multiple instances of ELOas in the
same archive. It is not possible for multiple ELOas instances to
share the same base folder.
To install additional Automation Services instances for an archive,
proceed as follows. The following example assumes an archive
named Archive.
1. Create a copy of the ELOas Base folder.
Fig. Second ELOas Base folder
2. Copy the GUID of the new ELOas Base folder to a text editor.
226
Fig. ELOas Base 2 folder GUID (your folder's GUID may differ)
3. Stop the instance of Tomcat where you will install the new
ELOas.
4. Go to the Tomcat's webapps directory and copy ELOas under a
new name. In this example, name the new instance of ELOas asArchive2.war.
5. Go to the web application configuration directory (<tomcat install>\conf\Catalina\localhost) and copy the
application's xml file in the same way as step 4. In this example,
copy as-Archive.xml to as-Archive2.xml.
6. Open the copied .XML file in Notepad or a similar text editor and
change the entry for webappconfigdir and Context path to
reflect the new ELOas instance. In this example, it would be:
<Context path="/as-Archive2">
<Environment name="webappconfigdir" value="C:\ELOenterprise\config\as-Archive2" type="java.lang.String"
override="false"/>
</Context>
227
7. Now navigate to the config directory as defined in step 6. Copy

the original configuration directory for ELOas to create a new configuration directory for the new instance.
Fig. New 'as-Archive2' directory
8. Enter the new directory, then open the config.xml file within
it in a text editor. Change the rootguid entry to reflect the folder
in the archive from step 2:
Fig. Edited GUID for the second ELOas instance
9. Open log4j.properties in the same directory and define a

different name for the log file.
228
10. Start Tomcat.

Check in the Tomcat Server Manager that the new instance of
ELOas is running properly:
Fig. Second instance of Automation Services running on ELO server
229
ELO Workflow
One of ELO's greatest advantages as a document management

system is its powerful and versatile workflow functions. When the
workflow functions were first developed for the Windows Client,
they required direct user interaction to initiate, send on, and complete their associated workflows. Over time, automation functions
were included in several steps, and now it is possible for workflows
to be automated to a large degree.
In a similar vein, a new type of workflow, called the form-based
workflow, has been developed more recently for use in ELO environments. They do not need to be associated with a document
to run and offer several advantages compared to the traditional
workflow functions. Please consult the ELO Workflow user guides
for the Windows Client and Java Client to learn more about these
possibilities.
The form-based workflow is prepared and controlled by the
ELOwf module. Install the ELO workflow forms server by running
the server setup program as an administrator.
ELOwf must be installed on the same instance of Tomcat as ELO
Automation Services to ensure proper functionality. This means
both must run on the same server and use the same port. This is
required for AJAX commands to run properly - otherwise, all requests from ELOwf to ELOas will fail without reporting an error.
230
ELO Workflow
Select Additional applications (requires a Document Manager) and

click Next.
ELO Workflow
231
Select Workflow Forms Server (requires an Indexserver and local

Automation Services) and click Next.
Select the language used in your ELO database for entries and click
Next.
232
ELO Workflow
Select your database type and click Next.
Select the directory used by your ELO Application Server (Tomcat)

and click Next.
ELO Workflow
233
Select the directory where ELOwf log files will be saved and click
Next.
The General Settings for the Access Manager and Fulltext service
are required next.
234
ELO Workflow

an alias. When using a non-standard installation of Microsoft SQL
Server, enter the instance name as well, separated from the server
name by a \.
Port: Port used by the database. The existing value in the text field
is the default port used by Microsoft SQL Server.
web applications. The account used for the Access Manager and
Document Manager installation should be used. The standard account name is elodb.
Database of ELOam: The name of the database used by the Access Manager, which is usually eloam.
Database of ELOdm: Name of the database used by the Document Manager, which is the same as the archive name. The database and all of the database tables must already exist.
Oracle
ELO Workflow
235
not the global database name. An entry in the oracle file
Port: Port for the database. The default value in the text field is
the standard value from Oracle for databases. Check whether the
entry is correct and change it as needed.
Database account (with role DBA): This account must already exist and is used by the setup program to manage accounts and their
corresponding tables. The separate document ELO_oracle.pdf
should be consulted when setting up this user. The file is supplied
with the installation DVD and explains the various rights that the
user requires.
used by the previously installed Document Manager.
Password for these accounts: Password for the existing database
accounts.
236
ELO Workflow
IBM DB2
the setup program to manage the accounts with the corresponding database tables.
Document Manager.
ELO Workflow
237
All database types
Enter the computer name or IP address, and Tomcat port number

to the Access Manager, Indexserver, and Automation Services. Use
an instance of ELOas that is running locally. Click Next to continue.
Start the ELO Application Server (Tomcat) if it is not already running, then click Next.
238
ELO Workflow
Enter the user credentials for an ELO user. Use the service user
here. For most ELO environments, the user will require administrator rights.
Click Next to install ELOwf.
ELO Workflow
239
A progress bar appears along with installation messages. After "Installation finished." appears, click Finish to close the server setup
program.
Open the ELO Application Manager to make sure ELOwf has been
installed properly:
240
ELO Workflow
ELO Web Client
The ELO Web Client allows users to log on to and use the ELO
archive via most common Internet browsers. For more information
on using and managing the Web Client, see the corresponding
manual.
A separate license is required to use the full Web Client functionality. If you install the Web Client without purchasing a license, access will be restricted to devices running ELO for Mobile Devices.
Full vs. FMD Web
Client
The ELO Web Client application provides two different ranges of

functions: the Web Client itself and the Web Client for Mobile Devices.
If you have purchased a license for the Web Client, you can log on
to the ELO archive via any Internet browser. You may also access
the ELO archive via ELO for Mobile Devices for the Android and
iOS platforms.
If you have not purchased a license for the Web Client, it will install as an FMD version. This means that you can log on to the ELO
archive via the ELO for Mobile Devices apps, but not via the browser.
If you install the Web Client and later decide to purchase a full
license, you do not need to reinstall the Web Client server application. Instead, change the ELO server license via the server setup program or directly in the Access Manager amoptions table.
Restart the ELO server after changing the license number.
To install the Web Client, run the ELOenterprise server setup program.
ELO Web Client
241

click Next.
242
ELO Web Client
Select Web Client (requires an Indexserver and Workflow Forms

Server) and click Next.
Select your database type and click Next.
ELO Web Client
243
Select the directory in which you installed Tomcat and click Next.
Select the directory in which you want to store Web Client log files
and click Next.
244
ELO Web Client
Select the directory where the Web Client will store its data and
click Next.
Enter the names of the Access Manager and Document Manager

databases that will be used by the Web Client. Click Next to continue.
ELO Web Client
245
Oracle

database accounts that will be used by the Web Client. Click Next
to continue.
IBM DB2
246
ELO Web Client

schemas that will be used by the Web Client. Click Next to continue.
All database types
Enter the computer names (or aliases) of the computers running

the Access Manager application and the Indexserver, as well as
their Tomcat ports. Click Next to continue.
ELO Web Client
247
Make sure that Tomcat is running on the computer to which you

are installing the Web Client. Click Next to continue.
Enter the user name and password of an existing ELO user. This
user needs to have Main administrator rights. The ELO service user
is normally used here. Click Next to continue.
248
ELO Web Client
Click Next to install the ELO Web Client.
When installation is complete, click Finish to close the server setup.

To check that the ELO Web Client has installed correctly, go to the
Tomcat Manager to check its status:
ELO Web Client
249
Click the link to /web-<archivename> to reach the Web Client

logon screen:
A shortcut to this link can be created on the desktop, the Windows

start screen, and so on. Add status to the end of the logon link
to reach the Web Client status page:
250
ELO Web Client
Bookmark this page to see the current status of the Web Client at
a glance.
ELO Web Client
251
Administration
Console
The Administration Console is a module in ELO that allows you
to perform administrative tasks, such as setting up and managing
users, keywording forms, ELOas rulesets, backup settings, client
configuration and so on. To install the Administration Console, run
the server setup program.
252
Administration Console

click Next.
Select Administration Console (requires an Indexserver) and click

Next.
253
Select the database type used by ELO and click Next.
Select the directory into which the ELO Application Server was installed and click Next.
254
Select a directory for the Administration Console log files and click
Next.
ELOdm database: Enter the archive name here.
255
ELOix server name: Enter the computer name to which the Indexserver was installed.
ELOix server port: Enter the port used by the Indexserver.
Note: In Oracle environments, the Document Manager database
account is required here. In IBM DB2, you must enter the Document Manager schema. The Administration Console is otherwise
the same for all database types.
If you are installing the Administration Console to a server on Linux, you will be given the option to set ownership for certain directories. Enter the Tomcat user and (optionally) the Tomcat user's
group. Click Next to continue.
Make sure the ELO server is running, then click Next to continue.
256
Click Next to install the Administration Console.
Click Finish to close the installer. Open the ELO Application Manager to check whether the Administration Console is running properly:
257
You can now start the Administration Console by clicking the link.
It is a good idea at this point to create a shortcut to the application
on the desktop, in the Windows start menu, and wherever else it
will be useful.
For information on how to use the Administration Console, continue to the Administration Console user guide.
258
Updating
ELOenterprise
Due to its high degree of modularity, updating ELOenterprise requires more work than updating ELOprofessional. Since ELOenterprise can be distributed to several different servers, it may be necessary to repeat the update process on each of them. Follow the
steps in this chapter to correctly update your server software.
Before updating ELOenterprise web applications:
Back up ELOenterprise and the database
Backup
Update Java if necessary
Update Tomcat if necessary
Before making any major changes to the ELO server (such as updating it), make sure to back up a working version of the software.
Repeat steps 1-3 for each computer that runs ELOenterprise applications.
1. Back up the Tomcat installation directory and all child directories.
2. Back up the config and data directories. By default, these are
child directories of the Tomcat installation directory.
3. Back up the webapps directory. By default, this is a child directory of the Tomcat installation directory (<Tomcat installation>\server\webapps, as well as <Tomcat installation>\prog\webapps in ELOenterprise 9).
4. Back up the database. The storage format differs depending on
which database (Microsoft SQL, IBM DB2, or Oracle) is used, but
create backup copies of all archives and all Access Managers.
Updating ELOenterprise
259
Update Java
1. Check the version compatibility table in the server update documentation to see which version of Java is required for the update
you are performing. If you are updating from the ELOenterprise
DVD, the required version of Java is included on the DVD.
2. Next, open a command window and enter java -version.
If your installed version of Java is lower than the version required
for the ELOenterprise server update, you must update Java.
3. Download Java JRE from the Internet or click the link to it on the
ELOenterprise DVD and run the setup program to update Java.
4. Update Java in the same way on all computers running ELOenterprise server applications.
Update Tomcat
When updating ELOenterprise, an update is often required to the

Tomcat server software as well. If you need to update Tomcat, proceed as follows.
The Apache Tomcat software may add or remove significant features between minor releases that affect ELO functionality. Check
the version compatibility list in Server Update.pdf to see which versions of Tomcat are compatible with which versions of ELOenterprise.
1. Download the version of Tomcat required for ELO from
http://archive.apache.org/dist/tomcat/tomcat-7/.
2. See the Tomcat Migration Guide at http://
tomcat.apache.org/migration.html. When updating between versions of Tomcat 7, usually the configuration from the
earlier version can be kept.
3. Upgrade Tomcat according to the Migration Guide. Remember
to update all Tomcat servers that are running ELOenterprise server
applications.
Update ELOenterprise
260
ELO provides updates to ELOprofessional server applications on a

regular basis. There are several ways to apply these updates:
Use the newest release DVD of ELOenterprise. Please ensure that you update Java and Tomcat first if necessary.
Download and run the newest server setup update from

the ELO SupportWeb. New server setups are published
more frequently than DVD releases.
Update individual ELO server applications manually. This

is more complicated than the other options, but it ensures that you have the most current version of the application.
All of these update options are described in the following.

Update from DVD or
Server Setup
The easiest way to update the ELOenterprise server files is to run

the server setup program. This can also be used to update from
ELOprofessional 2011 to ELOprofessional 9.
When you perform an update in this way, the ELO server will be
stopped for a short time. Make sure that no users are using the
archive at this time.
1. Back up your existing copy of ELOenterprise. It is easiest to back
up the entire ELOenterprise install directory (such as C:\ELOenterprise) and all child directories. Also back up the databases for the
Access Manager and all archives.
Update from DVD
2. Place the ELOenterprise DVD in the ELO server's DVD drive and
run Start.exe.
3. Navigate to the Basic Installation tab and click Server Installer for
Windows.
Update from Server

Setup
3. Download the newest version of the ELOenterprise Server Setup files from the ELO SupportWeb. Extract the ZIP file to a local
directory and run ELOenterprise.exe.
261
4. The ELOenterprise file extractor starts. Select the ELOenterprise

root directory (C:\ELOenterprise by default) and select the option to Start the server installation at the end. Click Start extracting.
The ELOenterprise server setup program starts automatically after
extraction is complete.
262
5. The ELOenterprise Server Setup program starts. Select Update all

applications and click Next.
263
6. A warning note is shown. It is recommended to make a backup

of the directories noted above if you have not yet done so. Click
Next to continue.
7. Select the language used in the database for ELO entries, then
click Next.
264
8. An option is shown that must be selected if ELO is based on

an Oracle database. If some or all of your ELO server applications
use an Oracle database, select the option Oracle is used by ELO
applications. Click Next to continue.
265
9. Select the directory in which Tomcat is installed and click Next.
10. Select the directory in which you want to store log files and
click Next.
266
11. The setup program now lists the server applications that it detects and can update. If the list is not correct, click Cancel to close
the program. Click Next to continue.
12. The setup program gives you the opportunity to change the serial number. If you are upgrading ELOenterprise from version 2011
to ELOenterprise 9, you must change the serial number to perform
the update. Click Next to continue.
267
Oracle
13. This screen only appears if you are updating an ELOenterprise

server based on an Oracle database. Enter the authentication data
for an Oracle user that possesses the DBA. Click Next to continue.
268
14. This screen also only appears in Oracle environments. Enter the
tablespace and index tablespace for the Access Manager and Document Manager. Click Next to continue.
All database types
15. Stop the Tomcat server before proceeding. It is recommended to check the Task Manager in Windows or to check the list of
running processes in Linux or Solaris environments to ensure the
server has completely shut down. Click Next to install the updates.
269
Fig. Completed update
16. A progress window appears, showing you information on the

course of the update. Wait until the progress bar reaches 100 %,
then check the progress messages for errors. If the message Update finished appears, the updates have installed correctly. If errors occur, attempt to correct them and run the update again. Click
Next to continue.
270
17. The final screen reminds you that certain post-installation

steps may be required. The directory containing the server setup
files also contains a document, server_update.pdf, with information on any additional work that needs to be performed. Click Finish to close the setup program.
18. Restart the ELO server (Tomcat).
19. Run the server update program on any other computers running ELO server applications.
Manual application
update
There are several ways to update ELOprofessional server applications. In ELOprofessional 2011 and earlier, the applications
were extracted to separate directories, complicating the update
process. Starting with ELOprofessional 9, the WAR files that contain the ELO applications are loaded dynamically to Tomcat at runtime. To update ELOprofessional 9 server applications, proceed as
follows:
The ELO Application Server does not need to be stopped to perform an update in this way. However, increased server RAM will
be required until the ELO server is restarted. It is recommended to
perform a server restart after performing an ELO application update as soon as it is convenient to do so.
271
1. Download the new ELO application from the ELO SupportWeb.

See the included documentation for any dependencies between
the application and other ELO server applications or client programs. Also check whether the configuration files for the application need to be changed.
2. Navigate to the directory:
<ELOprofessional>/prog/webapps/
Check to see that the application you want to update already exists in this directory. Each ELO application uses a special abbreviation (such as dm.war for the ELO Document Manager, ix.war for
the Indexserver, and so on.
If the updated application is not located in this directory, use the
update method following this one titled Manual update with
transfer directory.
3. Extract the updated ELO application to your hard drive and rename it (if necessary) so it has the same name as the old ELO application.
4. Copy the updated ELO server application to the prog/webapps
directory so that it overwrites the old application.
5. Tomcat will automatically load the updated application to
memory. Check the status page of the updated application in your
browser in the ELOprofessional Server Manager. If the application
has a status of Running and no errors are displayed, the application has updated successfully.
Manual update with
transfer directory
If you are running ELOprofessional 2011 or your server application

is not stored in the prog/webapps directory, use the following
method to update your ELO server applications:
1. Create a directory on the server where the updated application
files will be stored. This is called the transfer directory.
2. Copy the servlet configuration file from the server into the transfer directory. This configuration file is located in <ELO server installation directory>\server\conf\Catalina\localhost. It is an .XML
file with the same name as the web application, such as trArchive1.xml.
272
3. Copy the new web application (a .WAR file) into the transfer
directory, then give it the same name (without extension) as the
configuration file, such as tr-Archive1.war.
4. Open the ELO Server Manager and locate the application you
want to update, then click Undeploy:
This deletes the old version of the application and configuration

file, though the data associated with it (such as the archive, iSearch
database and so on) is retained.
5. At the bottom of the ELO Server Manager, enter the information
for the updated application:
Context Path: The name of the old application with a forward
slash in front, such as /tr-Archive1.
XML Configuration file URL: The UNC path to the XML file in the
transfer directory, such as C:\transfer\tr-Archive1.xml.
WAR or Directory URL: The same directory as the path above, but
with .war instead of .xml. For example: C:\transfer\tr-Archive1.war.
6. Click Deploy. You will normally not have to restart ELO or Tomcat. You can delete the files in the transfer directory now if you
wish.
273
ELO Viewer
The portable archive
The ELO Viewer is a tool that allows you to export archive contents
along with a read-only version of ELOoffice, which allows anyone
with a Windows PC to view archive contents. A portable archive
retains all the advantages of a normal ELO export data set and
can be reimported as usual. However, the portable archive lets you
also do the following:
Create a multimedia presentation for customers
Send out annual reports
Provide information to auditors
Or any other scenario where you need to give non-users

of ELO access to a collection of documents.
The ELO Viewer should not be confused with the ELO viewer plugins, which are used to view special file types in the ELO client applications.
The ELO Viewer is installed automatically with ELOprofessional.
Use the following instructions to install it in ELOenterprise:
To install the ELO Viewer, place the ELO installation medium in
the computer to which you installed ELOam. This is the ELO server if you installed ELOprofessional. Navigate to the Basic Installation tab and click the link to Viewer. The ZIP file containing
the installation files opens. Open the files directory and copy all
files within it to <server installation directory>\data\am-eloam\configuration\viewerpostbox. This directory will have been created automatically during ELOam installation.
274
ELO Viewer
Fig. ViewerPostbox files in the ELOam directory
The Viewer can now be used to export a portable archive from any
Windows Client on the ELO system. See the Windows Client Manual for instructions on how to export and use a portable archive.
Alternative ELO Viewer languages
The Viewer on the ELO installation medium is provided with the

language files for English, German, and French. If you wish to create portable archives in another language, additional languages
are available on the ELO SupportWeb. Portable archives can only
be created in one language at a time.
The language packs are provided as ZIP files. Unpack the UIT file to
your Viewer directory and rename it to Elo320.uit. If a file named
Elo320.uit already exists in that directory, delete it first.
Open Elo320.uit in Notepad and look at the first few entries. A
letter appears at the start of every second line of the file:
Next, open the file titled EloOVw.uit in the Viewer directory. If you
installed the German-language Viewer, the file will need to be created. It must be a text file with the following contents:
ELO Viewer
275
[Settings]
Language="E"
Replace the E in the example above with the letter in your downloaded UIT file.
ELO320.uit must be saved in UTF-8 (little-endian) format to work
properly.
276
ELO Viewer
ELO Windows Client
The installation process for the ELO Windows Client is the same for
both ELOenterprise and ELOprofessional. The ELO Windows Client
can be installed to computers running the Microsoft Windows operating system. There are two ways to install the client:
ELO Windows Client Installation
Automatic Client Installation
The first option is installed directly from the DVD. The second (automatic installer) option is rolled out to users over the network.
Either can be used for any ELO installation process, but the first
option is perhaps most appropriate for administrator computers
or testing environments. The second installer option is useful for
quickly installing ELO to a network using group policy options, because the installation information only needs to be entered once
on one computer for any number of client installs.
The following sections first describe the standard installation routine for the ELO Windows Client. The setup instructions for the automatic client installer follow.
ELO Windows Client
277
Please note: Please see the following chapter for instructions on

installing the ELO Java Client. Either the ELO Windows Client or
ELO Java Client can be installed for an ELOenterprise or ELOprofessional server. If you are unsure of which client is right for your
ELO environment, please contact the ELO Sales or Consulting departments.
278
ELO Windows Client
Standard Client Installation

Preparation
The ELO Windows Client can be installed directly from the DVD or
from a shared location on the network. A server running ELOenterprise or ELOprofessional must be working correctly on the network for the client to work, but it is not required at installation.
If the ELO server uses an Oracle database, the Oracle Client must
also first be installed on each client computer.
Installation
1. Place the installation DVD in the computer's DVD drive.
Fig. Welcome screen with link to ELO Client for Windows
2. If the computer is configured to run DVDs automatically, the

welcome screen will appear. Otherwise, navigate to the DVD and
double-click Start.exe. Select your preferred menu language in the
upper right.
ELO Windows Client
279
3. Click ELO Windows Client on the left-hand side of the DVD

menu, then select ELO Windows Client Installation at the top of the
subsequent menu.
Fig. Installation wizard for ELOprofessional 2011 Client
4. When the Installation Wizard appears, click Next to start the installation process.
280
ELO Windows Client
Fig. Select target folder
5. Here you can define the directory to which the client will be
installed. Click Next to continue.
Some configuration files (such as language files for non-German
ELO environments) are stored directly to the installation directory. Windows Vista and later virtualize access to the Program Files
directory, which can cause compatibility problems if the ELO Windows Client is installed there. For this reason, it is recommended to
choose an alternative directory, such as C:\ELOprofessional.
ELO Windows Client
281
Fig. Access Manager settings
6. In this dialog box, enter access settings for the Access Manager.
Enter the computer name of the server, the port used by the ELO
Application Server ("8080" is the default setting for ELOenterprise,
"9090" for ELOprofessional), and in ELOenterprise, the name of
the database instance (not applicable for ELOprofessional). Click
Next to continue.
282
ELO Windows Client
Fig. ODBC settings
7. Next, the dialog box to enter the ODBC settings appears. The
ELO Windows Client uses an ODBC connection to access the database. Enter the SQL server name here, followed by the Data Source
Name and the ELO user account on the database. If you are using
Microsoft SQL Server, the installer can create a System DSN automatically at this point. If your ELO environment uses an Oracle or
IBM database, the DSN must be created manually outside of the
installer. Click Next to continue.
ELO Windows Client
283
Fig. Ready to install the client
8. You are now ready to begin the client installation. Click Back to
review or change your settings. Otherwise, click Install to start the
installation.
284
ELO Windows Client
9. Once the installation is completed, the final dialog box gives you
the option of starting the ELO Windows Client immediately and/
or to view the readme file. Click Finish to close the installer.
ELO Windows Client
285
Automatic Client Installation

This installation method is designed for automated network installations of the Windows Client (to multiple computers at once).
The automatic client installation saves all installation files to a directory along with the settings required for the client computers.
Unlike the standard client installation, no user input is required
during installation.
Preparation
The automatic client installer requires access to the DVD during

initial configuration. After it has stored the necessary files to a directory, the directory is used to install the software to the client
computers. Share a directory on the network before running the
automatic client installer.
The ELO Application Server should already be running and accessible on the network. If ELO uses an Oracle database, the Oracle
Client must also be installed on each computer that will run the
ELO Windows Client.
Installation
286
1. Place the installation DVD in the computer's DVD drive. If the

welcome screen does not appear, navigate to the DVD and double-click Start.exe.
ELO Windows Client
Fig. DVD menu with link to automatic installer
2. After the DVD menu has loaded in the browser, select the entry
on the left for ELO Windows Client, then click Automatic Client Installation.
ELO Windows Client
287
Fig. Automatic client installation settings
The Automatic Client Setup starts. Enter the following data to this
screen:
288
ELO Windows Client
Setup Directory: This is the shared folder in which the directory

structure will be created. This must be a shared directory on the
network.
ODBC Data Source Name: This is the name that will be created for
the ODBC data source (DSN), which will be used on Windows
computers to access the SQL database used by ELO. If ODBC data sources other than the ELO database also need to accessed,
make sure the ELO DSN is unique.
Database User Name: This is the user name for the database which
was created when installing the ELO server.
Computer name on which the SQL database is running: This is
the name of the computer on which the SQL database is located.
EloAmUrl: Enter the location of the Access Manager here. Please
note that the address format is slightly different from that of
a pure URL: do not enter http:// at the beginning and place
colons before and after the port number. Click Use above computer name to apply the SQL computer name to the EloAmUrl.
Client InstDir: Enter the path (on the client PC) to which the
client will be installed. Environment variables (like %ProgramFiles%) can be used. On Windows Vista and above, it is recommended to select an installation directory outside of the program files.
Tiff-Printer Name: Here you can specify under which name the
ELO TIFF Printer should appear.
Pdf-Printer Name: Here you can specify under which name the
ELO PDF Printer should appear.
Pdf Printer InstDir: This is the path to which the PDF printer is installed on the client computers. Environment variables can be
used here.
OCR InstDir: This is the path to which the OCR module is installed
on the client computers. Environment variables can be used
here.
3. Modify the default values as appropriate for your system and
then click Start.
ELO Windows Client
289
The files and folders needed for installing the client software will
now be copied into the shared folder entered in Setup Directory.
4. Once the process has finished, click Exit to close the dialog box.
The setup.exe for the client program and other modules will
now be available on the network in the ClientInst subfolder of the
designated folder.
Fig. Subfolders created by the automatic client setup
To install the ELO Windows Client to the client computers, each

client computer must run AutoInst.exe in the <network share>/
ClientInst/Client directory. When this program is run, all
client components are silently installed according to the settings
from the previous screen. You can edit the installation settings
again by opening AutoInst.ini in a text editor. Alternatively, you
can run each installer manually by running setup.exe in each of the
ClientInst/ subdirectories.
290
ELO Windows Client
ELO Java Client
The ELO Java Client can be installed in several different ways on

your network. The following table describes the advantages and
disadvantages of each.
The MSI-based Java Client installer is easy to set up and
run. Note that this installer
does not install client-side
OCR, PDF/TIFF printers, or ELO
macros. They may be installed
later if you wish.
ELO Java Client Web Start
This menu item opens a ZIP
file from the DVD containing
the Web Start version of the
ELO Java Client. The Web Start
permits the Java Client to run
on a local computer without
requiring an installation.
Installation Program for ELO Use this option to install the
Java Client (Windows) with Java Client to multiple compuAdditional Components
ters at once. It allows a silent
installation to run with several
default install presets selected.
ELO Java Client for Mac
This menu item contains the
install files to install the ELO
Java Client for the Mac OS X
operating system.
ELO Java Client for Linux
This menu item contains the
install files to install the ELO
Java Client for the Linux operating system.
ELO Java Client Windows
ELO Java Client
291
ELO Java Client (Windows) MSI Installation

Click the menu item from the DVD menu and select a language to
be displayed during installation.
Fig. Select ELO Java Client install language
The installer language does not affect the languages available to

the client once it is installed. The user may select from all available
languages each time the Java Client starts.
292
ELO Java Client
Fig. InstallShield Wizard
The InstallShield Wizard opens to guide you through the installation process.
ELO Java Client
293
Fig. Install directory
Next, select the directory to which you want to install the ELO Java
Client. The default directory within the program files folder can be
used in most cases.
294
ELO Java Client
You are given the option to enter a serial number for the ELO Barcode component. Click Next to continue.
ELO Java Client
295
Fig. InstallShield Wizard
Click Install to install the ELO Java Client. When it is complete, click
Finish to exit the wizard.
296
ELO Java Client
After installing the Java Client, run it from the Windows start
menu or by double-clicking the icon on the desktop.
Enter a name for the archive to the Name field. You can use any
name you want and is used locally to distinguish between profiles. In the Indexserver URL field, enter the URL to the Indexserver
in the format http://<server name>:<Tomcat port>/ix<Archive name>/ix. If your Indexserver URL entry is correct,
the Java Client then connects to the Indexserver and you can enter your user name, password, and select a different language and
archive if you wish.
You can also create profiles for the Java Client in the registry so
that this screen does not appear. See the section titled Java Client
registry entries for more information.
ELO Java Client
297
ELO Java Client web start

The ELO Java Client Web Start is unique among the installation
methods described here. First, it does not need to be installed (in
the classic sense) to run. All it requires to run is for a compatible Java Runtime Environment to be installed on the corresponding device. This has certain advantages: when a client computer first connects to the Web Start link, it automatically downloads and runs
the ELO Java Client. Each subsequent time the application is run,
the application checks whether the newest version is available locally, and if it is, runs the Java Client in a Java virtual machine. This
makes application deployment and update exceedingly easy.
However, the tradeoff to this comfort is that certain functions are
affected or unavailable: the PDF and TIFF printer drivers, as well as
the OCR and barcode functions, must be installed separately. Additionally, the macros (add-ins) for Microsoft Office and other applications can never be used with the Web Start. The COM interface cannot be used by the Web Start client as well. Finally, though
the Java Client Web Start is able to generate ELO link files, it is
not possible to use them to open the Web Start to their associated document. If these limitations make the Web Start unsuitable
for your ELO environment, please use one of the other installation
methods.
The ELO Java Client Web Start is also useful for administrators: it
can be used to log on with several users at once for testing purposes. If the installed version of the ELO Java Client .EXE file is run multiple times, it will request logon credentials once, but afterwards
open additional ELO windows for the same user. However, each
time the Web Start is run, it will open to the logon window, allowing you to test multiple users on the same computer.
Installation
298
To install the ELO Java Client Web Start, extract the .ZIP file to a
local directory. You will need to change a configuration file before
it can be deployed to the server.
ELO Java Client
1. Depending on whether you are using ELOenterprise or ELOprofessional, rename ELOenterprise.html or ELOprofessional.html to
index.html.
2. Open EloClient.jnlp in the main directory in a text editor and
change the following line of code:
codebase="http://[SERVER]:[PORT]/[DIRECTORY]/"
to the server name and port of your ELO Application Server, followed by a directory name of your choosing like ELOJavaClient.
3. In EloClient.jnlp change an additional two lines of code. The
original file has the following two lines of code:
<property name="elo.archive.default.name" value="[ARCHIVEPROFILE-NAME]"/>
<property name="elo.archive.default.path"
value="[INDEXSERVER-URL]"/>
Change the text in the first set of brackets to include the name of
the archive profile. This is the name shown in the logon window
when selecting an archive in the client. On the second line, enter
the URL to the Indexserver, just as you would when creating a profile directly in the Java Client.
4. Depending on your specific environment requirements, you
may add additional archive profiles, enter Kerberos authentication information, or change the amount of RAM allocated to the
Java Client at startup and at maximum.
5. Stop the ELO Application Server.
6. Create a directory with the same name as in step 2 above in
your ELO Application Server's /server/webapps/ directory. In the
example above, it would be /server/webapps/ELOJavaClient. Copy
all Web Start files from the .ZIP into this new directory.
7. Start the ELO Application Server.
Result
ELO Java Client
The ELO Java Client Web Start should now be correctly installed
and configured. Test this by opening the ELO Server Manager,
where an application named the same as the directory you created should now appear. Click the link to the application. A new tab
in the browser will open, showing you the following screen:
299
Fig. ELO Java Client Web Start screen
If you are using an ELOenterprise environment (and therefore renamed ELOenterprise.html to index.html), the title at the top will
show ELOenterprise instead. If you wish the button to show "Start
ELO Java Client" instead of the German title, edit index.html accordingly. Click the button to start the client. Test logging on to
the archive to make sure it is working properly.
When you click the link to Start ELO Java Client, your computer will
download and run a file of type .jnlp. This must be run with a 32bit version of the Java (TM) Web Start Launcher, which by default
is located at C:\Program Files (x86)\Java\jre7\bin\javaws.exe.
After testing that the Java Client Web Start works properly, you
can copy the link in the browser to add it to your favorites, create a
shortcut on the desktop, link to it from other applications or documents, and so on.
300
ELO Java Client
ELO Java Client with additional components
When you select the Installation Program for ELO Java Client (Windows) with Additional Components menu item on the DVD, the
window to the left opens. The program selects by default a directory shared as ELO JC OIA Installer on the local computer. If you
attempt to start copying files and the directory does not exist, you
will receive an error message.
Click the browse button to the right of the field to select a directory on the local computer or network. Click Start Copy to copy the
files. After all files have been copied successfully, the progress bar
will show solid green and you will see the status message Copying
finished. Click End and navigate to that directory in a file browser.
You will see a number of files and folders in this directory that allow you to customize the installer for the ELO Java Client. Immediately after copying the files, you will see two files (an .EXE and
a .TXT file) that both start with EloJC. Run the .EXE file to see the
following window:
ELO Java Client
301
As you can see in the image, the all-in-one installer by default installs the ELO Java Client along with all available optional components. The default entries for installation directory, archive profile name, and Indexserver URL are only samples of valid entries
and usually need to be adjusted for your specific requirements.
Though all options can be selected or cleared from this window,
you can also affect the presets by changing the name and parameters of the .EXE file. The latter option is particularly useful for
network rollouts. The following is a list of possible installation options:
Installation directory
302
This is the directory to which the ELO Java Client will be installed
on the local machine when it is run. You can change the default
directory by adding INSTALLDIR="<path>" as a command line
parameter when the file is run.
ELO Java Client
Archive profile name
This is the name the user will see for the profile when logging on
to the archive with the ELO Java Client. Any name you wish can be
entered here, but it is recommended to use a name that helps the
user recognize what archive they are about to enter. Define the
profile name by entering a text string to the area between the last
underscore and the .EXE in the file name.
Indexserver URL
This
is
the
URL
to
the
Indexserver
for
your
archive.
Change
the
default
by
changing
the
file name from ...http_localhost_9090_elo... to
...<http(s)>_<server domain name or IP>_<port
number>_<archive name>.
Select the features you want to install: Here you will probably
want to keep the Java Client selected. The ELO OCR service performs text recognition on image files, usually from the ELO Mailbox. The TIFF and PDF printer options install printer drivers that
allow documents to be printed from or to ELO in each of the respective output formats. See the ELO Java Client user guide for
more information on these features. To select or remove each of
these features from the AIO installer by default, change the .EXE
in the area after the first underscore and add or remove the J (Java
Client), C (OCR service), T (TIFF printer), or P (PDF printer).
Select the programs you want to link to ELO with the macro:
In this area, define to which programs in Windows you want to
install an ELO add-in. The add-in provides you with additional inprogram buttons that send documents directly to the ELO archive
or Mailbox. To change the defaults, change the .EXE file name in
the same area as the above and add or remove W (Microsoft Word
macro), E (Microsoft Excel macro), I (Microsoft PowerPoint), O (Microsoft Outlook), N (Microsoft Internet Explorer), D (Windows Explorer), and F (Mozilla Firefox).
Unlisted options
ELO Java Client
A few other options are available in the all-in-one installer that are
particularly useful for a rollout installation. The first is that of the
silent installation. To activate it, add an S to the block of other
activated options in the .EXE file name. This causes the installer to
run without user interaction in the background. Note that the nature of the silent installation option only permits the installation
options to be affected by the file name and the additional parameters.
303
The Java memory reservation settings allow maximum and minimum sizes of memory used by the Java Virtual Machine which
runs the ELO Java Client. The default value allows up to 1000 MB
of RAM to be used, which is fine for most environments. However, increasing the maximum value may increase performance
in certain situations. This is done with the command line parameter XMX="<number>m". Increasing the minimum memory
can yield performance benefits as well, especially if users have
a lot of unused RAM available to them and regularly work with
image-heavy documents. Increase the minimum RAM allocation
with XMS="<number>m".
The barcode serial number is added to the installation by adding
the command line parameter SERNO_BARCODE="<serial
number>".
File name prefix: The section of the all-in-one installer file name
before the first underscore can be anything you want. However,
the last two characters shown when the files are initially copied to
the hard drive signify the defined installer interface language: En
for English, Ge for German, or Fr for French.
Result
304
After changing the title of the all-in-one installer .EXE, the

options for installation can be preselected for users. Afterwards, the file can simply be run on each workstation
that needs to use the Java Client. For example, after renaming the file to JavaClient_JCPWED_https_xeloserver
_3456_ConteloArchive_CRM System.exe and running it
with the command line parameter INSTALLDIR="C:\Company
Software\ELO\Java Client", you will see the following window when you run the file:
ELO Java Client
The order of the flags selected for the all-in-one installer

does not matter. For example, naming the file ...DWCJPE... selects the same options as ...JWDCEP.... However, the order of the options in general must always follow the pattern: <prefix>_<flags>_<http(s)>_<server>
_<port>_<archive>_<profile name>.exe. If you make an
error in naming the file, you will see the following message:
ELO Java Client
305
Fig. Incorrectly named AIO file
However, after clicking OK, the installer will open as usual, allowing you to perform a manual installation.
306
ELO Java Client
Java Client registry entries

You can configure the server settings for your users by making an entry to the registry. To do so, click the Windows
button and enter regedit.exe. In the Registry Editor, navigate to HKEY_CURRENT_USER\Software\JavaSoft\Prefs
\ELO Digital Office\eloenterprise.
Create a string named archive1 and a string value of the Indexserver URL with the forward slashes replaced by backslashes. For
example, the value could read http:\\localhost:9090\ixelo\ix. Next, create a second string named name1 and enter the
name of the archive profile to the field. Capital letters must have
a forward slash in front of them - /E/L/O archive, for example.
Additional rules exist for special characters - if you need them in
the archive name, create a profile in the Java Client and check the
result in the registry.
Additional archive profiles can be added the same way with
archive2/name2, archive3/name3, and so on. Additional possible
entries:
ELO Java Client
307
(String) name
language
lastlogin
lastselected
rrc_<...>
serno
308
Value
en, de, fr, etc. Determines the
default display language for
the Java Client at logon. Entering an invalid language code
will cause the fallback language, English, to be used.
User name shown by default
in the logon window.
The name of the archive profile selected by default in the
logon window.
Please see the documentation
titled Registry Remote Control for a detailed explanation
of these settings.
This registry entry shows up
in bold in the lower left of the
logon window. It will be overwritten by the value from the
Indexserver at next logon.
ELO Java Client
Appendix
The following topics are covered in the appendix: Additional Installation Information, Directory Access Rights, Parameters in the
File config.xml, Log Files, Increasing Tomcat Memory, and Thirdparty Licenses.
Appendix
309
Additional Installation Information

The installation of the ELO applications is designed to be flexible.
ELOenterprise can be installed all on one computer, on a number of virtual computers, or on various physical servers. The simplified setup program for ELOprofessional must be installed to a
single computer, but it can also have the database and OCR components installed to separate systems for load balancing. To keep
this guide as simple as possible, we have not covered all possible configurations. If a custom installation scenario is required,
the config.xml file for each of the ELO web applications can
be adapted to such requirements. However, this requires detailed
knowledge of ELOenterprise along with a thorough understanding of the Tomcat Application Server and the structure of the configuration files.
310
Appendix
Directory Access Rights

After a standard installation, Tomcat runs as a service under the
system account and has full access to all local directories. There are
several disadvantages to using this account. First, in the event of a
security breach in Tomcat, an attacker would gain complete access
to all local files. Second, the system account would have reduced
access to networked resources like file servers. The Tomcat installation chapter describes the procedure for creating a separate user
account for Tomcat in Windows. The section below describes how
to create this account in Linux and Solaris.
Linux and Solaris
In Linux or Solaris, Tomcat should be given its own user account

with restricted access rights instead of running under the root account. SUSE Linux generally includes Tomcat and pre-configures it
with the appropriate access rights.
When using Solaris it may be necessary to create a start script under /etc/init.d which sets the account for Tomcat. An appropriate owner for the Tomcat directory must also be set.
The ELOenterprise installation is performed using the root account
and the ownership of file and archive directories (including subdirectories and files) is normally set during the installation of an
application. If this is not done, certain applications like the Access
Manager will be unable to write or create files due to insufficient
access rights. This means that the configuration must be carried
out manually. This applies to the following directories:
Data directory (default value: ELOenterprise/data)
Archive directory (default value: ELOenterprise/archive)
When installing to Linux or Solaris, the setup program informs

the administrator at the end of the installation process about the
ownership of the directories if they have not been correctly configured. This is the data directory for the Access Manager, Fulltext
module, Indexserver and XML importer, and the archive directory
for the Document Manager.
Appendix
311
Example
In SUSE the name of the Tomcat account is tomcat (see file /etc/
init.d/tomcat). There is also a user group with the same name.
From within the ELOenterprise directory, the commands are as
follows:
For the data directory: chown -R tomcat:tomcat data
312
For the archive directory: chown -R tomcat:tomcat

archive
Appendix
Parameters in config.xml
For most cases, the config.xml file is correctly configured with
the appropriate values during the installation process and will not
require manual changes. In special situations which demand a customized installation, the file must be manually changed. The following table includes a list of all parameters for the file.
The description of the config.xml files for the Administration
Console, the form-based workflow service, ELOas, and the XML
Importer is included in their respective manuals.
ELOam, ELOdm,
ELOix, and ELOft
Parameter
dbdriver
jdbcurl
database
dbconnections
dbuser
dbpwd
eloftoptgroup
proxyslot
Appendix
Description
Java database driver (pure JDBC driver)
Java database connection via JDBC.
Database used
This parameter should only be set when
Microsoft SQL Server is used, or a compatible database engine that permits switching between databases with the USE
commands is used instead.
If nothing is entered here, the database
must be included in jdbcurl (Oracle).
Number of database connections that are
permanently in use (not for ELOix).
Name of the database user.
When using Oracle, an individual database
account is used by the Document Manager
for each archive.
Password of the database user. It is created
in an encrypted form during installation
(multiple numbers separated by a hyphen),
but can be used in a non-encrypted form.
Group number for the values in the database table eloftopt. This should not normally be changed. (Only ELOft)
Slot number (1-4) of the branch office
sharing the same ELOdm when proxy mode is used. "0" is for the main office. (Only
ELOdm)
313
Textreader (ELOtr)
Parameter
dirs_doc
dirs_docx
dirs_dot
dirs_pdf
dirs_xls
dirs_xla
dirs_xlsx
dirs_htm
dirs_html
dirs_mht
dirs_mmf
dirs_msg
dirs_eml
dirs_pps
314
Description
Source and target directory for files with
the .doc extension, separated by a pipe
character.
the .docx extension, separated by a pipe
character.
the .dot (Word templates) extension, separated by a pipe character.
the .pdf extension, separated by a pipe
character.
the .xls extension, separated by a pipe character.
the .xla (Excel add-in) extension, separated
by a pipe character.
the .xlsx extension, separated by a pipe
character.
the .htm extension, separated by a pipe
character.
the .html extension, separated by a pipe
character.
the .mht extension, separated by a pipe
character.
the .mmf (COLD documents) extension, separated by a pipe character.
the .msg (Microsoft Outlook) extension, separated by a pipe character.
the .eml extension, separated by a pipe
character.
the .pps (Powerpoint slideshow) extension,
separated by a pipe character.
Appendix
Textreader (ELOtr),
cont.
Appendix
Parameter
dirs_ppt
Description
the .ppt (Powerpoint presentation) extension, separated by a pipe character.
dirs_pptx
the .pptx extension, separated by a pipe
character.
dirs_rtf
the .rtf extension, separated by a pipe character.
dirs_vcf
the .vcf extension (vCard), separated by a
pipe character.
dirs_vsd
the .vsd extension (Microsoft Visio), separated by a pipe character.
dirs_xml
the .xml extension, separated by a pipe
character.
dirs_zip
the .zip extension, separated by a pipe character.
dirs_jpg &
The path for JPEG files extracted from text
dirs_jpeg
documents (e.g. PDF files).
dirs_png
The path for PNG files extracted from text
dirs_tif & dirs_tiff The path for TIFF files extracted from text
file_max_error
If files of a particular type cannot be converted for any reason, they will remain in
their respective directory. When the total size of all files remaining in a particular directory reaches the value entered in
file_max_error, the Textreader will stop
with an error message and the files must
be manually removed from the directory.
file_max_size
Maximum size in MB of the files that can
_MB
be processed. If the size of a file exceeds
this value, it will be deleted and not processed. If a large value is entered here, the
RAM assigned to Tomcat may need to be
increased.
315
Textreader (ELOtr),
cont.
Parameter
Description
file_err_move_dir An existing directory can be entered here
and any files that cannot be processed will
be moved into this directory. If a value is
not entered here the files will be deleted.
convert not pos- Error value used when conversion fails.
sible value
ELOsx and ELOis
Parameter
user
password
ixurl
316
Description
The account used for ELO iSearch and ELO
iSearch Indexer. The default user created
when initially installing ELOenterprise is
ELO Service.
This is the password for the user account in
encrypted form. (Passwords can be encrypted by using password.bat.)
The URL of the Indexserver.
Appendix
Log Files
Various log files are written during ELO's installation as well as
afterwards when using ELO applications like the Access Manager. These files are found in various locations depending upon
whether ELOprofessional Server or ELOenterprise is used. The information contained in these files is useful not only when searching for errors, but also when analyzing the normal operation and
status of the ELO applications.
Tomcat
The standard location for the log files of the Tomcat application
manager is the sub-directory logs in either the Tomcat program
folder (ELOenterprise) or in the child directory of the same name
in the ELO program folder (ELOprofessional). If another path was
chosen for these files during installation, then they will be located
there.
tomcat7-stderr.*.log
and tomcat7-stdout.*.log
These two log files save any messages received from Tomcat. Messages from ELO can also occasionally be found within these log
files. Normally these logs must only be checked when problems
have occurred.
ELO Components
Separate log files are written for each of the ELO applications. These are located either in Tomcat's sub-directory logs
(ELOenterprise)or in the same-named sub-directory in the ELO
program folder (ELOprofessional)
am-*.log
as-*.log
This log file contains the log data for ELO Automation Services.
dm-*.log
This log file contains the log data for the Document Manager.
ft-*.log
im-*.log
Appendix
This log file contains the log data for the Access Manager.
This log file contains the log data generated when operating the
Fulltext module.
This log file contains the log data for the XML Importer.
is-*.log
This log file contains the log data for iSearch.
ix-*.log
This log file contains the log data for the Indexserver.
sx-*.log
This log file contains the log data for the iSearch Indexer.
317
tr-*.log
log4j
318
This log file contains the log data for the Textreader.
wf-*.log
This log file contains the log data for the form-based workflow
service.
serversetup.log
This log file contains the log data for the installation process and
is located in the server installation directory.
The log4j library is used by web applications and controls the storage of data in the log files. Each log file has an individual configuration file, log4j.properties, and the format of the log data
can be modified within this file. The default location for these files
is the ELO sub-directory ...\prog\serversetup\configdata\templates. The protocol level for the log file can also be
modified here by changing the level from INFO to DEBUG. Note
that changing the logging level to DEBUG can reduce performance significantly and cause the log file to grow exponentially
in size over time. The log files should be saved in an area of the
server where they cannot influence system performance by filling
up hard drives, for example. New log files are started every day
at midnight and the existing file is renamed with the appropriate
date at the end of the name. These files can be deleted at any time.
Normally no modifications to the configuration file or the log file
are needed. Further information on this subject is included in the
log4j manual from the Apache Software Foundation.
Appendix
Third-Party Licenses
Comprehensive information to the licenses can be found on the ELOenterprise or ELOprofessional installation medium. For the Apache License see http://www.apache.org/licenses.
Library name
Log4j
Jakarta Commons
Logging
Jakarta Commons
HttpClient
JDOM
Jakarta POI
Java Excel API
PDFBox
JZlib
Majix
Xp
Xt
Java Web Services
Developer Pack 2.0
2012 R2 JDBC Driver
Oracle 11g JDBC Driver
DB2 JDBC Driver
JAR-File
log4j-1.2.8.jar
commons-logging.jar
commons-httpclient- 2.0.jar
jdom.jar
poi-3.7-final.jar
jxl.jar
pdfbox-1.4.0.jar
jxl.jar
majix.jar
xp.jar
xt.jar
(diverse)
License
Apache SW Lic. 2.0
Apache SW Lic. 2.0
Apache SW Lic. 2.0
sqljdbc4.jar
JDOM License
Apache SW Lic. 2.0
GNU Lesser GPL
Apache SW Lic. 2.0
BSD
Mozilla Public Lic. 1.1
Xp License
Xt License
(siehe Textdatei auf der
CD)
Microsoft
ojdbc6.jar
Oracle
db2jcc.jar
IBM
319
Further references
It is impossible for this guide to cover all areas relevant to managing an ELO environment. If your question was not covered by the
present documentation, please visit the links below for further information.
Internet links
ELO partner forum: The ELO partner forum is a primarily German-language Internet forum where ELO partners can exchange
information on all topics relating to ELO. It is recommended
for non-German speakers to browse the website using the auto-translate feature in the Chrome browser. It is located at: http://
forum.elo.com.
ELO SupportWeb: The ELO SupportWeb provides links to all current documentation and program files. It is located at: http://
forum.elo.com/supportweb.
ELO Knowledge Base: This specific area of the SupportWeb deserves special mention. The Knowledge Base is divided into categories of server and client modules and deal with most common
ELO configuration issues. It is located at: http://forum.elo.com/
supportweb/en/knowledge-base.
ELO Documentation: This area of the SupportWeb provides complete documentation for all ELO modules, as well as current language files for the ELO Windows Client. The documents with Manual in the name are specifically designed to be useful for end users
as well as developers. The documentation is located at: http://
forum.elo.com/supportweb/en/documentation.
320
Appendix
Index
Access Manager, IBM DB2 - 127
Further references - 320
Access Manager, Microsoft SQL - 125
IBM DB2, Automation Services - 221
Access Manager, Oracle - 126,130
IBM DB2, ELOprofessional - 62
Access Manager installation - 119
IBM DB2, Fulltext - 185
Access rights - 311
IBM DB2, Indexserver - 147
Administration Console, installation - 252
IBM DB2, iSearch - 164
Appendix topics - 309
IBM DB2, Web Client - 246
Automation Services, installation - 216
IBM DB2, Workflow - 237
Automation Services, multiple - 226
IBM DB2, XML Importer - 209
Checklist, installation - 21
Indexing - 175
Coded information - 172
Indexing process - 172,173
config.xml - 313
Indexserver, Microsoft SQL - 143
Conventions - 8
Indexserver installation - 137
Copyright - 5
Installation, Administration Console - 252
Database user, creating - 41
Installation, ELOas - 216
Directory access rights - 311
Installation, ELOenterprise - 90,117
Disclaimer - 6
Installation, ELO software - 20
Document Manager, IBM DB2 - 127
Installation, Fulltext - 176
Document Manager, Microsoft SQL - 125
Installation, iSearch - 156
Document Manager, Oracle - 126,130
Installation, Linux/Solaris - 118
Document Manager installation - 119
Installation, Textreader - 192
Document storage - 13
Installation, Tomcat - 97
Document types, Fulltext - 191
Installation, Web Client - 241
elodb, user - 41
Installation, Windows Client - 277
ELOenterprise, Linux/Solaris install - 118
Installation, Workflow - 230
ELOenterprise, manual update - 271
Installation Information - 310
ELOenterprise, update - 259
Installation parameters - 313
ELOenterprise 9 server installation - 117
Internet links - 320
ELOenterprise installation - 90
iSearch installation - 156
ELO for Mobile Devices - 241
ixUrlBase - 69,153
ELOprofessional, manual update - 87
JAVA_HOME - 92
ELOprofessional, update - 72
JAVA_HOME, Linux - 95
ELOprofessional 9 installation - 45
JAVA_HOME, Solaris - 96
ELO Viewer, language - 275
Java, update - 260
External document links - 69,153
Java Client, install MSI - 292
Fulltext - 14,171
Java Client, install options - 291
Fulltext, installation - 176
Java Client, registry - 307
Index
321
Java Client install, AIO - 301
Textreader - 314,315,316
Java Client Webstart, install - 298
Textreader installation - 192
Java installation - 90
Tomcat, Linux - 107
Keywording - 175
Tomcat, Linux/Solaris memory - 111
Keywording, automatic - 173
Tomcat, Solaris - 108
log4j - 318
Tomcat, update - 260
Log files - 317
Tomcat installation - 97
Manual update, ELOprofessional - 87
Tomcat memory - 109
Memory, Tomcat - 109
Tomcat port - 97
Microserver architecture - 12
Trademarks - 6
Microsoft SQL, Automation Services - 220
Update, ELOprofessional - 72
Microsoft SQL, ELOprofessional - 59
User accounts - 17
Microsoft SQL, Fulltext - 183
Viewer - 274
Microsoft SQL, iSearch - 162
Viewer, installation - 274
Microsoft SQL, Web Client - 245
Web Client, installation - 241
Microsoft SQL, Workflow - 234
Web Client, versions - 241
Microsoft SQL, XML Importer - 208
Website, ELO - 320
Microsoft SQL Server 2012 - 22
Windows Client, installation - 277
Mobile Devices, ELO for - 241
Workflow, installation - 230
Non-coded information - 172

OCR analysis - 173
Operating system - 17
Oracle, Automation Services - 221
Oracle, ELOenterprise update - 268
Oracle, ELOprofessional - 61
Oracle, Fulltext - 184
Oracle, Indexserver - 145
Oracle, iSearch - 163
Oracle, Web Client - 246
Oracle, Workflow - 235
Oracle, XML Importer - 208
PermGen error - 109
Port 8080 - 97
RAM, Tomcat - 109
Re-indexing, iSearch - 169
Scalability - 15
SQL server configuration - 28
System architecture - 9
System requirements - 17
322
Index

En Elo Server 9

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

En Elo Server 9

Uploaded by

Copyright:

Available Formats

ELO

Document Management and Archiving Software

ELO server structure................................................................... 9

Microsoft SQL Server................................................................22

ELO Access Manager and Document Manager................ 119

ELO iSearch and Search Indexer..........................................156

ELO Textreader........................................................................ 192

ELO Workflow......................................................................... 230

ELO Java Client........................................................................ 291

This manual is intended to be used by system administrators. It

Whether documents are to be archived, searched for, forwarded

What to expect from

When especially important information needs to be conveyed by

Warning: This information must be noted, as otherwise program

The names of menus, options, dialog boxes, folders, references to

Notes and titles are highlighted in bold in this guide, as well as

ELO server structure

This chapter discusses the ELO server components in a general

ELO server structure

The ELO environment

ELO server structure

ELO Document Manager

The ELO Document Manager controls the documents (and their

ELO Access Manager

ELO Fulltext module

The ELO Fulltext module is a servlet that controls an additional

ELO server structure

Fig. Server Component Architecture

The Access Manager is responsible for the central administration

ELO server structure

Fig. Client logon

An individual Document Manager is required for each archive. The

ELO server structure

Fig. Archiving documents

ELO server structure

Fig. Full text indexing

The ELOenterprise services are scalable. Nearly all of the services

ELO server structure

Fig. ELOenterprise scalability

ELO server structure

The following installation guide is based upon the Microsoft

Please see the document titled System Requirements on the ELO

It is recommended to run both Tomcat and the database services

Fig. Creating a new user

Fig. New User dialog box

ELO installation software

Windows accounts: (name and password)

ELO Server Engine/Tomcat

Database administrator (default: sa)

ELO database user (default: elodb)

Service account (default: ELO Service)

Script user (manager-script)

Database type (MSSQL/Oracle/DB2)

Database storage location

Miscellaneous: instance name, authentication mode,

Computer name (names for ELOenterprise)

Microsoft SQL Server

A database must be running before the ELO server components

Microsoft SQL Server 2012 is one of the supported database types

Before installing SQL Server 2012, the Microsoft .Net Framework

Microsoft SQL Server

The SQL server 2012 installation starts automatically. The first

Fig. SQL Server Installation Center