Page History

...

A significant change in the file transfer configuration of JADE will be introduced with release 1.11.This will mark the end of the use of text-based settings *.ini files and the introduction of XML-based configurations in line with an XSD schema. In parallel, a new new XML Editor will be available that will automatically generate mandatory required elements where appropriate as well as allow configurations to be verified according to the schema.

...

File transfers are configured in JADE up to Release 1.10 in text-based .ini files.

A settings *.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.

The settings The *.ini file and transfer profile to be used for a file transfer operation are specified when a command is sent to the JADE client.

Settings files *.ini files can be configured using a text or code editor.

...

Although longer and seemingly more complex than a comparable configuration using the settings*.ini file approach (see The JADE Client Tutorial 1), the XML code for this example was produced using the XML Editor and therefore has been validated against the JADE Client XSD Schema. It is therefore conflict free and dependencies are correctly specified.

...

Comparing *.ini File and XML Configurations

Comparison of the two formats reveal a significant difference in the concept behind the two approaches to configuration:

• Settings file *.ini file configuration
  Parameters such as host, protocol, user, password and dir (directory) are usually grouped separately in the settings the *.ini file 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.
• XML configuration
  • Parameters are divided up into hierarchical branches - the Profiles and Fragments branches being the most relevant here.
    (Note that the expressions Profiles and Fragments are here defined differently to elements with the same names in the *.ini file configuration.)
    • Authentication and connection parameters (Account & Password and Hostname & Port respectively) and the protocol (defined through the use of FTP) are part of the Fragments branch of the configuration.
    • The operation (Copy) and the source and target file paths (FilePath and LocalTarget respectively) are specified in the Profiles branch.
    • The CopySourceFragmentRef element refers to An FTPFragmentRef element in the Profile branch is used to specify the FTPFragment specified in the Fragments branch that contains the detailed information about the authentication and connection parameters.
  • The division between Fragments and Profiles branches allows the reuse of elements whilst working within the strict hierarchical structure of XML.
    • The use of a reference in the Profiles branch (in the example, using the CopySourceFragmentRef FTPFragmentRef element) to specify the authentication and connection parameters in the Profiles branch allows any number of Profiles elements to be defined and specified as required.

Migrating

...

from *.ini File to XML-based Configurations

Parameter Mapping

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.

...