Update Notes

enaio® 10.0 »

As usual, all components must be updated simultaneously – server, clients, services, and microservices.

Both functional and security-related errors may occur when accessing data if some components have not been updated.

The installation data can be obtained via the Service Portal. There, you can also request test licenses.

enaio® server

The 32-bit application server has been discontinued as of version 10.0. Adjustments are necessary for updates to 64-bit servers. 64-bit servers of version 9.10/9.0 can be easily updated to version 10.0 via setup.

enaio® version 10.0: Updates

The previous enaio® setup is no longer available with version 10.0. All updates and installations are made via MSI packages or individual component setups.

We provide a migration tool that adjusts the data from the previous enaio® setup and its previous installation directories in preparation of an update from versions 9.0 and higher. After the adjustments, updates of the installed components are possible via the new MSI packages or component setups in the existing directories. Configuration files are retained. The same holds true for files that were created there for specific projects.

The migration tool must be run on each workstation where components were installed via the previous enaio® setup.


MSI packages and component setups can be found under the installation data in a new directory structure:

  • Backend: server, services, optional services, Elasticsearch, FineReader.

  • Frontend: administrative components, clients, add-ons.

    The administrative components and enaio® client are available in 32-bit ANSI and 64-bit Unicode versions and can only be used in ANSI and Unicode installations, respectively. Clients in non-corresponding installations are stopped after startup with a corresponding message.

  • Prerequisites: technical components that may be required for components to work together.

  • Tools: applications used for specific updates and adjustments.

Updates within the version will be performed via updated MSI packages and component setups in the future. Patches are still delivered for enaio® server.

Update Process

With the discontinuation of the 32-bit server, starting point of an update to version 10.0 is always version 9.10 or version 9.0 with 64-bit server. This means that the migration must be performed before the update in installations with 32-bit server.

These are the work items for the update:

  • Copy the respective installation directories to the computers on which the update is to be performed. Installations via network directories can lead to errors.

  • Migration tool

    Run the migration tool setup.exe located in the \Tools\Migration\<Version>\Disk1\ directory on the computers on which the components were installed with the previous enaio® setup.

    Use the migration tool in a current version (creation date as of 24 April 2021, 5:12 p.m.; setup.inx as of 27 April 2021, 9:58 a.m.).

    The migration tool adjusts the data in the existing installation directories and is a prerequisite for ensuring that configuration files, project-specific files, and customer-specific files are retained and correctly integrated in the existing installation directories during subsequent installations.

  • Backend

    Install the backend components using the component setups from the appropriate directories into the existing installation directories.

    • Server

      enaio® server must be started after the update.

    • Services

      enaio® gateway must be installed after all other services for new installations; however, it is not necessary for updates.

    • Microservices/service manager

      If necessary, install new or previously unnecessary services, for example, the DMS service for enaio® webclient.

    • Webclient

    • Elasticsearch

      An update is only possible from version 9.10.

    • FineReader

      ABBYY FineReader needs to be uninstalled and reinstalled.

  • Frontend

    Install the frontend components using the MSI packages from the appropriate directories into the existing installation directories.

    • ANSI/Unicode administration

      enaio® administrator, enaio® editor, enaio® enterprise-manager, enaio® editor-for-workflow, and enaio® administrator-for-workflow will be installed.

      The included asinit.cfg file does not need to be adjusted for updates; the existing file is retained with the connection data.

    • ANSI/Unicode client

      The included asinit.cfg file does not need to be adjusted for updates; the existing file is retained with the connection data.

    • Capture

      enaio® capture is not supported in Unicode installations.

    • Add-ons/printer

    • Webclient desktop app

      enaio® webclient as a desktop application is automatically updated on startup with the update of enaio® webclient.

You will find other components in the directories that also need to be updated depending on your installation.


version 10.0 integrates Elasticsearch in the version 7.9.3. The update of Elasticsearch 7.2.1 from version 9.10 will be performed by the current Elasticsearch setup. No further adjustments are required. A migration is necessary when updating earlier versions.

