sorry fo late response but no..it is not possible with current version of
RFT.
On 2/19/08, Roelof Kemp <[EMAIL PROTECTED]> wrote:
>
> Hi Folks,
>
> Haven't got any reply on this mail. Am I sending it to the wrong list? I
> want to know whether it's possible to copy a file using rft to a location
> relative to your ${GLOBUS_USER_HOME} without knowing beforehand the exact
> content of this variable.
>
> Cheers,
>
> Roelof
>
> Roelof Kemp wrote:
>
> Hi Folks,
>
> I've got a problem copying a file from machine A to machine B using RFT. I
> want to have a file from A to end up at B in "${GLOBUS_USER_HOME}/file".
> However, this seems to be impossible, unless you know the contents of
> ${GLOBUS_USER_HOME}.
>
> I construct the transferArray according to (
> http://www.globus.org/toolkit/docs/4.0/data/rft/developer-index.html#s-rft-developer-tutorials)
> like this:
>
> TransferType[] transferArray = new TransferType[1];
> transferArray[0] = new TransferType();
> transferArray[0].setSourceUrl("gsiftp://foo/bar");
> transferArray[0].setDestinationUrl("gsiftp://blah/");
>
> The path part of the URL is in the first case '/bar' and in the second
> '/'. So it copies '/bar' to '/', which is the root of the filesystem, and on
> grid machines you normally don't have permission to copy your file to that
> location. What I'd like to have is something similar to the staging with
> GRAM, for instance:
>
> TransferType[] transferArray = new TransferType[1];
> transferArray[0] = new TransferType();
> transferArray[0].setSourceUrl("gsiftp://foo/bar");
> transferArray[0].setDestinationUrl("gsiftp://blah/${GLOBUS_USER_HOME}/baz");
>
> Which will end up in your own directory. I noticed that this doesn't work
> RFT.
>
> Is there a work-around (where you don't know the contents of
> ${GLOBUS_USER_HOME} beforehand)?
>
> Any ideas?
>
> Cheers,
>
> Roelof Kemp
>
>
>
>
--
-- Ravi
Ravi K Madduri
The Globus Alliance | Argonne National Laboratory
http://www-unix.mcs.anl.gov/~madduri