Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Server to Server Transfer
Example: server to server transfer without touchdown:
Graphviz |
---|
digraph "Example: Server to Server Transfer" { rankdir=LR; edge [color="#31CEF0"]; source_server [label="Host A\nData Source (SFTP)"]; target_server [label="Host B\nData Target (FTP)"]; jade_client [label="Host C\nJADE Client \n API \n JITL Job"]; jade_config [label="JADE Configuration"]; source_server->target_server [label="data transfer"]; source_server->jade_client [dir=both label="commands" color="grey"]; jade_client->target_server [dir=both label="commands" color="grey"]; jade_config->jade_client [color="green"]; } |
...
A profile definition for Server to Server transfer, from SFTP to FTP:
Code Block | ||
---|---|---|
| ||
[ftp_server_2_server] ssh_auth_method=password source_user=kb source_password=***** source_ssh_auth_method=password source_host=wilma.sos source_protocol=sftp source_port=22 target_user=test target_password=***** target_host=8of9.sos target_protocol=ftp target_port=21 file_spec=^.*\.txt$ operation=copy log_filename=${TEMP}/sosftphistory.log |
...
In this example all files with the extension ".txt" should be transfered from the server wilma
via SFTP to the server 8of9
by FTP. The folder is not explicitely specified and therefore the home folder of the user will be chosen.
To start this sample with the JADE Client CLI one must type:
Code Block | ||
---|---|---|
| ||
jade.sh -settings=name_of_settings_file -profile=ftp_server_2_server |
...
To make the profile more reusable and readable it is possible to reuse organize profiles like this:
Code Block | ||
---|---|---|
| ||
[wilma_as_source] ssh_auth_method=password source_user=kb source_password=***** source_ssh_auth_method=password source_host=wilma.sos source_protocol=sftp source_port=22 [8of9_as_target] target_user=test target_password=***** target_host=8of9.sos target_protocol=ftp target_port=21 [globals] log_filename=${TEMP}/sosftphistory.log |
The profiles for wilma
as source and 8of9
as target are defined once. They could be used as many time times as needed. There is a "globals" profile as well.
Now we will specify the profile again:
Code Block | ||
---|---|---|
| ||
[ftp_server_2_server] include=wilma_as_source,8of9_as_target operation=copy file_spec=^.*\.txt$ [ftp_more] include=wilma_as_source,8of9_as_target operation=move file_spec=^.*\.(txt|pdf|dat)$ source_folder=/outbound/daily target_folder=/inbound/transfer |
...
The include parameter will include the named profile snippets in the order they are defined. The globals profile is included automatically, no need to specifiy it in an include parameter. The profiles hast have to be defined in the same settings file.
...