You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Diagram

Unable to render 'XSD Viewer' macro

Could not find the given XSD (xsd_macro611b535d5e1f57a29d15bd06aa4c6db2.png) on page (JADE Parameter Reference - AlternativeGetListSourceFragmentRef)

Elements

AlternativeGetListSourceFragmentRef
References Notes

Alternative fragements can be specified as a replacement for existing file transfer fragments in case that a connection cannot be established with those fragments.

Alternative fragments can be specified from a range of protocol fragments for use with the source of a file transfer operation without modifying files.

For each fragment type depending on the file transfer protocol in use an alternative fragment type is available.

Element Type Required Description
FTPFragmentRef
  • Occurrence: 1
Required
References Notes

This element references the fragment that is used for an FTP file transfer operation.

Any number of reusable FTPFragment elements can be configured and are distinguished by YADE based on their name attribute.

The reference to a fragment is based on the value of the ref attribute of this element to the corresponding name attribute of the FTPFragment element.

ref

This attribute identifies the fragment that is used for the FTP protocol.

FTPSFragmentRef
  • Occurrence: 1
Required
References Notes

This element references the fragment that is used for an FTPS file transfer operation. Any number of reusable FTPSFragment elements can be configured and are distinguished by YADE based on their name attribute.

The reference to a fragment is based on the value of the ref attribute of this element to the corresponding name attribute of the FTPSFragment element.

ref

This attribute identifies the fragment that is used for the FTPS protocol.

LocalSource
  • Occurrence: 1
Required
References Notes

A local source is considered to be located locally to the YADE Client, i.e. in the local file system.

SFTPFragmentRef
  • Occurrence: 1
Required
References Notes

This element references the fragment that is used for an SFTP file transfer operation. Any number of reusable SFTPFragment elements can be configured and are distinguished by YADE based on their name attribute.

The reference to a fragment is based on the value of the ref attribute of this element to the corresponding name attribute of the SFTPFragment element.

ref

This attribute identifies the fragment that is used for the SFTP protocol.

SMBFragmentRef
  • Occurrence: 1
Required
References Notes

This element references the fragment that is used for an SMB file transfer operation. Any number of reusable SMBFragment elements can be configured and are distinguished by YADE based on their name attribute.

The reference to a fragment is based on the value of the ref attribute of this element to the corresponding name attribute of the SMBFragment element.

ref

This attribute identifies the fragment that is used for the SMB protocol.

WebDAVFragmentRef
  • Occurrence: 1
Required
References Notes

This element references the fragment that is used for an WebDAV file transfer operation. Any number of reusable WebDAVFragment elements can be configured and are distinguished by YADE based on their name attribute.

The reference to a fragment is based on the value of the ref attribute of this element to the corresponding name attribute of the WebDAVFragment element.

ref

This attribute identifies the fragment that is used for the WebDAV protocol.

Directory string
  • Min: 1
  • Whitespace: preserve
  • Occurrence: 0..1
Optional
References Notes

This parameter is used to specify a directory on one of the involved servers. Directories can be adressed using a folder structure, e.g. /folder1/folder2.

For Windows systems when used with the LocalSource parameter then a Windows path including a drive letter can be specified. For all server systems the standard syntax using can be used which includes forward slashes to separate folder names.

The directory can be set absolute or relative to the working directory, where the working directory depends on the server configuration. If for example a user "test" connects to an SFTP server then this user might have /home/test/ as a working directory. This applies to servers that use the home directory as the working directory. In this case you can use relative and absolute adressing as in

  • data
  • /home/test/data
as values for the Directory parameter.

  

 

  • No labels