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 Tag: navigation

How do I keep an SP from being rewritten by the MNM (Muse Navigation Manager)?

The MNM entries are set: A) at individual Source Package level B) at the Application level To stop the rewriting for a Source Package, one must: A) Remove the MNM entries at individual Source Package level The MNM entries can be removed from the individual Source Package level through the Muse Source Console (MSC) as…

Where are the Navigation Sessions used?

The Navigation Sessions are used only by the ‘Navigation Manager’ Web Context (the Muse Navigation Manager component) to store useful data regarding a specific link navigation using a certain target site authentication context (cookies, referrer, next proxy access details, encoding etc.) through Muse Navigation Manager. This type of session is managed using an ID (named…

What is Proxy Chaining?

In Muse, there are 2 types of proxy chaining: a) “ProxyChaining” happens when the MNM chains with the proxy used for source authentication. In a Muse application where we have configured a MNM_HOST to re-write the record links and a PROXY_HOST to use for authentication we have the following scenarios: 1) If the MNM and…