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 Datacenter 64-bit
Windows Server 2022	Datacenter 64-bit Standard 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 minimum and exclusive 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.

Updates to enaio® may result in the minimum system requirements being increased. Keep this in mind when planning the sizing of the system.

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. Please also note the recommendations on system sizing.

Likewise, it can be possible to still have full operational capability of the test systems and demo systems 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	Exclusive memory: 8 GB Processor cores: 2	Address space up to 4 GB is available
enaio® appconnector	Exclusive memory: see below Processor cores: 2 Storage: 100 GB
Services 'index'/'search'	Exclusive memory: see below Processor cores: 2 Storage: 200 GB Operating system environment: 64-bit
enaio® documentviewer /  enaio® rendition-plus	Exclusive 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	Exclusive memory: see below Processor cores: 2 to 4 Storage: 100 GB
enaio® service-manager	Exclusive memory: see below Processor cores: 4 Data storage: >100 GB
Service 'ocr'	Exclusive 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	Exclusive 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	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® gateway	Central proxy and authentication function	256 MB	80
Service 'license'	Manages preconfigured licenses and controls the assignment to clients	128 MB	7371
EMS service 'mailstorage'	Creating e-mails	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	128 MB	7261
Service 'admin'	Microservice for service administration	128 MB	7273
'argus' service	Microservice for service monitoring	128 MB	7281
Service 'messaging'	Internal message service	512 MB	7311
Service 'dms'	Microservice for document management	4096 MB	7981 – 7989
'office365-client' service	Microservice for the Office 365 integration	1024 MB	8099
'office365-dashlet' service	Microservice for the Office 365 integration	256 MB	8091
'repositorymanager' service	Microservice for the SAP connection	1024 MB	8010
'archive' Service	Microservice for connecting to storage systems	768 MB	7530
'ccservice' service	Microservice for periodically checking the full-text index in projects.	2048 MB	8047
'migration' service	Microservice for migrating the full-text index in projects.	2048 MB	8048
'tagging' service	Microservice for tagging processes in projects	512 MB	7560 – 7569
'msteams-client' service	Microservice for the connection to Microsoft Teams	1024 MB	7111
'msteams-actions' service	Microservice for the connection to Microsoft Teams	1024 MB	7112
'osweb' service	Microservice for the webclient backend	1024 MB	7900
'restdashlet' service	Microservice for integrating enaio® coLab	256 MB	8282
'mailjournaling' service	Microservice for the e-mail transfer	512 MB	8100

An Elasticsearch service with version 7.16 is installed for full-text indexing. This is configured as follows:

Memory: 2048 MB/port: 8041

Office documents are only shown in enaio® documentviewer in high quality if Microsoft Office (2016, 2019, Office 365 – on-premises, 32- or 64-bit) has been installed with enaio® rendition-plus on the computer. enaio® documentviewer does not need Microsoft Office to work.

Ghostscript must be installed to generate TIFF files from the PDF format.

You need Ghostscript version 10.01.2 or later for security reasons.