FAQ

The “Login error: Maximum number of sessions for user … has been reached. Please try again later.” occurs when the application or system level limit on the number of simultaneous users is reached. Limits are built in by default as a protection against one single application logging in so many users that it occupies all the resources of the host server and other application users are effectively denied access. Under normal circumstances the limits can be set appropriately for the expected user population and available server resources (see below) so this error should not occur. But in the case of a software problem or some kind of robot targeting the application this is a useful line of protection. Note that Muse allows administrators to set these logon limits at both the application and system levels. These setting are kept in the MAX_USER_CONCURRENT_SESSIONS variable, which can be modified as follows: – system wide level: edit the $MUSE_HOME/use/ice/ICECore.xml file and change the value of the MAX_USER_CONCURRENT_SESSIONS tag. – application level ($APPLICATION_HOME/profile.xml): access the application settings via MCAA console (Application Actions > Edit Configuration Options) and set the “User Concurrent Sessions” value as needed. Changes here affect only the application you’re editing. Note: please be aware that low values can deny access too often while high values can allow unmanageable load on the server. We recommend multiple, small adjustments rather than a single large change.

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".

The Application ID must begin with a letter and can contain only letters, numbers, and underscores. However, the first character of an application ID can only be alphabetic (NOT a numeric or underscore). There is no limitation on the number of characters that the Application ID can contain (no length restrictions). Alphabetic characters can be upper or lower case.

Some suggestions regarding how Application IDs should be created might be:
– add a identifying prefix for each customer if a single customer has many Applications
– add a suffix with the creation date
– keep the ID as brief as possible, but still efficient and easy to identify/intelligible.

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.

The “:” character is a keyword in Muse syntax, used to search on the simple search formfor a complex query (example: to search on both author and title on the simple search form : “:CREATOR john AND :TITLE design”).

Note that words that contain a “:” character can be searched if the text is in quotes (ex: “asthma:”).