Orange County NC Website
Browse       Search
<br /> <br />“D” - 1 <br />SCHEDULE “D” <br />TECHNICAL REQUIREMENTS <br />Subscriber must meet the following requirements in order to take advantage of the Service. These requirements may be <br />amended from time to time by BiblioCommons in accordance with evolving technical standards in the industry. <br />ILS SERVER AND DATABASE <br />● The ILS server must be an instance of an ILS system as may be agreed to by BiblioCommons. <br />● The ILS server must offer or accommodate a reliable programmatic method: <br />○ to access cataloguing and patron data; and <br />○ to execute circulation requests on behalf of a User <br />○ to execute any other ILS-based services stipulated in this Agreement. <br />● Libraries must be able to provide the version number of the ILS application and its underlying database and <br />operating system. Database version is only required for CARL.X, Evergreen and Horizon ILSs. <br />● The ILS must perform user authentication via barcode and PIN (personal identification number) or password. <br />CONNECTOR <br />The Services will communicate with Subscriber’s ILS via a connector, which will either be locally hosted in Subscriber’s <br />network (the “Local Connector”) or hosted by BiblioCommons (the “Cloud Connector”). Connector type will be determined <br />based on Subscriber’s ILS. The following requirements will apply based on the connector type. <br />CLOUD CONNECTOR <br />Access <br />● Subscriber shall ensure that full access to the ILS API is externally available. <br />○ BiblioCommons uses technical and logical controls to protect its environment and to ensure that users can <br />only access and act on information for which they have authorization. <br />○ Any additional security requirements from Subscriber may be accommodated for a supplementary <br />implementation fee by written agreement. <br />LOCAL CONNECTOR <br />Tomcat Server <br />● There must be a new and correct installation of Apache Tomcat on a server (“the Tomcat server”) in the library <br />environment. Tomcat Manager must be installed using BiblioCommons’ pre-configured Tomcat instance, or <br />installed to meet BiblioCommons’ configuration requirements. <br />● There must be an instance of Java 1.8 on the Tomcat server, and it must be modifiable as BiblioCommons <br />requirements evolve. <br />● Tomcat must be available through Subscriber’s firewall to the BiblioCommons servers with sufficient privileges <br />and access required to comply with integration requirements. <br />● As required for monitoring and testing, BiblioCommons must be given unconditional SSH or Remote Desktop <br />access to the server running Tomcat. In the event that such access is not provided by Subscriber, the uptime <br />standard and remedy outlined in Schedule “C” will be void and additional subscription fees will apply (see “If <br />Subscriber Does Not Meet the Required Conditions” below). <br />○ Access must be provided through a single set of credentials. <br />● Applicable only for Symphony ILS: <br />○ The Tomcat Server must be installed on the same server in which any Unicorn/Symphony API server <br />commands are located. <br />○ For Unicorn/Symphony, the Tomcat Server must be run using the ‘sirsi’ user. <br />Docusign Envelope ID: 49D5B7A4-3432-4225-B626-F266F1A79679