Transferology Technical Documentation

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

Old Version 8

changes.mady.by.user Unknown User (podnardb)

Saved on

compared with

New Version 9

changes.mady.by.user Unknown User (klemant)

Saved on

Key

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

The Connector depends on a u.achieve server uAchieve Server to provide degree audits.

Two database connections are required to successfully produce degree audits through the Connector via u.achieve uAchieve:

  1. u.achieve serveruAchieve Server
  2. Connector

Keep the following points in mind to minimize degree audit troubleshooting when installing the Connector:

  • A u.achieve uAchieve server specific to Transferology can be used for Transferology degree audits.
  • The Connector must interact with the same JOB_QUEUE_xxx tables as the u.achieve uAchieve server.
  • Degree audits for Transferology do not use the STU_xxx tables. Therefore, those tables do not need to be accessible by the u.achieve server uAchieve Server and Connector.
  • For u.achieve uAchieve audits, you must specify daversion=uachieve in the cas4.properties file.

The database user for the u.achieve uAchieve server must have the following permissions:

  • Select, insert, update, and delete on the CURRENT_JOBS and JOB_QUEUE_xxx tables

  • Select permission on the following u.achieve uAchieve tables:

    No Format
    CHART_CATEGORIES
COM
CRS_CONVERT
DPROG
DPROG_REQ
GMASTER
INCLUDE_TEXT
MASTREF
MASTREF_ADDRESS
MASTREF_SEG
REPEAT
REQ_MAIN
REQ_TEXT
REQ_XY
STRING
STRING_CRSE
SUB_REQ
SUB_REQ_AR
SUB_REQ_TEXT
TCA_MASTER
TCA_RULE
TCA_SOURCE
TCA_TARGET

Anchor
isolateconnector
isolateconnector

Isolating the Connector From Your Existing u.achieve Audit Data

Some schools want to prevent the Connector from accessing the audit data contained in the JOB_QUEUE_xxx tables used by their existing uuAchieve Server. achieve server. This is accomplished in the following tasks:

  • Creating new JOB_QUEUE_xxx tables
  • Creating a new u.achieve uAchieve daemon
  • Make sure the database user for the Connector has select, insert, update, and delete permissions on the newly created JOB_QUEUE_xxx tables
  • Make sure the database user for the u.achieve uAchieve daemon has select, insert, update, and delete permissions on the newly created JOB_QUEUE_xxx tables as well as select permission on the tables listed above

...