SMARTS Production has multiple active NOC Users spread across multiple regions working at different time zones and at night shifts.
As Admins of SMARTS, we don't know how the users keep the SMARTS GUI/Console/Thick-Client Connection when they are done for that day. If the Thick Client is idle with no end-user clicks on Alerts or Properties for about 15 minutes (Or Configurable time based on our use cases) Can we terminate that connection ?
How to terminate all Stale End User Thick Client Connections, if there are any.
All supported versions
Through the documents, we had found customer can set the parameter
-Dsmarts.inactivityTimeout
when you launch the Smarts GUI like so:
<BASEDIR>/smarts/bin/sm_gui.exe -Dsmarts.inactivityTimeout=<Time Duration in seconds>
However if customer opens mulptile consoles in the same session/at the same time, we've experience a "timer leak" scenario where the consoles will not close like expected.
The tentative release of SMARTS toward the end of January will address this issue. The fix is part of the SAM console so it would be enough if one only upgraded only the console portion. However, one should also upgrade the domain manager to keep the compatibility intact.