...
- The Fragments elements cover the protocol-specific parts of the configuration - in the current configuration these are that the protocol that is to be used, and the connection and authentication.
- Note that a file transfer operation usually requires two Fragments - one for the source part of the transfer and one for the target. However a target fragment is not required here as the the target is the local file system.
- Any number of Fragments can be predefined within a configuration and specified as required using their name attribute - in the example configuration this is ftp_demo_sos-berlln. This predefinition of Fragments allows their reuse and keeps the configuration well structured.
- The Profile elements contain the parameters that are specific to the current operation
- the Operation to be carried out is copy,
- the ftp_demo_sos-berlin Fragment that is to be used for the source part of the operation,
- the the files that are to be transferred:
- all files defined using the .* FileSpec
- the directory in which the files to be transferred is looked for: (all) from the directory
- defined using / file path,
- the directory that files are to be transferred to: ${USERPROFILE}\jade_demo\a
(on a Linux system the equivalent location would be ${HOME}/jade_demo/a ).
- The ref attribute in the FTPFragmentRef element is used to specify the Fragment to be used - in this case for the source part of the operation.
When the configuration is saved it will be validated against the XSD schema specified for the configuration (see XML Editor - Operation for more information)
The structure of the configuration is described in more detail in the JADE User Manual - Configuring and Running File Transfers article and its child articles.
...