Summary
Profiles form the starting points for specifying file transfers, with a Profile being specified for each file transfer operation that is to be run.
A Profile can be seen as a specification of what is to be done.
A Profile contains hierarchical information about:
- the Operation to be carried out - e.g. copy or move,
- the protocols to be used for the source and, if relevant, target, parts of the transfer and
- references specifying the protocol fragments that in turn define in detail how the file transfer connections are to be made.
Any number of profiles can be defined within a configuration, with the profile to be used being specified as part of the command used to start JADE.
See Running File Transfers with the JADE Client for an example of how to call a Profile.
Profiles can be seen as file transfer specifications that together build up a library and are selected as required.
All Profile elements require a profile_id attribute which is used to call the profile with.
Profiles in the JADE Schema
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 is shown schematically below:
- Fragments
- Profiles
- Profile
- Profile
- etc....
- General
We recommend that you use the SOS XML Editor to generate your configuration file. 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.
Further Information
- 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.