http://glite.org/wms/wmproxy
This operation triggers the submission a previously registered job. It starts the actual processing of the registered job within the Workload Manager. It is assumed that when this operation is called, all the work preparatory to the job (e.g. input sandbox upload, registration of input data to the Data Management service etc.) has been completed by the client.
To better clarify, an example of the correct sequence of operations for submitting a job could be:
1. jobId = jobRegist(JDL)
2. destURI = getSandboxDestURI(jobID)
3. transfer InputSandbox file to destURI (e.g. using GridFTP)
4. jobStart(jobId)
Note that the jobStart operation is not allowed on subjobs of a complex object, i.e. the input parameter must be either the id of a simple job or the main id of a complex object.
Input: string containing the jobId.
Output: no output.
Faults:
AuthenticationFault: a generic authentication problem occured.
AuthorizationFault: client is not authorized to perform this operation.
InvalidArgumentFault: the provided job Id expression is not valid.
JobUnknownFault: the provided job has not been registered to the system.
OperationNotAllowedFault: current job status does not allow requested operation.
GenericFault: another problem occured.
Operation Type: Request-response
Parameter order:
jobId
Fault:
Bindings |
Binding: WMProxy <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
Input: jobStartRequest <soap:body namespace="http://glite.org/wms/wmproxy" use="literal" />
Output: jobStartResponse <soap:body namespace="http://glite.org/wms/wmproxy" use="literal" />
Fault:
AuthenticationFault: AuthenticationFault
<soap:fault name="AuthenticationFault" use="literal" />
AuthorizationFault: AuthorizationFault
<soap:fault name="AuthorizationFault" use="literal" />
GenericFault: GenericFault
<soap:fault name="GenericFault" use="literal" />
JobUnknownFault: JobUnknownFault
<soap:fault name="JobUnknownFault" use="literal" />
|
|
XML |
-<wsdl:operation name="jobStart" parameterOrder="jobId">
<wsdl:documentation>
This operation triggers the submission a previously registered job. It starts the actual processing of the registered job within the Workload Manager. It is assumed that when this operation is called, all the work preparatory to the job (e.g. input sandbox upload, registration of input data to the Data Management service etc.) has been completed by the client.
To better clarify, an example of the correct sequence of operations for submitting a job could be:
1. jobId = jobRegist(JDL)
2. destURI = getSandboxDestURI(jobID)
3. transfer InputSandbox file to destURI (e.g. using GridFTP)
4. jobStart(jobId)
Note that the jobStart operation is not allowed on subjobs of a complex object, i.e. the input parameter must be either the id of a simple job or the main id of a complex object.
Input: string containing the jobId.
Output: no output.
Faults:
AuthenticationFault: a generic authentication problem occured.
AuthorizationFault: client is not authorized to perform this operation.
InvalidArgumentFault: the provided job Id expression is not valid.
JobUnknownFault: the provided job has not been registered to the system.
OperationNotAllowedFault: current job status does not allow requested operation.
GenericFault: another problem occured.
</wsdl:documentation>
</wsdl:operation>
|