LYNX Database Integration

The Series25 LYNX Interface uses a database integration to connect to any student information system which is hosted locally on an institution's servers.

The integration has two parts:

  1. A series of custom tables that track historical changes to SIS data
  2. The LYNX-APP, a lightweight Java application that exchanges data between those tables and the hosted Series25 database

All database integrations follow the same process for installing the LYNX-APP, but the LYNX history tables are constructed differently based on the SIS type and database management system. Follow the steps below for your SIS type and database management system to deploy the LYNX history tables, then install the LYNX-APP to continue the integration.

SIS type (DBMS)

LYNX History Table Installation

Banner (Oracle)

Deploy scripts in your existing SIS database to configure the LYNX history tables and triggers.

LYNX Database Integration - Banner (Oracle)

Campus Solutions (Oracle or MSS)

Deploy scripts in your existing SIS database to configure the LYNX history tables and triggers.

LYNX Database Integration - Campus Solutions (Oracle)

LYNX Database Integration - Campus Solutions (MSS)

Colleague (MSS)

Deploy scripts in your existing SIS database to configure the LYNX history tables and triggers.

LYNX Database Integration - Colleague (MSS)

Colleague (UniData)

Establish a new MSS database to hold LYNX history tables and configure the Colleague environment to interface with it.

LYNX Database Integration - Colleague (UniData)

Other

LYNX Universal is a generic implementation of the LYNX history tables used by other integrations.

Establish a new Oracle or MSS database (or use the existing one for your SIS) to hold the tables and create a method to populate these tables with data from your SIS.

LYNX Database Integration - Universal (Oracle or MSS)

Connecting LYNX Universal to Your SIS