Re: [gridsam-discuss] BES interface

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Dr Stephen Crouch:

Thank you very much for your kind explanation.
I have succeeded in using bes-interface.

> Out of interest, could I ask how you are currently using GridSAM?  And
> also, how you intend to use the BES interface?  It's always very

I intended to use the BES interface only because of getting a better understaing of BES.
I am now developing a seamless user interface for job-submission and
monitoring GUI tool for GridSAM and NAREGI(Japanese grid http://www.naregi.org). GridSAM service is on laboratory resources, 
and NAREGI is on grid resources.

Y.Tanaka

Steve Crouch wrote:
> Hi Y.Tanaka,
> 
> Yes, the OGSA-BES v1.0 interface is indeed supported within GridSAM.  By
> default, the GridSAM service already has this interface ready for use,
> so from the client, in the omii-uk-client/gridsam/bin directory for
> example, you can run:
> 
> ./bes-create-activity -s
> https://yourserver:port/gridsam/services/bes?wsdl -j something.jsdl
> 
> An EndpointReference (EPR) will be returned on std output which uniquely
> identifies the job, e.g. (formatted for clarity):
> 
> <?xml version="1.0" encoding="UTF-8"?>
> <EndpointReference xmlns="http://www.w3.org/2005/08/addressing">
> <Address>https://blade10.omii.ac.uk:18443/gridsam/services/bes</Address>
>   <ReferenceParameters>
>     <JobIdentifier xmlns="http://www.icenigrid.org/service/gridsam">
>       <ID>urn:gridsam:18ce6dd322a31d1b0122a70745c90028</ID>
>     </JobIdentifier>
>   </ReferenceParameters>
> </EndpointReference>
> 
> ...which you can capture like this:
> 
> ./bes-create-activity -s
> https://yourserver:port/gridsam/services/bes?wsdl -j something.jsdl >
> epr.text
> 
> And then use the following to check the status of the submission (see
> caveat below!):
> 
> ./bes-get-activity-statuses -s
> https://yourserver:port/gridsam/services/bes?wsdl -file epr.text
> 
> Which returns a GetActivityStatusResponse with the status(es) included.
>  This epr file can contain a number of EPRs, which means you can query
> the status of many jobs at a time.
> 
> You can also use the bes-terminate-activities command in a similar
> manner to pre-emptively kill jobs, and similarly the
> bes-get-activity-documents command to return JSDLs that were submitted
> for a given list of jobs.
> 
> Of course, being an open interface, you should be able to use any
> BES-v1.0 compliant client to submit jobs to GridSAM using this
> interface, although the tricky part is to configure compatible security
> between the BES client and GridSAM.  In addition, GridSAM also supports
> HPC Basic Profile v1.0 and HPC Profile Application Extension v1.0, which
> may be handy to look at when constructing JSDL that works between
> different BES implementations.
> 
> 
> In terms of how to use this interface within a client-side Java
> application, you can see how to use the API by looking within
> modules/client/src/main/java/org/icenigrid/gridsam/client/cli/ within
> the GridSAM source release on SourceForge, and looking at the API docs
> within the client release e.g.
> omii-uk-client/gridsam/docs/gridsam-client/apidocs
> 
> At the moment, however, there are a number of minor issues with the BES
> interface we are currently working on:
> 
> -- Completed documentation for the BES interface, support and commands
> 
> -- The bes-* commands currently return the following message when used:
> {http://schemas.xmlsoap.org/soap/envelope/}encodingStyle already exists
> 
> ...on the first line, which doesn't cause the commands to fail, but is a
> nuisance.  When submitting a job using bes-create-activity, you can
> filter this out using something like:
> 
> ./bes-create-activity -s
> https://yourserver:port/gridsam/services/bes?wsdl -j something.jsdl |
> grep -v 'encodingStyle already exists' > epr.text
> 
> Which removes the unwanted message and ensures the EPR can be used
> correctly.
> 
> -- The bes-get-factory-attributes-document command (which returns a list
> of available computational resources provided by the BES service)
> currently isn't supported within the Globus connector.
> 
> Out of interest, could I ask how you are currently using GridSAM?  And
> also, how you intend to use the BES interface?  It's always very
> valuable to know how our products are being used, and this can help us
> to be more informed when helping you in the future.
> 
> I hope this helps, please let us know if you have any further questions,
> 
> Regards,
> 
> Steve Crouch
> 
> 逕ー荳ュ縲セゥ荳wrote:
> > Hello
> > 
> > I have installed and used Gridsam2.1.4 by globus engine.
> > Paper says that Gridsam supports OGSA-BES standard.
> > If we can use BES-interface, please show me examples(how to 
> > use this interface in GridSAM)
> > 
> > Thanks in advance.
> > 
> > National Institute of Informatics
> > Y.Tanaka
> > 
> > 
> > 
> > ------------------------------------------------------------------------------
> > Enter the BlackBerry Developer Challenge  
> > This is your chance to win up to $100,000 in prizes! For a limited time, 
> > vendors submitting new applications to BlackBerry App World(TM) will have
> > the opportunity to enter the BlackBerry Developer Challenge. See full prize  
> > details at: http://p.sf.net/sfu/Challenge
> > _______________________________________________
> > GridSAM-Discuss mailing list
> > Gri...@li...
> > https://lists.sourceforge.net/lists/listinfo/gridsam-discuss
> 
> -- 
> Dr Stephen Crouch,
> Software Architect,
> OMII-UK,
> School of Electronics and Computer Science,
> Room 4067, Level 4, Building 32,
> University of Southampton,
> Highfield, Southampton SO17 1BJ
> Tel: +44 (0)23 8059 8787        EMail: s.c...@om...
> Fax: +44 (0)23 8059 3045        WWW: http://www.ecs.soton.ac.uk/~stc
> 
> 
> 