Tomcat OPAC interface displays data from wrong instance
- Article Type: General
- Product: Voyager
Problem Symptoms:
* After upgrade, the OPAC interface for one Voyager database instance (xxxdb) is styled correctly, but searches retrieve data from a different instance.
Cause:
The /m1/voyager/xxxdb/tomcat/vwebv/context/vwebv/WEB-INF/web.xml file had the wrong value for XServicePort (where xxxdb is the Voyager Database Instance).
Example:
<context-param>
<description>
The port at which voyager XServices can be found
</description>
<param-name>XServicePort</param-name>
<param-value>7014</param-value>
</context-param>
Resolution:
1) Edit /m1/voyager/xxxdb/tomcat/vwebv/context/vwebv/WEB-INF/web.xml
2) Find the XServicePort section
3) Change the param-value to the correct port
Additional Information
If you are unsure of the correct port, check the Apache configuration: grep Listen /m1/shared/apache2/conf/ActivatedVirtualHosts/xxxdb_vxws_httpd.conf
Category: Opac
- Article last edited: 11/26/2013