Access Keys:
Skip to content (Access Key - 0)
 

4. Technical Considerations

These technical considerations are valid for CAS Server sites as well as EDAG Institutions.

COM Table

There must be a separate COM table created specifically for audit requests made from CAS. The COM table should be named to match the UNIQ of your institution in CAS. Follow the COM Necessities values listed in the Planning Guide Considerations section of this guide.

DARwin Daemon

Currently, the DARwin Daemon is set up to run for a local DARwin process. For the CAS Planning Guide Requests, a separate daemon is necessary, and must be identified in the daemon.cfg. Example of such is available on the Downloads, CAS Software area of the Support Center.

Control File (CTLFLE.DAT)

The Control File for the DARwin audits must be modified for CAS Planning Guides. CAS Planning Guides require: use of the information in the sysin file, a 1-column audit, and do not want to save evaluation results. Example of the CTLFLE.DAT is available on the Downloads, CAS Software area of the Support Center.

Considerations Specifically for EDAG Institutions

COM Values

NCOL Must be set to 1
WEBOPTION
Must be set to 2
EVALRUN
Should be set to A
TOPLNECT
Set to -0001 to include file. However, the audit report will not include automatic Top File; one must create a file to be included. Store the file as topfile.dat in the directory defined in the daemon.cfg for data_dir.
BOTLNECT
Set to -0001 to include file. However, the audit report will not include automatic Top File; one must create a file to be included. Store the file as botfile.dat in the directory defined in the daemon.cfg for data_dir.

Daemon and Control File should be set according to the information above.

Added by Melissa Brooks , last edited by Melissa Brooks on Jun 30, 2008 14:26

(None)

Adaptavist Theme Builder (3.1.3) Powered by Atlassian Confluence 2.8.0, the Enterprise Wiki.