FAQ

Most Popular

Load More

Latest

The Muse Embedded Tomcat is needed because it entirely replaces Muse HTTP Server which was also used for the internal XML protocol and for the XMLDB. The external Tomcat could not have been used for the XML protocols and XMLDB. If there are no other services than Muse in the External Tomcat then this can be disabled. Muse contexts should be deactivated from there. The Muse Embedded Tomcat will come with its own Muse contexts, thus everything will be ok. Also consider lowering the Java memory for the external Tomcat because Muse servers will not run in it anymore. If there is an External Tomcat running on the same machine which didn’t have anything in common with the Muse Servers then normally one doesn’t have to worry about the embedded Muse Tomcat server, because this one just takes the place of Muse HTTP Server, and since there were no conflicts between that External Tomcat and Muse HTTP Server there shouldn’t be any here. If it is a fresh install of Muse then the only conflicts are given by port 8005 as described below. This conflict was always present between the Muse HTTP Server and an External Tomcat. But in case there was no service running in that External Tomcat we recommend that is shut down and disabled so that it doesn’t start at boot time. In the rare event that there is an external Tomcat that is used both for Muse and for other external services and both Muse and the other services contexts are all defined on the same port (e.g. 80) and you don’t want to change the Muse port to another port (e.g. 8000) then the front end Muse Servlets will remain defined and further used in the External Tomcat server and the Muse Embedded Tomcat will be used for what Muse HTTP Server was used, namely for XML protocols and XMLDB. Regarding the port conflicts there should be none effecting you in normal situation. For rare events, the cases below would help troubleshooting a port conflict in case it would appear. – The Muse HTTP Server already conflicted with an external Tomcat on port 8005 used for internal XML Muse protocols in Muse and for Shut Down in Tomcat. Hence, because Muse HTTP Server and the external Tomcat co-existed it means that the port value was changed from 8005 on one side or another so that both were running. As the Muse Embedded Tomcat takes the Muse HTTP Server configuration the port 8005 should not be an issue. – In case the External Tomcat was connected to the Apache Web Server then the AJP ports will conflict and only one Tomcat will be able to run through the Apache Web Server. For this change the AJP 8009 port from the Muse Embedded Tomcat. However note that other changes to the interconnection between Apache Web Server and both Tomcats are necessary in order to differentiate which requests received by the Apache Web Server are redirected to which Tomcat. These are described in the document Muse External Servlets Engine (Tomcat), chapter entitled “Web service adapters for Tomcat”. – There can be other applications on the same machine conflicting to the External Tomcat. For this a netsat or fuser command can be run on Unix like environments. The Tomcat files were ports are defined are tomcat/conf/server.xml. Check these files both for the External Tomcat and for the Embedded also for the case when one modified in the past the default values of the External Tomcat server.

Elsevier does not permit HTTP access to their resources through federated search products. For federated search Elsevier provides specialized APIs for which we have the following Source Packages: ScienceDirectRESTXML, ScienceDirectRESTXMLBooks, ScienceDirectRESTXMLJournals and ScopusRESTXML.
Arrangements with Elsevier for this access must be handled by you (the partner), or by your customer, following the steps below:

Install Procedure:

1. You (the partner) or your customer must contact the Elsevier E-Helpdesk (for APAC: sginfo@elsevier.com) and tell helpdesk that MuseGlobal federated search or API needs to be enabled.
2. Helpdesk will be able to find the customer’s account (based on C* numbers), API key based on name (MuseGlobal) and generate appropriate instTokens.
3. Confirm with the representative that they have enabled the MuseGlobal federated search or API (not a different federated search product).
4. After Elsevier staff has enabled access for the customer, they will report this back to the customer or to you, the vendor, and will disclose the appropriate instTokens to the customer.
5. Using the Muse Source Console, upload appropriate the ScopusRESTXML or the ScienceDirectRESTXML Source Packages, as covered by your subscription.
6. Configure the Source Package(s), making sure to fill the API_KEY, INST_TOKEN parameters from “Custom Parameters:” at bottom of the page with the two instTokens provided by Elsevier. Contact Muse Support if this is not the case.
7. Test the Source Package while in the Console.

Categories: Muse Search, Sources

Load More