My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for
SymphonyInstallation  
Updated Mar 31, 2011 by michelle...@gtempaccount.com

Symphony Installation

Prework:

  1. Download, install and test the Core Installation of the xcncip2toolkit. Find detailed instructions for the Core installation here



  2. Download, configure, install and test the Perl scripts that will communicate with the Symphony api:
  3. Download

    Download the XCNCIP2ToolkitScripts.zip from www.sirsiapi.org. This zip file contains one script for each supported service (acceptItem,checkinItem,checkoutItem,lookupUser). The user id and password for the www.sirsiapi.org site are available from the SirsiDynix API Wiki.

    Configure

    Each of the scripts will have to be modified to run on your server (e.g. Path to Unicorn) and to use your institutions data codes (e.g. FE - STATION LIBRARY, FW - STATION USER'S USER ID). Notes pertaining to this are included within the script files.

    Install & Test

    These scripts can be tested outside of the Toolkit by calling them directly through a web browser (for example): http://myserver.domain.edu/sirsiscripts/lookupUser.pl?id=123456789

Installing the Symphony connector:

Download the Symphony connector ZIP file from Google Code

The Zip file contains the following files:
  • driver.jar -- The connector Jar file.
  • driver_config.properties -- The Symphony connector configuration file.

Steps to install:

  1. Extract the symphony connector zip file



    Extract the contents of symphony connector zip into %NCIP_ROOT_DIR%\NCIP-instances\ncipv2\driver.

    Note: NCIP_ROOT_DIR% is configured while installing NCIPToolkit core.



  2. Configuration files

driver_config.properties - Contains configuration for connector service implementation classes.
Note: Change Sirsi script location (SirsiScriptURL) to point to the scripts on your server

Please Note:

At this time the Symphony connector does not implement the entire NCIP protocol for each service. The functionality is limited to the input and output needed for our particular project. Ideally, this connector can be built upon to include additional functionality. The input/output supported by this connector has been documented by the Extensible Catalog team here: https://spreadsheets.google.com/ccc?key=0Ah4r3w4XYLVddGNkUEdQWUdRblJua2ZBRUt6Y3cyTFE&hl=en&authkey=CLeiw9wM#gid=0


Sign in to add a comment
Powered by Google Project Hosting