What are the practical differences between an IISRESET and recycling the application pool? There is an excellent article over at https://fullsocrates.wordpress.com/2012/07/25/iisreset-vs-recycling-application-pools/ that discusses the concepts in depth. With that in mind, how does this apply to OnBase in particular? I’m so glad you asked.
Modules that use the Application Server do not reflect changes made in OnBase Config until after the App Server is refreshed. In order of least to greatest user impact, this can be done by resetting the cache, recycling the application pool, or performing an IISRESET. (A refresh is not required for changes to user privileges and rights, because these configurations are not cached.)
Resetting the Cache
A cache reset can be performed at any time without kicking the user base out of their sessions. Changes will go into effect for each user the next time the user logs in. This also applies to any automated services you may have running, so remember to restart your timer service, etcetera. Changes can take up to a minute to take effect after a reset while the server cache is rebuilt.
To reset the cache, log into OnBase Config and go to Utils | Service Monitoring. This will reset the cache for all Application Servers using the current ODBC data source.
This option should be used only for small, additive changes, such as adding a new note type, print queue, or print format. 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.
Caution: 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. When a cache reset occurs, it triggers a memory dump. If more than one cache reset occurs within 5 minutes, then multiple memory dumps taking place can be very problematic to the health of an active production system. 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.
To identify who, when, and where a cache reset was performed, use the following query:
SQL
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED
SELECT u.username, ru.registername AS ‘Workstation Name’, sl.logdate, sl.messagetext
FROM hsi.systemlog sl
JOIN hsi.useraccount u ON sl.usernum = u.usernum
JOIN hsi.registeredusers ru ON sl.registernum = ru.registernum
WHERE actionnum = 7 AND subactionnum = 1
ORDER BY sl.logdate ASC
ORACLE
SELECT u.username, ru.registername AS “Workstation Name”, sl.logdate, sl.messagetext
FROM hsi.systemlog sl
JOIN hsi.useraccount u ON sl.usernum = u.usernum
JOIN hsi.registeredusers ru ON sl.registernum = ru.registernum
WHERE actionnum = 7 AND subactionnum = 1
ORDER BY sl.logdate ASC;
Recycling the Application Pool
Recycling the application pool immediately 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.
If you make a change to the web.config file, the corresponding application pool will automatically reset when you save the file. Again, remember to restart supporting services and automated tasks.
Performing an IISRESET
This is the “nuke it from orbit” approach. All application pools are reset and all OnBase connections are immediately dropped. The two most common times when this option should be used are when making changes to web.config files and to clean up any zombie connections that may be hoarding client licenses. The latter is the main reason Hyland recommends scheduling a nightly IISRESET. As always, remember to restart supporting services and automated tasks.
Note: You can set up a batch file to do the IISRESET and restart the windows services.
Hyland Resources: Studio MRG, System Administration MRG, Web Server MRG
