FAQ

The difference in the Content Mining (CM) results is given by the difference in the results returned by the sources. Using “Full Text” limiters limits the number and the ‘quality’ (with regard to the CM) of the results returned by the search sources. The configuration of the module and the different results returned by the different searches are factors that limit the number of terms in the “Refine your results” window. We actually don’t display any term unless its threshold weight is above 3, which usually means that the term must be found at least 2-3 times in the returned records. Of course the limit can be lowered to 1 so that the CM always returns something, no matter the search, but the results will not always be meaningful with respect to the search query. It will also waste quite a lot of heap memory since we will have to keep more terms into the main memory until they are being sent to the browser to be displayed. Having many CM terms is less important than having only the relevant terms even if it means that there is only one relevant term. The CM process must be focused on quality and not quantity.

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.

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.