| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Server-to-Server File Transfer
...
Schema for Server-to-Server file 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="datafile 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"];
}
|
...
Profile for Server-to-Server file transfer without touchdown
A profile definition for Server-to-Server file transfer , from SFTP to FTPusing SFTP for the source system and FTP for the target system:
| 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 example with the JADE Client CLI one must type:
...
To make the profile more reusable and readable it is possible to organize profiles organise profile fragments 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 profile fragments for wilma as source and 8of9 as target are defined once. They could be used as many times as needed. There is a globals profile as well.
Now we will specify the profile againusing fragments:
| 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 fragments in the order they are defined. The globals profile is included automatically, no need to specifiy it in an include parameter. The profiles profile fragments have to be defined in the same settings file.
...