Page History

...

• Fragments
  • ProtocolFragments
    • FTPFragment (name= 'af1')
    • FTPFragment (name= 'bf2')
    • FTPSFragment (name= 'cf3')
    • etc...
• Profiles
  • Profile (profile_id='p1')
  • Profile (profile_id='p2')
  • etc....
• General

The Fragments branch is the second-most important configuration branch in the Schema, containing the ProfileFragments elements that specify in detail how the transfer is to be carried out.

This two-stage configuration procedure allows a flexibility not possible with a single XML hierarchy and, in particular, allows elements to be reused.

Profile Element Functions

A Profile can be seen as a specification of what is to be done and contains hierarchical information about:

• the Operation to be carried out - e.g. copy Copy or move Move,
• the protocols to be used for the source and, if relevant, target, parts of the transfer and
• references that specify ProtocolFragment elements. These in turn define in detail how the file transfer connections are to be made.

...

• The use of the Operations element - the only Profiles child element whose use is required - is described in the Operation Element section of this manual.
• The Profile child elements are described in detail in the Profiles parameter reference.

configuration