Page History

...

Among the parameters specified within a Profile is the ProtocolFragment(s) to be used - i.e. one or more references specifying predefined connection configurations.

...

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

• ProfilesFragments
  • ProtocolFragmentsFTPFragment (nameProfile (profile_id='f1p1')FTPFragment
  • Profile (nameprofile_id='f2p2')
  • etc....
• Fragments
  • ProtocolFragments
  • Profile (profile_id
    • FTPFragment FTPSFragment (name= 'f3f1')
    • etc...
  Profiles
  • • FTPFragment (name= '
    p1
    • f2')
    Profile
    • FTPSFragment (
    profile_id
    • name= '
    p2
    • f3')
    • 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.

...

Whilst Profiles form the starting points when running a file transfer command, with the ProtocolFragments then being called from within a Profile Element, the configuration procedure is usually carried out in the reverse order: The necessary ProtocolFragments are configured first, before the Profile elements which call these fragments are specified.

...

We recommend that you use the SOS XML Editor to generate your whole configuration file. Due The editor effectively functions like a wizard: due to the use of the JADE XSD schema in the editor, you will be effectively guided through the configuration process and end up with a validated configuration that you can implement as required.

...