FAQ
FAQ by Product
Most Popular
Load More
Latest
$MUSE_HOME/admin/MuseAdmin.xml file, locate the Not seeing the SPs related data, as status, version, install and build dates, can point an issue with the Local InfoBase.
The most comon issues that have these results are:
1) XMLDB corruption
For more information about this, please see the “How do I perform a backup/restore operation of the XML database?” (1019) FAQ.
2) InfoBase Bridge not started due to a port conflict
Muse InfoBase Bridge is using the 8005 port, so please check the Embedded Apache Tomcat logs to see if there are any entries of the form (which point a conflict):
Address already in use: JVM_Bind:8005
This port can cause a conflict if on the machine there is an external Apache Tomcat (or other software) running and listening on this port. In case of Apache Tomcat, the 8005 port is used for shutdown and it is configured in the $TOMCAT_HOME/conf/server.xml. For other servers, please consult their documentation.
The advice is to change the port of external Apache Tomcat or any other software (not Muse) to something else, eg: 8115, and restart that server and Embedded Apache Tomcat.
The ports that need to be locally accessible are:
1. 2100 – Muse Z39.50 Bridge
Configuration file: – ${MUSE_HOME}/z3950/MuseZBridge.xml
Note: This port works as a client for the Information Connection Engine (ICE) server, but it is also a server for all the Z39.50 clients connecting to it.
2. 2504 – Muse ICE Server
Configuration file: – ${ICE_HOME}/ICECore.xml
Files that contain references to this port:
${MUSE_HOME}/web/MusePeer.xml;
${MUSE_HOME}/use/tools/ICEClient.xml;
${MUSE_HOME}/z3950/MuseZBridge.properties
Note: This port is also configured in all Muse bridges used for the Muse ICE Server (in either one of the following two files) (${MUSE_HOME}/ and in ${MUSE_HOME}/
3. 2505 – 3000 – Muse ICE Server
Note: This is the control port for the Muse ICE Server. If it is not accessible, the next port is used, and so on. An error is retrieved if none of the ports up to 3000 can be opened.
4. 8001 –8004, 8006 – Custom XML Bridges
Configuration file: – ${MUSE_HOME}/http/conf/contexts.xml or ${MUSE_HOME}/tomcat/conf/server.xml; ${MUSE_HOME}/
5. 8005 – Muse Local Infobase Bridge
Configuration file: – ${MUSE_HOME}/http/conf/contexts.xml or ${MUSE_HOME}/tomcat/conf/server.xml
Files that contain references to this port: ${MUSE_HOME}/factory/SourceFactory.xml
Note: This port acts as a bridge, the communication protocol being XML.
6. 8007 – Muse Admin
Configuration file: ${MUSE_HOME}/http/conf/contexts.xml or ${MUSE_HOME}/tomcat/conf/server.xml
Note: This port handles XML connections.
7. 8010 – Muse HTTP Server
Configuration file: ${MUSE_HOME}/http/MuseHTTPServer.xml or ${MUSE_HOME}/tomcat/conf/server.xml
Note: This is the Muse HTTP Server or Tomcat control port.
Note: If you want to access some of the above Muse services from the Internet or from machines other than localhost, then the port(s) corresponding to the desired service must be open to the machine making the request.
Further information about this can be found in the "$MUSE_HOME/doc/Muse Advanced Configuration.pdf"document, “Server Type Ports Opened by Muse within Local LAN Scope” chapter.
The ports that need to be accessible from the Internet are:
1. 8000 – Apache Tomcat or Muse HTTP Server
Configuration file – ${MUSE_HOME}/tomcat/conf/server.xml or ${MUSE_HOME}/http/conf/contexts.xml
Files that contain references to this port:
- ${MUSE_HOME}/factory/MuseInfoBase.xml
- ${ICE_HOME}/ICECore.xml
- ${ICE_HOME}/jaas.config
- ${MUSE_HOME}/proxy/jaas.config
- ${MUSE_HOME}/web/MusePeer.xml
2. 8443 – Apache Tomcat or Muse HTTP Server
Configuration file – ${MUSE_HOME}/tomcat/conf/server.xml or ${MUSE_HOME}/http/conf/contexts.xml
Files that contain references to this port:
- ${MUSE_HOME}/web/MusePeer.xml
- ${MUSE_HOME}/enrich/MuseEnrichmentService.xml
- ${MUSE_HOME}/enrich/index/index.xml
- ${MUSE_HOME}/z3950/MuseZBridge.properties
3. 9797 – Muse Proxy
Configuration file – ${MUSE_HOME}/proxy/MuseProxy.xml
Files that contain references to this port:
- ${MUSE_HOME}/web/MusePeer.xml;
- ${MUSE_HOME}/enrich/MuseEnrichmentService.xml;
- ${MUSE_HOME}/enrich/index/index.xml;
- ${MUSE_HOME}/z3950/MuseZBridge.properties
Note: Also configured in all Muse bridges that use the MNM: (${MUSE_HOME}/ and in ${MUSE_HOME}/
Note: This is the secured mode of the Muse HTTP server (SSL connections).
Warning: One of the server type ports Muse opens for its components may be occupied by other server programs. One
such example is the Ajp12 connector from Tomcat. See “${MUSE_HOME}/doc/Muse External Servlets Engine (Tomcat).pdf" manual for further reference regarding the ports used by Tomcat.
Warning: If one of the Muse Servers fails to start the user is advised to check the log file for detailed information.
Finding the message below in the log file means that the port is already used by some other Application. When such a
situation occurs a reconfiguration is necessary to change the port used by the respective Muse server or by the already
existing service.
Cannot listen on port
Note: Not all ports are required by all Muse installations. They are required only if the corresponding components are installed. For example, port 9797 is only required if the Muse Proxy is installed.
Note: All server type ports can be remapped. The best way to accomplish this remapping is by using the Muse PostInstall Configuration package, which makes this process simple and ensures that the correct files are updated.
Further information about this can be found in the "$MUSE_HOME/doc/Muse Advanced Configuration.pdf"document, “Server Type Ports Opened by Muse within Internet Scope” chapter.
If there is no proxy defined (Proxy Host field) in either the application level or Source Package level, then no proxy will be used, no matter the other proxy related settings (Proxy Port, Proxy PAC also) from either level.
Secondly, if there are proxy settings both at application level and at the Source Package level, then the Source Package ones will have priority over the application level ones.