enaio® server
enaio® server must be run on a Windows server operating system. For this reason, you need to take into consideration licenses for the operating system. The same system requirements apply to load balancing scenarios. It is assumed for all operating systems that necessary security patches provided by the manufacturer are promptly installed. For installations at distributed locations, recommend checking and measuring the data throughput and latency of the network, in particular between the application server and RDBMS in order to verify its suitability in project scenarios.
Operating Systems
The following operating systems (including the service pack level) are supported by enaio®:
Operating system | Version | Service pack |
---|---|---|
Windows Server 2012 |
Standard Edition 64-bit |
|
Windows Server 2012 R2 |
Standard Edition 64-bit |
|
Windows Server 2016 |
Standard Edition 64-bit |
|
Windows Server 2019 |
Standard Edition 64-bit |
|
Windows Server 2022 | Standard Edition 64-bit |
enaio® supports server operating systems from the Long Term Servicing Channel (LTSC). Server operating systems from Microsoft's Semi-annual Channel are not supported for use with enaio®. Operating systems that are no longer supported by Microsoft are not supported. The Core versions of the Microsoft server are not supported.
Other Components
The following components have to be installed and must work properly to ensure secure and correct operation of enaio® server:
Component | Parameter/value | Comment |
---|---|---|
Connection to database |
Local or via high-speed network (1 Gbit) |
Please make sure there is enough memory available for local database operation. |
Connection to storage media |
Local or via high-speed network (1 Gbit) for work, cache, and archive media. |
|
Storage media |
Latency period <=60 ms |
|
Data backup |
A backup of the Work area and the database has to be executed on a regular basis. |
|
Network connection for client applications |
At least 100 Mbps |
|
Hardware Requirements
enaio® can be configured in many ways and covers an extremely wide field of application from small to very large systems.
The listed requirements are the minimum for the system equipment needed for a productive enaio® system to provide adequate operational performance for approximately 50 users in an average office scenario with average data processing.
This information is a set of non-binding guidelines. OPTIMAL SYSTEMS can only give a guarantee for a specific system environment on the basis of a customized system concept, which we absolutely recommend.
Likewise, it can be possible to still have full operational capability of the test systems, demo systems, or systems with only partially used functionality if the minimum system requirements are not reached.
The requirements are based on the assumption that the corresponding resources (memory, processor cores) are solely used by the relevant services, that is, they are not used by the operating system and other components that are installed on the hardware unit. If different services are operated on a shared hardware platform, the relevant values must be totaled (memory/storage, processor cores).
Parameter | Value | Comment |
---|---|---|
enaio® server 64-bit |
Excl. memory: 8 GB Processor cores: 2 |
Exclusive memory: At least enough memory for the operating system has to be added as a minimum system requirement. |
enaio® server 32-bit |
Excl. memory: 2 GB Processor cores: 2 |
Address space up to 4 GB is available (64-bit) |
Web server for |
Excl. memory: see below Processor cores: 2 Storage: 100 GB |
|
enaio® appconnector |
Excl. memory: see below Processor cores: 2 Storage: 100 GB |
|
Services 'index'/'search' |
Excl. memory: see below Processor cores: 2 Storage: 200 GB Operating system environment: 64-bit |
|
enaio® documentviewer / enaio® rendition-plus |
Excl. memory: see below Processor cores: 4 Online cache: >100 GB; see comment |
About 1 MB of storage is necessary for each document (8 pages). For example, 100 GB of storage are required if 100,000 documents are to be cached. |
enaio® gateway
|
Excl. memory: see below Storage: 100 GB |
|
enaio® service-manager |
Excl. memory: see below Processor cores: 4 Data storage: >100 GB |
|
Service 'ocr' |
Excl. processor core(s): 1 to 4 |
1 processor core is supported by the integrated ABBYY FineReader Engine by default. 1 to 4 can be connected through acquisition of additional licenses. OCR throughput is approximately 6 to 10 seconds per processor core. |
elasticsearch |
Excl. memory: see below Processor cores: 2 to 4 Storage: 400 GB Operating system environment: 64-bit |
As for indexing, fast internal memory is important for this server. We recommend having storage with 25% of the size required for all text documents to be indexed in the system. The VTX database doubles in size during an update. |
The enaio® services setup installs an Apache Tomcat and a JAVA JDK for each service. Separate product requirements apply for both. HTTP ports are reserved by the enaio® services setup and must not be used by other applications. The setup determines and assigns available shutdown ports.
All services have to be configured as follows in each installed instance:
Service | Description | Memory | HTTP port |
---|---|---|---|
enaio® documentviewer / enaio® rendition-plus |
Document display and conversion component |
1024 MB |
8070 |
enaio® appconnector |
REST service and enaio® detailsviewer |
1024 MB |
8060 |
enaio® webservices |
API web service interface service |
512 MB |
8050 |
enaio® gateway |
Central proxy and authentication function |
256 MB |
80 |
enaio® webclient |
Web server for enaio® webclient |
1024 MB |
The port is defined during installation. |
Service 'license' |
Manages preconfigured licenses and controls the assignment to clients |
128 MB |
7371 |
EMS service 'mailstorage' |
E-mail creation |
384 MB |
7361 |
Service 'extraction' |
Extracts XMP and meta data from files |
256 MB |
7211 |
Service 'ocr' |
OCR in conjunction with ABBYY FineReader |
512 MB |
7241 |
Service 'Search' |
Microservice for the full-text search |
2048 MB |
8040 |
Service 'Index' |
Microservice for full-text indexing |
2048 MB |
8045 |
Service 'discovery' |
Services registry |
64 MB |
7261 |
Service 'admin' |
Monitor for service monitoring |
64 MB |
7273 |
Service 'messaging' |
Internal message service |
512 MB |
7311 |
Service 'dms' | Microservice for enaio® coLab and SAP connections | 512 MB | 7981 |
An Elasticsearch service with version 7.2.1 is installed for full-text indexing. This is configured as follows:
Memory: 2048 MB/HTTP port: 8041
The enaio® Microservices 9.10 can only be operated in 64-bit environments. An update of earlier versions in 32-bit environments is not performed by the setup. This also applies to the updating of full-text indexing.
Office documents are only shown in high quality with enaio® documentviewer if Microsoft Office has been installed on the computer together with enaio® rendition-plus. The following versions of Microsoft Office can be used: Microsoft Office 2013, Microsoft Office 2016, Microsoft Office 2019, Office 365 – locally, 32-bit or 64-bit. As a general rule, enaio® documentviewer does not need Microsoft Office to work. Additionally, Ghostscript version 9.25 or later has to be installed for TIFF creation from files in PDF format.