Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

titleRewrite/Restructure Page

The Configuring Profiles and Fragments - 1 an Overview page gives an overview of the considerations to be made when using the Editor and thereby makes a good part of the information below redundant

The information presented here can be reduced to:

...

Table of Contents

Specifying Connection Parameters with Protocol Fragments

...

Protocol fragments usually form the starting point when configuring a file transfer. Profiles, which reference protocol fragments, can then be specified after the necessary protocol fragments have been defined.

Operationally, the starting point is a Profile, which then calls the protocol fragment(s).

...

See the Configuring Profiles and Fragments - 3 The Profile Branch article for more information about configuring the elements around a ProtocolFragment reference.

...

Optional fragments

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.