FAQ

The default session timeout of a Muse Proxy Application is of 30 minutes. When the authentication session of the Muse Proxy Application is close to end, a Session Timeout warning pop-up and/or a Session Timeout warning window will appear. Each of them displays a message which notifies the user regarding the remaining time from the current authentication session. The time when the warning pop-up and / or a Session Timeout warning window will appear is configurable using the AUTHENTICATION_TIMEOUT_ALERT_WINDOW_DURATION field for the Application Web Module from the ${WEB_CONTEXT_HOME}/WEB-INF/web.xml configuration file. By default, this is set to 60 seconds before the Muse Proxy application session will end. The Muse Proxy Application interface is on top of other core layers, hence increasing the interface timeout value involves increasing the underlying timeouts to avoid the expiration of system sessions before the interface. The underlying timeout values must be bigger than the interface value, or at most equal. For example, to increase the application inactivity timeout to 60 minutes, the following must be done:

Increase timeout values at the system level

1. ${MUSE_HOME}/proxy/modules/handlers/RequestHandlerWeb.xml Edit this file on disk and change the value of CLIENT_SESSION_TIMEOUT to 3900000 . The default value is: (35 minutes) The new value: 3900000 (65 minutes)
2. ${MUSE_HOME}/proxy/webcontexts/NavigationManager/profiles/NavigationSession.xml Edit this file on disk and change the value of NAVIGATION_SESSION_TIMEOUT to 3600000 . The default value is: 1800000 (30 minutes) The new value: 3600000 (60 minutes)
3. ${MUSE_HOME}/proxy/webcontexts/NavigationManager/profiles/filters/MuseProxyAuthenticationToken.xml Edit this file on disk and change the value of AUTHENTICATION_TOKEN_TIMEOUT to 7200000 . The default value is: 3600000 (60 minutes) The new value: 7200000 (120 minutes) The value of AUTHENTICATION_TOKEN_TIMEOUT must be significantly higher than the NAVIGATION_SESSION_TIMEOUT.

For the new system timeout values to be considered, the Muse Proxy service must be restarted.

Increase the timeout value at the application level

  ${MUSE_HOME}/proxy/webcontexts/Applications/APPLICATION_ID/WEB-INF/web.xml This file can be edited in the Muse Proxy Administrator Console, Applications -> Manage Applications, hover the desire proxy application and click the WEB.xml button. Locate the AUTHENTICATION_TIMEOUT field and change its value from the default 1800000 (30 minutes) to 3600000 (60 minutes) To load the new value immediately, go to the Advanced -> Operations menu and click the Refresh Applications button.

The following must be done to achieve this functionality:

1. Search the $APPLICATION_HOME/www folder for files containing an HTML form called “logoffForm”.
2. In the files found at #1 add the following in the “logoffForm”: , where app_name is the name of the Application you’re working with.
3. In the $MUSE_HOME/web/www/logon folder create a folder “app_name”, if it doesn’t already exist, where app_name is the name of the Application you’re working with.
4. In the $MUSE_HOME/web/www/logon/app_name folder create a redirect.html file such as the example below:






Simply use the URL of the target page you want in place of "http://www.museglobal.com".

1) At the application level:

This can be done by changing the value of the “User Concurrent Sessions” field from the application’s properties using the Muse Admin Console.
The file from within the application which contains this setting is $APPLICATION_HOME/profile.xml, field: .
Note that this field sets the maximum number of simultaneous sessions for one user (application). New connections for the same user are rejected if the number of simultaneous sessions reaches maximum.

2) At the system level:

In the $ICE_HOME/ICECore.xml file there are 2 fields that control the maximum sessions:

Maximum number of simultaneous sessions. New clients are rejected if the number of simultaneous sessions reaches maximum.
Maximum number of simultaneous sessions for one user (application). New connections for the same user are rejected if the number of simultaneous sessions reaches maximum.

By default the configured values are:
100
25

This means that no more than 25 simultaneous sessions are allowed for an user/application and no more than 100 simultaneous sessions for all users/applications. The value of the MAX_USER_CONCURRENT_SESSIONS field must be always smaller or equal with the MAX_CONCURRENT_SESSIONS value. Also, when changing the value of MAX_CONCURRENT_SESSIONS one must be aware that the new value must accommodate enough sessions to cover the largest number of MAX_USER_CONCURRENT_SESSIONS set in the applications. It is not necessary nor recommended for this to be the sum of all MAX_USER_CONCURRENT_SESSIONS from applications.

Please Note:

The MAX_USER_CONCURRENT_SESSIONS value set in the $ICE_HOME/ICECore.xml file is the default one and it is being overwritten by the value from the application level. In other words the value from the application level has the highest priority.

A new Muse session starts every time you perform a LOGON action through the Bridge. The session is then active until you perform a LOGOFF action or until it times out. You may do multiple SEARCH actions through the Bridge in one LOGON session.

1) At the application level:

This can be done by changing the value of the “User Concurrent Sessions” field from the application’s properties using the Muse Admin Console.
The file from within the application which contains this setting is $APPLICATION_HOME/profile.xml, field: .
Note that this field sets the maximum number of simultaneous sessions for one user (application). New connections for the same user are rejected if the number of simultaneous sessions reaches maximum.

2) At the system level:

In the $ICE_HOME/ICECore.xml file there are 2 fields that control the maximum sessions:
Maximum number of simultaneous sessions. New clients are rejected if the number of simultaneous sessions reaches maximum.
Maximum number of simultaneous sessions for one user (application). New connections for the same user are rejected if the number of simultaneous sessions reaches maximum.

By default the configured values are:
100
25

This means that no more than 25 simultaneous sessions are allowed for an user/application and no more than 100 simultaneous sessions for all users/applications. The value of the MAX_USER_CONCURRENT_SESSIONS field must be always smaller or equal with the MAX_CONCURRENT_SESSIONS value. Also, when changing the value of MAX_CONCURRENT_SESSIONS one must be aware that the new value must accommodate enough sessions to cover the largest number of MAX_USER_CONCURRENT_SESSIONS set in the applications. It is not necessary nor recommended for this to be the sum of all MAX_USER_CONCURRENT_SESSIONS from applications.

Please Note:

The MAX_USER_CONCURRENT_SESSIONS value set in the $ICE_HOME/ICECore.xml file is the default one and it is being overwritten by the value from the application level. In other words the value from the application level has the highest priority.