Update Notes

enaio® • 10.10 »

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

The following services require JDK 17:

  • indexservice, searchservice, ccservice, migration, dashlet365, office365, msteams, msteamsactions, restdashlet, repositorymanager

Office 365 Services

Once enaio® service-manager has been updated, additions need to be made in the servicewatcher-sw.yml configuration file for Office 365 Services, dashlet365, and office365. As in the example, jdk: jdk17 must be inserted in each case.

- name: dashlet365
  type: microservice
  profiles: prod,cloud,blue
  instances: 1
  memory: 256M
  port: 8091
  path: ${appBase}/dashlet365/dashlet365-app.jar
  jdk: jdk17
  options:
  - -Dfile.encoding=UTF-8
- name: office365
  type: microservice
  profiles: prod,cloud,blue
  instances: 1
  memory: 1024M
  port: 8099
  jdk: jdk17
  path: ${appBase}/office365/office365-app.jar
  options:
  - -Dfile.encoding=UTF-8

New installations do not need any adjustments.

Scripting

Server jobs: The 'Client: Delete objects from recycle bin' system role was previously not considered for server jobs. This system role is now considered. System roles and access rights will continue to not be considered for server jobs for objects of an object type with the 'Mind security system - No' property.

Event 'OnCellFocusGained': The event has not been executed on read-only tables yet. This has been changed so that the content can be evaluated in this case as well.

COM Interface: Creating E-mails

The 'InsertNewDMSObject' method is no longer supported for creating e-mails via the COM interface. The 'ArchiveMailFile' method must be used. The EMS service is therefore used to create e-mails.

Restoring Previous Versions

Previously, 'Rights group control' fields were emptied when previous versions were restored. These fields now always contain their last value.

enaio® webclient

In this version, enaio® webclient is installed as a microservice with enaio® service-manager and has to be reconfigured with enaio® services-admin.

enaio® service-manager

The version 9.0, 9.0 SP1, and 9.10 versions of enaio® service-manager can be updated directly to version 10.10 if the latest services of the respective version have been installed before.

Elasticsearch

version 10.10 integrates Elasticsearch in the version 7.16.2. The update of Elasticsearch from version 10.0 will be performed by the current Elasticsearch setup. No further adjustments are required.

TLS 1.3.

TLS 1.3. is also supported along with TLS 1.2.

enaio® gateway now also supports TLS 1.2 and TLS 1.3 only.

AxPreview.exe

AxPreview.exe requires Windows components that are part of the Chromium version of Microsoft Edge. If this version is not installed on the workstation, then these components must be installed later. To do this, use MicrosoftEdgeWebView2RuntimeInstallerX64.exe or MicrosoftEdgeWebView2RuntimeInstallerX86.exe located in the directories of the enaio® client MSI packages.

Previously, the necessary components were installed automatically enaio® client was installed.

SAP Integration

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

enaio® version 10.0: Updates

Update Process

The starting point of an update to version 10.10 in this case is version 10.0. Please refer to the update notes for version 10.0, especially for updating the 32-bit server to the 64-bit server, if you are updating version 9.10.

These are the work items for the update from version 10.0 to version 10.10:

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

  • 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 'osweb' service.

    • Elasticsearch

      Updates from version 10.0 are possible without customization.

    • FineReader

      ABBYY FineReader does not need to be updated and does not require new a license.

  • 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 ANSI / Unicode

      enaio® capture is available for Unicode installations for the first time and can be installed.

    • Add-ons/printer

    • Webclient desktop app

      The MSI installer for a 32-bit version of enaio® webclient as a desktop application is no longer available.

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