Date: Fri, 29 Mar 2024 16:00:57 +0000 (UTC) Message-ID: <1240022092.13097.1711728057245@change.sos-berlin.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_13096_1464620492.1711728057244" ------=_Part_13096_1464620492.1711728057244 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The focus of this article is the configuration of individual parameters = - a more general description of the considerations involved in setting up a= jump host file transfer can be found in the following article:
The following diagram shows schematically how files are sent via the Int= ernet from one network with a DMZ to another network with a DMZ.
The XML element hierarchy for the configuration of a jump host is shown = below for a Co= py operation with the jump host on the target side of the operatio= n:
A fragment element is specified in the usual manner= and is called from a CopySourceFragmentRef or CopyTargetFra= gmentRef element in the Profiles branch of the configurat= ion.
The jump host is specified as part of the configuration of the file tran= sfer fragment using the JumpFragmentRef element, which can be sp= ecified as an optional child of all connection fragment elements, with the = exception of SMBFragments.
The JumpFragmentRef element references a JumpFragment = element, which is basically a second connection fragment element and specif= ies the jump host configuration.
Note that the JumpFragment element allows the specification of = an optional JumpDirectory element that can be used for intermediat= e file storage during the transfer operation. All files written to the = JumpDirectory will be removed at the end of the operation.
Neither configuration data nor log files are stored by YADE on the jump = host.
Only a single JumpFragment can be specified as part of a connecti= on fragment element.
Jump hosts cannot be specified as part of AlternativeFragment elements.