Assuming you have successfully installed UCC, this section shows you how to manage and monitor jobs on OGSA-BES services using UCC. The set of commands not only supports UNICORE based implementation, but also implementations in other Grid middlewares compliant with OGF's OGSA-BES specification.
Learn more on UNICORE's OGSA-BES implementation.
In UNICORE style, users are required to provide a Registry URL inside the preferences file. For BES users it is not always the case that an endpoint is hosted via a UNICORE Registry. Therefore, the configuration options allow user to modify this behaviour.
contact-registry=[true|false]
Users willing to disable UCC calling the registry can set the "contact-registry" option to false. By default the "contact-registry" option is true.
After setting "contact-registry" to false, OGSA-BES users must provide at least one BESFactory URL using the following format.
bes.1=https://site1.com/services/BESFactory bes.2=https://site2.com/services/BESFactory bes.3=https://site3.com/services/BESFactory bes.4=file:///tmp/bes-jugene.xml bes.5=/tmp/bes-juropa.xml ...
If the "contact-registry" option is set to false and no OGSA-BES URL is specified, UCC will report an error.
To use EPR file path for a BESFactory service, the contents of a EPR file must validate against the WS-Addressing's endpoint reference schema. See below the contents of the sample endpoint reference file,
<wsa:EndpointReference xmlns:wsa="http://www.w3.org/2005/08/addressing"> <wsa:Address> https://localhost:8080/DEMO-SITE/services/BESFactory?res=default_bes_factory </wsa:Address> </wsa:EndpointReference>
In the above XML snippet, under the "Address" tag, you must specify the URL of a target BESFactory service.
For the sake of convenience, here is an XML infoset representation taken from the WS-Addressing specification,
<EndpointReference> <Address>xs:anyURI</Address> <ReferenceParameters>xs:any*</ReferenceParameters> ? <Metadata>xs:any*</Metadata>? </EndpointReference>
UCC provides an easy to use command for submitting jobs on OGSA-BES complaint endpoints. Following is the typical command usage for sending job as a JSDL file,
ucc bes-submit-job -c conf/preferences -j hellompi.xml -s bes.3 -v
Alternatively job can be submitted using a BESFactory URL or endpoint reference file path.
ucc bes-submit-job -c conf/preferences -j hellompi.xml -s https://example3.com/services/BESFactory -v
or
ucc bes-submit-job -c conf/preferences -j hellompi.xml -s file:///tmp/bes-jugene.xml -v
UCC can also take a JSON based job description, though a minimal set of JSON constructs are supported for the OGSA-BES extensions. Thus, it is strongly recommended to supply job requests in JSDL format.
Users can easily fetch a job status by specifying the descriptor (.job) file. This file is automatically generated after a successful execution of "bes-submit-job" command.
Example ucc bes-job-status jobid.job
Job can be terminated using a job descriptor file.
ucc bes-terminate-job jobid.job
To list BESFactory properties
ucc bes-list-att -s bes.1
The above command will result in BESFactory's properties without jobs information.
To see the list of the user's jobs on a BESFactory
ucc bes-list-job -s bes.1