http://glite.org/wms/wmproxy
The jobCancel Operation
This operation cancels a previously submitted job identified by its JobId. If the job is still maaged by the WM then it is removed from the WM tasks queue. If the job has been already sent to the CE, the WM simply forwards the request to the CE. For suspending/eleasing and sending signals to a submitted job the user has to chek that the job has been scheduled to a CE and access directly the corresponding operations made avalable by the CE service. 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 is not valid. JobUnknownFault: the provided job has not been registerd to the system. OperationNotAllowedFault: current job status does not allow requested operation. GenericFault: another problem occured.
 Collapse Bindings
Binding: WMProxy
<soap:binding  style="rpc"
  transport="http://schemas.xmlsoap.org/soap/http" />
Operation:
 
Input: jobCancelRequest
<soap:body  namespace="http://glite.org/wms/wmproxy"
  use="literal" />
Output: jobCancelResponse
<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" />
 
InvalidArgumentFault: InvalidArgumentFault
<soap:fault  name="InvalidArgumentFault"
  use="literal" />
 
GenericFault: GenericFault
<soap:fault  name="GenericFault"
  use="literal" />
 
JobUnknownFault: JobUnknownFault
<soap:fault  name="JobUnknownFault"
  use="literal" />
 
OperationNotAllowedFault: OperationNotAllowedFault
<soap:fault  name="OperationNotAllowedFault"
  use="literal" />
 

 Collapse XML
-<wsdl:operation  name="jobCancel"  parameterOrder="jobId">
<wsdl:documentation> This operation cancels a previously submitted job identified by its JobId. If the job is still maaged by the WM then it is removed from the WM tasks queue. If the job has been already sent to the CE, the WM simply forwards the request to the CE. For suspending/eleasing and sending signals to a submitted job the user has to chek that the job has been scheduled to a CE and access directly the corresponding operations made avalable by the CE service. 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 is not valid. JobUnknownFault: the provided job has not been registerd to the system. OperationNotAllowedFault: current job status does not allow requested operation. GenericFault: another problem occured. </wsdl:documentation>
<wsdl:input  message="glitens:jobCancelRequest"  name="jobCancelRequest" />
<wsdl:output  message="glitens:jobCancelResponse"  name="jobCancelResponse" />
<wsdl:fault  message="glitens:AuthenticationFault"  name="AuthenticationFault" />
<wsdl:fault  message="glitens:InvalidArgumentFault"  name="InvalidArgumentFault" />
<wsdl:fault  message="glitens:JobUnknownFault"  name="JobUnknownFault" />
<wsdl:fault  message="glitens:OperationNotAllowedFault"  name="OperationNotAllowedFault" />
<wsdl:fault  message="glitens:GenericFault"  name="GenericFault" />
<wsdl:fault  message="glitens:AuthorizationFault"  name="AuthorizationFault" />
</wsdl:operation>
Generated by WSDLdoc ©