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 History
...
| Note | ||
|---|---|---|
| ||
Two database connections are required to successfully produce degree audits through the Connector via uAchieve:
Keep the following points in mind to minimize degree audit troubleshooting when setting up database access and installing the Connector:
|
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 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 minimum access (synonyms and privileges):.
| Anchor | ||||
|---|---|---|---|---|
|
JOB Tables
Private synonyms
...
, as well as select, insert, update, and delete privileges on the CURRENT_JOBS and JOB_QUEUE_xxx tables.
...
| Anchor | ||||
|---|---|---|---|---|
|
Other Tables
Private synonyms and select 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 | ||||
|---|---|---|---|---|
|
Isolating the Connector From Your School's Existing uAchieve
...
JOB_QUEUE_xxx tables
Some schools want to prevent the Connector from accessing the enrolled student's audit data contained in the JOB_QUEUE_xxx tables used by their the school's existing uAchieve Server.
The two alternatives below assume this initial setup, prior to performing the isolation steps:
- Db user/schema UACHIEVE owns all UACHIEVE tables.
- The uAchieve server connects to the database as the UACHIEVE database user.
- Db user/schema TFO_CONNECTOR has access (privileges and synonyms) to the UACHIEVE schema JOB_QUEUE_xxx tables as indicated above.
- The Transferology Connector connects to the database as the TFO_CONNECTOR database user.
The following sections show identify the important points for the two alternatives.
Isolation via 3 Database Users
This isolation requires three database users and is the most secure.
Coming soon!Database user specifics:
- Db user/schema UACHIEVE owns all UACHIEVE tables.
- Db user/schema TFO_UACH_SRVR will be used by the new uAchieve server.
- Db user/schema TFO_CONNECTOR will be used by the Connector.
- Grant select, insert, update, and delete privileges on the newly created JOB_QUEUE_xxx tables to the TFO_CONNECTOR schema/user.
- Make sure the database user for the uAchieve daemon has
- as well as select privilege on the tables listed above but not STU_ACADREC.
...
- Db user/schema UACHIEVE owns all UACHIEVE tables.
- Db user/schema TFO_CONNECTOR has access (privileges and synonyms) to the UACHIEVE schema tables as indicated above, with exception to the JOB_QUEUE_xxx, CURRENT_JOBS and STU_ACADREC tables which will also exist in the TFO_CONNECTOR schemawill be used by the new uAchieve server and Connector.
It is accomplished with the following tasks:
- Grant select privilege on the tables listed above but not STU_ACADREC.
- Create JOB_QUEUE_xxx, CURRENT_JOBS and STU_ACADREC tables, in the TFO_CONNECTOR schema/user.
- Grant select privilege on the tables listed above but not STU_ACADREC.
- Install the uAchieve server into a different directory, edit create daemon.
...
Overview
Content Tools