Discontinuation of the 32-bit Application Server in enaio® version 10.0

Valid for: enaio® version 10.0

We are officially discontinuing the 32-bit application server with enaio® version 10.0. There will only be a 64-bit server available. Why are we going this route?

  • 32-bit servers are outdated as all server operating systems are now 64-bit.

  • enaio® performs better with the 64-bit application server because it can address more memory. It is especially noticeable in systems with many users and processes.

  • A significantly higher number of users can work on one system with the 64-bit application server, reducing operating and administrative costs.

  • We want to improve the focus of our quality assurance.

There are no incompatibility issues or disadvantages for you. In short,

  • server scripts (in the DMS and workflow area) are compatible under the following conditions (see the section on server scripts).

  • The long-term archive systems that the product previously supported (according to the enaio® Storage Guide) can also continue to be used with the enaio® 64-bit server

  • All officially supported APIs are compatible

  • All action DLLs are available

  • The client side is not affected

  • Administrative components and core services are not affected

You only need to follow the update procedure listed below when updating a 32-bit server to a 64-bit server. The amount of effort involved in performing the update is equivalent to migrating the hardware of the enaio® server at the very most and it depends on the number of documents archived in the system.

We want to give you sufficient time to plan for this since the release of enaio® version 10.0 is slated for May 2021. No maintenance will be provided for enaio® version 9.10 by 2023 at the earliest. Until then, you have time to prepare and implement the update to the enaio® 64-bit server.

Installing a 64-bit Server/Updating to a 64-bit Server

New Installation

32-bit server can no longer be reinstalled from enaio® version 10.0.

Updating an Existing System (32-bit to 64-bit)

The server is updated when the enaio® version is updated. The amount of additional effort involved is equivalent to migrating the hardware of the enaio® server. You can find the description of how to switch from a 32-bit server to a 64-bit system in the Documentation Portal here. Please also note the information on database settings in the system requirements.

Currently, it is not possible to update an ANSI 32-bit server to a UNICODE 64-bit server. For this reason, you always need to update an ANSI 32-bit server to an ANSI 64-bit server.

The following intermediate steps are required for updating the application server, starting from the existing enaio® installation:

Server Scripts

Server scripts run in the 64-bit server in a 64-bit script engine on version 10.0 and later. For this reason, all COM libraries used in the script must be 64-bit capable. We assume that only 32-bit COM libraries are used and available at all in existing systems. Adjustments to the runtime environment are necessary in order to also use the "legacy" 32-bit COM libraries in the existing scripts now running in a 64-bit environment.

With Microsoft Windows you can use registry switches to embed the 32-bit DLLs in a 32-bit runtime environment, which is then used by the 64-bit script engine. We will perform this adjustment automatically via the setup for basic OS components that we do not provide in 64-bit. The adjustments are always related to the components. For project-specific 32-bit components, these registry adjustments must be made manually, as they are not known to the product setup. You can find detailed instructions under Using COM Components Between Different Platforms (32-/64-bit).

Using these mechanisms, the compatibility of the server scripts is ensured for update projects and no further adjustments to the scripts themselves are required.

 

Archiving

The storage systems previously supported by the product can also be used with the 64-bit enaio® server without any adjustments to the database, as long as they have not already been discontinued by the respective manufacturer. If this is the case, the customer needs to migrate to the current storage system. Specifically, this refers to the storage solutions listed in the following table.

Supported Storage Systems

Manufacturer Storage name Storage version
(up to and including)
Interface Connection via the 'archive' microservice
Cloudian HyperStore 7 Proprietary API yes
Dell EMC Unity
(replaces VNX/Centera)
5.x file-based* No
Dell EMC ECS
(replaces Centera)
3.5 Proprietary API yes
FAST LTA 3404 Silent Bricks/Cube 2.3 file-based* No
Grau Data FileLock 2.3 file-based* No
Hitachi HCP 9.1.0 Proprietary API yes
Hitachi HCP 9.1.0 file-based* No
iTernity iCAS 3.7 Proprietary API yes
NetAPP Ontap 9.7 file-based* No

* CIFS/SMB/NFS

All other storage systems that are not included in the enaio® Storage Guide can be connected to the specific project using a custom driver.

Archiving with 64-bit servers is carried out either via the 'archive' microservice or via the file-based interface. Details on archiving via the 'archive' microservice are available in the documentation portal here. There you can also find information about the transition of the old 32-bit virtual archive drivers to the microservice-based ones introduced in the version 9.0.

Looking Forward Now

Plan an update to a 64-bit server in good time and test the update procedures. Unexpected side effects cannot be completely ruled out despite careful testing. Please contact technical support (support@optimal-systems.de) with any questions or problems during an update.