...
- Fragments
- ProtocolFragments
- FTPFragment (name='f1')
- BasicConnection
- Hostname
- Port (optional)
- BasicAuthentication
- Account (user name)
- Password (optional)
- BasicConnection
- FTPFragment (name='f1')
- ProtocolFragments
Protocol fragment elements are protocol-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.
...
- A Copy operation requires that CopySource and CopyTarget elements are specified.
- The CopySource and CopyTarget elements in turn are used to specify CopySourceFragmentRef and CopytargetFragmentRef elements, that respectively define the Fragments fragments to be used for each of the two parts of the operation.
...