CREAM.CREAMJavaCLIDocumentation History

Hide minor edits - Show changes to markup - Cancel

April 02, 2012, at 03:14 PM by 87.14.255.198 -
Added lines 1-4:

This web site should be used for installations up to gLite 3.2. For EMI installations please refer to the new web site https://wiki.italiangrid.it/CREAM

January 20, 2009, at 10:18 AM by 193.205.157.115 -
Added lines 13-23:

Before you start, you need to create a file named ~/.glite/dlgor.properties, with content similar to this one:

issuerCertFile=/tmp/x509up_u219
issuerKeyFile=/tmp/x509up_u219
issuerPass=
delegationStorage=/tmp/dlgor_delegationStorage

where /tmp/x509up_u210 should be replaced with the path of your VOMS proxy file.

October 16, 2008, at 03:26 PM by 193.205.157.115 -
Changed lines 30-33 from:

the needed parameters. The commands are the ones described in the following sections.

to:

the needed parameters. The commands are the ones described in the following sections. To get help about a specific command, you can issue:

./CREAMClient.sh <command> --help
October 16, 2008, at 03:25 PM by 193.205.157.115 -
Changed lines 158-159 from:
JobCancel -e|--epr <endpoint> [-h|--help] [-a|--all] [-s|--status <status>] [-d|--delegId <deleg_id>] [-l|--leaseId <lease_id>} [-f|--fromData <from_date>] [-t|--toDate <to_date>] <jobId> ...
to:
./CREAMClient.sh JobCancel -e|--epr <endpoint> [-h|--help] [-a|--all] [-s|--status <status>] [-d|--delegId <deleg_id>] [-l|--leaseId <lease_id>} [-f|--fromData <from_date>] [-t|--toDate <to_date>] <jobId> ...
Changed lines 184-185 from:
JobList -e|--epr <endpoint> [-h|--help]
to:
./CREAMClient.sh JobList -e|--epr <endpoint> [-h|--help]
Changed lines 216-217 from:
JobInfo -e|--epr <endpoint> [-h|--help] [-s|--status <s>] [-f|--fromDate <date>] [-t|--toDate <date>] [-l|--leaseId <l>] [-d|--delegId <d>] [-a|--all|<jobId> ...]
to:
./CREAMClient.sh JobInfo -e|--epr <endpoint> [-h|--help] [-s|--status <s>] [-f|--fromDate <date>] [-t|--toDate <date>] [-l|--leaseId <l>] [-d|--delegId <d>] [-a|--all|<jobId> ...]
Changed lines 231-232 from:
JobInfo -e https://grid006.pd.infn.it:8443 --from "2005/07/18 08:00:00" -a
to:
./CREAMClient.sh JobInfo -e https://grid006.pd.infn.it:8443 --from "2005/07/18 08:00:00" -a
Changed lines 238-239 from:
JobInfo -e https://cream-01.pd.infn.it:8443 --to "2005/07/18 07:30:00" -s PENDING -s UNKNOWN
to:
./CREAMClient.sh JobInfo -e https://cream-01.pd.infn.it:8443 --to "2005/07/18 07:30:00" -s PENDING -s UNKNOWN
Changed lines 259-260 from:
JobPurge -e|--epr <endpoint> [-h|--help] [-d|--delegId <deleg_id>] [-l|--leaseId <lease_id>] [-f|--fromDate <date>] [-t|--toDate <date>] [-a|--all|<jobId> ...]
to:
./CREAMClient.sh JobPurge -e|--epr <endpoint> [-h|--help] [-d|--delegId <deleg_id>] [-l|--leaseId <lease_id>] [-f|--fromDate <date>] [-t|--toDate <date>] [-a|--all|<jobId> ...]
Changed lines 283-284 from:
SetLease -e|--epr <endpoint> [-h|--help] -l|--leaseId <lease_id> -x|--leaseExpTime <time>
to:
./CREAMClient.sh SetLease -e|--epr <endpoint> [-h|--help] -l|--leaseId <lease_id> -x|--leaseExpTime <time>
Changed lines 304-305 from:
GetLease -e|--epr <endpoint> [-h|--help] -l|--leaseId <lease_id>
to:
./CREAMClient.sh GetLease -e|--epr <endpoint> [-h|--help] -l|--leaseId <lease_id>
Changed lines 325-326 from:
DeleteLease -e|--epr <endpoint> [-h|--help] -l|--leaseId <lease_id>
to:
./CREAMClient.sh DeleteLease -e|--epr <endpoint> [-h|--help] -l|--leaseId <lease_id>
Changed line 345 from:
GetServiceInfo -e|--epr <endpoint> [-h|--help]
to:
./CREAMClient.sh GetServiceInfo -e|--epr <endpoint> [-h|--help]
October 16, 2008, at 03:06 PM by 193.205.157.115 -
Changed line 44 from:
JobRegister [-d|--delegationId <did>] [--delegate] -r|--resource <endpoint> [-h|--help] [--autostart] <jdl>
to:
JobRegister [-d|--delegationId <did>] [--delegate] -e|--epr <endpoint> [-h|--help] [--autostart] <jdl>
June 06, 2008, at 01:23 PM by 193.205.157.115 -
Changed line 16 from:

To get the most up-to-date (jan 26, 2007) version of the Java client programs, please get the

to:

To get the most up-to-date (june 6, 2008) version of the Java client programs, please get the

June 06, 2008, at 01:22 PM by 193.205.157.115 -
Changed line 17 from:

java-cli-20070126.tar.gz archive. This

to:

java-cli-20080606.tar.gz archive. This

June 05, 2008, at 04:54 PM by 193.205.157.115 -
Changed line 17 from:

(-java-cli-20070126.tar.gz-) archive. This

to:

java-cli-20070126.tar.gz archive. This

June 05, 2008, at 04:53 PM by 193.205.157.115 -
Changed line 17 from:

java-cli-20070126.tar.gz archive. This

to:

(-java-cli-20070126.tar.gz-) archive. This

June 05, 2008, at 04:47 PM by 193.205.157.115 -
Changed line 72 from:

