View Source

The Connector depends on the DARS daemon and server to provide Degree Audits.

There are three database connections required to successfully produce degree audits for u.select through the Connector via DARwin, namely:

DARS server (i.e. Cobol program)
DARS daemon (java program)
Connector

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

The Connector must interact with the same JOB_QUEUE_xxx tables as the DARS daemon and server.
Degree audits for u.select don't use the STU_xxx tables and therefore those tables don't need to be accessible by the DARS server, daemon and Connector.

The database user for the DARS daemon (java program) must have:

Select, insert, update and delete on the JOB_QUEUE_xxx tables

The database user for the DARS Server (i.e. cobol program) must have:

Select, insert, update and delete on the JOB_QUEUE_xxx tables

Select permission on these DARwin tables

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
TCA_MASTER
TCA_RULE
TCA_SOURCE
TCA_TARGET

Isolating the Connector from your existing DARwin 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 DARS server. This is accomplished by:

Creating new JOB_QUEUE_xxx tables
Creating a new DARS server and daemon
Make sure the database user for the Connector has select insert, update and delete on the newly created JOB_QUEUE_xxx tables.
Make sure the database user for the DARS daemon has select insert, update and delete on the newly created JOB_QUEUE_xxx tables
Make sure the database user for the DARS server (i.e. cobol) has select, insert, update and delete on the newly created JOB_QUEUE_xxx tables as well as select permission on the tables show above.

See OWL-14766 for the Oracle scripts.