What is the Transferology Connector?

...

Compatible with u.achieve and DARwinFormerly known as:
u.select Connector, CEGXML, CEG, XML Interface, External CEG

Network Architecture

Image RemovedImage Added

Minimum Requirements

Java 6, 7 or 8

Java application server (we recommend Tomcat 7 or 8.5)

CollegeSource tables, uAchieve 4.4 minimum table definitions:

...

...

JDBC Driver compatible with your database

For degree audits, minimum degree audit server version:

...

u.achieve server 4.

...

2.

...

2 or higher.

External Firewall

The school’s firewall must allow Transferology and the Transferology Connector to communicate:

• PROD Transferology 20618.251207.24624.21242
• TEST Transferology 21623.6822.115104.16435

Internal Firewalls

If the JDBC connection traverses an internal firewall, then TCP keepalive must be enabled between the school’s java application server and database.

...

• Table definitions
• Database user and password for jdbc connection
• Database user access privileges

DARwin Table Access

Equivalencies require Select on:

• mastref
• mastref_address
• tca_master
• tca_rule
• tca_source
• tca_target

Degree Audits require Insert, Update, Delete and Select on:

• job_queue_sysin
• job_queue_detail
• job_queue_list
• job_queue_accept
• job_queue_course
• job_queue_subreq
• job_queue_req
• job_queue_out
• job_queue_destination

uAchieve Table Access

Equivalencies require Select on:

...

• job_queue_sysin
• job_queue_detail
• job_queue_list
• job_queue_accept
• job_queue_course
• job_queue_subreq
• job_queue_req
• job_queue_out
• job_queue_exceptions
• job_queue_incl_text
• job_queue_markers
• job_queue_report
• job_queue_req_text
• job_queue_subreq_text
• job_queue_destination

...

HTTP/HTTPS and POST

Transferology establishes connections to the Transferology Connector

• Uses HTTP or HTTPS when defined
• Sends/requests data via the POST method not GET

Transferology Connector Usage Scenarios

Let’s review the three usage scenarios:

1. Transferology user requests a program (i.e., degree audit)
2. Transferology Connector sends completed plan to Transferology
3. Transferology retrieves school’s equivalencies

1. User Requests a Program

• Transferology user chooses a school, a program, and provides answers to any predefined program questions
• Transferology creates an XML document with above information, user’s course work, and return (i.e. callback) URL
• Transferology connects to Transferology Connector and sends XML document
• Transferology Connector saves data into the Job Queue table
• Transferology Connector returns success or failure status and description
• Transferology closes the connection

2. Degree Audit server processes the degree audit request

• Transferology Connector polls the job_queue_list table for completed degree audits, previously requested by Transferology
• After finding a completed degree audit, previously requested by Transferology, the Transferology Connector creates an XML document from the Job Queue data
• Transferology Connector connects to Transferology and sends XML document
• Transferology formats and saves program data
• Transferology returns success or failure status and description
• Transferology Connector closes the connection
• If configured, Transferology Connector deletes the relevant Job Queue rows

3. Transferology Retrieves School’s Equivalencies

Transferology makes the necessary requests to the Transferology Connector to retrieve the following MASTREF and TA data:

• IREF Source schools
• Equivalency rules

Additional Considerations

Where appropriate, use an SSL Certificate to secure data exchange between Transferology and the Transferology Connector

Restrict access to Transferology Connector

• Firewall only allows traffic from Transferology
• PROD Transferology 18.207.24.42
• TEST Transferology  23.22.104.35

Transferology Connector does NOT access a school’s Student Information System

Degree audits are optional but equivalencies are mandatory