Page History

...

In the XSD Schema used to structure the JADE configuration parameters, the parent of all individual Profile elements, the Profiles element, lies at the top of one of the three major main branches in the configuration, alongside the Fragments and General branches. This hierarchy is shown schematically below:

• Profiles

  Status
  colour Yellow title To Replace with GraphViz diagram showing flow?

  
  
  • Profile (profile_id='p1')
    • Operation
      
      • ...
        • *FragmentRef (attribute = 'f1')
  • Profile (profile_id='p2')
    etc.
    • Operation
      
      • ...
        
        • *FragmentRef (attribute = 'f2')
    • Profile (profile_id='p3')
      • etc.
  • Fragments
    • ProtocolFragments
      • FTPFragment (name= 'f1')
      • FTPFragment (name= 'f2')
      • FTPSFragment (name= 'f3')
      • etc.
  • General
    • etc.

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

  The General branch is used to specify overall aspects of JADE's operation that are not directly related it individual file transfers, such as logging. It is not directly relevant for the purpose if this manual article and is only mentioned here for completeness.

  This two-stage configuration procedure - calling a profile Profile which contains a reference to a fragment Fragment - allows a flexibility not possible with a single XML hierarchy and, in particular, allows profile fragment elements to be reused.

  ...

  All ProfileFragments require a name attribute which is used to reference the fragment from an element in the Profile element.

  Further information

  ...

  .

  ...

  Configuring File Transfers with the SOS XML Editor

  ...