Modules that use an Application Server do not reflect changes made in OnBase Configuration until after the Application Server is refreshed. You can refresh the Application Server by recycling its application pool or resetting its cache. For example, if you add a new print queue or a print format, you need to refresh the Application Server in order for the changes to be reflected in the Web Client. A refresh is not required for clients to reflect changes to user privileges and rights, because these configurations are not cached.
Recycling the application pools disconnects users who are logged on to OnBase through the Application Server or Web Server. Any unsaved work by these users will be lost. Application pool recycling should occur during scheduled maintenance hours when no users are connected to the Application Server.
To reset the Application Server's cache without recycling the application pool, use the Reset Cache option in OnBase Configuration. This option resets the cache for all Application Servers using the current data source. All clients and modules that communicate with the Application Server are affected when the cache is reset.
Using the Reset Cache option in OnBase Configuration or the Reset Server Cache option in OnBase Studio may have a negative impact on system performance. Requests to the Application Server will be forced to wait until the cache is rebuilt before they can be processed. Depending on the size of the OnBase system, as well as the current server load, the performance impact of resetting the cache may be severe. To avoid performance issues, only reset the cache of the Application Server during off-peak hours. For more information about the Reset Cache option in OnBase Configuration, see the System Administration documentation. For more information about the Reset Server Cache option in OnBase Studio, see the Studio documentation.
Changes can take up to a minute to take effect after a reset. Some changes will take effect without requiring users to log off; however, it is considered a best practice to have users log off and log back on to ensure all changes take effect. Notify users of changes only after the Application Servers have had time to reset.
The Reset Cache option should be used only for small, additive changes, such as adding a new Note Type. Do not use this option for large changes, such as Workflow process changes or removal of a configuration someone might currently be using. For large changes, schedule system downtime to recycle the application pool. For more recommendations, see the OnBase Configuration help files.