ABBYY FineReader

ABBYY FineReader is updated to version 12.4 for version 10.0. To do so, ABBYY FineReader must be uninstalled from the setup it was installed with, and then reinstalled from the current FineReader setup. You will need a new license from OPTIMAL SYSTEMS. The version can be used temporarily with test license. No further adjustments are required.

enaio® webclient

Installation requirement: enaio® webclient requires the 'dms' microservice, in addition to the previous installation requirements. The DMS service is installed via enaio® service-manager and requires no further configuration by default.

Settings for enaio® gateway: Additional settings are required for enaio® webclient.

Form design: The responsive form design for enaio® webclient introduced with version 9.0 can no longer be disabled. If you have not yet changed the forms, check them after the update.

enaio® app for Smartphones and Tablets

The iOS version 7.1 is no longer supported. You need the iOS version 8 or higher.

TLS 1.2.

Due to reasons of backward compatibility, TLS 1.0 and TLS 1.1 were still used by enaio® server by default. This is no longer the case for enaio® server after an update to version 10.0. Only TLS 1.2 will be supported. Check your projects, if necessary, for their compatibility with TSL 1.2.

enaio® gateway still needs to be manually adjusted.

enaio® repository-manager

enaio® repository-manager was newly developed and will now be installed as a microservice. The configuration must be done again. The microservice provides configuration interfaces that simplify the configuration. It is not necessary to make changes within SAP and to the connectors. The SAP client component is now installed via an MSI package. Existing SAP client components need to be replaced.

Support for the ILM interface has been added.

An up-to-date SAP transport for enaio® data2ecm data2ecm/jump2ecm, Version 4.0A, needs to be imported into all connected SAP systems.enaio® jump2ecm

Import/Export: Excel and Access

When importing and exporting Excel and Access data, it is necessary to update the Microsoft Access Database Engine on the enaio® administrator workstation. A version of the Database Engine can be found under the prerequisites directory in the installation data. Check if Microsoft provides a more recent version.

Excel 3 and 4 are no longer supported.

DICOM import

The automatic action is no longer available.

Debugging Components for enaio® client

Components for debugging scripts used to be installed together with the installation of enaio® client. For licensing reasons, this is no longer possible. Instead, Visual Studio can be installed on the corresponding workstations. Visual Studio is available with different licensing models. Recommendation: Visual Studio Community Edition with workload 'Cross-platform .NET Core Development' installed.

enaio® client: Object Definition and Security System

enaio® client automatically updates the object definition and the security system at midnight every night. All hit lists are closed for this purpose.

E-Mail Deduplication

Configurations for e-mail deduplication in the 'mailstorage' EMS service are now also used by enaio® client. This enables the user to create another location or reference document for e-mails there as well, provided that is has been configured accordingly.

DMS service

Modifying functions and returns:

  • GET dms/objects/{objectId}/native/variants

    The original is now always returned, even if there are no variants.

  • Tables: The data had previously been attached by default when tables were updated. Now it is replaced (default: REPLACETABLEFIELDS=1).

If you are already using the DMS service, please check the processing.

SQL Queries in enaio® client

The action buttons of SQL queries used to execute scripts are active even if no hits are produced. This was not the case previously. Please note this change in behavior for scripts.

Apache Formatting Objects Processor

FOP will now be installed in the updated 2.5 version and integrated. Will be installed in the \etc\fop25 directory of the data directory. The corresponding registry key \Conversion\FOPPath will also be changed. The existing installation in the \etc\fop directory is retained. Adjustments also need to be made to projects using FOP.

enaio® service-manager

Spring Boot will be updated to version 2.3 when enaio® service-manager is updated. This changes in the interface of enaio® services-admin. However, there are no functional differences for configurations.

If the 'Connection to server failed' error message appears when launching enaio® services-admin, then reload the page. It will generally be shown correctly after reloading.

enaio® enterprise-manager

Some settings that are no longer evaluated were removed. For example, settings for the full text and for IMAP.