Please note: The following chapter describes a manual installation of ELOas after other applications have been installed. Normally, ELOas will be installed by default during the ELO server installation. You may have to make some adjustments.

ELO user

1. In the ELO menu, go to System settings and click the User manager entry.

The User manager screen opens.

2. Click the Add user button and create a new user with the name ELOas Service.

3. Assign the password elo to the ELOas Service user.

Information: The new user must have access rights to the part of the repository that the configuration files are stored in.

The user for ELO Automation Services has now been created and configured.

Rules folder

The Rules folder contains user-defined processing rules.

In the sample data, you may find templates for processing rules that you can adapt to your own requirements.

If you define your own processing rules, save these rules to the Rules child folder in ELOas Base.

as-<repository name>.xml

You must enter the path to the configuration directory in your ELO environment to the as-<repository name>.xml file before deploying the application. For the repository arc901, the file could look like this:

Example

After installation, the file is available in the configuration directory of ELO Automation Services.

Naming convention

The name of the configuration directory should start with as-, followed by the repository name. For a repository named arc002, the name must be <as-arc002>.

Log files

The output directory path for log files in the log4j.properties file - the same directory as the config.xml file - needs to be customized to the local installation paths. For the repository arc901, this would be:

In the config.xml file, the parameters for Indexserver access must be adjusted:

Please note: The port specified here (8080) differs from the default settings for ELOenterprise (8080, 8070, 8060) and ELOprofessional (9090).

url: This line contains the access path to the Indexserver. Please note that the URL is case-sensitive. If the incorrect case is used, the Indexserver will not be found.

user: This line contains the ELO user name that ELO Automation Services logs on to the ELO Indexserver with. Normally, you should create a separate account for additional services. This account should not be used by other users.

password: This line contains the ELO password for the ELO user account. You can make this entry in plain text for testing purposes. After starting the service, the report displays a note about the corresponding encryption. You can copy the text from the log into the configuration.

rootguid: This line contains the GUID of the ELOas Base folder. The GUID of the sample folder from the import data set is used by default. If you have created a separate folder for this data, you will find the GUID in the keywording information.

Please note: If you are creating a new user for this service, please consider that the ELO Indexserver only registers this modification after a delay. To make sure it is applied, you can delete the user cache on the Indexserver status page. This forces an immediate refresh.