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. Click the ELO menu > System settings > Users.

The Users dialog box opens.

2. Click New user to 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 repository area in which the configuration files are located.

The user for ELO Automation Services is created and configured.

Rules folder

The Rules folder contains the defined processing rules.

Templates for processing rules are available in the sample data, if needed. They can be modified according to your needs.

If you define your own processing rules, file these rules to the child folder of the ELOas BaseRules.

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 installing (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 the 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 example for the repository arc901:

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

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

url: This row 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 row contains the ELO user name for ELO Automation Services to log on to the ELO Indexserver. Normally, you should create a separate account for additional services. This account should not be used by other users.

password: This row contains the ELO password for the ELO user account. This can be entered in plaintext for testing purposes. The report then shows a note about the corresponding encryption after the service starts. You can copy the text from the log into the configuration if you wish.

rootguid: This row 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.