Currently Supported Schemes

SCHEME

SUPPORTED OPERATIONS

file

ALL

ftp, gsiftp, gridftp, mssftp

ALL except touch

http

delete, copy (as source only; = GET)

resource

verify, ls, copy (as source only; also see note below)

ssh, scp, gsissh, gsiscp

ALL

webdav

ALL except touch

NOTES

  1. All ftp operation schemes map to the same set of clients implemented using the jglobus library. The mssftp scheme is specific to the UNITREE mass-storage system; if the source or target is on such a system, its URI must have this scheme.
  2. When doing a resource-copy, it is always best to specify the plugin (if known) as the host; else, if running inside an RCP/OSGI container, the operation is not guaranteed to work. See the example.
  3. Of the verify operations for the resource:/ scheme, only exists is guaranteed to work both in and outside of RCP/OSGI. Listing is always "shallow".
  4. If ssh:/ or scp:/ are used, then either a user:password should be included in the URI, or a public-key-pair should exist for the user on the two endpoints involved. The gsissh:/ and gsiscp:/ schemes assume the presence of GSISSH on the target, and use the same proxy mechanism as GridFTP.

Examples

<ogrescript name="test-resource">
   <copy>
   	<uri-pair source="resource://ncsa.tools.trebuchet.tests/oracles/FileCopyClientTest_test00CopyAll" target="file:/tmp"/>
   	<uri-pair source="resource://ncsa.tools.ogrescript.tests/test-task-with-attribute.xml" target="file:/tmp"/>
   </copy>
</ogrescript>
  • No labels