Skip to main content
OCLC Support


Find an overview of the Amlib SIP2 Manager procedure.

SIP2 (Standard Interchange Protocol, Version2) provides communication between the Amlib Library system and other SIP2 compliant computer based applications. It provides controlled access to certain information from Amlib (for example details about Patrons or Items) via a TCP/IP connection through a nominated Port

These applications include Self-Service Circulation (DIY) terminals, accessing Ebooks from Online Suppliers, managing Library Internet PC processes such as PC Reservations, electronic resources and other communications. Ebook applications need to verify that a patron has proper borrowing rights before allowing downloads of Ebooks

Request messages to access information or perform operations are sent via a connection and the Response messages sent in return

There are three components that comprise the SIP2 module

    1. SIP2 Server which runs as a service in Windows
    2. Configuration Manager client program enables settings to be made in relation to:
      • Database (Database definition, Usernames and Passwords to the Database)
      • SIP2 Server settings (Database prefix, Port Number and maximum No of connections)
      • Logging settings (Enabling, Log Files and Archive Files)
    3. SIP2 Manager client program which is used to maintain the SIP2 settings including:
      • Listener
      • Instance settings. These include:
        • Parameters
        • Messages, Message fields and values

A Self Check device is the connection initiator and the SIP2 server is a TCP/IP listener

  • From Amlib Version 6.0, a multi-threaded SIP2 Server is a replacement for the existing Amlib DIY module. There can be multiple listeners using a single instance
  • The multi-threaded server supports multiple TCP/IP connections from SIP2 clients whereas the Version 5.3 and older versions of the Amlib DIY module only supported a single SIP2 client connection
  • Each instance has its own set of messages, message fields and parameters. The parameters are not dependent on SIP2 client vendor types. The new SIP2 Manager is able to be customised to a greater degree than in the previous versions, in relation to customised messages and parameters

Functionality exists within the SIP2 Manager for the creation, editing or deleting of Listeners, associated Instance parameters, Instance messages and Instance message fields and values

SIP2 redevelopment includes the reorganisation of existing parameters and addition of new parameters. The new parameters will facilitate vendor independent coding. It is possible to convert existing Amlib DIY parameters to the new SIP2 parameters during the Version 6.0 upgrade or later using the SIP2 Manager