Real Time Availability (RTA) not providing accurate data from Voyager in Primo
- Product: Voyager
- Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare
Question
Troubleshoot inaccuracies in Real Time Availability (RTA) data from Voyager in Primo.
Answer
Make sure the availability/unavailability and enrichment tag settings in the PrimoExp-*.ini files and PrimoExp.ini file match.
Make sure vxws is running.
Check the RemoteAddrValve setting for vxws in the server's server.xml file for access restrictions.
Check for errors in access logs (/m1/voyager/xxxdb/tomcat/vxws/logs/access*)
Check local firewalls.
Make sure Base URL is correctly configured in the Primo Back Office.
Additional Information
RTA depends on obtaining real time availability information via web services. RTA only updates the browser display, not the record in the Primo database.
The purpose of RTA was to remove the need for running the Voyager availability extracts (i.e., PrimoExp-Availability.ini).
Fall-back when RTA is not functioning via vxws is for Primo to display the information in the <availlibrary> tag in the PNX. PNX data are updated during extract.
RTA web services test template using http:
http://{Voyager server}:{X-service port}/vxws/VoyagerAvailabilityService?op=publish_avail&doc_num={Voyager bib_id}
See also these RTA-related Primo articles:
- Article last edited: 04-Dec-2020