FAQ

There are several methods for adding new resources into the Muse Proxy Application for handling the rewriting of vendor platforms, the recommended method is by using the Muse Proxy Administrator Console. The rewriting definitions for a vendor platform are stored in XML files, which we call Muse Proxy Sources.
Mainly the steps for adding a new Muse Proxy Source are:

1. Identify the source profile in the existing repository from the EduLib website by accessing this link:
   https://www.edulib.com/products/muse-proxy/support/muse-proxy-sources-profiles/
   Make use of the search functionality to narrow the results. Any term entered in the search box is searched in the source’s identifier and in the following field values from the source profile: NAME and DESCRIPTION.
   Once identified, click on the name link and a popup window will open with the details of the source’s profile. Click the Download Profile link to download the XML file.
2. Access your Muse Proxy Administrator Console, the URL should be of the form:
   https://proxy.domain.com/admin
   Login with the administrator user and the password that you configured during the setup.
3. Navigate to the left menu Aplications item, Manage Applications link. Locate the Muse Proxy Application in use and click on the Sources button to access the list of installed sources.
4. In the Sources page, click on the Create source from an existing profile icon, next to the Quick Filter search box.
5. In the new page, upload the XML file downloaded at step #1. Upon succesfull upload, you are requested to specify the Source Identifier value, place here the file name without the .xml extension. Also you can change the default name and description values for the source. When done, click the Create button.
6. The next step is to add the new source profile into a sources group. For doing this, in the Sources page click the Edit Sources Groups icon, next to the Quick Filter search box. In the new page click on the Sources icon from the Actions column, corresponding to the group in which to add the new source. By default only one group exists.
7. In the new Sources Groups page, click on the plus (+) icon found next to the new source in the List of available sources column.
8. Test by accessing a proxified link for the newly added resource. E.g. https://proxy.domain.com/applicationID?url=vendor_URL, where replace the hostname, applicationID and vendor_URL with the appropriate values.

MuseGlobal provides the following method for search and retrieval of EBSCOhost content: EBSCO Integration Toolkit (EIT)

This is a SOAP-based Web Service approach which provides the optimal combination of performance and completeness. You can find the EIT Source Packages by searching in your Muse Console’s “Add Sources” section in the “IDs Containing” field for the term EIT. EIT SPs have Source IDs which start with the string EBSCOEIT.

URLs:

The HTTP Source Packages for EBSCO search on the URL
http://search.ebscohost.com/. The EIT Source Packages use
http://eit.ebscohost.com/Services/SearchService.asmx as the Home URL and Search URL.

AUTHENTICATION:
Authentication for the EBSCOEIT Source Packages is two-fold.

1) Authentication for search and retrieval can done by user/pw (with the USER_NAME and USER_PASSWORD fields of the profile) or IP (with the CUSTOM_PARAMETERS field of the profile).

For search/retrieval authentication by IP, a value must be placed in the CUSTOM_PARAMETERS tag from the EBSCOEIT* source profile. Again, this is used to connect to and search a certain database. Using this IP authentication, you may be authenticated to a number of databases.

Example :
AUTH_TYPE=ip;IP_PROFILE=eit;IP_ADDRESS=1.2.3.4
where : IP_ADDRESS=your IP which authenticates to EIT.

Please note that your EBSCO account must be specifically enabled in order to use of EIT. The user/pw used for connecting to http://search.ebscohost.com/ will not work for EIT. Also note that the IP_PROFILE will be either eit or eitws; — this string matches the 3rd section of your 3-part EIT authentication string (ex. s123456.main.eit or s123456.main.eitws). Please check with EBSCO if you are not sure which it is.

2) The aforementioned authentication by IP or user/pw gives us access to the EBSCOEIT API, but it does not provide successful link navigation on the record links obtained.

For this, the PROXY_HOST and PROXY_PORT in the profile must be configured. IMPORTANT: authentication to EBSCO for link navigation is only done by IP.

Example :
proxy.you.com
9797

So, in conclusion, 2 IP authentication settings are needed: one (user/pw or IP) for accessing and searching the EBSCOEIT database desired and the other one (proxy IP) to successfully navigate on the record links obtained.

Questions about your EIT account status should be referred to Gregory Julien [GregoryJulien@ebscohost.com].