...
Example: server to server transfer without touchdown:
A profile definition for Server to server 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_path=test.txtspec=^.*\.txt$ operation=copy log_filename=$\{TEMP\}/sosftphistory.log |
In this example all files with the file name extension ".txt" should be transfered from the server "wilma" via sftp to the server 8of9 by ftp. the folders are not explicitely specified and therefore the "home" folders of the user are selected.
To start this with the command line client one must type
| Code Block |
|---|
jade.sh -settings=name_of_settings_file -profile=ftp_server_2_server
|
To make the profile more resusable and readable it is possible to reuse profiles in the way 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
|
| Code Block |
|---|
[8of9_as_target]
target_user=test
target_password=*****
target_host=8of9.sos
target_protocol=ftp
target_port=21
|
| Code Block |
|---|
[globals] log_filename=$\{TEMP\}/sosftphistory.log |
The profiles for wilma as source and 8of9 as source are defined once. 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$
|
The "include" parameter will include the named profiles in the order they are defined. The "globals" profile is included automatically, no need to specifiy it in an include parameter.
The profiles must be defined in the same settings file.