[=log4j:WARN No appenders could be found for logger (org.apache.axis.i18n.ProjectResourceBundle).

to:

@@[=log4j:WARN No appenders could be found for logger (org.apache.axis.i18n.ProjectResourceBundle).

Changed line 78 from:

property: name=CREAMOutputSandboxURI value="gsiftp://cream-01.pd.infn.it/opt/glite/var/cream_sandbox/infngrid/C_IT_O_INFN_OU_Personal_Certificate_L_Padova_CN_Moreno_Marzolla_infngrid_Role_NULL_Capability_NULL/CREAM317462346/OSB=]

to:

property: name=CREAMOutputSandboxURI value="gsiftp://cream-01.pd.infn.it/opt/glite/var/cream_sandbox/infngrid/C_IT_O_INFN_OU_Personal_Certificate_L_Padova_CN_Moreno_Marzolla_infngrid_Role_NULL_Capability_NULL/CREAM317462346/OSB=]@@

June 05, 2008, at 04:46 PM by 193.205.157.115 -
Changed line 58 from:

[@[

to:

@@[=[

Changed line 64 from:

]@]

to:

]=]@@

June 05, 2008, at 04:35 PM by 193.205.157.115 -
Changed line 356 from:

[@service descrition: CREAM 2

to:

@@[=service descrition: CREAM 2

Changed line 363 from:

0) cemon_url = https://cream-01.pd.infn.it:8443/ce-monitor/services/CEMonitor@]

to:

0) cemon_url = https://cream-01.pd.infn.it:8443/ce-monitor/services/CEMonitor=]@@

June 05, 2008, at 04:34 PM by 193.205.157.115 -
Changed line 58 from:

[=[

to:

[@[

Changed lines 64-65 from:

]=]

to:

]@]

Changed lines 339-363 from:

lease id = pippo123 time = Thu Jun 05 16:59:59 CEST 2008

to:

lease id = pippo123 time = Thu Jun 05 16:59:59 CEST 2008

GetServiceInfo

This operation returns information on a given CREAM service.

GetServiceInfo -e|--epr <endpoint> [-h|--help]
-e|--epr <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM2.
-h|--help
(optional) Get a brief description of the command line options.

Example

In order to get informations about the CREAM service on the host https://cream-01.pd.infn.it:8443, issue the following command:

./CREAMClient.sh GetServiceInfo -e https://cream-01.pd.infn.it:8443

service descrition: CREAM 2 interface version: 2.0 service version: 2.0 service startup time: Thu Jun 05 16:01:58 CEST 2008 service status: RUNNING messages: 0 properties: 1 0) cemon_url = https://cream-01.pd.infn.it:8443/ce-monitor/services/CEMonitor

June 05, 2008, at 04:22 PM by 193.205.157.115 -
Changed lines 277-278 from:
./CREAMClient.sh JobPurge -e https://grid006.pd.infn.it:8443 -a
to:
./CREAMClient.sh JobPurge -e https://cream-01.pd.infn.it:8443 -a
Changed lines 294-295 from:
./CREAMClient.sh SetLease -e https://cream-01:8443 --leaseId pippo123 -x "2008/06/05 17:00:00"
to:
./CREAMClient.sh SetLease -e https://cream-01.pd.infn.it:8443 --leaseId pippo123 -x "2008/06/05 17:00:00"
Changed lines 314-315 from:
./CREAMClient.sh GetLease -e https://cream-01:8443 --leaseId pippo123
to:
./CREAMClient.sh GetLease -e https://cream-01.pd.infn.it:8443 --leaseId pippo123

The output is something as follows:

lease id = pippo123 time = Thu Jun 05 16:59:59 CEST 2008

DeleteLease

This command can be used to remove an existing lease and all associated jobs.

DeleteLease -e|--epr <endpoint> [-h|--help] -l|--leaseId <lease_id>
-e|--epr <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM2.
-l|--leaseId <lease_id>
(mandatory) The ID of an existing lease.
-h|--help
(optional) Get a brief description of the command line options.

Examples

To remove lease ID pippo123 from the cream-ce-01.pd.infn.it:8443 CREAM CE, issue the following command:

./CREAMClient.sh DeleteLease -e https://cream-01.pd.infn.it:8443 --leaseId pippo123
June 05, 2008, at 04:15 PM by 193.205.157.115 -
Changed lines 281-282 from:

These command can be used to request the creation of a new lease.

to:

This command can be used to request the creation of a new lease.

Added lines 301-308:

This command can be used to get informations on an existing lease.

GetLease -e|--epr <endpoint> [-h|--help] -l|--leaseId <lease_id>
-e|--epr <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM2.
-l|--leaseId <lease_id>
(mandatory) The ID of an existing lease.
-h|--help
(optional) Get a brief description of the command line options.
June 05, 2008, at 04:12 PM by 193.205.157.115 -
Changed line 196 from:

[=0) CREAM317462346

to:

@@[=0) CREAM317462346

Changed lines 198-200 from:

2) CREAM651715059=]

to:

2) CREAM651715059=]@@

Changed lines 288-310 from:
-h|--help
(optional) Get a brief description of the command line options.
to:
-h|--help
(optional) Get a brief description of the command line options.

Examples

To create a lease with ID pippo123, issue the following command:

./CREAMClient.sh SetLease -e https://cream-01:8443 --leaseId pippo123 -x "2008/06/05 17:00:00"

The output is something like this:

lease time: Thu Jun 05 16:59:59 CEST 2008

GetLease

Examples

To query a lease with ID pippo123, issue the following command:

./CREAMClient.sh GetLease -e https://cream-01:8443 --leaseId pippo123

The output is something as follows:

lease id = pippo123 time = Thu Jun 05 16:59:59 CEST 2008

June 05, 2008, at 04:07 PM by 193.205.157.115 -
Changed lines 283-284 from:
SetLease -e|--epr <endpoint> [-h|--help] -l|--leaseId <lease_id> [-x|--leaseExpTime <time>]
to:
SetLease -e|--epr <endpoint> [-h|--help] -l|--leaseId <lease_id> -x|--leaseExpTime <time>
Changed line 287 from:
-x|--leaseExpTime <time>
(optional) Defines the expiration time for the lease.
to:
-x|--leaseExpTime <time>
(mandatory) Defines the expiration time for the lease. The expiration time must be in the format "AAAA/MM/DD HH:MM:SS"
June 05, 2008, at 03:44 PM by 193.205.157.115 -
Changed lines 277-288 from:
./CREAMClient.sh JobPurge -e https://grid006.pd.infn.it:8443 -a
to:
./CREAMClient.sh JobPurge -e https://grid006.pd.infn.it:8443 -a

SetLease

These command can be used to request the creation of a new lease.

SetLease -e|--epr <endpoint> [-h|--help] -l|--leaseId <lease_id> [-x|--leaseExpTime <time>]
-e|--epr <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM2.
-l|--leaseId <lease_id>
(mandatory) The unique ID of the newly created lease.
-x|--leaseExpTime <time>
(optional) Defines the expiration time for the lease.
-h|--help
(optional) Get a brief description of the command line options.
June 05, 2008, at 03:34 PM by 193.205.157.115 -
Changed lines 163-167 from:
-s|--status <status>
(optional)
-d|--delegId <deleg_id>
(optional)
-l|--leaseId <lease_id>
(optional)
-f|--fromDate <from_date>
(optional)
-t|--toDate <to_date>
(optional)
to:
-s|--status <status>
(optional) Cancel all jobs which are currently in the given status; multiple -s options can be used to request cancellation of jobs being in any of the given states. <status>:=RUNNING| PENDING| DONE-OK| DONE-FAILED| CANCALLED| IDLE| ABORTED| UNKNOWN| REGISTERED| HELD
-d|--delegId <deleg_id>
(optional) Cancel all jobs with the given delegation ID.
-l|--leaseId <lease_id>
(optional) Cancel all jobs with the given lease ID
-f|--fromDate <from_date>
(optional) Cancel all jobs submitted after <from_date>. The date can be specified as "AAAA/MM/DD HH:MM:SS"
-t|--toDate <to_date>
(optional) Cancel all jobs submitted before <to_date>.
June 05, 2008, at 03:26 PM by 193.205.157.115 -
Changed lines 263-266 from:
-d|--delegId <deleg_id>
(optional)
-l|--leaseId <lease_id>
(optional)
-f|--fromDate <from_date>
(optional)
-t|--toDate <to_date>
(optional)
to:
-d|--delegId <deleg_id>
(optional) Purge all jobs with the given delegation ID.
-l|--leaseId <lease_id>
(optional) Purge all jobs with the given lease ID.
-f|--fromDate <from_date>
(optional) Purge all jobs submitted after the given date.
-t|--toDate <to_date>
(optional) Purge all jobs submitted before the given date.
Added lines 270-272:

NOTE: the --delegId, --leaseId, --fromDate, --toDate parameters can be combined. The result is to purge all jobs matching all criteria specified in the command line.

