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
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

The Connector depends on the u.achieve daemon to provide degree audits.

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

  1. u.achieve daemon (Java program)
  2. Connector

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

  • The Connector must interact with the same JOB_QUEUE_xxx tables as the u.achieve daemon
  • Degree audits for u.select do not use the STU_xxx tables. Therefore, those tables do not need to be accessible by the u.achieve daemon and Connector.
  • For u.achieve audits, you must specify daversion=uachieve in the cas4.properties file.

The database user for the u.achieve daemon (Java program) 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 tables:

    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
    

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 u.achieve server. This is accomplished in the following tasks:

  • Creating new JOB_QUEUE_xxx tables
  • Creating a new u.achieve 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 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

 

  • No labels