Update Notes
As usual, all components must be updated by setup or MSI 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 64-Bit
enaio® server 64-bit can only be used against an Oracle database with a native 64-bit ODBC database driver from Oracle if the following registry entry is added to the DataBase key: String: AlternativeODBC / value: 1
Database Adjustments
Adjustments to the database are necessary for the update and are carried out automatically. Depending on the data, these adjustments can take much longer than usual due to the separation of links and notes in hit lists and database.
While the enaio® setup executes the adjustments, a log is made in the %temp% directory, and when finished, the log is saved in the \ server\log directory.
Full text: Elasticsearch
Elasticsearch needs to be installed in the 7.2.1 version with the version 9.10. Likewise, the existing index data needs to be migrated. Installation and migration take place before the update.
As of this version, the integration of Elasticsearch requires the configuration of user and password. It is no longer possible to configure an IP filter before Elasticsearch, as in previous versions.
Encryption of Client-server Communication
The update automatically encrypts client-server communication.
Make sure that all installed clients of the previous version are closed before carrying out the update. This can be achieved either via server notification to all logged-in clients of a server via enaio® enterprise-manager or network-wide using Windows tools.
Failure to do so can cause significant performance issues with enaio® server and an overflow of error logs.
When planning the update, it is important to consider whether third-party applications are connected to the enaio® system, for example, via the Java JDL interface. These are to be dealt with separately and may need to be adjusted individually before the update.
Old components cannot communicate with enaio® server after the update due to the encryption.
TLS 1.0 and 1.1
TLS 1.0 and TLS 1.1 are still supported by default due to backwards compatibility issues although these logs do not meet criteria set out in the latest security policies. Connections can be restricted to TLS 1.2 by changing the configuration of enaio® server and enaio® gateway. TLS 1.3 is still not supported.
-
enaio® server: Modify the osssl.cfg file in the server directory: MinProtocol = TLSv1.2
-
enaio® gateway: Integrate the security.properties file in enaio® gateway.
enaio® http-service
enaio® http-service was not converted to encrypted client-server communication and is therefore no longer available. Projects that use this service can be converted to enaio® appconnector.
Retrieve original file – DocumentFileService(/documentfiles)-/osrest/api/documentfiles/[id]/[page]
Retrieve PDF – DocumentFileService(/documentfiles)-/osrest/api/documentfiles/[id]/pdf
If you have any questions, contact Product Management. This will be discontinued starting from Version 10.
'organization' Microservice
The 'organization' microservice, which had previously been available as a beta version, will no longer be available. Its functions have been integrated into the DMS service.
If the service was installed, it must be disabled via the servicewatcher-sw.yml configuration file:
name: organizationservice / instances: 0
Afterwards, the organizationservice directory can be deleted.
'archive' Microservice
Archiving via the 'archive' microservice needs to be reconfigured; the structure of the configuration file was changed.
The 'archive' microservice was previously used for archiving with 64-bit servers; as of enaio® version 9.10 it can be used with 32-bit servers.
enaio® appconnector
enaio® appconnector serves as an interface to mobile applications and as a communication component that allows any application via REST structured access to enaio® server, among other things.
For an external connection of enaio® appconnector
- you previously used standard HTTP authentication up to and including enaio® version 9.0 SP1 (NTLM, HTTP SPNEGO Negotiate (Kerberos), and HTTP Basic Authentication (RFC2617)).
- As of enaio® version 9.10 the connection must be made via enaio® gateway. Standalone operation of enaio® appconnector with direct access is no longer possible.
enaio® webservices
Authentication: the 'EcmWsMtomWsSecurity' endpoint is no longer available and needs to be changed to 'EcmWsMtomServiceAuth'.
SAP Integration
The following activities must be performed and observed when updating installations with the SAP components enaio® data2ecm/jump2ecm:
-
Connections to enaio® are made exclusively via enaio® gateway; the connection data in SAP are to be switched to enaio® gateway.
-
Authentication to enaio® gateway needs to be done using the 'basic authentication' authentication method.
-
The network rules used (firewalls, NAT) need to be checked and potentially switched from the previously used port (default: 8050) to the port of enaio® gateway (default: 443).
-
An up-to-date SAP transport for enaio® data2ecm/jump2ecm, Version 3.4C, needs to be imported into all connected SAP systems.
enaio® documentviewer
The following hotfixes must be installed for enaio® documentviewer:
- enaio® documentviewer 9.10 Hotfix 3 from 14 August 2020
- enaio® gateway 9.10 Hotfix 13 from 17 August 2020
It was possible to call up the administration page without logging in due to errors in the integration.
The call is made via the following address:
http://<gateway-address>/osdocumentviewer/admin
Read-only Mode and Crosscheck Property in enaio® webclient
You can assign the Controlled by crosscheck property for text fields in index data forms in enaio® editor so they will be prepopulated when a value is selected in a structure tree catalog or when an add-on is selected. It is not possible to also assign read-only status at the object definition level to text fields with this property due to technical reasons. If you need to assign read-only status to these fields, it must be performed in an event script at the level of the deployed clients. If you are using both clients (mixed operation of enaio® webclient and enaio® client), then you need to create the corresponding event scripts for each one.
- Properties of text fields:
-
Event scripts:
Events
OnCreateCopy/OnMove: it was previously the case that the events did not run if the object already existed at the new location. They will be run now. The handoff file contains the new parameter 'OBJECTEXISTONTARGETLOCATION' that indicates whether this is the case or not.
Workflow scripts: scripts that previously specified the color of index data via the 'Flags2' parameter need to be switched to the 'TextColor' parameter.
Debugging Event Scripts
The components needed to debug scripts were removed from enaio® setup and client MSI starting from Version 9.10. These are not necessary in the general workstation environment and can lead to irresolvable interference with software packages of other manufacturers. If debugging is to be enabled on a single workstation, enaio® client must be installed at this workstation via MSI with the parameter REGISTER_MSDEBUGGER=1.
Access Rights with Clauses
Clauses on access rights in the clause syntax up to Version 8.10 are not correctly evaluated in some specific cases and also not converted. This only affects clauses on the date/time fields with operators '<', '<=', '>' and '>='. Other operators and fields are not affected.
If you use these types of clauses in your system, please update enaio® server, enaio® administrator, and enaio® client to the latest versions dated September 2020 or later. After you have done this, the clauses will be evaluated correctly and can also be converted to the up-to-date format.
enaio® client Network Setup
The enaio® setup is no longer able to run a network installation to access the shared network folder of a client installation.
Instead, a network installation is performed via the MSI package enaio_client_netsetup.msi. A reinstallation via the MSI package is required for an existing network installation.
'XSLT Directory Synchronization' Action
The 'XSLT directory synchronization' action synchronizes Active Directory data with the enaio® user administration. DSDE is installed and integrated for the AD connection by default. Since DSDE cannot be converted to LDAP-S, we recommend integrating the Softerra LDAP Browser:
-
Download Softerra LDAP Browser from the manufacturer's website and install it.
-
The PATH system variable must be modified to include the path to the installation.
-
The AD call also has to be modified.
No changes are necessary for existing installations that are not to be converted to LDAP-S.
MSI enaio® capture
enaio® capture can be installed via an MSI package as an alternative to a setup installation.
Setup installations cannot be updated via the MSI package; installations via the MSI package cannot be updated through the setup.
enaio® pdfa-dispatcher
Previously, the installation file for enaio® pdfa-dispatcher was copied to the server directory when installing enaio® server 32-bit.
The axvbdispatcher.exe installation file will now be copied to the desired location via an MSI. Updates are also performed via a reinstallation using MSI.
MSI Administration Components 64-bit
The 9.10 version provides administration components in a 64-bit version. enaio® enterprise-manager and enaio® administrator-for-workflow are installed to access a Unicode database.
The installation is performed via the enaio_administration_x64.msi MSI package.
These administration components are only used for specific projects for new installations with a Unicode database.
MSI Outlook Add-in for Drag and Drop
The new 'Outlook Add-in for Drag and Drop' add-in enables the drag and drop feature for moving e-mails from Microsoft Outlook to other applications. The e-mails are output in the 'EML' format.
The installation is performed via MSI packages:
OS_32bit_outlook_add-in_dd.msi for Microsoft Windows 32-bit and Microsoft Outlook 32-bit.
OS_64bit_outlook_add-in_dd.msi for Microsoft Windows 64-bit and Microsoft Outlook 32-bit or Microsoft Outlook 64-bit.