Changed line 277 from:
JobPurge -e https://grid006.pd.infn.it:8443 -a
to:
./CREAMClient.sh JobPurge -e https://grid006.pd.infn.it:8443 -a
June 05, 2008, at 03:23 PM by 193.205.157.115 -
Changed lines 231-233 from:
JobInfo -r https://grid006.pd.infn.it:8443 --from "2005/07/18 08:00:00" -a

shows informations for all jobs registered to grid006.pd.infn.it after

to:
JobInfo -e https://grid006.pd.infn.it:8443 --from "2005/07/18 08:00:00" -a

shows informations for all jobs registered to cream-01.pd.infn.it after

Changed lines 238-239 from:
JobInfo -r https://grid006.pd.infn.it:8443 --to "2005/07/18 07:30:00" -s PENDING -s UNKNOWN
to:
JobInfo -e https://cream-01.pd.infn.it:8443 --to "2005/07/18 07:30:00" -s PENDING -s UNKNOWN
Changed lines 241-247 from:

and have been registered to grid006.pd.infn.it before jul 18, 2005 07:30:00.

to:

and have been registered to cream-01.pd.infn.it before jul 18, 2005 07:30:00.

Changed lines 259-262 from:
JobPurge -r|--resource <endpoint> [-h|--help] -a|--all|<jobId> ...
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
-a|--all
(optional) If the user does not specify a list of job IDs, then all jobs in state DONE-OK, DONE-FAILED, CANCELLED or REGISTERED are purged.
to:
JobPurge -e|--epr <endpoint> [-h|--help] [-d|--delegId <deleg_id>] [-l|--leaseId <lease_id>] [-f|--fromDate <date>] [-t|--toDate <date>] [-a|--all|<jobId> ...]
-e|--epr <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM2.
-a|--all
(optional) If the user does not specify a list of job IDs, then all jobs in state DONE-OK, DONE-FAILED, CANCELLED or REGISTERED are purged.
-d|--delegId <deleg_id>
(optional)
-l|--leaseId <lease_id>
(optional)
-f|--fromDate <from_date>
(optional)
-t|--toDate <to_date>
(optional)
Changed line 274 from:
JobPurge -r https://grid006.pd.infn.it:8443 -a
to:
JobPurge -e https://grid006.pd.infn.it:8443 -a
June 05, 2008, at 02:49 PM by 193.205.157.115 -
Changed lines 146-149 from:
JobStart -e https://cream-01.pd.infn.it:8443 CREAM566926885
to:
./CREAMClient.sh JobStart -e https://cream-01.pd.infn.it:8443 CREAM566926885
Changed lines 174-178 from:
JobCancel -e https://grid006.pd.infn.it:8443 CREAM51113
to:
./CREAMClient.sh JobCancel -e https://grid006.pd.infn.it:8443 CREAM51113
Changed lines 193-194 from:
JobList -r https://grid006.pd.infn.it:8443
to:
./CREAMClient.sh JobList -e https://cream-01.pd.infn.it:8443
Changed lines 196-206 from:

resource: https://grid006.pd.infn.it:8443 - Client CN=grid006.pd.infn.it, L=Padova, OU=Host, O=INFN, C=IT accepted 0) https://grid006.pd.infn.it:8443/CREAM18091 1) https://grid006.pd.infn.it:8443/CREAM51113 2 jobs listed

to:

0) CREAM317462346 1) CREAM566926885 2) CREAM651715059

Changed lines 210-211 from:
  1. If the --from option is given, then only jobs from step (1) which are registered after then given date are considered.
  2. If the --to option is given, then only jobs from step (1-2) which are registered before then given date are considered.
to:
  1. If the --fromDate option is given, then only jobs from step (1) which are registered after then given date are considered.
  2. If the --toDate option is given, then only jobs from step (1-2) which are registered before then given date are considered.
