JADE - Reference Documentation - Parameter Reference

Introduction

• The Parameter Reference is used for configuring JADE file transfer settings.
• The Parameter Reference is generated from the JADE - Reference Documentation - XSD Schema Reference and includes additional explanations of configuration elements.
• The JADE - User Manual provides an overview of features, explains use cases and includes references to this documentation.

Parameter Reference

Diagram

Explanations

The XML file transfer configuration that is introduced with version 1.11 of the JADE Client uses an XSD schema to define relationships between parameters and which parameters can be used together.

The top two levels of the schema are shown in the diagram at the top of this page:

The Configurations element is the top level element in the transfer configuration and has three child elements, representing three main branches of the configuration:

• Fragments branch:
  • Parameters set in the Fragments configuration branch specify how the transfer is to be carried out.
  • An example transfer fragment could specify that FTP protocol should be used, via a SOCKS5 proxy on a particular port, with password authentication.
  • At least a minimum set of Fragments parameters is required.
  • More than one transfer method can be specified in the Fragments branch.
    The transfer method that will be used is specified as a reference in the Profiles configuration branch.
• Profiles branch:
  • Profiles are the central defining file transfer elements - it is a profile that is called when a file transfer is to be carried out.
  • The Profiles element specifies what is to be done – i.e. the operations involved.
  • An example transfer Profile could specify that files are to be moved from a source to a target and renamed.
  • At least a minimum set of Profile parameters is required.
• General branch:
  • The General Configuration options mainly refer to background features, such as use of the JADE Background Service and logging.
  • The specification of General configuration parameters is not mandatory.

In addition there are:

• Reusable elements
  • (Not shown on the diagram above.) Reusable Elements can be included at different points in the configuration as allowed in the schema - eventually more than once.
  • Example Reusable Elements are:
    • the BasicConnection element, which requires a Hostname and optionally a Port and can be used, for example, in an FTPFragment and FTPSFragment but not in a HTTPFragment.
    • the ProxyForFTPS element, which requires that either a SOCKS4Proxy or a SOCKS5Proxy is specified and can only be used in an FTPSFragment.
      Note that both the SOCKS4Proxy and SOCKS5Proxy elements are themselves Reusable Elements.