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

    NCIP over HTTP and HTTPS transport doesn't recognize the local ADM library

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Problem Symptoms:
    When communicating with an external application using NCIP over HTTP or HTTPS, Aleph is using the default USM50 as the relevant ADM library, even though there are entries in www_server.conf table in $alephe_root pointing to the local ADM. For example:

    setenv www_ncip_library_111.11.1.111 ABC50

    Cause:
    Faulty configuration in www_server.conf

    Resolution:
    The 4 octets in the dotted quad IP Address definition must each be 3 digits long. If shorter than 3, then must be zero-padded. Change the setenv variable in www_server.conf to this format:

    setenv www_ncip_library_111.011.001.111 ABC50

    NOTE: In Aleph V.21 and higher, the format of the setenv variable in www_server.conf uses underscores to designate the divisions of the IP Address, rather than periods:
    setenv www_ncip_library_111_011_001_111 ABC50

    Category: NCIP

    Subject: Communication over HTTP and HTTPS transport

    • Article last edited: 12/18/2014