Operation
The Search Service tool operates as a standalone web application on a Tomcat server. Once it is deployed, operations include modifying the configuration and leveraging the PDS and PDAP protocols to query data and metadata that has been extracted from the Registry (see the Search Core for more information). The following topics will be covered below:
Configuration
See the
Apache Solr website and
wiki for more information on configuring Apache Solr. More Search Service configuration changes TBD.
Common Errors
org.xml.sax.SAXParseException: A pseudo attribute name is expected.
This error usually means there is a typo in the Search Service Tomcat context file. More specifically, make sure the first line in $TOMCAT_HOME/conf/Catalina/localhost/search-service.xml matches this exactly:
<?xml version="1.0" encoding="utf-8" ?>
See
Deploying the Application in the Install Guide for more information on creating this file.
Provider net.sf.saxon.TransformerFactoryImpl not found
This error occurs when the saxon-9.jar is not in the classpath. The following are mitigation strategies:
- Verify the following line is in $TOMCAT_HOME/conf/Catalina/localhost/search-service.xml:
<Loader className="org.apache.catalina.loader.VirtualWebappLoader" virtualClasspath="/usr/local/search-service/lib/saxon-9.jar"/>
- Verify the path specified for virtualClasspath actually exists.
XSLT transformation error java.io.IOException: XSLT transformation error
This error occurs when the CATALINA_OPTS environment variable is not properly set, or set multiple times in /usr/local/tomcat/catalina.sh (or /etc/init.d):
export CATALINA_OPTS="${CATALINA_OPTS} -Dsolr.pds.home=/usr/local/search-service"
All Searches Return 0 Results
This error occurs when the Search Service is not populated with data. See the Search Core for information on populating the Search Service.
