ELONIQ Platform

ELONIQ is an integration platform that runs as a Windows service or Linux service. It provides two web interfaces, a modular architecture and extensive integration capabilities.

What Can ELONIQ Do?

• Import documents — Automatically ingest from file systems, email mailboxes or CSV files into ELO or SharePoint.
• Export documents — Deliver from the DMS to the file system or via webhook to third-party systems.
• Process documents — Automatic classification (AI), barcode recognition, file conversion and metadata enrichment.
• Automate processes — Automation chains link multiple steps into complete workflows.
• Integrate systems — DATEV booking proposals, Dynamics synchronization, TANSS ticketing and more.
• Provide infrastructure — SMTP relay, file synchronization and reverse proxy as built-in components.

AdminUI vs. UserUI

The AdminUI is the central management interface. Administrators configure modules, manage users, monitor logs and control integrations here.

The UserUI is the interface for end users. It offers a dashboard with tasks, document search, upload functionality and a workflow inbox — without access to administrative functions.

Logs

ELONIQ logs all activity to a rotating log file (application.log). The following logs are available via the Log Center in AdminUI:

• System log — All platform messages (startup, module activation, errors)
• Audit log — Security-relevant actions (login, configuration changes)
• Module log — Activities per module (import jobs, export results, etc.)
• Service log — Component status (SMTP proxy, OmniSync, etc.)

Log level can be set in config.yml: trace, debug, info, warn, error. Default is info.

• Modular Architecture — Over 20 independent modules that can be individually activated and configured. Dependencies are resolved automatically.
• Two User Interfaces — AdminUI for system administration and UserUI for end users, each with its own port and permission model.
• Multi-DMS Support — Connect to various document management systems (ELO, SharePoint) via dedicated connector modules.
• Automation — Automation chains, policies and scheduled jobs for automatic document processing.
• Multi-Channel Notifications — Email, Discord, Teams, Slack, Telegram and browser push via the central messaging system.
• Integrations — Connect to DATEV, Microsoft Dynamics, TANSS and Centron for end-to-end business processes.
• Infrastructure Components — SMTP relay, file synchronization (OmniSync), reverse proxy (SecureProxy) as built-in services.
• REST API — Versioned API (v1) for programmatic access to all functions.
• Real-Time Updates — Server-Sent Events (SSE) for live notifications, log streaming and status updates.
• Multi-Language — Full i18n support in German, English and French.
• Document Processing — Import, export, classification, barcode recognition, file conversion and PDF processing.
• Security — TLS/HTTPS, CSRF protection, session management, API token management and role-based access control.
• Monitoring — Health checks, status monitoring, log rotation, backup management and Sentry integration.

1. Installation — Install ELONIQ as a Windows service or Linux service. The config.yml configuration file is created on first start.
2. Basic configuration — Set the instance name, license key and web server ports in config.yml.
3. Open AdminUI — Navigate to http://localhost:8080 in your browser. On first access, an admin user is created.
4. Set up DMS connection — Under Configuration, activate and configure the desired DMS connector module (ELO Base, SharePoint Base).
5. Activate modules — Under Configuration > Modules, enable the desired function modules (Importer, Exporter, Classifier, etc.).
6. Set up integrations — If needed, configure DATEV, TANSS, Dynamics or Centron under Integrations.
7. Set up components — If needed, configure SMTP Proxy, OmniSync or SecureProxy under Components.
8. Enable UserUI — Make the UserUI available to end users on port 8081 and create user accounts.
9. Set up monitoring — Configure log watcher, status monitoring and backup jobs for ongoing operations.

• Dedicated service accounts — Use a dedicated service user for each DMS connection (ELO, SharePoint). Never use personal accounts.
• Enable TLS — Enable HTTPS for AdminUI and UserUI in production environments, especially when accessed over the network.
• Regular backups — Back up the ConfigStore database and configuration files regularly via the Backup module.
• Monitor logs — Check the Log Center regularly for errors and warnings. Set the log level to info for production.
• Activate modules selectively — Only enable the modules that are actually needed. Fewer active modules means less resource consumption.
• UserUI for end users — Only grant end users access to the UserUI (port 8081), not the AdminUI.
• Manage API tokens — Use API tokens with minimal permissions for automated access. Rotate tokens regularly.
• Set timezone correctly — Configure the timezone in config.yml so that schedules and logs are consistent.

1. Minimal Configuration (Single Server)

app:
  instancename: MyCompany
  license: XXXX-XXXX-XXXX
  webserver:
    host: 0.0.0.0
    admin:
      port: 8080
    user:
      enabled: true
      port: 8081

2. Production Environment with TLS

app:
  instancename: Production
  debug: false
  timezone: Europe/Berlin
  webserver:
    tls:
      enable: true
      certfile: /etc/ssl/certs/eloniq.crt
      keyfile: /etc/ssl/private/eloniq.key
    auth:
      enabled: true
      session_ttl: 8h
      enable_csrf: true

3. Debug Mode for Troubleshooting

app:
  debug: debug  # Possible values: trace, debug, info, warn, error
  logpath: /var/log/eloniq/application.log

In debug mode, detailed information about API calls, cache operations and module actions is logged.

4. MariaDB as ConfigStore

app:
  configstore:
    type: mariadb
    host: db-server
    port: 3306
    database: eloniq
    username: eloniq_svc
    password: secret