Muse Search FAQ
Muse Search
MCAA > select application > expand "Application Modules" > click "Search Module" > "Stop If Limiter Not Supported" option.
“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 (they appear or not in the interface).
“Total number of unique sources used in groups from all applications” – This is the total number of SPs from all applications listed in the report. Unique meaning that if the same SP appears in many applications it is counted only once. Furthermore only the SPs that belong to a group (they are visible in the interface) are counted here.
The reason why the search is not automatically starting when using the following search form:
is that there are no SP targets provided on which to perform the search.
Specifying/providing the SP targets can be done in 2 ways:
a) Setting in the application the default sources for the searches. This can be done using the Muse Console for Customer Support or Muse Console for Applications Administration as follows:
– login into the Muse Console for Customer Support or Muse Console for Applications Administration, select the desired application and click on the “Setup and Organize Sources” left menu item;
– go to “Organize Sources” left menu item and click on the “Update Interface” sub-item;
– in the right section of the “Update Interface” panel check the Source Packages that should be selected as default from each defined group;
– press the Update button; this will update the interface for the default language with the selected Source Packages; if you want to specify default selected Source Packages for other languages available than the default one, select the desired language from the “Language” combobox and make the same operations, e.g. select the sources and press the “Update” button.
b) Extend the HTML form presented below and include the targets on which to perform the search. For example if one wants to perform the search on the XX and YY SPs, add the following lines inside the form:
The dbList parameter is documented in the “2.0 Use of MusePeer – Auto-logon and Pass-through mechanisms” chapter from the Muse Web Bridge Communication Interface.pdf document.
The Source Packages installed in a Muse application can be seen in the Muse Administrator Consoles (Muse Console for Customer Support or Muse Console for Applications Administration) as follows:
– login into the Muse Console for Customer Support or Muse Console for Applications Administration console, select the desired application and click on the “Setup and Organize Sources” left menu item;
– the source IDs (dbList values) are in the “ID” column of the sources listing.
Additionally, another parameter could be added: “reuseSession=true” parameter (also documented in the above mentioned chapter) in the HTML form so that the sessions are reused for consecutive usage of the passthrough form from the same end-user. For this add int he form above:
If all Sources work within a Muse application individually but some fail when they are searched together, this is an indication that the target site(s) and/or your Internet connection might be slow or under stress conditions.
First check the following:
– Is the Internet connection slow? Check independently (outside of Muse) to see if the network is generally slow. If so, increase the timeout for all Sources (see below), or possibly limit the number of Sources users search simultaneously to conserve bandwidth or relieve Source overloading issues.
– Do the same Source Packages always timeout no matter how many other Sources are searched simultaneously? In this case it is likely that the Source site is the problem rather than the network. Increase the timeout only for those Sources (see below).
– Does the machine running Muse have a high load? Stop unnecessary processes and/or increase the memory allocated to Muse servers. Check the “Search Details” (or “+” button) if it is available on the search page and look at the information icon for each failed source to see the cause of the failure. This will be useful in diagnosing where the problem lies.
In cases where the target site is working but the communication is slow for some reason the solution is to increase the
If you experience this problem only in only the Muse Admin Console (where a source works when tested individually but fails when tested in a group with others). You may have a different issue. See FAQ “Why do some Sources fail when tested in a group in the Admin Console but they work when tested individually?”
If all Sources work within a Muse application individually but some fail when they are searched together, this is an indication that the target site(s) and/or your Internet connection might be slow or under stress conditions.First check the following:
– Is the Internet connection slow? Check independently (outside of Muse) to see if the network is generally slow. If so, increase the timeout for all Sources (see below), or possibly limit the number of Sources users search simultaneously to conserve bandwidth or relieve Source overloading issues.
– Do the same Source Packages always timeout no matter how many other Sources are searched simultaneously? In this case it is likely that the Source site is the problem rather than the network. Increase the timeout only for those Sources (see below).
– Does the machine running Muse have a high load? Stop unnecessary processes and/or increase the memory allocated to Muse servers. Check the “Search Details” (or “+” button) if it is available on the search page and look at the information icon for each failed source to see the cause of the failure. This will be useful in diagnosing where the problem lies.
In cases where the target site is working but the communication is slow for some reason the solution is to increase the
If you experience this problem only in only the Muse Admin Console (where a source works when tested individually but fails when tested in a group with others). You may have a different issue. See Why do some Sources fail when tested in a group in the Admin Console but they work when tested individually?
Load More
Load More
Load More
Load More
Load More
“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 (they appear or not in the interface).
“Total number of unique sources used in groups from all applications” – This is the total number of SPs from all applications listed in the report. Unique meaning that if the same SP appears in many applications it is counted only once. Furthermore only the SPs that belong to a group (they are visible in the interface) are counted here.
The reason why the search is not automatically starting when using the following search form:
is that there are no SP targets provided on which to perform the search.
Specifying/providing the SP targets can be done in 2 ways:
a) Setting in the application the default sources for the searches. This can be done using the Muse Console for Customer Support or Muse Console for Applications Administration as follows:
– login into the Muse Console for Customer Support or Muse Console for Applications Administration, select the desired application and click on the “Setup and Organize Sources” left menu item;
– go to “Organize Sources” left menu item and click on the “Update Interface” sub-item;
– in the right section of the “Update Interface” panel check the Source Packages that should be selected as default from each defined group;
– press the Update button; this will update the interface for the default language with the selected Source Packages; if you want to specify default selected Source Packages for other languages available than the default one, select the desired language from the “Language” combobox and make the same operations, e.g. select the sources and press the “Update” button.
b) Extend the HTML form presented below and include the targets on which to perform the search. For example if one wants to perform the search on the XX and YY SPs, add the following lines inside the form:
The dbList parameter is documented in the “2.0 Use of MusePeer – Auto-logon and Pass-through mechanisms” chapter from the Muse Web Bridge Communication Interface.pdf document.
The Source Packages installed in a Muse application can be seen in the Muse Administrator Consoles (Muse Console for Customer Support or Muse Console for Applications Administration) as follows:
– login into the Muse Console for Customer Support or Muse Console for Applications Administration console, select the desired application and click on the “Setup and Organize Sources” left menu item;
– the source IDs (dbList values) are in the “ID” column of the sources listing.
Additionally, another parameter could be added: “reuseSession=true” parameter (also documented in the above mentioned chapter) in the HTML form so that the sessions are reused for consecutive usage of the passthrough form from the same end-user. For this add int he form above: