Page History

...

This tutorial describes the use of the SOS XML Editor to generate the necessary transfer configuration file. The use of the Editor is intended to simplify and speed up the configuration process, particularly for complex file transfer situations, and reduce the occurrence of configuration errors. The Editor uses an XSD schema to generate and validate the YADE configuration. In addition, the Editor is able to generate the the new XML format that will be introduced with release 1.11 of YADE. A comparison between the new XML format and the current (i.e. used in releases up to and including 1.10) is available in the JADE YADE user manual manual Configuring and Running File Transfers section.

...

This tutorial is part of a series describing how to get started with using the YADE Client via its Command Line Interface and configuring simple file management tasks.

...

YADE Client Command Line Interface

1. Getting Started and Downloading files
2. Simple File Selection
3. More Advanced File Selection

4. File Transfer

5. Checking files for completeness
6. Public / Private Key Authentication
7. Transfer via a Jump Host / DMZ

...

1. Installation, Configuration and Use

See the Using the tutorials with the YADE Client Command Line Interface article for information about setting-up and running the tutorial examples.

...

• The XML Editor can save configurations in XML format using the standard Save or Save as buttons shown in the editor task bar. This file is compatible with the YADE version 1.11 described ...
  The YADE Xml2ini Converter Button in the task bar causes the Editor to generate a settings.ini file that is compatible with earlier YADE releases.
• For more information about using the Editor see the XML Editor Usage for compatible .ini and .xml configuration files article.

Calling the transfer operation (YADE Releases 1.10 and earlier)

...

• The YADE Background Service is not able to directly access the YADE Client on the jump server. This means while the Background Service can access the transfer history and log files of the local YADE Client, it is not able to access log or file transfer information from the JADE YADE Client on the jump host.
  However the originating YADE Client (i.e. the current example, the client on the source server) receives feedback from the client on the jump host containing information about whether transfer from the jump host to the target server was successful.

...