...
File transfer source and target are specified using Fragments elements.
ProtocolFragments are children of the Fragments element and have child elements that specify the parameters such as the authentication method, connection type and proxy.
...
ProtocolFragments are protocol specific - that is, there is a ProtocolFragments element defined in the XSD schema for each file transfer protocol. This enables the properties of each protocol to be reflected in the schema and allows dependencies and incompatibilities to be defined. A trivial example would be that a PassiveMode element can be specified for an FTPFragment but not for an FTPSFragment SFTPFragment.
Any number of ProtocolFragments can be specified within a file transfer configuration.
Operation-dependent source and target elements specify the ProtocolFragments element that is to be used. For example:
- A Copy operation requires that CopySource and CopyTarget elements are specified.
- The CopySource and CopyTarget elements in turn require that are used to specify CopySourceFragmentRef and CopytargetFragmentRef elements are defined, that respectively specify define the Fragments to be used for both each of the two parts of the operation.
| Status | ||||||
|---|---|---|---|---|---|---|
|
...
ProtocolFragments can also be referenced from other fragments:
- AlternativeFragments elements can specify a number of Fragments. These fragments will be applied in order, should, for example a server not be available. For example, it is conceivable that in some situations a less secure protocol would be tried if a secure one is not available.