FAQ

Most Popular

Load More

Latest

The configuration file for setting the SMTP_HOST, SUPPORT_EMAIL (the email address where problems are reported) and other SMTP characteristics such as port, SSL/TLS, username/password, certificates, is $MUSE_HOME/admin/MuseAdmin.xml. A description for each SMTP property can be found in the comments area of the MuseAdmin.xml file and in the “Muse Administrator.pdf” manual. The email settings from this file are used for sending a Source Problem Report using a Muse Administrator Console, like Muse Console for Applications Administration or Muse Console for Customer Support. Notes:
  • The SMTP_HOST must be configured to relay emails for the Muse server;
  • If the SMTP server uses a secure connection (SSL/TLS) you must provide the necessary certificates. If the SMTP certificate is signed by a known Certificate Authority like Verisign for example, which is in the JDK’s keystore, there is no need to provide the certificate anymore;
  • If the SMTP requires authentication then you must provide a working username/password too;
  • In order for the changes in the $MUSE_HOME/admin/MuseAdmin.xml file to take effect, the Muse HTTP or Muse Embedded Apache Tomcat server (depending on which is available in your Muse version) must be restarted.

Updating a Source Package installed in a Muse Application or adding a new one make use of the Global InfoBase service. The access to the Global InfoBase service is done with a username/password combination that were assigned to you by MuseGlobal.

The fact that you get “Source package decode error” messages when updating Muse Source Packages in the Muse Administration Console shows that you did not configure in your Muse installation the username/password for accessing the Global Source Factory service.

There are 2 ways for configuring the access details for the Global Source Factory service in a Muse installation:

  1. At the Muse system level. This means that you configure the username/password for accessing the Global Source Factory service at the system level and all administrative users like mcaa and mccs make use of it. To do this setting edit the ${MUSE_HOME}/factory/SourceFactory.xml file and fill in the GLOBAL_IB_USERand GLOBAL_IB_PASSWORD fields with the username/password that were provided to you by MuseGlobal. You should have there the startersf default restrictive details, just replace them with the ones provided to you. A restart of the Muse Embedded Tomcat server is required for this setting to take effect.
  2. At the administrative user level. This means that you can configure the username/password for accessing the Global InfoBase service individually, for each Muse Administration user (like mcaa, mccs). The advantage of this configuration is that you can specify different access details for the Global InfoBase service for each Muse Administration user. Another advantage is that the restart of the Muse Embedded Tomcat server is no longer required. Specifying the access details for the Global InfoBase service for a Muse Administration user is done through the Muse Console for Applications Administration interface (mcaa user) as follows:
    • login into the Muse Console for Applications Administration interface as the mcaa user.
    • go to the Users tab, locate the desired administration user, select it and click on the "Edit Properties" leftmenu item.
    • in the "Edit MAB User Properties" panel fill in the "Global InfoBase User Name" and "Global InfoBase User Password" fields with the appropriate values.
    • re-login into the Muse Administration Console if the setting was done for the mcaa user or login with the user for which the Global InfoBase details were updated.

Muse has the possibility to control the behavior of searches in cases when queries having unsupported limiters are launched. By unsupported limiter, we mean that one wants to search a source for records between 2 dates, even if the native site does not support this (i.e., does not have this option).

The control is done by means of the of the “Stop If Limiter Not Supported” parameter. It is a property of the Search Module and can be set by:
– logging into the MCAA Muse Console;
– selecting the desired application;
– selecting “Application Modules” from the left panel;
– clicking on the “Search Module” link.

The “Stop If Limiter Not Supported:” field appears along with 2 values that can be set:
– “Stop If Limiter Not Supported:” field on YES – if the limiters are not supported, the search will stop and no records will be retrieved;
– “Stop If Limiter Not Supported:” field on NO – if the limiters are not supported the search will bring results (searching by default without any limiter) with the warning “Unsupported limiter(s): …”

Categories: Muse Search, Sources

A Source Package can be added only once in each source group defined in an application. The Source Package name cannot be different – it will have the same name in all the groups it belongs to.

Categories: Muse Search, Sources

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 follows:
– login into MSC
– select an Application using the radio button
– select the “Sources” section
– go to “Configure” section
– click the “Advanced” button next to the Source Package to be edited
– the value for MNM entered in the “Link URLs” field must be empty

B) Removing additional MNM entries from Application level
The MNM entries can be removed from Application level using Muse Source Console (MSC) as follows:
– login into MSC
– select an Application using the radio button
– select the “General Settings” section
– go to “Navigation Management” section
– the value for the MNM at the Application level in the “Link URLs” field sould be empty, or that particular Source Package moved to the exclude section.

Note*: The MNM entries at the Application level are additional to the ones for individual Source Package level. So for each Source Package the the MNM entries set up for that Source Package plus the MNM entries set up at application level (A + B above) will be used.

Note**: in old Muse systems use for rewriting purposes the settings found in ${MUSE_HOME}/web/Users.properties. This method is obsolete now, so all the entries inside it of the form “application_id.navigationManagerMode” should be set to “none” (application_id.navigationManagerMode=none). This operation must be done after the values set here were merged with the ones from application level (see point B above).

Categories: Muse Search, Sources

Load More