Diagram
A jump host is an intermediate server that is used for file transfers when the YADE Client cannot connect directly to a target server, e.g. if such connections are exclusively available in a DMZ. In such cases the YADE Client can be installed on a server in the DMZ that is used as a jump host. The YADE Client would in a first step transfer files between the source server and the jump host and in a second step execute the YADE Client on the jump host to perform the transfer to the target host. This element includes the parameters for an jump host file transfer connection including SSHAuthentication and BasicConnection configuration items. Any number of fragments can be configured and are distinguished by YADE according to their name attribute. A fragment is referenced by a transfer profile using the value of the JumpFragmentRef ref attribute. This attribute identifies the current fragment. Any number of fragments can be used and are distinguished by YADE based on their name. A fragment is referenced via this attribute value by a transfer profile. This attribute identifies the current fragment. Any number of fragments can be used and are distinguished by YADE based on their name. A fragment is referenced via this attribute value by a transfer profile. A connection specifies parameters for a Hostname and a Port to which a connection is established. The SSHAuthentication element specifies the credentials for authentication with a server, e.g. an FTP Server or a Proxy. Child elements include: This command is used to invoke the YADE Client on a jump host that is used to store files intermediately during file transfer between source and target host. The command includes the full path to your YADE Client installation on the jump host and ends with the file name YADE.sh (Unix) or YADE.cmd (Windows). Specifies the commands to be executed for each file on the jump server before transfer of files. Specifies the commands to be executed for each file on the jump server after the transfer. Commands to be executed before the transfer of files starts on the jump server. Post transfer commands execution in case of the successful transfers. Post transfer commands execution on transfer error. Post transfer commands execution at transfer end independent of the transfer status. A command delimiter option for executing the jump pre- and postcommands: This directory on the jump host is used to store files intermediately during file transfer between source and target host. The files in this directory are removed at the end of the transfer operation. This element references the fragment that is used to insert configuration items from a secure store into a file transfer configuration. Any number of reusable CredentialStoreFragment elements can be configured and are distinguished by YADE based on their name attribute. The reference to a fragment is based on the value of the ref attribute of this element to the corresponding name attribute of the CredentialStoreFragment element. Support for a jump host. Note: Availability starting with YADE-488. This attribute identifies the fragment that is used for inserting secure configuration items. ProxyForSFTP - will use the HTTP, SOCKS4 or SOCKS5 proxy This parameter specifies the behavior for hosts that have not previously been involved in a file transfer. An application configuration file contains settings that are specific to an app. YADE allows to specify configuration files individually per transfer fragment. Sets the interval in milliseconds to send a keep-alive message. If zero is specified, any keep-alive message must not be sent. Use ServerAliveCountMax parameter to specify the number of keep-alive messages which may be sent without receiving any messages back from the server. Possible values: Combined values (with blank as separator): Sets the number of keep-alive messages which may be sent without receiving any messages back from the server. If this threshold is reached while keep-alive messages are being sent, the connection will be disconnected. This value is used as the socket timeout parameter, and also as the default connection timeout. A value of 0 (the default value) indicates no timeout. Possible values: Combined values (with blank as separator): The maximum time to wait for the channel to be established. If 0, we wait as long as needed (but at most 2000 times 10 milliseconds each). Possible values: Combined values (with blank as separator):
JumpFragment
Notes
Element
Type
Required
Description
Attribute: name
NMTOKEN
Required
BasicConnection
[BasicConnectionType]
Required
Notes
SSHAuthentication
[SSHAuthenticationType]
Required
Notes
JumpCommand
string
Required
Notes
JumpCommandBeforeFile
string
Optional
Notes
JumpCommandAfterFileOnSuccess
string
Optional
Notes
JumpCommandBeforeOperation
string
Optional
Notes
JumpCommandAfterOperationOnSuccess
string
Optional
Notes
JumpCommandAfterOperationOnError
string
Optional
Notes
JumpCommandAfterOperationFinal
string
Optional
Notes
JumpCommandDelimiter
Optional
Notes
JumpDirectory
string
Optional
Notes
CredentialStoreFragmentRef
Optional
ProxyForSFTP
Optional
StrictHostkeyChecking
boolean
Optional
Notes
ConfigurationFiles
[ConfigurationFilesType]
Optional
Notes
ServerAliveInterval
string
Optional
Notes
ServerAliveCountMax
int
Optional
Notes
ConnectTimeout
string
Optional
Notes
ChannelConnectTimeout
string
Optional
Notes
Platform
string
Optional
References
References
References
References
References
References
References
References
References
References
References
References
References Notes
References
References
References
References
References
References
Overview
Content Tools