| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Modularizing Profiles: include directive
An Example Transfer Profile
A profile definition for Server to Server transfer, from a sftp to a ftp server:
| 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 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 make the profile more reusable and readable it is possible to reuse profiles snipets in the way like this:
| Code Block |
|---|
[wilma] user=kb password=***** ssh_auth_method=password host=wilma.sos protocol=sftp port=22 [8of9] user=test password=***** host=8of9.sos protocol=ftp port=21 [globals] log_filename=$\{TEMP\}/sosftphistory.log |
The profiles for wilma and 8of9 are defined only once. They could be used as many time as needed in different transfer profiles. There is a "globals" profile as well.
...
Now we will specify the transfer profile again:
| Code Block |
|---|
[ftp_server_2_server]
source_include=wilma
target_include=8of9
operation=copy
file_spec=^.*\.txt$
[ftp_more]
target_include=wilma
source_include=8of9
operation=move
file_spec=^.*\.(txt|pdf|dat)$
source_folder=/outbound/daily
target_folder=/inbound/transfer
|
...