Page History

...

• The YADE profile has three sections 1. globals section 2. Protocol sections and 3. Transfer profile sections.
• The system properties configure under globals section with option system_property_files will be available to all the protocol fragments and transfer profiles.
• In following example the location of hashed known hosts file is configured as name value pair in the file hashed_known_hosts.ini.

• The known_hosts system property will be available and applied to all the fragments and profile using SFTP data provider e.g. to protocol fragments protocolfragments protocol_fragment_sftp@sftp-uk.sos and sos and protocol_fragment_sftp@sftp-japan.sos.

...

• Code Block
  language bash title SFTP packet compression configuration sftp-zlip-compression.ini
  compression.s2c=zlib@openssh.com,zlib,none compression.c2s=zlib@openssh.com,zlib,none compression_level=9

• Code Block
  language bash title SFTP Cipher configuration sftp-cipher-aes128-ctr.ini
  cipher=aes128-ctr

Description 

• The global SystemProperty file will be used as described in the previous section.
• In following example the location of hashed known hosts file is configured as name value pair in the file hashed_known_hosts.ini.two configuration files are created, both of them has configuration properties for the SFTP data provider
  1. sftp-zlip-compression.ini :  effects packet compression during transfer over SFTP.
  2. sftp-cipher-aes128-ctr.ini : effects Cipher used by SFTP data provider.

• The sftp-zlip-compression.ini is being assigned to the protocol fragment protocol_fragment_sftp@sftp-uk.sos using, thus the packet compression properties will only be applicable to the protocol fragment protocol_fragment_sftp@sftp-uk.sos.

• Similarly the sftp-cipher-aes128-ctr.ini is being assigned to the protocol fragment The known_hosts system property will be available and applied to all the fragments and profile using SFTP data provider e.g. to protocol fragments protocol_fragment_sftp@sftp-ukjapan.sos and protocol, thus the Cipher aes128-ctr will only be applicable to the transfers using the protocol fragment protocol_fragment_sftp@sftp-japan.sos. 

YADE Settings

• Code Block
  language bash collapse true
  [globals] history = /home/test/sos-berlin.com/jade_client/logs/jade_history.csv system_property_files = /home/test/sos-berlin.com/jade_client/configurations/known_hosts_file.ini   [protocol_fragment_sftp@sftp-uk.sos] protocol = sftp host = uk.sos port = 22 user = london ssh_auth_method = publickey ssh_auth_file = ${HOME}/.ssh/id_rsa configuration_files = /home/test/sos-berlin.com/jade_client/configurations/sftp-zlip-compression.ini     [protocol_fragment_sftp@sftp-japan.sos] protocol = sftp host = japan.sos user = tokyo ssh_auth_method = publickey ssh_auth_file = ${HOME}/.ssh/id_rsa configuration_files = /home/test/sos-berlin.com/jade_client/configurations/sftp-cipher-aes128-ctr.ini [CopyLocal2SFTPUKSOS] operation = copy file_spec = TEST-M-1111.TXT source_protocol = local source_dir = /mnt/r2d2/nobackup/data/from_galadriel target_include = protocol_fragment_sftp@sftp-uk.sos target_dir = /home/london/data/to_london/     [CopySFTPJapanSOS] operation = copy file_spec = TEST-M-2222.TXT source_protocol = sftp source_include = protocol_fragment_sftp@sftp-japan.sos source_dir = /home/tokyo/data/from_tokyo/ target_protocol = local target_dir = /mnt/r2d2/nobackup/data/to_galadriel

...

References

Change Management References

...