System 3 – Notes, Thoughts, and Calculation

enaio® • 11.0 »

  • An MSSQL server is already available in the infrastructure. enaio® receives its own database, schema, and login for this. The specified resources are still available on the instances.
    Four CPUs with more complex rights system, 12 GB resulting from ten million objects.

  • WORK is centrally located – space requirement 1:1 in line with the object volume generated from Capture and by the REST interface.

    The rendition cache is also located centrally. The calculated cache size here is 100 GB. Long cache retention time for rapid dispatch to enaio® webclient.

  • 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 3 (enaio® documentviewer).

  • An app server with eight CPUs is required due to the complex rights system, the number of workflows, and for long-term archiving.

  • All services in the chain required for the enaio® webclient are duplicated or clustered.
    Browser > Load balancer > Gateway > WebClient > AppConnector > Appserver > DB

  • An external load balancer is required, which distributes 50 percent of the load to each of the two gateways.

  • No special features with regards to enaio® documentviewer and enaio® fulltext. Scaled up in line with database, still to be performed individually for each instance. Drive F:\ has a 500 GB buffer for up to approx. 12 to 15 million documents for the full-text database (if the number of documents increases, the RAM must also be scaled up accordingly; if not, the response speed decreases).

  • Due to high demand for OCR, four cores will be needed just for OCR. 1,800 pages could potentially be processed in an 8-hour workday (225 pages per hour, or 3.75 pages per minute).

  • Server 1 – CPU calculation:
    1 Windows, 3 app servers, 0.5 enaio® gateway, 2 enaio® appconnector, 1 enaio® webclient, 0.25 enaio® service-manager, 0.25 buffer

  • Server 1 – RAM calculation:
    1.5 Windows, 4 app servers, 0.5 enaio® gateway, 1 enaio® appconnector, 0.5 enaio® webclient, 0.5 buffer

  • Server 2 – CPU calculation:
    1 Windows, 3 app servers, 0.5 enaio® gateway, 2 enaio® appconnector, 1 enaio® webclient, 0.25 enaio® webclient, 0.25 buffer

  • Server 2 – RAM calculation:
    1.5 Windows, 4 app servers, 0.5 enaio® gateway, 1 enaio® appconnector, 0.5 enaio® webclient, 0.5 buffer

  • Server 3 – CPU calculation:
    1 Windows, 4 enaio® documentviewer, 6.5 enaio® webclient (consisting of: 4 OCRs, 1 search and index, 1.5 other services), 0.5 buffer

  • Server 3 – RAM calculation:
    1.5 Windows, 1.5 enaio® documentviewer, 3 enaio® webclient, 10 Elasticsearch, 0 buffer