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.


.
Note
titleThe Connector depends on a uAchieve Server to provide degree audits

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

  1. uAchieve Server
  2. Connector

Keep the following points in mind to minimize degree audit troubleshooting when setting up database access and installing the Connector:

A 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 uAchieve server.
  • Degree audits for Transferology do not use all of the STU_xxx tables. Therefore, those tables do not need Only the STU_ACADREC table needs to be accessible by the uAchieve Server and Connector.
  • The Transferology Connector doesn't need access to any of the STU_xxx tables.
  • For uAchieve audits, you must specify daversion=uachieve in the cas4.properties file.

...

uAchieve Server Minimum Database Access

This section is important when the database user used by the uAchieve server is different than the schema owner of the uachieve tables. If the database user used by the uAchieve server is the same as the database owner of the uAchieve tables, the points in this section aren't necessary.

When the database user used by the uAchieve server is different than the schema owner of the uachieve tables, the database user for the uAchieve server must have the following permissions: minimum access (synonyms and privileges):

  • Private synonyms are required for all tables identified in this section.
  • Select, insert, update, and delete privileges on the CURRENT_JOBS and JOB_QUEUE_xxx tables.
  • Select permission privilege on the following uAchieve tables:

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


Anchor
isolateconnector
isolateconnector

Isolating the Connector From Your School's Existing uAchieve 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 uAchieve Server

The alternatives below assume this initial setup, prior to performing the isolation steps:

  1. Db user/schema UACHIEVE owns all UACHIEVE tables.
  2. The uAchieve server connects to the database as the UACHIEVE user.
  3. Db user/schema TFO_CONNECTOR has access (privileges and synonyms) to the UACHIEVE schema tables as indicated above.
  4. The Transferology Connector connects to the database as the TFO_CONNECTOR user.

The following sections show the two alternatives.

Isolation via 3 Database Users

This is accomplished in isolation requires three database users and is the most secure. 

Coming soon!

Isolation via 2 Database Users

This isolation only requires two database users. It is slightly less secure than the above 3 Database User alternative.

It is accomplished with the following tasks:

  • Creating Create new JOB_QUEUE_xxx, CURRENT_JOBS and STU_ACADREC tablesCreating , in the TFO_CONNECTOR schema/user.
  • Create a new uAchieve daemonMake sure the database user for the Connector has .
  • Grant select, insert, update, and delete permissions privileges on the newly created JOB_QUEUE_xxx tables Make sure the database user for the uAchieve daemon has to the TFO_CONNECTOR schema/user.
  • Grant select, insert, update, and delete permissions delete privileges on the newly created JOB_QUEUE_xxx tables
  • Make sure the database user for the uAchieve daemon has 
  • as well as select permission privilege on the tables listed above but not STU_ACADREC.
  • By using an empty STU_ACADREC table in the user/schema for the isolation.