...
- Fragments branch:
- Parameters set in theFragments configuration branch specify how the transfer is to be carried out.
- An example transfer fragment could specify that FTP protocol should be used, via a SOCKS5 proxy on a particular port with password authentication.
- At least a minimum set of Fragments parameters is required.
- More than one transfer method can be specified in the Fragments branch.
The transfer method that will be used is specified as a reference in the Profiles configuration branch.
- Profiles branch:
- Profiles are the central defining file transfer elements - it is a profile that is called when a file transfer is to be carried out.
- The Profiles element specifies what is to be done – i.e. the operations involved.
- An example transfer Profile, could could specify that files are to be moved from a source to a target and renamed.
- At least a minimum set of Profile parameters is required.
- The prof
- General branch:
- The General Configuration options mainly refer to background transfer features, such as use of the JADE Background Service or Credential Store and logging.
- The specification of General configuration parameters is not mandatory.
...
- Reusable elements
- (Not shown on the diagram above.) Reusable Elements can be included at different points in the configuration as allowed in the schema - eventually more than once.
- Example Reusable Elements are:
- the BasicConnectionType element BasicConnection element, which requires a Hostname and optionally a Port and can be used, for example, in FTP- and FTPSFragments an FTPFragment and FTPSFragment but not HTTPFragmentsin a HTTPFragment.
- the ProxyForFTPS element, which requires that either a SOCKS4Proxy or a SOCKS5proxy SOCKS5Proxy is specified and can only be used in FTPSFragmentsan FTPSFragment.
Note that both the SOCKS4Proxy and SOCKS5proxy SOCKS5Proxy elements are themselves Reusable elementsElements.