# System 2 – Notes, Thoughts, and Calculation

enaio® • 10.10 »

- 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 instance.

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

  The rendition cache is also centrally located, calculated here as a cache size of 50 GB, approx. 8,000 pages per day == approx. three to four month cache retention time. Additional 50 GB as buffer.

- 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).

- The services are distributed roughly evenly. OSR3 and app server on the same host to make it possible to work against localhost.

- Elasticsearch with one replica on servers 1 and 2. enaio® documentviewer and OCR separate due to high number of read/write operations, separate LUN (F:\) for full-text databases.

- Server 1 – CPU calculation:
  1 Windows, 2 app servers, 1 OSR3, 1 Elasticsearch, 1 enaio® service-manager, 0 buffer

- Server 1 – RAM calculation:
  1.5 Windows, 3 app servers, 5 Elasticsearch, 2 enaio® service-manager, 0.5 buffer

- Server 2 – CPU calculation:
  1 Windows, 0.5 enaio® gateway, 0.5 enaio® appconnector, 1 Elasticsearch, 1 enaio® service-manager, 0 buffer

- Server 2 – RAM calculation:
  1.5 Windows, 0.5 enaio® gateway, 0.5 enaio® appconnector, 5 Elasticsearch, 2 enaio® service-manager, 0.5 buffer

- Server 3 – CPU calculation:
  1 Windows, 4 enaio® documentviewer, 0.5 enaio® service-manager, 0.5 buffer

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

Except for the more extensive requirements for enaio® fulltext, this is a standard scenario. An existing SQL server is shared. There is a central domain for filing, moderate document volume, and no special requirements.

If the SAP interface is not scheduled for weekly or monthly runs (i.e., the total amount of documents comes in several batches), expectations are that a reassessment will not be carried out until after three to five years.

Navigation | Navigate through the help pages using the table of contents on the left. If it is not displayed when the window width is small, you can temporarily show it via the hamburger menu on the right. Use the arrows on the toolbar to navigate to the next/previous page. You can show hidden areas. Use the toolbar to show all hidden areas at once:
--- | ---
Clicking the product icon in the header returns you to the beginning of the current area. Use the toolbar to access the initial page:

Full-text Search | The search does not feature case sensitivity. A search term is also found as part of a string. Multiple search terms in the exact order as entered will be found if they are enclosed in quotation marks (").
--- | ---
Boolean Operators | You can use the following Boolean operators:
AND | Finds the pages that contain all search terms. Spaces, '+', and '&' function the same.
OR | Finds the pages that contain at least one of the search terms. The pipe character (|) functions the same.
You can combine search terms and Boolean operators using parentheses. Example: Paul AND (Peter OR Meyer)
The current portal area is used for the search. You can use Google to search through all portal areas. Example: follow-ups site:help.optimal-systems.com

Please contact the OPTIMAL SYSTEMS technical editorial staff for questions and comments regarding the documention at dokumentation(at)optimal-systems.de.