What are the application (inactivity) timeouts in Muse?
There are three inactivity timeouts levels in Muse. In ascending order they are:
– application level
– WebBridge level
– ICE level
So the application times out before the WebBridge which times out before ICE. This means that values for the timeout levels must go in ascending order too where ICE is longest and application is shortest. Getting this wrong can mean that the WebBridge or ICE session could expire before the application session expires. In that case a user can still access application features but searches will fail because there is no WebBridge session (the application’s path to ICE) or no ICE session (ICE performs the search and returns results to the application).
Default values for these levels are as follows:
– application level15 minutes
– WebBridge level20 minutes
– ICE level30 minutes
To set each of the above timeouts, the user have to:
a) for application timeout: access the applciation settings via MCAA console
(Application General Settings>Interface Options>Logoff) and set the “Session Timeout” value as needed. Changes here affect only the application you’re editing.
b) for WebBridge timeout: edit the file
$MUSE_HOME/web/MusePeer.xml and modify the MAX_INACTIVE_INTERVAL tag. Values of this tag are specified in seconds. Http server restart is necessary to load this value. Changes here affect all applications using the Muse WebBridge.
c) for ICE level: edit the file
$MUSE_HOME/use/ice/ICECore.xml and modify the MAX_INACTIVE_INTERVAL tag. Values of this tag are specified in milliseconds. ICE server restart is necessary to load this value. Changes here affect the application on the installation.