From Java CoG Kit

Contents 1 Checkpoint related options 2 Output controling Options 3 Database integration 4 Gregor

Checkpoint related options

• -label label -- a unique lable that distinguishes the job based on a used defined label (if the filename is not used the filename will be label.xml)
• -c filename
• -c file://..../filename

Output controling Options

• -o xml - output is returned in xml
• -o txt - output is returned in : seperated list (if no -o option is specified, thi sis the default)
• -seperator - specifies the seperator for txt output, default is :

Database integration

The Java CoG Kit job submisison can be easily integrated in a database. This can be done through two mechanisms. First a global specification that communicates each time with a database, whithout explicitly useing the database options. Second each command can have options that can use an individually specified database

Depti will do this at a later time once we have done the preliminary stuff worked out.

• -c sql://...
• -c postgres://

cog-set -database -authenticate -p password

cog-set -database file://directory -- all checkpoint files are written in a named directory

-t sql:// .... -p password (chaches the password, should be integrated with single sign on, check how rft does this) if -p is not specified interaction is required in case -t sql or similar is used

Gregor