A significant change in the file transfer configuration of YADE will be introduced with release 1.11.This will mark the end of the use of text-based
*.ini files and the introduction of XML-based configurations in line with an XSD schema. In parallel, a new XML Editor will be available that will automatically generate required elements where appropriate as well as allow configurations to be verified according to the schema.
The two configuration formats are compared on this page.
.iniFiles up to Release 1.10
File transfers are configured in YADE up to Release 1.10 in text-based
*.ini file contains a number of transfer profiles: blocks that contain the actual configuration parameters. As profiles can be used to specify other profiles, it is possible to develop a set of reusable "configuration building blocks'" that can be set together as required.
*.ini file and transfer profile to be used for a file transfer operation are specified when a command is sent to the YADE client.
*.ini files can be configured using a text or code editor.
Whilst this approach is relatively straightforward to understand when used with simple file transfer situations:
For further Information about configuring YADE using
*.ini approach see:
The XML file transfer configuration introduced with release 1.11 of YADE allows parameter dependencies in YADE to be validated before the configuration file is transferred to an operating environment.
Dependencies and conflicts between configuration elements are avoided through the use of an XSD schema.
We have written an XML Editor that will simplify the creation and validation of schema-compatible file transfer configurations.
The basic principles behind the organization of the schema elements and parameters is described in Configuring File Transfers with the YADE Client.
A detailed description of individual parameters can be found in our Parameter Reference.
The following screen shot of the the SOS XML Editor shows the configuration for a Simple File Transfer with Basic Authentication example.
*.iniFile and XML Configurations
Comparison of the two formats reveal a significant difference in the concept behind the two approaches to configuration:
*.inifile configuration depending on their use as source or target. This usually has no functional meaning (the files are processed from top to bottom) and is partly simply for convenience (grouping parameters together makes them easier to find) and partly to allow their reuse in the form of so-called profile fragments if required.
*.iniFile to XML-based Configurations
With the change to the XML-based configuration not only has a hierarchical structure been introduced to configuration elements but many of the names used for configuration elements have been changed. We have therefore written a parameter mapping table to help users with conversion of their configurations.