Products
- Muse^® Federated Search, today’s most powerful of its kind, is known as best of multiple target searching and content normalization to a single data model.
- Muse^® Proxy is a highly customizable multi-platform proxy server, easy to use and manage, acting as a gateway to authenticated content.
- Muse^® Harvest is based on different types of controlled extraction, such as search, date or feed based. it features a consistent delivery record format.
  - Overview
  - Features
- Muse^® Hybrid brings a powerful new approach to content discovery by combining real-time global federated searching with high performance central indexed searching.
  - Overview
  - Features
Services
Support
- FAQ
- Downloads
About
Contact

FAQ Category: Muse User Interface Application

How can I set the maximum number of simultaneous sessions?

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: <MAX_USER_CONCURRENT_SESSIONS>. Note that this field sets the maximum number of simultaneous sessions for one…

Wich is the difference between “Total number of unique sources from all applications” and “Total number of unique sources used in group from all aplications”?

“Total number of unique sources from all applications” is the total number of SPs from all applications listed in the report. In this case, unique means that if the same SP appears in many applications it is counted only once. Also they are counted no matter if they are part or not of any group…

Under what circumstances does Muse produce an “Unsupported Query” error?

Here are some details about the query remapping mechanism in Muse: if a search on one or more search attributes is performed on a Muse Source Package, the ICE Search module analyses the Source Package CPB (capabilities) file and all the search attributes included in query which are not present in the CPB file are…

What happens when a query sent to Muse includes a limiter not supported by a SP?

If a search with limiters is performed on a Muse Source Package then all the limiters which are not supported by that Source Package are ignored – only supported ones are processed. There will never be an unsupported query caused by the presence of some search limiters in the query. This is valid for all…

We are trying to integrate the federated search engine into our site by adding a html form.Everything seems ok only that the search does not start.

The reason why the search is not automatically starting when using the following search form: <form name=”logonForm” action=”http://www.museserver.com/muse/servlet/MusePeer” target=”_blank” method=”get” onsubmit=”return beforeSubmit()”> <input type=”text” name=”query” size=”30″ value=””/> <input type=”submit” name=”submit” value=”Search”/> <input type=”hidden” name=”action” value=”logon” /> <input type=”hidden” name=”userID” value=”applicationid” /> <input type=”hidden” name=”userPwd” value=”applicationpassword” /> <input type=”hidden” name=”languageCode” value=”” /> <input type=”hidden” name=”templateFile” value=”/passThrough.html”…

What indices (indexes) can Muse search on?

Muse maintains a set of internally recognized index labels or attributes for use in queries. These are recognized within the Muse Query Syntax by the parser on input and stored internally. When a search statement is translated for a particular Source, the internal forms are translated (using a Source-specific Translator) into the actual indices the…