Date: Fri, 29 Mar 2024 06:27:42 +0000 (UTC) Message-ID: <925202772.12471.1711693662333@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12470_378924654.1711693662333" ------=_Part_12470_378924654.1711693662333 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The YADE Client can use a number of protocols to make connections for th= e source and target parts of the transfer. These protocols are specified in= parameters set in protocol fragment elements in the YADE XML configuration= .
Each protocol fragment has a number of required and optiona= l child elements, depending on the properties of the protocol itself. = For example, the FTPS protocol element has:
As noted for the FTPS protocol element example above, each protocol elem= ent requires a connection type. The connection types available are:
Connection protocols are specified in the Fragments elements of the = XSD Schema. All fragments elements are child elements of the ProtocolFra= gments element as shown schematically below:
As explained in the Configuration 2 - The Fragments Branch a= rticle, fragments elements are called from the Profiles branch of = the configuration and are identified by a name attribute specified= in the *Fragment element.
Note that any number of ProtocolFragments can be specified with= in a configuration, allowing a number of authentication methods to be prede= fined for a particular file transfer operation. The Alternati= veFragments element can be used to specify a number of alternative= connections and authentication methods for a file transfer profile.
An example configuration for an FTP connection showing both the Frag= ments and Profiles branches can be seen in the YADE User Manual - Simple File Transfer with Basic Authentication<= /a> article.