Not necessarily. At least for streaming, you'd need one. But you
can send stdout/err to whatever gridftp server you want, including
the one on the GRAM4 machine itself. All you need is a globus-url-
copy client to retrieve it later, which CoG has, doesn't it?
Charles
On Sep 13, 2007, at 12:18 PM, Mihael Hategan wrote:
On Thu, 2007-09-13 at 18:26 +0200, Olivier Ricou wrote:
die 13/09/07, ad 17h50, Mihael Hategan <[EMAIL PROTECTED]> dixit :
On Thu, 2007-09-13 at 17:29 +0200, Olivier Ricou wrote:
die 13/09/07, ad 00h41, Mihael Hategan <[EMAIL PROTECTED]>
dixit :
On Thu, 2007-09-13 at 00:17 +0200, Olivier Ricou wrote:
but the mailing lists are dead (so ?). It is said Java COG is
GT4 compatible but the is no globusrun-ws.
There is cog-job-submit. If you specify "gt4" as a provider
(the -p
argument), it will submit to WS-GRAM.
fine, but it seems we cannot get back the results with GT4.
I'm not sure what you mean by that.
-r is not working with -p gt4
Right. Redirection in ws-gram can only be done if you have a GridFTP
server installed on your client machine as far as I know. Which was
mainly the reason CoG doesn't support it.
However, WS-GRAM has a Java client (accessible through the API) which
CoG uses. You could install that and wrap it in a command line
thing. In
the Globus source tree, it's in ws-gram/client/java.
However, if I'm right about the GridFTP issue above, you would still
need a GridFTP server on the client machine. And then you're back to
square one.
Mihael