Changed lines 216-223 from:
JobInfo -r|--resource <endpoint> [-h|--help] [-s|--status <s>] [--from <date>] [--to <date>] [-a|--all|<jobId> ...]
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
--from <date>
(optional) Retrieve informations only for jobs registered after this date. <date> must be in the format yyyy/mm/dd hh:mm:ss (default: registration time of user's oldest job).
--to <date>
(optional) Retrieve informations only for jobs registered before this date. The <date> parameter must be in the format yyyy/mm/dd hh:mm:ss (default: now).
-a|--all
(optional) If the user does not specify a list of job IDs, then all non-purged jobs are retrieved (however, other filtering might be applied, see above).
-s|--status <s>
Displays informations for jobs in a given status; multiple -s options may be combined to list all jobs in one of the given states. <s>:=RUNNING| PENDING| DONE-OK| DONE-FAILED| CANCALLED| IDLE| ABORTED| UNKNOWN| REGISTERED| HELD. Note: Option -s implies option -a.
-h|--help
(optional) Get a brief description of the command line options
to:
JobInfo -e|--epr <endpoint> [-h|--help] [-s|--status <s>] [-f|--fromDate <date>] [-t|--toDate <date>] [-l|--leaseId <l>] [-d|--delegId <d>] [-a|--all|<jobId> ...]
-e|--epre <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM2.
-f|--fromDate <date>
(optional) Retrieve informations only for jobs registered after this date. <date> must be in the format yyyy/mm/dd hh:mm:ss (default: registration time of user's oldest job).
-t|--toDate <date>
(optional) Retrieve informations only for jobs registered before this date. The <date> parameter must be in the format yyyy/mm/dd hh:mm:ss (default: now).
-a|--all
(optional) If the user does not specify a list of job IDs, then all non-purged jobs are retrieved (however, other filtering might be applied, see above).
-s|--status <s>
(optional) Displays informations for jobs in a given status; multiple -s options may be combined to list all jobs in one of the given states. <s>:=RUNNING| PENDING| DONE-OK| DONE-FAILED| CANCALLED| IDLE| ABORTED| UNKNOWN| REGISTERED| HELD. Note: Option -s implies option -a.
-d|--delegId <d>
(optional)
-l|--leaseId <l>
(optional)
-h|--help
(optional) Get a brief description of the command line options
June 05, 2008, at 02:42 PM by 193.205.157.115 -
Changed lines 162-167 from:
-a|--all
This option can be used to cancel all jobs owned by the user. Use with care!
-s|--status <status>
-d|--delegId <deleg_id>
-l|--leaseId <lease_id>
-f|--fromDate <from_date>
-t|--toDate <to_date>
to:
-a|--all
(optional) This option can be used to cancel all jobs owned by the user. Use with care!
-s|--status <status>
(optional)
-d|--delegId <deleg_id>
(optional)
-l|--leaseId <lease_id>
(optional)
-f|--fromDate <from_date>
(optional)
-t|--toDate <to_date>
(optional)
Changed line 186 from:
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
to:
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM2.
June 05, 2008, at 02:37 PM by 193.205.157.115 -
Changed lines 158-159 from:
JobCancel -e|--epr <endpoint> [-h|--help] -a|--all|<jobId> ...
to:
JobCancel -e|--epr <endpoint> [-h|--help] [-a|--all] [-s|--status <status>] [-d|--delegId <deleg_id>] [-l|--leaseId <lease_id>} [-f|--fromData <from_date>] [-t|--toDate <to_date>] <jobId> ...
Changed line 184 from:
JobList -r|--resource <endpoint> [-h|--help]
to:
JobList -e|--epr <endpoint> [-h|--help]
June 05, 2008, at 02:34 PM by 193.205.157.115 -
Changed line 138 from:
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
to:
-e|--epr <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM2.
Changed lines 158-160 from:
JobCancel -r|--resource <endpoint> [-h|--help] -a|--all|<jobId> ...
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
to:
JobCancel -e|--epr <endpoint> [-h|--help] -a|--all|<jobId> ...
-e|--epr <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM2.
Added lines 163-167:
-s|--status <status>
-d|--delegId <deleg_id>
-l|--leaseId <lease_id>
-f|--fromDate <from_date>
-t|--toDate <to_date>
Changed lines 172-174 from:

To cancel the job with CREAM ID https://grid006.pd.infn.it:8443/CREAM51113, you give:

JobCancel -r https://grid006.pd.infn.it:8443 https://grid006.pd.infn.it:8443/CREAM51113
to:

To cancel the job with CREAM ID CREAM51113, you give:

JobCancel -e https://grid006.pd.infn.it:8443 CREAM51113
June 05, 2008, at 02:30 PM by 193.205.157.115 -
Changed lines 23-24 from:

to see the list of available options.

to:

to see the list of available commands.

Changed lines 31-34 from:

To get a full list, just type:

./CREAMClient.sh
to:
Changed line 123 from:
  1. Manually copy any file from your client machine to the ISB URI reported by the JobRegister command (you may use the JobInfo command to examine the value of ISB URI); ISB files residing on gridftp servers will be automatically copied in the ISB by the Job Wrapper;
to:
  1. Manually copy any file from your client machine to the CREAMInputSandboxURI reported by the JobRegister command (you may use the JobInfo command to examine the value of CREAMInputSandboxURI); ISB files residing on gridftp servers will be automatically copied in the ISB by the Job Wrapper;
Changed lines 125-128 from:
  1. When the job terminates, any file in the OSB is automatically copied to the gridftp server specified in the OutputSandboxDestURI JDL attribute.
to:
  1. When the job terminates, any file in the OSB is automatically copied to the gridftp server specified in the OutputSandboxDestURI JDL attribute.
Changed lines 136-137 from:
JobStart [-h|--help] -r|--resource <endpoint> <jobID>
to:
JobStart [-h|--help] -e|--epr <endpoint> <jobID>
Changed lines 144-148 from:

To start a job with CREAM ID https://grid006.pd.infn.it:8443/CREAM51113, you give:

JobStart -r https://grid006.pd.infn.it:8443 https://grid006.pd.infn.it:8443/CREAM51113
to:

To start a job with CREAM ID CREAM566926885, you give:

JobStart -e https://cream-01.pd.infn.it:8443 CREAM566926885
June 05, 2008, at 02:24 PM by 193.205.157.115 -
Changed line 54 from:
-l|--leaseId <lease_id>
(optional) Use the lease whose id is <lease_id>. This lease has to be previously created with the JobLease command (see below).
to:
-l|--leaseId <lease_id>
(optional) Use the lease whose id is <lease_id>. This lease has to be previously created with the JobLease command (see below). If this option is omitted, the job is created with no lease (i.e., the job never expires).
Changed lines 61-66 from:

[=[ VirtualOrganisation = "topolino"; executable="/bin/sleep"; arguments="300"; BatchSystem="lsf"; QueueName="grid02"

to:

[=[ VirtualOrganisation="EGEE"; executable="/bin/sleep"; arguments="600"; BatchSystem="lsf"; QueueName="cert";

Changed lines 71-72 from:
JobRegister -r https://grid006.pd.infn.it:8443 test.jdl
to:
./CREAMClient.sh JobRegister -e https://cream-01.pd.infn.it:8443 --delegate -d DELEG001 test.jdl
Changed lines 75-87 from:

resource: https://grid006.pd.infn.it:8443 delegation ID: null autostart? false jdlfile: test.jdl Using Delegation ID: 1121770063225 Delegation Port: https://grid006.pd.infn.it:8443/ce-cream/services/CREAMDelegation - Client CN=grid006.pd.infn.it, L=Padova, OU=Host, O=INFN, C=IT accepted - Client CN=grid006.pd.infn.it, L=Padova, OU=Host, O=INFN, C=IT accepted - Client CN=grid006.pd.infn.it, L=Padova, OU=Host, O=INFN, C=IT accepted https://grid006.pd.infn.it:8443/CREAM51113 ISB URI: gsiftp://grid006.pd.infn.it/opt/glite/var/cream/CN_Moreno_Marzolla,L_Padova,OU_Personal_Certificate,O_INFN,C_IT/CREAM51113/ISB

In this case, the job ID is the string https://grid006.pd.infn.it:8443/CREAM51113, and can be used to

to:

log4j:WARN No appenders could be found for logger (org.apache.axis.i18n.ProjectResourceBundle). log4j:WARN Please initialize the log4j system properly. job descrption id: 0 jobId: CREAM317462346 cream url: https://cream-01.pd.infn.it:8443/ce-cream/services/CREAM2 property: name=CREAMInputSandboxURI value="gsiftp://cream-01.pd.infn.it/opt/glite/var/cream_sandbox/infngrid/C_IT_O_INFN_OU_Personal_Certificate_L_Padova_CN_Moreno_Marzolla_infngrid_Role_NULL_Capability_NULL/CREAM317462346/ISB property: name=CREAMOutputSandboxURI value="gsiftp://cream-01.pd.infn.it/opt/glite/var/cream_sandbox/infngrid/C_IT_O_INFN_OU_Personal_Certificate_L_Padova_CN_Moreno_Marzolla_infngrid_Role_NULL_Capability_NULL/CREAM317462346/OSB

In this case, the job ID is the string CREAM317462346, and can be used to

Changed line 89 from:

Input Sandbox (ISB) using globus-url-copy. In the example above, the ISB URI: line

to:

Input Sandbox (ISB) using globus-url-copy. In the example above, the CREAMInputSandboxURI attribute

Changed line 94 from:

@@[=globus-url-copy file:///home/marzolla/SomeFile.txt gsiftp://grid006.pd.infn.it/opt/glite/var/cream/CN_Moreno_Marzolla,L_Padova,OU_Personal_Certificate,O_INFN,C_IT/CREAM51113/ISB

to:

@@[=globus-url-copy file:///home/marzolla/SomeFile.txt gsiftp://cream-01.pd.infn.it/opt/glite/var/cream_sandbox/infngrid/C_IT_O_INFN_OU_Personal_Certificate_L_Padova_CN_Moreno_Marzolla_infngrid_Role_NULL_Capability_NULL/CREAM317462346/ISB

Changed line 98 from:

ISB URI: line reported by the JobRegister.

to:

CREAMInputSandboxURI attribute value reported by the JobRegister.

June 05, 2008, at 02:16 PM by 193.205.157.115 -
Changed lines 25-101 from:

CREAM compiled with Axis 1.1 (Obsolete!)

In order to facilitate execution of the Java programs, the following Shell script can be useful; note that this script must be used if you are using the version of CREAM compiled with Axis1.1:

#!/bin/sh dir=$HOME/workspace classpath=.:$dir/repository/bcprov-jdk14/1.22/share/jars/jce-jdk13-122.jar:\ $dir/repository/bcprov-jdk14/1.22/share/jars/bcpg-jdk14-122.jar:\ $dir/repository/xerces2-j/2.6.2/share/xercesImpl.jar:\ $dir/repository/xerces2-j/2.6.2/share/xml-apis.jar:\ $dir/repository/xerces2-j/2.6.2/share/resolver.jar:\ $dir/repository/xerces2-j/2.6.2/share/xmlParserAPIs.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/jaxrpc.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/axis.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/commons-discovery.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/commons-logging.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/log4j-1.2.8.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/saaj.jar:\ $dir/stage/share/java/glite-ce-cream-api-java.jar:\ $dir/stage/share/java/glite-ce-cream.jar:\ $dir/stage/share/java/glite-ce-cream-examples.jar:\ $dir/stage/share/java/glite-ce-delegation.jar:\ $dir/stage/share/java/glite-security-delegation-java.jar:\ $dir/stage/share/java/glite-security-util-java.jar:\ $dir/stage/share/java/glite-security-trustmanager.jar:\ $dir/stage/share/java/glite-security-authz-framework-java.jar java -cp $classpath org.glite.ce.cream.client.<Command> "$@"

where <Command> is one of JobRegister, JobStart, JobCancel, JobList, JobInfo and JobPurge. The script(s) could be put anywhere in the filesystem, but the user must redefine the variable dir to point to the workspace where CREAM has been built.

The scripts, along with the compiled Java programs needed to run the CLI tools can be found on the CREAM Java client page.

CREAM compiled with Axis 1.2 (Obsolete)

The most recent version of CREAM uses Axis 1.2. From the Java CLI point of view, this requires a different set of jars to be executed. The shell script in this case is the following:

#!/bin/sh dir=$HOME/workspace classpath=.:$dir/repository/bcprov-jdk14/1.22/share/jars/jce-jdk13-122.jar:\ /usr/share/java/activation.jar:\ $dir/repository/javamail/1.3.1/share/lib/mailapi.jar:\ $dir/repository/bcprov-jdk14/1.22/share/jars/bcpg-jdk14-122.jar:\ $dir/repository/xerces2-j/2.6.2/share/xercesImpl.jar:\ $dir/repository/xerces2-j/2.6.2/share/xml-apis.jar:\ $dir/repository/xerces2-j/2.6.2/share/resolver.jar:\ $dir/repository/xerces2-j/2.6.2/share/xmlParserAPIs.jar:\ $dir/repository/axis/1.2/share/lib/axis.jar:\ $dir/repository/axis/1.2/share/lib/commons-logging-1.0.4.jar:\ $dir/repository/axis/1.2/share/lib/jaxrpc.jar:\ $dir/repository/axis/1.2/share/lib/commons-discovery-0.2.jar:\ $dir/repository/axis/1.2/share/lib/log4j-1.2.8.jar:\ $dir/repository/axis/1.2/share/lib/saaj.jar:\ $dir/repository/axis/1.2/share/lib/wsdl4j-1.5.1.jar:\ $dir/stage/share/java/glite-ce-cream-api-java.jar:\ $dir/stage/share/java/glite-ce-cream.jar:\ $dir/stage/share/java/glite-ce-cream-examples.jar:\ $dir/stage/share/java/glite-ce-delegation.jar:\ $dir/stage/share/java/glite-security-delegation-java.jar:\ $dir/stage/share/java/glite-security-util-java.jar:\ $dir/stage/share/java/glite-security-trustmanager.jar:\ $dir/stage/share/java/glite-security-authz-framework-java.jar java -cp $classpath org.glite.ce.cream.client.<Command> "$@"

A slightly different script, along with the compiled Java programs needed to run the CLI tools can be found on the CREAM Java client for Axis1.2 page.

Note: The new script, called CREAMClient.sh, must be used differently from the old scripts. The syntax is the following:

to:

The general syntax of the script is the following:

Changed lines 49-51 from:
-d|--delegationId <did>
(optional) Use the given delegation ID (if omitted, a new ID is generated).
--delegate
Use automatic delegation. If the -d option is not given, then --delegate MUST be used.
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM. The Delegation Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAMDelegation.
to:
-d|--delegationId <did>
(mandatory) Use the given delegation ID. The delegation ID can be an arbitrary string.
--delegate
(optional) Force creation of a new delegation. The -d option specifies the delegation ID to create, which must NOT already exist on the CE.
-e|--epr <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM2. The Delegation Service is assumed to be at https://<host>:<port>/ce-cream/services/gridsite-delegation.
Added line 54:
-l|--leaseId <lease_id>
(optional) Use the lease whose id is <lease_id>. This lease has to be previously created with the JobLease command (see below).
January 26, 2007, at 03:29 PM by deleted -
Changed lines 19-20 from:

various utilities. Refer to the

to:

various utilities. Type

./CREAMClient.sh

to see the list of available options.

January 26, 2007, at 03:28 PM by deleted -
Changed lines 14-15 from:

CREAM compiled with Axis 1.1

to:

CREAM Java Clients

To get the most up-to-date (jan 26, 2007) version of the Java client programs, please get the java-cli-20070126.tar.gz archive. This archive contains the required .jars, plus a CREAMClient.sh script which can be used to launch the various utilities. Refer to the

CREAM compiled with Axis 1.1 (Obsolete!)

Changed lines 55-58 from:

found on the CREAM Java client page.

CREAM compiled with Axis 1.2

to:

found on the CREAM Java client page.

CREAM compiled with Axis 1.2 (Obsolete)

June 16, 2006, at 04:01 PM by 193.205.157.206 -
Deleted lines 125-126:

requirements = other.GlueCEStateStatus == "Production"; Rank = -other.GlueCEStateEstimatedResponseTime;

March 09, 2006, at 05:02 PM by 193.205.157.115 -
Changed lines 111-112 from:
JobRegister [-d|--delegationId <did>] -r|--resource <endpoint> [-h|--help] [--autostart] <jdl>
to:
JobRegister [-d|--delegationId <did>] [--delegate] -r|--resource <endpoint> [-h|--help] [--autostart] <jdl>
Added line 114:
--delegate
Use automatic delegation. If the -d option is not given, then --delegate MUST be used.
September 19, 2005, at 12:34 PM by 193.205.157.115 -
Changed line 296 from:
-s|--status <s>
Displays informations for jobs in a given status; multiple -s options may be combined to list all jobs in one of the given states. <s>:=RUNNING| PENDING| DONE-OK| DONE-FAILED| CANCALLED| IDLE| ABORTED| UNKNOWN| REGISTERED| HELD
to:
-s|--status <s>
Displays informations for jobs in a given status; multiple -s options may be combined to list all jobs in one of the given states. <s>:=RUNNING| PENDING| DONE-OK| DONE-FAILED| CANCALLED| IDLE| ABORTED| UNKNOWN| REGISTERED| HELD. Note: Option -s implies option -a.
September 07, 2005, at 05:32 PM by 193.205.157.115 -
Changed lines 48-49 from:

found on the CREAM Java client examples page.

to:

found on the CREAM Java client page.

Changed lines 86-87 from:

found on the CREAM Java client examples for Axis1.2 page.

to:

found on the CREAM Java client for Axis1.2 page.

September 06, 2005, at 02:33 PM by 193.205.157.115 -
Changed lines 156-157 from:

If the job needs to process some input files, they can be uploaded in the job's Input Sandbox (ISB) using gridftp. In the example above, the ISB URI: line

to:

If the job needs to process some input files which are on the client machine, they can be uploaded in the job's Input Sandbox (ISB) using globus-url-copy. In the example above, the ISB URI: line

Changed lines 159-162 from:

using the InputSandbox JDL Attribute (see the CREAM JDL attribute specification document for mode details). So, in order to upload files /home/marzolla/SomeFile.txt on the ISB, you do something like this:

@@[=gridftp file:///home/marzolla/SomeFile.txt gsiftp://grid006.pd.infn.it/opt/glite/var/cream/CN_Moreno_Marzolla,L_Padova,OU_Personal_Certificate,O_INFN,C_IT/CREAM51113/ISB

to:

using the InputSandbox JDL Attribute (see the CREAM JDL attribute specification document for mode details). So, in order to upload a file /home/marzolla/SomeFile.txt from the client machine to the ISB, you do something like this:

@@[=globus-url-copy file:///home/marzolla/SomeFile.txt gsiftp://grid006.pd.infn.it/opt/glite/var/cream/CN_Moreno_Marzolla,L_Padova,OU_Personal_Certificate,O_INFN,C_IT/CREAM51113/ISB

Changed lines 168-178 from:
to:

Note that in the JDL it is possible to specify two kinds of ISB files:

  1. Files residing on the client machine;
  2. Files residing on a gridftp server.

Only type 1) files (the ones residing on the client machine) need to be moved to the CREAM server using globus-url-copy. Moreover, this command has to be given after registering a job, but before actually starting it using the JobStart command.

Added lines 187-199:

Putting it all together

So, if you need to manage the ISB/OSB, these are the steps you do to submit and execute the job:

  1. Register the job using the JobRegister command;
  2. Manually copy any file from your client machine to the ISB URI reported by the JobRegister command (you may use the JobInfo command to examine the value of ISB URI); ISB files residing on gridftp servers will be automatically copied in the ISB by the Job Wrapper;
  3. Start the job using the JobStart command;
  4. When the job terminates, any file in the OSB is automatically copied to the gridftp server specified in the OutputSandboxDestURI JDL attribute.
September 06, 2005, at 02:18 PM by 193.205.157.115 -
Added lines 168-176:

Using the Output Sandbox

If the job produces some output files, they must be listed in the OutputSandbox JDL Attribute. Moreover, the OutputSandboxDestURI attribute must be specified as well, and point to a suitable gridftp server. The Job Wrapper (JW) will transfer every file specified in the OutputSandbox attribute to the given gridftp server, as soon as the job is succesfully completed.

September 06, 2005, at 02:08 PM by 193.205.157.115 -
Changed lines 154-156 from:
to:

Using the Input Sandbox

If the job needs to process some input files, they can be uploaded in the job's Input Sandbox (ISB) using gridftp. In the example above, the ISB URI: line describes the URI where the ISB is located. The content (list of file names) of the ISB must be specified using the InputSandbox JDL Attribute (see the CREAM JDL attribute specification document for mode details). So, in order to upload files /home/marzolla/SomeFile.txt on the ISB, you do something like this:

gridftp file:///home/marzolla/SomeFile.txt gsiftp://grid006.pd.infn.it/opt/glite/var/cream/CN_Moreno_Marzolla,L_Padova,OU_Personal_Certificate,O_INFN,C_IT/CREAM51113/ISB

where the gsiftp:///<...> string is exactly the content of the ISB URI: line reported by the JobRegister.

August 04, 2005, at 06:03 PM by 193.205.157.115 -
Changed lines 14-17 from:

In order to facilitate execution of the Java programs, the following Shell script can be useful:

If you are using the version compiled for Axis1.1:

to:

CREAM compiled with Axis 1.1

In order to facilitate execution of the Java programs, the following Shell script can be useful; note that this script must be used if you are using the version of CREAM compiled with Axis1.1:

Changed lines 45-46 from:

If you are using the version compiled for Axis 1.2:

to:

where <Command> is one of JobRegister, JobStart, JobCancel, JobList, JobInfo and JobPurge. The script(s) could be put anywhere in the filesystem, but the user must redefine the variable dir to point to the workspace where CREAM has been built.

The scripts, along with the compiled Java programs needed to run the CLI tools can be found on the CREAM Java client examples page.

CREAM compiled with Axis 1.2

The most recent version of CREAM uses Axis 1.2. From the Java CLI point of view, this requires a different set of jars to be executed. The shell script in this case is the following:

Changed lines 85-93 from:

where <Command> is one of JobRegister, JobStart, JobCancel, JobList, JobInfo and JobPurge. The script(s) could be put anywhere in the filesystem, but the user must redefine the variable dir to point to the workspace where CREAM has been built.

The scripts, along with the compiled Java programs needed to run the CLI tools can be found on the CREAM Java client examples page.

to:

A slightly different script, along with the compiled Java programs needed to run the CLI tools can be found on the CREAM Java client examples for Axis1.2 page.

Note: The new script, called CREAMClient.sh, must be used differently from the old scripts. The syntax is the following:

./CREAMClient.sh <command> <parameters>

where <command> is one of the CREAM commands, and <parameters> are the needed parameters. The commands are the ones described in the following sections. To get a full list, just type:

./CREAMClient.sh
August 04, 2005, at 10:48 AM by 193.205.157.115 -
Added lines 16-17:

If you are using the version compiled for Axis1.1:

Added lines 44-74:

If you are using the version compiled for Axis 1.2:

#!/bin/sh dir=$HOME/workspace classpath=.:$dir/repository/bcprov-jdk14/1.22/share/jars/jce-jdk13-122.jar:\ /usr/share/java/activation.jar:\ $dir/repository/javamail/1.3.1/share/lib/mailapi.jar:\ $dir/repository/bcprov-jdk14/1.22/share/jars/bcpg-jdk14-122.jar:\ $dir/repository/xerces2-j/2.6.2/share/xercesImpl.jar:\ $dir/repository/xerces2-j/2.6.2/share/xml-apis.jar:\ $dir/repository/xerces2-j/2.6.2/share/resolver.jar:\ $dir/repository/xerces2-j/2.6.2/share/xmlParserAPIs.jar:\ $dir/repository/axis/1.2/share/lib/axis.jar:\ $dir/repository/axis/1.2/share/lib/commons-logging-1.0.4.jar:\ $dir/repository/axis/1.2/share/lib/jaxrpc.jar:\ $dir/repository/axis/1.2/share/lib/commons-discovery-0.2.jar:\ $dir/repository/axis/1.2/share/lib/log4j-1.2.8.jar:\ $dir/repository/axis/1.2/share/lib/saaj.jar:\ $dir/repository/axis/1.2/share/lib/wsdl4j-1.5.1.jar:\ $dir/stage/share/java/glite-ce-cream-api-java.jar:\ $dir/stage/share/java/glite-ce-cream.jar:\ $dir/stage/share/java/glite-ce-cream-examples.jar:\ $dir/stage/share/java/glite-ce-delegation.jar:\ $dir/stage/share/java/glite-security-delegation-java.jar:\ $dir/stage/share/java/glite-security-util-java.jar:\ $dir/stage/share/java/glite-security-trustmanager.jar:\ $dir/stage/share/java/glite-security-authz-framework-java.jar java -cp $classpath org.glite.ce.cream.client.<Command> "$@"

July 19, 2005, at 02:20 PM by 193.205.157.115 -
Changed lines 143-144 from:
<jobID>
The CREAM Job ID returned by JobRegister, which identifies the job to be cancelled; multiple job IDs can be

specified, separated by spaces.

to:
<jobID>
The CREAM Job ID returned by JobRegister, which identifies the job to be cancelled; multiple job IDs can be specified, separated by spaces.
Changed lines 193-196 from:
  1. If the --from option is given, then only jobs from step (1) which are registered after then given

date are considered.

  1. If the --to option is given, then only jobs from step (1-2) which are registered before then given

date are considered.

to:
  1. If the --from option is given, then only jobs from step (1) which are registered after then given date are considered.
  2. If the --to option is given, then only jobs from step (1-2) which are registered before then given date are considered.
Changed lines 202-207 from:
--from <date>
(optional) Retrieve informations only for jobs registered after this date. <date> must be

in the format yyyy/mm/dd hh:mm:ss (default: registration time of user's oldest job).

--to <date>
(optional) Retrieve informations only for jobs registered before this date. The <date>

parameter must be in the format yyyy/mm/dd hh:mm:ss (default: now).

-a|--all
(optional) If the user does not specify a list of job IDs, then all non-purged

jobs are retrieved (however, other filtering might be applied, see above).

to:
--from <date>
(optional) Retrieve informations only for jobs registered after this date. <date> must be in the format yyyy/mm/dd hh:mm:ss (default: registration time of user's oldest job).
--to <date>
(optional) Retrieve informations only for jobs registered before this date. The <date> parameter must be in the format yyyy/mm/dd hh:mm:ss (default: now).
-a|--all
(optional) If the user does not specify a list of job IDs, then all non-purged jobs are retrieved (however, other filtering might be applied, see above).
Changed lines 243-244 from:
-a|--all
(optional) If the user does not specify a list of job IDs, then all

jobs in state DONE-OK, DONE-FAILED, CANCELLED or REGISTERED are purged.

to:
-a|--all
(optional) If the user does not specify a list of job IDs, then all jobs in state DONE-OK, DONE-FAILED, CANCELLED or REGISTERED are purged.
July 19, 2005, at 01:09 PM by 193.205.157.115 -
Added lines 3-4:
Added lines 44-50:

The scripts, along with the compiled Java programs needed to run the CLI tools can be found on the CREAM Java client examples page.

Changed lines 61-67 from:

The JobRegister command accepts the following parameters:

-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM. The Delegation Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAMDelegation
-d|--delegationId <did>
(optional) Use the given delegation ID (if omitted, a new ID is generated)
--autostart
(optional) Automatically start the job (does not require to call jobStart explicitly)
-h|--help
(optional) Get a brief description of the command line options
to:

The JobRegister command supports the following command-line parameters:

JobRegister [-d|--delegationId <did>] -r|--resource <endpoint> [-h|--help] [--autostart] <jdl>
-d|--delegationId <did>
(optional) Use the given delegation ID (if omitted, a new ID is generated).
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM. The Delegation Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAMDelegation.
-h|--help
(optional) Get a brief description of the command line options.
--autostart
(optional) Automatically start the job (does not require to call jobStart explicitly).
<jdl>
(mandatory) The JDL (Job Description Language) file containing informations on the job to be registered.

Example

Consider the file test.jdl with the following content:

[ VirtualOrganisation = "topolino"; requirements = other.GlueCEStateStatus == "Production"; Rank = -other.GlueCEStateEstimatedResponseTime; executable="/bin/sleep"; arguments="300"; BatchSystem="lsf"; QueueName="grid02" ]

To register this job you execute:

JobRegister -r https://grid006.pd.infn.it:8443 test.jdl

The output might look like this:

resource: https://grid006.pd.infn.it:8443 delegation ID: null autostart? false jdlfile: test.jdl Using Delegation ID: 1121770063225 Delegation Port: https://grid006.pd.infn.it:8443/ce-cream/services/CREAMDelegation - Client CN=grid006.pd.infn.it, L=Padova, OU=Host, O=INFN, C=IT accepted - Client CN=grid006.pd.infn.it, L=Padova, OU=Host, O=INFN, C=IT accepted - Client CN=grid006.pd.infn.it, L=Padova, OU=Host, O=INFN, C=IT accepted https://grid006.pd.infn.it:8443/CREAM51113 ISB URI: gsiftp://grid006.pd.infn.it/opt/glite/var/cream/CN_Moreno_Marzolla,L_Padova,OU_Personal_Certificate,O_INFN,C_IT/CREAM51113/ISB

In this case, the job ID is the string https://grid006.pd.infn.it:8443/CREAM51113, and can be used to later start the job.

Added lines 111-131:

The JobStart command is used to start an already registered job. The job status can be inquired using the JobInfo command.

The JobStart command supports the following command line parameters:

JobStart [-h|--help] -r|--resource <endpoint> <jobID>
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
<jobID>
The CREAM Job ID returned by JobRegister, which identifies the job to be started.
-h|--help
(optional) Get a brief description of the command line options.

Example

To start a job with CREAM ID https://grid006.pd.infn.it:8443/CREAM51113, you give:

JobStart -r https://grid006.pd.infn.it:8443 https://grid006.pd.infn.it:8443/CREAM51113
Added lines 134-156:

This command can be used to cancel a job which has been started either using the --autostart flag of JobRegister, or has been manually started via the JobStart command.

The syntax is the following:

JobCancel -r|--resource <endpoint> [-h|--help] -a|--all|<jobId> ...
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
<jobID>
The CREAM Job ID returned by JobRegister, which identifies the job to be cancelled; multiple job IDs can be

specified, separated by spaces.

-a|--all
This option can be used to cancel all jobs owned by the user. Use with care!
-h|--help
(optional) Get a brief description of the command line options.

Example

To cancel the job with CREAM ID https://grid006.pd.infn.it:8443/CREAM51113, you give:

JobCancel -r https://grid006.pd.infn.it:8443 https://grid006.pd.infn.it:8443/CREAM51113
Added lines 159-184:

Lists the CREAM IDs of all jobs owned by the user, which are known to CREAM; this means all jobs which have not been purged. Note that only the job IDs are shown.

JobList -r|--resource <endpoint> [-h|--help]
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
-h|--help
(optional) Get a brief description of the command line options.

Example

To show the IDs of all non-purged jobs, you give:

JobList -r https://grid006.pd.infn.it:8443

The output may look like this: resource: https://grid006.pd.infn.it:8443 - Client CN=grid006.pd.infn.it, L=Padova, OU=Host, O=INFN, C=IT accepted 0) https://grid006.pd.infn.it:8443/CREAM18091 1) https://grid006.pd.infn.it:8443/CREAM51113 2 jobs listed

Changed line 194 from:
  1. If the --from option is given, then only jobs from step (1) which are registered "after" then given
to:
  1. If the --from option is given, then only jobs from step (1) which are registered after then given
Changed line 196 from:
  1. If the --to option is given, then only jobs from step (1-2) which are registered "before" then given
to:
  1. If the --to option is given, then only jobs from step (1-2) which are registered before then given
Changed lines 204-205 from:
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
--from <date>
(optional) Retrieve informations only for jobs registered after this date. <date> "must" be
to:
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
--from <date>
(optional) Retrieve informations only for jobs registered after this date. <date> must be
Changed line 208 from:

parameter "must" be in the format yyyy/mm/dd hh:mm:ss (default: now).

to:

parameter must be in the format yyyy/mm/dd hh:mm:ss (default: now).

Changed line 211 from:
-s|--status <s>[,<s>...]
Displays informations for jobs whose status is in the given comma-separated list of states. <s>:=RUNNING| PENDING| DONE-OK| DONE-FAILED| CANCALLED| IDLE| ABORTED| UNKNOWN| REGISTERED| HELD
to:
-s|--status <s>
Displays informations for jobs in a given status; multiple -s options may be combined to list all jobs in one of the given states. <s>:=RUNNING| PENDING| DONE-OK| DONE-FAILED| CANCALLED| IDLE| ABORTED| UNKNOWN| REGISTERED| HELD
Changed lines 214-234 from:
to:

Examples

The following command:

JobInfo -r https://grid006.pd.infn.it:8443 --from "2005/07/18 08:00:00" -a

shows informations for all jobs registered to grid006.pd.infn.it after jul 18, 2005 08:00:00.

The command:

JobInfo -r https://grid006.pd.infn.it:8443 --to "2005/07/18 07:30:00" -s PENDING -s UNKNOWN

shows informations for all jobs which are either in PENDING or UNKNOWN status and have been registered to grid006.pd.infn.it before jul 18, 2005 07:30:00.

Changed lines 237-238 from:
to:

This command can be used to purge non-running jobs from CREAM. Purging a job means erasing all temporary files (including the JDL, the proxy certificate and so on) from CREAM working directory. From the moment a job has been purged, CREAM will know nothing about it.

A job can be purged only if it is in one of the following states: DONE-OK, DONE-FAILED, CANCALLED or REGISTERED. To purge running jobs, they first must be cancelled with JobCancel.

JobPurge -r|--resource <endpoint> [-h|--help] -a|--all|<jobId> ...
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
-a|--all
(optional) If the user does not specify a list of job IDs, then all

jobs in state DONE-OK, DONE-FAILED, CANCELLED or REGISTERED are purged.

<jobId>...
The list of CREAM job IDs to purge.
-h|--help
(optional) Get a brief description of the command line options.

Examples

To purge all terminated jobs, issue the following command:

JobPurge -r https://grid006.pd.infn.it:8443 -a
July 18, 2005, at 03:52 PM by 193.205.157.115 -
Changed lines 38-39 from:

java -cp $classpath org.glite.ce.cream.client.<Command> $@=]

to:

java -cp $classpath org.glite.ce.cream.client.<Command> "$@"=]

Changed lines 54-58 from:
-r|--resource <endpoint>
The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM. The Delegation Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAMDelegation
-d|--delegationId <did>
Use the given delegation ID (if omitted, a new ID is generated)
--autostart
Automatically start the job (does not require to call jobStart explicitly)
-h|--help
Get explanation on the command line options
to:
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM. The Delegation Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAMDelegation
-d|--delegationId <did>
(optional) Use the given delegation ID (if omitted, a new ID is generated)
--autostart
(optional) Automatically start the job (does not require to call jobStart explicitly)
-h|--help
(optional) Get a brief description of the command line options
Added lines 67-94:

The JobInfo command can be used to get informations on jobs currently known to CREAM. Each user can get information on all its owned jobs which has been registered to the CREAM service and which have not been purged yet. Thus, it is possible to access registered, terminated or cancelled jobs.

The selection algorithm used by CREAM to choose the jobs to examine is the following:

  1. If the user specifies a list of job IDs, only a subset of those jobs is considered; otherwise, all non-purged jobs owner by the user are considered.
  2. If the --from option is given, then only jobs from step (1) which are registered "after" then given

date are considered.

  1. If the --to option is given, then only jobs from step (1-2) which are registered "before" then given

date are considered.

  1. If the --status option is used to provide a list of job states, then only jobs from step (1-3) which are in one of the given states are queried.

The JobInfo command accepts the following parameters:

JobInfo -r|--resource <endpoint> [-h|--help] [-s|--status <s>] [--from <date>] [--to <date>] [-a|--all|<jobId> ...]
-r|--resource <endpoint>
(mandatory) The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM.
--from <date>
(optional) Retrieve informations only for jobs registered after this date. <date> "must" be

in the format yyyy/mm/dd hh:mm:ss (default: registration time of user's oldest job).

--to <date>
(optional) Retrieve informations only for jobs registered before this date. The <date>

parameter "must" be in the format yyyy/mm/dd hh:mm:ss (default: now).

-a|--all
(optional) If the user does not specify a list of job IDs, then all non-purged

jobs are retrieved (however, other filtering might be applied, see above).

-s|--status <s>[,<s>...]
Displays informations for jobs whose status is in the given comma-separated list of states. <s>:=RUNNING| PENDING| DONE-OK| DONE-FAILED| CANCALLED| IDLE| ABORTED| UNKNOWN| REGISTERED| HELD
-h|--help
(optional) Get a brief description of the command line options
July 08, 2005, at 12:36 PM by 192.135.8.20 -
Added lines 44-58:

The JobRegister command must be used in order to register a new job on the CE. Registering a job means that a new temporary directory is created for that node on the CE, and some files are created there (a copy of the JDL, a copy of the certificate, the job wrapper...).

It is possible to immediately start the job (that is, submit it to the batch system), or start the job later by invoking the JobStart command.

The JobRegister command accepts the following parameters:

-r|--resource <endpoint>
The endpoint to use (in the form https://<host>:<port>). The CREAM Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAM. The Delegation Service is assumed to be at https://<host>:<port>/ce-cream/services/CREAMDelegation
-d|--delegationId <did>
Use the given delegation ID (if omitted, a new ID is generated)
--autostart
Automatically start the job (does not require to call jobStart explicitly)
-h|--help
Get explanation on the command line options
July 07, 2005, at 04:08 PM by Moreno Marzolla -
Changed lines 12-13 from:

In order to facilitate the execution of the programs, the following Shell script can be useful:

to:

In order to facilitate execution of the Java programs, the following Shell script can be useful:

July 07, 2005, at 04:07 PM by Moreno Marzolla -
Changed lines 3-4 from:

(Under preparation)

to:

Introduction

A few sample CLI Java tools are provided inside the org.glite.ce.cream package. These tools can be used to test the CREAM service, and as examples for building custom Java CREAM clients.

This document describes the basic usage of the Java CLI clients; the commented source code can be found in org.glite.ce.cream/examples.

In order to facilitate the execution of the programs, the following Shell script can be useful:

#!/bin/sh dir=$HOME/workspace classpath=.:$dir/repository/bcprov-jdk14/1.22/share/jars/jce-jdk13-122.jar:\ $dir/repository/bcprov-jdk14/1.22/share/jars/bcpg-jdk14-122.jar:\ $dir/repository/xerces2-j/2.6.2/share/xercesImpl.jar:\ $dir/repository/xerces2-j/2.6.2/share/xml-apis.jar:\ $dir/repository/xerces2-j/2.6.2/share/resolver.jar:\ $dir/repository/xerces2-j/2.6.2/share/xmlParserAPIs.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/jaxrpc.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/axis.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/commons-discovery.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/commons-logging.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/log4j-1.2.8.jar:\ $dir/repository/axis/1.1/share/axis-1_1/lib/saaj.jar:\ $dir/stage/share/java/glite-ce-cream-api-java.jar:\ $dir/stage/share/java/glite-ce-cream.jar:\ $dir/stage/share/java/glite-ce-cream-examples.jar:\ $dir/stage/share/java/glite-ce-delegation.jar:\ $dir/stage/share/java/glite-security-delegation-java.jar:\ $dir/stage/share/java/glite-security-util-java.jar:\ $dir/stage/share/java/glite-security-trustmanager.jar:\ $dir/stage/share/java/glite-security-authz-framework-java.jar java -cp $classpath org.glite.ce.cream.client.<Command> $@

where <Command> is one of JobRegister, JobStart, JobCancel, JobList, JobInfo and JobPurge. The script(s) could be put anywhere in the filesystem, but the user must redefine the variable dir to point to the workspace where CREAM has been built.

JobRegister

JobStart

JobCancel

JobList

JobInfo

JobPurge

July 07, 2005, at 03:41 PM by 192.135.8.20 -
Added lines 1-4:

CREAM Java Command Line Interface Documentation

(Under preparation)