Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Server-to-Server File Transfer
Schema for Server-to-Server
...
File Transfer without touchdown
Graphviz |
---|
digraph "Example: Server to Server File Transfer" { rankdir=LR; edge [fontname=Verdana,fontsize=8,color="#31CEF0"]; node [fontname=Verdana,fontsize=8]; source_server [label="Host A\nData Source (SFTP)"]; target_server [label="Host B\nData Target (FTP)"]; jadeyade_client [label="Host C\nJADEnYADE Client \n API \n JITL Job"]; jadeyade_config [label="JADEYADE Configuration"]; source_server->target>yade_serverclient [label="file transfer"]; source_server->jade_client [dir=both label="commands" color="greygreen"]; jadeyade_client->target_server [dir=both label="commandsfile transfer" color="greygreen"]; jadeyade_config->jade>yade_client [color="greengrey"]; } |
- YADE can make use of different protocols when reading files from a source and writing files to a target system.
- Any combination of FTP, FTPS, SFTP, HTTP, WebDAV can be used for sources and targets.
- No touchdown of files on the server where YADE is located, instead all transfer operations are performed in memory.
Profile for Server-to-Server
...
File Transfer without touchdown
A profile definition for Server-to-Server file transfer File Transfer using SFTP for the source system and FTP for the target system:
...
To start this example with the JADE YADE Client CLI one must you could type:
Code Block | ||
---|---|---|
| ||
jade.sh -settings=name_of_settings_file -profile=ftp_server_2_server |
To make the profile more reusable and more readable it is possible to organise profile fragments like this:
...
The profile fragments for wilma
as source and 8of9
as target are defined just once. They could be used as many times as needed. There is a globals profile as well.
...
The include parameter will include the named profile fragments in the order they are defined. The globals profile is included automatically, no need to specifiy it in an include parameter. The profile fragments have to be defined in the same settings file.
See also
- YADE Implementation Architecture
- How to transfer files with YADE from Server A to Server B using polling and post-processing
- Example for YADE Server-to-Server File Transfer with polling