...
- Profiles
- Profile (profile_id='p1')
- Profile (profile_id='p2')
- etc.
- ...
- *FragmentRef (attribute = 'f2')
- ...
- Fragments
- ProtocolFragments
- FTPFragment (name= 'f1')
- FTPFragment (name= 'f2')
- FTPSFragment (name= 'f3')
- etc.
- ProtocolFragments
- General
...
The General branch is not directly relevant at this stage and is only mentioned here for completeness.
This two-stage configuration procedure - calling a profile which contains a reference to a fragment - allows a flexibility not possible with a single XML hierarchy and, in particular, allows profile fragment elements to be reused.
...
Any number of profiles can be specified within a file transfer configuration.
What
...
are ProtocolFragments Elements?
ProtocolFragment elements can be seen as a specification of how the file transfer is to be carried out. Each file transfer Profile contains a reference calling at least one ProtocolFragment.
The ProtocolFragment element ProtocolFragments elements contains hierarchical information about:
...
ProtocolFragments are protocol-specific - that is, they apply for a specific protocol and the . The XSD schema defines which configuration elements can be used for the protocol in question.
For example, the Schema does not allow SSH authentication to be specified for an FTPFragment.
...
Referencing Profiles and ProtocolFragments
Both Profiles and ProfileFragments ProtocolFragments can be seen as predefined file transfer specifications that are called up as required:
...
All ProfileFragments require a name attribute which is used to reference the fragment from a child an element of in the Profile element.
Further information
- See Running File Transfers with the JADE Client for an example of how
...
- a Profile is called from the command line.
- See JADE User Manual - Configuration 2 - The Fragments Branch for a description of the considerations behind specifying a profile fragment.
- See JADE User Manual - Configuration 3 - The Profile Branch for a description o the considerations behind specifying a profile
Configuring File Transfers with the SOS XML Editor
We recommend that you use the SOS XML Editor to generate all the parts of your whole configuration file. 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.
...
A Fragment can be used as both a source or as a target within the one Configuration.
Further Information
Related Sections of this User Manual:
- JADE User Manual - Configuration Formats & Tools
- JADE User Manual - Configuring and Running File Transfers
- JADE User Manual - Configuration 1 - An Overview (this page)
- JADE User Manual - Configuration 2 - The Fragments Branch
- JADE User Manual - Configuration 3 - The Profile Branch
- JADE User Manual - XSD Schema
- 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.
Other documents
- The Profile and ProtocolFragments child elements are described in detail in the Profiles parameter reference
- and ProtocolFragments sections of the Parameter Reference.