http://glite.org/wms/wmproxy
The jobSubmit Operation
This operation submits a job. The JDL description of the job provided by the client is validated by the service, registered to the LB and finally passed to the Workload Manager. The unique identifier assigned to the job is returned to the client. This operation assumes that 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. Usage of this operation (instead of jobRegister + jobStart) is indeed recommended when the job identifier is not needed prior to its submission (e.g. jobs without input sandbox or with a sandbox entirely available on a GridFTP server managed by the client). The service supports submission of simple jobs, parametric jobs, partitionable jobs, DAGs and collections of jobs; the description is always provided through a single JDL description (see "GLite JDL Attributes" document for details). When a clients requests for submission of a complex object, i.e. parametric and partitionable jobs, DAGs and collections of jobs (all those requests represent in fact a set of jobs), the operations returns a structure containing the main identifier of the complex object and the identifiers of all related sub jobs. Input: string containing the job jdl representation. Input: string containing the Id of the delegated proxy associated to the job. Output: no output. Faults: AuthenticationFault: a generic authentication problem occured. AuthorizationFault: client is not authorized to perform this operation. InvalidArgumentFault: the provided job JDL expression is not valid. GenericFault: another problem occured.
jobSubmitResponse  jobSubmit (string jdl, string delegationId)
[fault:  AuthenticationFault  InvalidArgumentFault  GenericFault  AuthorizationFault  ]
Operation Type: Request-response
Parameter order: jdl  delegationId 
Collapse Input: jobSubmitRequest
string jdl  
string delegationId  
Collapse Output: jobSubmitResponse
JobIdStructType jobIdStruct  
Collapse Fault:
AuthenticationFault 
AuthenticationFault fault  
InvalidArgumentFault 
InvalidArgumentFault fault  
GenericFault 
GenericFault GenericFault  
AuthorizationFault 
AuthorizationFault fault  
 Collapse Bindings
Binding: WMProxy
<soap:binding  style="rpc"
  transport="http://schemas.xmlsoap.org/soap/http" />
Operation:
 
Input: jobSubmitRequest
<soap:body  namespace="http://glite.org/wms/wmproxy"
  use="literal" />
Output: jobSubmitResponse
<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" />
 

 Collapse XML
-<wsdl:operation  name="jobSubmit"  parameterOrder="jdl delegationId">
<wsdl:documentation> This operation submits a job. The JDL description of the job provided by the client is validated by the service, registered to the LB and finally passed to the Workload Manager. The unique identifier assigned to the job is returned to the client. This operation assumes that 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. Usage of this operation (instead of jobRegister + jobStart) is indeed recommended when the job identifier is not needed prior to its submission (e.g. jobs without input sandbox or with a sandbox entirely available on a GridFTP server managed by the client). The service supports submission of simple jobs, parametric jobs, partitionable jobs, DAGs and collections of jobs; the description is always provided through a single JDL description (see "GLite JDL Attributes" document for details). When a clients requests for submission of a complex object, i.e. parametric and partitionable jobs, DAGs and collections of jobs (all those requests represent in fact a set of jobs), the operations returns a structure containing the main identifier of the complex object and the identifiers of all related sub jobs. Input: string containing the job jdl representation. Input: string containing the Id of the delegated proxy associated to the job. Output: no output. Faults: AuthenticationFault: a generic authentication problem occured. AuthorizationFault: client is not authorized to perform this operation. InvalidArgumentFault: the provided job JDL expression is not valid. GenericFault: another problem occured. </wsdl:documentation>
<wsdl:input  message="glitens:jobSubmitRequest"  name="jobSubmitRequest" />
<wsdl:output  message="glitens:jobSubmitResponse"  name="jobSubmitResponse" />
<wsdl:fault  message="glitens:AuthenticationFault"  name="AuthenticationFault" />
<wsdl:fault  message="glitens:InvalidArgumentFault"  name="InvalidArgumentFault" />
<wsdl:fault  message="glitens:GenericFault"  name="GenericFault" />
<wsdl:fault  message="glitens:AuthorizationFault"  name="AuthorizationFault" />
</wsdl:operation>
Generated by WSDLdoc ©