Page History

...

When a source or target is specified for a file transfer operation a reference is made to a ProtocolFragment element. ProtocolFragments are elements in the Fragments branch of the JADE 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.

...

In the JADE 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 have descendants that specify connection parameters such as the authentication method, the connection type and proxy.

...

Note that the links behind each parameter name in the diagram lead to the Parameter Reference page for that element, which provides detailed information about the parameter.

• Fragments
  • ProtocolFragments
    • FTPFragment (name='f1')
      
      • BasicConnection
        • Hostname
        • Port
      • BasicAuthentication
        • Account
        • Password

...

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.

Note that protocol fragments can be used for either a transfer source or target as required. This is described in more detail in the next section.

...

Any number of ProtocolFragments can be specified within a file transfer configuration and any number of fragments can be defined for a particular protocol. A particular fragment is referenced by a name attribute and this attribute is referenced by a corresponding fragment reference element in the configuration Profiles branch.

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 are used to specify CopySourceFragmentRef and CopyTargetFragmentRef elements, that respectively define the fragments to be used for each of the two parts of the operation.

...

The following optional fragments can be specified in addition to ProtocolFragments:

• AlternativeFragments elements are used to 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 the original (more secure) one is not available.
  AlternativeFragments are described in more detail here.
• NotificationFragments specify how e-mails informing about successful or unsuccessful file transfer operations are to be sent.
• CredentialStoreFragments are used to retrieve file transfer authentication credentials from a secure source.

...

Related Sections of this User Manual:

• JADE YADE User Manual - Configuration Formats & Tools
• JADE YADE User Manual - Configuring and Running File Transfers
  • JADE YADE User Manual - Configuration 1 - An Overview
  • JADE User Manual - Configuration 2 - The Fragments Branch (this page)
    • JADE User Manual - Configuring Alternative Fragments
      
  • JADE User Manual - Configuration 3 - The Profile Branch

...