FAQ

Muse source packages, by default, return only the metadata found in the native source’s list of results. The Ex functionality of a source means that when a search is performed on that source from the Muse interface the information brought back for each record includes information that normally can be found when the link to that record in the native web interface is accessed from the results list. If this functionality is desired, then the USE_EX_PARSER field from the SP profile must be “yes”(no quotes). Example: yes Please note that even if the source is free and the Ex functionlaity is desired, this field must be filled with “yes”. By default, this field is set to “no”. So such a connector will behave normally if the USE_EX_PARSER field from the profile is missing or has the “no” value, and will have an extended parsing if the USE_EX_PARSER field from the profile has the “yes” value.

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 MuseSessionID) stored in the path of the Muse Navigation Manager rewritten links. This ID has associated a Navigation Session object at server side that stores the information needed to serve the requests for that Navigation Session (cookies, referrer, authorization, proxy, encoding, etc.).

A Navigation Session is generated by Muse Proxy in the following cases:
– when a user navigates on a ‘Type 1’ rewritten link there is generated automatically a redirect to a ‘Type 2’ rewritten link. The ‘Type 2’ rewritten link generated has associated a new Navigation Session;
– when a user logs into a Muse Proxy application and navigates on a Muse Proxy source link there is generated automatically a redirect to a ‘Type 2’ rewritten link. The ‘Type 2’ rewritten link generated has associated a new Navigation Session.

Many Navigation Sessions can be created for a single client, each corresponding to the authentication context of each rewritten target site. All the Navigation Session objects created for a Muse Proxy client are stored inside the Client Session object associated with that client. There is no limit set for the number of Navigation Sessions associated with each client.