Muse Search FAQ
Muse Search
“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 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).
The MNM entries can be set:
A) at the individual Source Package level
B) additional MNM entries can be set at the Application level
A) Setting MNM entries at the individual Source Package level:
The MNM entries can be set at individual Source Package level using the Muse Source Console (MSC) as follows:
– login into the MSC
– select an Application using the radio button
– select the “Sources” section
– go to “Configure” section
– click the “Advanced” button near the Source Package in the list that is to be edited
– the value for MNM must be entered in the “Link URLs” field
B) Setting additional MNM entries at application level
The MNM entries can be set at the Application level using the Muse Source Console (MSC) as follows:
– login into the 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 must be entered in the “Link URLs” field
Note*: The MNM entries at the Application level are additional to the ones set for individual Source Package level. So for a Source Package 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**: The MNM entries at the Application level are usually used when many sources at the Application level are using a WAM (Web Access Management) software such as ezProxy as this provides a way to add a MNM entry that is to be used by multiple sources. Except in the case of WAM software it is not recommended that MNM entries be set at the Application level.
Load More
Load More
Load More
Load More
Load More
The Application ID must begin with a letter and can contain only letters, numbers, and underscores. However, the first character of an application ID can only be alphabetic (NOT a numeric or underscore). There is no limitation on the number of characters that the Application ID can contain (no length restrictions). Alphabetic characters can be upper or lower case.
Some suggestions regarding how Application IDs should be created might be:
– add a identifying prefix for each customer if a single customer has many Applications
– add a suffix with the creation date
– keep the ID as brief as possible, but still efficient and easy to identify/intelligible.
The Application ID may contain alphabetic, numeric or underscore characters. The first character in an Application ID must be alphabetic (NOT numeric or an underscore). No other characters are allowed. There is no limitation on the number of characters the ID can have.
“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.
Load More
Deleting a Source through the Console deletes all entry points to that Source from the Console. The backup files are not deleted, however, so the way to access the .bak files for the Source is to add the Source to the Application again. The backups will be available through the Backup/Restore tab once the Source is relinked to the Application. Previous settings will be restored to the Source once the Restore process is done. (Please note that your restore is successful even though there is no on-screen confirmation.)
The procedure of creating a new admin user is fully described in the “Muse Console for Application Administration.pdf” document, chapter “Administrative Users Setup and Maintenance”.
A particular case of creating a new admin user is if that user must has rights only on one application. Thus, when selecting a grant entry to grant a permission, from the list of available options one must chose “Modify Application”. Having only this grant added, then only one application will be available to be selected for administration. In the list of available applications, the new admin user will only see the selected aplication.
There is a “Forgot your password? Recover it.” feature in the Muse applications. When clicking on it, an email containing the configured password will be sent at the user’s email address. For this feature to work, the email settings configured at the application level must be correct and working.
Also, this feature is accessible from within the application, in other words you must login into the application in order to access the “Forgot your password? Recover it.” feature.
In the case of an application configured with IP authentication for “in Campus” and Personal User for “off Campus” access, the end user can access the “Forgot your password? Recover it.” feature only from in Campus.
We strongly recommend using a Muse admin console to do an Application backup instead of creating a copy of the Application’s directory.
The backup/restore feature is available starting Muse 2.2.0.0 and was especially created for such purposes. It backs up an entire Application under the "${MUSE_HOME}/admin/tmp/backup/"
directory by creating a file with the name "${APPLICATION_ID}.${timeStamp}.bak"
for each backup action.
Multiple Applications can be backed up simultaneously – however, the restore is a “one Application at a time” process. Also, a single Application can be backed up multiple times; upon restore, the user is prompted with all the backups ever made for that Application.