Page History

Protocol Fragments

When a source or target is specified for a file transfer operation a reference is made to a protocol fragment element. These elements  Protocol fragments are elements the Fragments branch in the XSD Schema and 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 pre-configured connections.usually form the starting point when configuring a file transfer. Profiles, which reference protocol fragments, are specified after the protocol fragments have been defined.

Operationally, the starting point is a Profile, which then calls the protocol fragments.

XML Hierarchy

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-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.

...

• Operation
  • Copy
    
    • CopySource
      
      • CopySourceFragmentRef
        
        • FTPFragmentRef (Has the ref Attribute specifying which specifies the source ProtocolFragment)
      • SourceFileOptions
        • Selection
    • CopyTarget
      
      • CopyTargetFragmentRef
        • LocalTarget (A ProtocolFragment does not need to be defined here as the target is the local file system )
      • Directory

...