Settings for ELOas can be viewed and edited in this area.

Installation and basics

The manual installation of the ELOas (ELO Automation Services) module is described below. In ELOprofessional, the module is automatically installed during the server installation. For a post-install process or in a distributed environment, you need to install and update ELOas manually.

In addition to the installation packages for the ELO Administration Console, there is a separate installation package for ELO Automation Services containing scripts and sample scripts that provide access to various functions and libraries.

Step by step

Installation of ELO Automation Services (ELOas)

Information: The scripts required for ELOas can be installed from the "ELO Scripts - Installation Overview" website.

1. Go to the following URL in your browser:

http://www.forum.elo.com/script/eloinst-en.html

The scripts you need are in "ELOasJavaScriptLibrary - JavaScript files for ELOas".

Warning: You need to be logged on as an administrator to install additional modules.

2. Click the link Install module for ELO 11 now.

The Automatic installation of a new module dialog box appears.

3. Click Allow installation.

The scripts are automatically installed to the ELOas Base folder of the repository you are currently using.

After the installation is finished, a message saying Installation completed will appear in the ELO Java Client. The scripts have been installed to the JavaScript child folder.

The rules for ELO Automation Services, the translation lists and the basic scripts are available in the ELOas Base folder of the ELO repository. You need to define the connection to the ELO Indexserver and the base folder in the configuration.

Warning: Check the ELOas Base folder GUID in the repository and compare the GUID with the settings in the ELOas configuration file.

config.xml for ELOas

<Path to the installation folder of the Tomcat Application Server>\config\as-<repository name>\config.xml ("rootguid").

Information: The path to the config.xml file may be different if you have installed ELOenterprise.

Information: If required, modify the settings in the log4j.properties file. Enter the path to the log file for the newly installed ELO Automation Services. The variable log4j.appender.FI.File must contain the path to the log file.

Example

log4j.appender.FI.File=d:/ELOenterprise/logs/as-Arc801.log

In the log4j.properties file, a directory is defined where the log files will be saved.

Information: You may need to modify your database connection in order to be able to use ELO Automation Services. A Microsoft SQL database is configured in the following example.

1. Select the Imports folder of the imported JavaScript child folder.

2. Switch to the Start tab on the ribbon.

3. Click Keywording.

The Keywording dialog box opens.

4. Click the Extra text tab.

5. Enter the computer name (here: Jupiter) in the script that is stored on the Extra text tab of the Imports folder. Example:

url: 'jdbc:sqlserver://jupiter:1433'

Alternatively: If ELO is used in combination with an Oracle, PostgreSQL, or DB2 database, then the scripts must be configured as shown in the example for Microsoft SQL Server. The database connections will be triggered in the scripts based on their consecutive numbers. The count starts at 1 on the first connection.

6. Enter the user name and password of the database user whose account ELO uses to connect to the database.

7. Click OK.

The modifications in the script have been applied. ELO Automation Services now has all the required information.

Please check the ELO Automation Services status page after restarting the ELO Application Server (Tomcat Manager, ELOprofessional Application Server Manager).

8. Open the ELO Application Server by entering its URL in the browser.

Example

http://localhost:9090/manager/html.

9. Click the entry for ELO Automation Services in your repository.

Information: You have not defined any rules (rulesets) yet. The status report will not be displayed.

The ELO Automation Services status page is displayed.