Update Notes

enaio® 11.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® service-manager

JDK 17

With JDK version 17, enaio® service-manager is provided with version 11.0. This means that JDK entries in servicewatcher-sw.yml are no longer needed and are no longer evaluated. Customer and project-specific services based on JDK 8 may need to be adapted.

The enaio® service-manager framework was upgraded to Spring Boot 3.


If certificates have been integrated into enaio® service-manager, then these must be reintegrated after the update.



The 'dms' service is installed in version 6.0. This version is not backwards compatible. If the service is used in projects, then adjustments are necessary.


The 'messaging' and 'tagging' services are not required and are no longer installed.

Microsoft Teams Services

The msteamsactions-prod.yml configuration file located in the \service-manager\config\ directory must be adapted. The previous 'zuul' section must be replaced by a 'gateway' section.

enaio® gateway and Kerberos

With JDK version 17, enaio® gateway is provided with version 11.0. This means that the weak encryptions DES3-HMAC-SHA1 and RC4-HMAC are no longer permitted by default. Administrators may need to adjust user profiles in the Kerberos environment.

For development and test systems, these encryptions may continue to be permitted at your own risk. To do this, the krb5.conf file in the \jdk\conf\security directory of enaio® gateway is required. This file can be copied from the existing directory before the update and then pasted or recreated:

allow_weak_crypto = true 

enaio® webclient

If you have not already updated enaio® webclient to version 10.10, then you can update directly to version 11.0. To do this, follow the instructions from the TRNs of version 10.10 using the installation data of version 11.0.

enaio® mobile

The current version of enaio® mobile requires Android 11 or iOS 15.


Elasticsearch will be updated to version 7.17.8 via the elasticsearch_setup.exe setup. This removes the need for adjustments to data and configurations.

ABBYY FineReader

ABBYY Finereader does not need to be updated when updating version 10.0 or version 10.10.

enaio® capture

The AXVBINAB subprogram has been discontinued and will no longer be installed. If configurations that have AXVBINAB as their subprogram have not yet been converted to the enaio® database synchronization subprogram, then this must be done with this update.

enaio® coLab

If you have not already updated to enaio® coLab version 10.11.5, then the login configuration for external users will have to be updated when updating to version 11.0.

enaio® mail-archive-service

enaio® mail-archive-service has been updated to version 2. enaio® mail-archive-service will be integrated via the new 'mas-smtp', 'mas-mailbox', and 'mas-storage' microservices. Updates will automatically delete the existing 'mailjournaling' service.

The services have to be reconfigured.

The license check is performed via the 'license' service. The 'MAS' license is integrated there by default.

If an existing 'MAS' license is already assigned to a station as a seat license, then it must be reassigned to the Station on which the service 'license' is running.

enaio® repository-manager

enaio® repository-manager has been updated to version 4.4.1. enaio® appconnector is no longer integrated. Connection parameters to enaio® appconnector will no longer be evaluated and can be deleted.

The technical user of enaio® service-manager from the application-blue.yml file will be used as the technical user by default. The enaio.dms.username parameter must be deleted unless another technical user is explicitly intended to be used with it.

The license check is performed via the 'license' service. The 'LR3' and 'ILM' licenses are integrated there by default.

If existing 'LR3' or 'ILM' licenses are already assigned to a station as seat licenses, then they must be reassigned to the Station on which the service 'license' is running.

enaio® erp-s Connectors

To use enaio® data2ecm, enaio® jump2ecm, and enaio® data2s in conjunction with enaio® version 11.0, at least version 4.4 of the three SAP connectors’ product transport must be imported into the SAP system.

Due to the discontinuation of enaio® webservices, adjustments to the connection settings are necessary.

The license checks are performed via the 'license' service. The licenses for the connectors must be integrated there.

enaio® data2ecm

Customizing enaio® data2ecm:

  • Previously, the address of enaio® webservices was specified for the connection to enaio® systems. Now, the address of enaio® gateway must be specified.

    This connection also applies for enaio® jump2ecm and enaio® data2s.

  • There, the system type for a call to enaio® jump2ecm via an .os file must be specified as 'R' or as 'W' for a call to enaio® webclient.

  • In every enaio® data2ecm project, the communication form /OSGMBH/DX_EXPORTER_HTTP or /OSGMBH/DX_EXPORTER_HTTP_NUC must be replaced by /OSGMBH/DX_EXPORTER_REST.

  • These adjustments must be made for all OS systems.

  • The systems must be accessible via the same enaio® gateway with basic authentication enabled.

  • All object types and fields in enaio® must have internal names, and these internal names must also be input or specified when customizing enaio® data2ecm.

enaio® jump2ecm

Calling a client from enaio® is done in accordance with the common connection settings of enaio® jump2ecm and enaio® data2ecm – that is, indirectly by calling an .os file or by calling enaio® webclient in the browser.

enaio® data2s

Using enaio® data2s is now only still possible in the new HTTP SOAP variant. The COM variant available for earlier versions in ANSI systems can no longer be used.

Before the update, please note that for the HTTP SOAP variant, new requirements are being placed on the SAP system and importing the product transport of the three SAP connectors in at least version 4.3 is also required.

In addition, all programs, scripts, and tasks that previously used the COM variant of enaio® data2s must be converted to the new HTTP SOAP variant. This is usually entails an increased amount of effort and cost during the update, which must be taken into account in the budget and schedule for the update.

WebView2 Control

With this version, enaio® client uses the WebView2 control from Microsoft, which is installed on Windows systems by default and is therefore also updated when Windows is updated.

If the WebView2 control is not installed, then with the installation of enaio® client, the MicrosoftEdgeWebView2RuntimeInstallerX86.exe or MicrosoftEdgeWebView2RuntimeInstallerX64.exe installer located in the directory of the MSI package is run automatically.

If the WebView2 control cannot be installed successfully, then the details preview and content preview will not be displayed with an error message in enaio® client. This particularly applies to Windows Server installations.
Then, reinstall the WebView2 control via the appropriate installer.

Outlook Redemption

The Redemption library that integrates enaio® is no longer registered. This helps avoid conflicts that may occur when third-party software accesses a registered Redemption library. Projects that require the previous registration via the client MSI must be reviewed.

Standard Ad-hoc Workflow and Taskflow

The osdefaultmodels.xml workflow model with the default ad-hoc workflow and taskflow has been updated and must be re-imported into enaio® editor-for-workflow.

Quickfinder Add-on

Previously, the Quickfinder add-on did not fully respect access rights when accessing other objects’ data. For example, data could be taken from objects to which the user had no access rights.

This behavior has been changed, and the access rights are now respected.