This document offers hardware recommendations and hardware sizing guidelines for OnBase solutions. Every OnBase solution has unique characteristics that may impact hardware requirements. Considerations such as solution size, infrastructure design, security, and user access to documents are examples of solution characteristics that can impact hardware needs. A few examples of this include:
-
Solution size
-
Infrastructure design
-
Security and user access to documents
This document divides OnBase solutions into categories and provides hardware recommendations for these categories, and links for more information about designing an OnBase solution. The guidelines presented in this document are based on the experiences of Hyland Software technical personnel. Hyland Technical Services is available to assist with questions about the infrastructure of new and existing solutions. The information in this document is subject to change as technologies advance. We hope this document assists with your OnBase infrastructure discussion.
Virtualization, or the use of virtual machines, is supported, but is outside the scope of this document.For more information about using OnBase in virtual environments, see Virtualizing OnBase on the Hyland Community Web site.
For software requirements, refer to the Technical Requirements Overview for New Installations and Upgrades as well as the individual module reference guides.