This section describes the general fundamentals of the ELOxc EWS system.

Technology

ELOxc is delivered with libraries based on Microsoft Exchange Web Services (EWS) for Microsoft Exchange 2010 and later. ELOxc uses EWS to access Exchange mailboxes and extract MIME data, which can then be stored in ELO repositories.

Configuration

ELOxc EWS, on the other hand, relies on a single multi-threaded instance that processes all published storage configurations. ELOxc.exe connects to the Indexserver to retrieve its processing actions from ELO.

In version 10.1, ELOxc EWS stores its configuration data in an XML file in the installation directory. Earlier versions of the software stored configuration data in the Windows registry.

Persistent changes

The configuration of ELOxc EWS provides virtually unlimited options for configuration.

ELOxc uses Exchange Named Properties to save item processing states. At least two processing states are supported at installation: "archived" and "finished". These terms are explained in more detail later in this documentation (see Archive action and Finish action). ELOxc also supports an unlimited number of account-defined states that are also stored as Named Properties.

When a message is marked as "finished", it will never be selected by ELOxc EWS for further actions. This status can be assigned regardless of whether a message has been stored in ELO or has been processed in any way at all.

ELOxc EWS also recognizes the attribute "EloArchived" set by ELOxc MAPI and does not process these messages, in order to support migration from the earlier architecture. ELOxc MAPI does not support the new attributes in ELOxc EWS. ELOxc MAPI ignores all items marked with an ELOxc EWS attribute.