Diagram
This parameter specifies the target of a Move operation. The following frequently used settings groups are available: This element references a writeable fragment that is used to move files in a Move operation. Any number of reusable Fragments elements can be configured and are distinguished by YADE based on their name attribute. A subsequent fragment reference element points to the fragment that is used as target in the Move operation. 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. This attribute identifies the fragment that is used for the FTP protocol. 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. This attribute identifies the fragment that is used for the FTPS protocol. This element references the fragment that is used for an HTTP file transfer operation. Any number of reusable HTTPFragment 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 HTTPFragment element. This attribute identifies the fragment that is used for the HTTP protocol. This element references the fragment that is used for an FTPS file transfer operation. Any number of reusable HTTPSFragment 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 HTTPSFragment element. This attribute identifies the fragment that is used for the HTTPS protocol. A local target is considered to be located on the server where the YADE Client is operated, i.e. in the local file system. 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. This attribute identifies the fragment that is used for the SFTP protocol. 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. This attribute identifies the fragment that is used for the SMB protocol. 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. This attribute identifies the fragment that is used for the WebDAV protocol. 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 or target of a file transfer operation that required modifying files. For each fragment type depending on the file transfer protocol in use an alternative fragment type is available. 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. This attribute identifies the fragment that is used for the FTP protocol. 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. This attribute identifies the fragment that is used for the FTPS protocol. This element references the fragment that is used for an HTTP file transfer operation. Any number of reusable HTTPFragment 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 HTTPFragment element. This attribute identifies the fragment that is used for the HTTP protocol. This element references the fragment that is used for an FTPS file transfer operation. Any number of reusable HTTPSFragment 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 HTTPSFragment element. This attribute identifies the fragment that is used for the HTTPS protocol. A local target is considered to be located on the server where the YADE Client is operated, i.e. in the local file system. 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. This attribute identifies the fragment that is used for the SFTP protocol. 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. This attribute identifies the fragment that is used for the SMB protocol. 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. This attribute identifies the fragment that is used for the WebDAV protocol. 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 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 These options apply to files on a target server. They specify e.g. the Atomicity of a file transfer for Copy and Move operations. This parameter specifies that after transfer of each file to a target server YADE will try to read the file from the target server and compare the number of bytes of the original file on the source server and the file on the target server. This option determines whether the individual files from the results list should be transferred individually and then should be cumulated (i.e. concatenated into a single file) to the transfer target. The name of the cumulative file is specified using the CumulativeFilename parameter. The CumulativeFileSeparator parameter is used to specify a string that is added to the target file, between the individual files in order to allow these files to be separated later on. Should the source files be deleted after transfer then the Move operation can be used. This parameter specifies whether or not the content of the source files should be compressed for the target files using a zip algorithm. In case of sending files each file will be compressed in a single zip file. The extension of the filename is configured with the parameter CompressedFileExtension. A gzip-compatible compression is used, no further software components are required. The following parameters are ignored should CompressFiles be used: This parameter specifies that YADE will try to assign the modification date of the source file to the target file. This functionality makes use of commands that are specific for the file transfer protocol, e.g. FTP, SFTP, and is therefore not available for all protocols. In addition server side settings might restrict the use of such commands. This parameter specifies that YADE will try to create the directory on the target server that is specified with the Directory parameter should this directory not exist. This parameter has no effect on the subfolders during a recursive transfer. Subfolders of recursive transfer are always created if they do not exist. This functionality makes use of commands that are specific for the file transfer protocol, e.g. FTP, SFTP, and is therefore not available for all protocols. Please consider that server side settings might restrict the use of such commands. This parameter specifies whether existing target files can be overwritten in a file transfer.
MoveTarget
Notes
Element
Type
Required
Description
MoveTargetFragmentRef
[WriteableFragmentRefType]
Required
WriteableFragmentRefType / FTPFragmentRef
Required
Notes
WriteableFragmentRefType / FTPSFragmentRef
Required
Notes
WriteableFragmentRefType / HTTPFragmentRef
Required
Notes
WriteableFragmentRefType / HTTPSFragmentRef
Required
Notes
WriteableFragmentRefType / LocalTarget
Required
Notes
WriteableFragmentRefType / SFTPFragmentRef
Required
Notes
WriteableFragmentRefType / SMBFragmentRef
Required
Notes
WriteableFragmentRefType / WebDAVFragmentRef
Required
Notes
AlternativeMoveTargetFragmentRef
Optional
FTPFragmentRef
Required
Notes
FTPSFragmentRef
Required
Notes
HTTPFragmentRef
Required
Notes
HTTPSFragmentRef
Required
Notes
LocalTarget
Required
Notes
SFTPFragmentRef
Required
Notes
SMBFragmentRef
Required
Notes
WebDAVFragmentRef
Required
Notes
Directory
string
Optional
as values for the Directory parameter.
Directory
string
Required
as values for the Directory parameter.
TargetFileOptions
Optional
Notes
Atomicity
[AtomicityType]
Optional
CheckSize
boolean
Optional
Notes
CumulateFiles
Optional
Notes
CompressFiles
Optional
Notes
KeepModificationDate
boolean
Optional
Notes
DisableMakeDirectories
boolean
Optional
Notes
DisableOverwriteFiles
boolean
Optional
Notes
References
References Notes
References
References
References
References
References
References
References
References
References Notes
References
References
References
References
References
References
References
References
References Notes
References Notes
References
References
References
References
References
References
References
Overview
Content Tools