http://glite.org/wms/wmproxy
This operation returns a destination URI associated to the job, identified by the jobId provided as input, where the job input sandbox files can be uploaded by the client on the WMS node. The location is created in the storage managed by the WM and the corresponding URI is returned to the operation caller if no problems has been arised during creation. Files of the job input sandbox that have been referenced in the JDL as relative or absolute paths are expected to be found in the returned location when the job lands on the CE.
Note that the WM service only provides a the URI of a location where the job input sandbox files can be stored but does not perform any file transfer. File upload is indeed responsibility of the client (through the GridFTP service available on the WMS node).
The user can also specify in the JDL the complete URI of files that are stored on a GridFTP server (e.g. managed by her organisation); those files will be directly downloaded (by the JobWrapper) on the WN where the job will run without transiting on the WM machine.
The same applies to the output sandbox files list, i.e. the user can specify in the JDL the complete URIs for the files of the output sandbox; those files will be directly uploaded (by the JobWrapper) from the WN to the specified GridFTP servers without transiting on the WMS machine.
Input: string containing the JobId.
Output: a vector containing the string representation of the Destination URI in all the available protocols
Faults:
AuthenticationFault: a generic authentication problem occured.
AuthorizationFault: client is not authorized to perform this operation.
InvalidArgumentFault: the provided job Id is not valid.
GenericFault: another problem occured.
JobUnknownFault: the provided job has not been registered to the system.
OperationNotAllowedFault: current job status does not allow requested operation.
Operation Type: Request-response
Parameter order:
jobId
Fault:
Bindings |
Binding: WMProxy <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http" />
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="getSandboxDestURI" parameterOrder="jobId">
<wsdl:documentation>
This operation returns a destination URI associated to the job, identified by the jobId provided as input, where the job input sandbox files can be uploaded by the client on the WMS node. The location is created in the storage managed by the WM and the corresponding URI is returned to the operation caller if no problems has been arised during creation. Files of the job input sandbox that have been referenced in the JDL as relative or absolute paths are expected to be found in the returned location when the job lands on the CE.
Note that the WM service only provides a the URI of a location where the job input sandbox files can be stored but does not perform any file transfer. File upload is indeed responsibility of the client (through the GridFTP service available on the WMS node).
The user can also specify in the JDL the complete URI of files that are stored on a GridFTP server (e.g. managed by her organisation); those files will be directly downloaded (by the JobWrapper) on the WN where the job will run without transiting on the WM machine.
The same applies to the output sandbox files list, i.e. the user can specify in the JDL the complete URIs for the files of the output sandbox; those files will be directly uploaded (by the JobWrapper) from the WN to the specified GridFTP servers without transiting on the WMS machine.
Input: string containing the JobId.
Output: a vector containing the string representation of the Destination URI in all the available protocols
Faults:
AuthenticationFault: a generic authentication problem occured.
AuthorizationFault: client is not authorized to perform this operation.
InvalidArgumentFault: the provided job Id is not valid.
GenericFault: another problem occured.
JobUnknownFault: the provided job has not been registered to the system.
OperationNotAllowedFault: current job status does not allow requested operation.
</wsdl:documentation>
</wsdl:operation>
|