System 1 – Notes, Thoughts, and Calculation

• MS SQL Server is installed on the application server. enaio® receives its own database, schema, and login for this. The specified resources are still available on the instance.

  MSSQL data and log files are located on the application server on F:\.

• WORK is centrally located – space requirement 1:1 in line with the generated object volume of imports.

  The rendition cache is also located centrally, calculated here as a cache size of 50 GB, two-year cache retention time at 10 GB/year.

• The size of the C:\ partition may be freely selected on all servers.

• enaio® components receive their own partition (here: E:\ on all servers).

• One Microsoft Office instance must be installed on server 2 (enaio® documentviewer).

• Full text: 25 to 30 GB per one million objects. Currently, 300,000 objects are in the system. Long lasting.

• Server 1 – CPU calculation:
  1 Windows, 2 MSSQL, 1 app server, 0.5 enaio® gateway, 0.5 enaio® appconnector, 1 buffer

• Server 1 – RAM calculation:
  1.5 Windows, 3 MSSQL, 1.5 app servers, 0.25 enaio® gateway, 0.25 enaio® appconnector, 1 buffer

• Server 2 – CPU calculation:
  1 Windows, 2 enaio® documentviewer, 1 enaio® service-manager, 1 Elasticsearch, 1 buffer

• Server 2 – RAM calculation:
  1.5 Windows, 3 enaio® documentviewer, 3 enaio® service-manager, 6 Elasticsearch, 0.5 buffer

Not all instances of enaio® capture should import at the same time (since there is only one application server).