Notes on Dedicated Server Hardware - Integration for Jack Henry jXchange - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Integration for Jack Henry jXchange

Integration for Jack Henry jXchange
Foundation 23.1

Hyland Software specifies that OnBase Web and Applications Servers be installed on server machines that are dedicated to that sole purpose. We do not support Application Server installations that place other applications, servers, or services on the same physical device.

Web and Application Servers must be dedicated purpose servers; they must not be used as a domain controller, DNS server, non- OnBase Web server, email server, print/database/file server, index server, proxy server, network backup server, jukebox manager, network performance monitor, OnBase Client processing workstation, or Workflow/API OnBase Client broker. Network and disk I/O hardware should be optimized for performance and redundancy. Two network ports can reduce server bottlenecks by using a segmented network for external and internal requests, where external requests are sent to the Web clients and internal requests are sent to the file and database servers. A Gigabit Ethernet connection to the file server and minimal latency connection to the database server are recommended.

The OnBase Application Server, combined with the OnBase Web Server, delivers both static and dynamic content utilizing Microsoft Internet Information Services and Microsoft ASP.NET technology. When both the OnBase Web Server and the OnBase Application Server reside on the same Microsoft Windows Server, high utilization may be seen during peak times. Retrieving search results lists in XML, rendering document images, executing text searches, and various retrieval-related queries place great demand on the Windows Server's hardware, especially the CPU(s) and I/O systems. The server is further loaded down when Microsoft IIS itself is required to perform HTTPS connection services on all content being served to attached browsers through HTTPS connections.

Workflow timers and OnBase processing, both manual and scheduled, should be run on separate servers or workstations. Due to the nature of IIS and how the Web Server utilizes memory, running these processes on the same machine can consume memory, bandwidth, and CPU resources at critical times when users or customers may be accessing the server. The risk of restarting IIS or rebooting the machine must also be kept to a minimum because either of these actions will cause connected users to lose their sessions and possibly lead to data loss.

With all these processing-intensive demands, it is imperative that dedicated server hardware be deployed for each OnBase installation. This will maximize performance, reliability, and maintainability.