Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    OPAC via Primo (OvP) not providing accurate data from Voyager in Primo

    • Product: Voyager
    • Relevant for Installation Type: Multi-Tenant Direct, Dedicated-Direct, Local, TotalCare



    Troubleshoot inaccuracies in OPAC via Primo (OvP) data from Voyager in Primo.

    Can show up as not getting data to display in My Account or the Locations area for a title.


    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.

    Check for problems in  This file contains variables which control the configuration of OvP such as item status text, text displayed when encountering borrowing or request blocks, the date and time formats, mapping for the Primo institute, and the connection information for WebVoyáge (for when you need to load certain request forms).

    Additional Information

    OvP depends on obtaining real-time data via web services (API) calls done from the Primo server (not the patron's browser like with RTA).

    OvP does matching with holdings data from the availlibrary tag in the PNX and gets item-level information for the Locations area in the display.

    OvP web services test template using http:

    http://{Voyager server}:{X-service port}vxws/record/{Voyager bib_id}/holdings?view=items&patron_homedb={home database_id}&patron={Voyager patron_id}&patron_group={Voyager patron group_id}&startPos=&noItems=100

    See also this related Primo documentation on OvP:

    Configuring OPAC Via Primo - Ex Libris Knowledge Center (


    • Article last edited: 04-Dec-2020
    • Was this article helpful?