The following best practices are related to the Web Server, Application Server, or the Workflow Server.
-
Consider using a mechanism for distributing the load. Load distribution tools are very useful for optimizing Web Server performance in larger implementations. The Web Server handles all requests from Web Clients (Workflow Client and traditional Web Client). A large number of Workflow users and Workflow logic operating in an insufficiently configured web environment is a significant performance hazard.
-
Consider having a separate Web Server for Workflow Users. Direct Workflow users to a different web site on a different web server. Build the OnBase Web Server on two different machines and serve user processing needs appropriately to distribute the load.
-
Separate the Application Server from the Web Server. While it is possible to use the existing Web Server as the Application Server, it is not advised. By pointing the Application Server to the existing Web Server, all Workflow logic execution is performed by the Web Server whether requests are coming from the Web Client or OnBase Client. In addition to executing Workflow logic, the Web Server is processing requests from non-Workflow users in the Web Client. Because the combined processing load can be extremely heavy, the Application Server should be deployed on a separate machine.
-
Ensure the Web Server is a powerful machine. When using a single machine, the OnBase Web Server should be equipped to handle the combined load of web users and Workflow users. Increase the hardware resources on the machine to ensure maximum performance.
-
Increase Processing Power of Web Server/Application Server/Workflow Server. In the Web Environment, Workflow related and general OnBase processing is performed on the Web Server; therefore, it is essential for the Web Server to be configured to handle such loads. The Application Server functions very similarly to the Web Server except that it is dedicated to handling Workflow logic alone and does not also have to provide processing resources for custom queries, foldering, etc. The Application Server should be a powerful machine. By increasing the power of the Application Server, Workflow users will be able to process more work more quickly. Workflow Servers (machines that monitor Workflow timers) should be powerful machines to handle all timer work processing.
-
Off load work from machines not dedicated to handling such loads. If there is system work or ad hoc tasks that are performing intense activities against the document, one should off load the work to the Workflow Server. This enables the machine that initiated the work to “hand off” the work and dedicate system resources to those tasks it was designed to handle.
-
Recycle the Application Pool after making configuration changes in OnBase when using Core-based Workflow. Recycling the Application Pool immediately ends all user sessions. For this reason, it is recommended to perform this operation during non-peak or off-hours.