Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Example: server to server transfer without touchdown:

Graphviz


<source>
 digraph "Example: Server to Server Transfer" \{
</source>

rankdir=LR;

edge [
color="#31CEF0"
];

source_server [label="Data Source (sFTP)"];
target_server  [label="Data Target (FTP)"];
jade_client  [label="JADE 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 file name extension ".txt" should be transfered from the server where YADE is installed to 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 via SFTP. YADE will check the file to be transferred for completeness: YADE will check every 1 second for the next 30 seconds if the file size changes. Once the file size would not change between check intervals, then YADE will start the file transfer.

To start this with the command line client one must type:

Code Block
languagebash

 jade.sh -settings=name_of_settings_file -profile=ftp_server_2_serversftp_to_wilma_with_stedy_state_check

To make the profile more reusable and readable it is possible to reuse profiles in the way like this:

Code Block
 [globals]
 log_filename=${TEMP}/sosftphistory.log

 [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
            = 22

The profile for wilma_as_source is defined once. It The profiles for wilma as source and 8of9 as target are defined once. They could be used as many time as needed. There is a "globals" profile as well.

Now we will specify the another profile again:

Code Block

 [ftp_server_2_serversftp_to_wilma_with_stedy_state_check]
 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
check_steady_state_of_files = true
 check_steady_count          = 30
 check_steady_state_interval = 1

The include 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 for an include parameter.
The profiles must be defined in the same settings file.