| Table of Contents |
|---|
Protocol Fragments
File transfer When a source and target are specified using elements in the configuration Fragments branchor target is specified for a file transfer operation a reference is made to a protocol fragment element. These elements can be thought of as a series of predefined part configurations that can be called up as required for specific file transfer operations. Protocol fragments are elements the configuration Fragments branch in the XSD Schema, which can be thought of as a library of preconfigured.
ProtocolFragments are children of the Fragments element and in turn can have any number of child elements. Example protocol fragment elements would be the FTPFragment and the SFTPFragment.
...
Protocol fragment elements are protocol parameter-specific - that is, there is a ProtocolFragments element defined in the XSD schema for each file transfer protocol. This approach enables the properties of each protocol to be reflected in the schema and allows dependencies and incompatibilities to be defined. A trivial example here would be that a PassiveMode element can be specified for an FTPFragment but not for an SFTPFragment.
...
| Status | ||||||
|---|---|---|---|---|---|---|
|
Note that there is, for example, a protocol fragment defined for each FTP host that can be addressed as either a source or target. Protocol fragment elements are not target or source specific.
Calling Protocol Fragments
...