QUICK LINKS

Support
Issue Tracker
[Services]
Questions
[uAchieve 4.5 Applications]
[uAchieve 5.0 Application]
[uAchieve 5.1 Application]
Transferology
TES
[Training & Conferences]
Accessibility

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

If you are unfamiliar with the Transferology Connector, please see Getting Started With the Transferology Connector.

The Transferology Connector is formerly known by several other names including: uselect Connector, CEGXML, External CEG/XML Interface, CEG, XML Interface, or External CEG.


Anchor
connector_mandatory_requirements
connector_mandatory_requirements

Tip
titleMandatory Requirements

The following requirements are mandatory to successfully install, configure, and operate the Transferology Connector:

  • Java SE 8 - If your institution is unfamiliar with java, please see Free Java 8 Implementations.When java 7 is used, the https.protocols java system property must be defined, see the next item for specifics.
  • TLSv1.2 - The Transferology web service which receives degree audits no longer supports TLSv1 or TLS v1.1. Java 8 and higher use TLSv1.2 by default. Java 7 must define the following java system property.
  • When starting your java web application server, you must define the java https.protocols system property to explicitly disable TLSv1 and TLSv1.1.

-Dhttps.protocols=TLSv1.2
  • Java Application Server - CollegeSource recommends Tomcat 7.0.x, 8.0.x or 8.5.x, which can be obtained from the following page: http://tomcat.apache.org/index.html
  • Firewalls
    • School's External firewall must allow traffic to:
      • Your production Transferology Connector from www.transfer.org (18.207.24.42).
      • Your test/development Transferology Connector from test.transfer.org (23.22.104.35).
      • CollegeSource recommends restricting access to the Transferology Connector only after it is correctly installed and configured. Restricting access prior to this makes troubleshooting difficult.
    • Internal - TCP keepalive must be enabled between your Java Application Server and database when the JDBC connection traverses an internal firewall.

...