You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

IN PROGRESS

Scope

  • YADE implements a Virtual File System that supports a number of data providers, e.g. SMB/CIFS protocol implementation by Samba.
  • Data providers can make use of individual Java properties, e.g. for SMB/CIFS to specify compatibility levels for authentication with NTLMv2 and newer or for SFTP to specify packet compression to zlib, compression level 9 or Cipher blowfish-cbc,aes192-ctr.
  • YADE allows to specify Java property files at a global level and individually per transfer fragment.
    • Properties from Java property files are applied as system properties by YADE.

YADE Java Property File Configuration

YADE System Property Configuration

The System property is a global property available to all protocol fragments and transfer profiles. The SystemPropertyFiles option can be assign a semicolon separated list of property files. The property files can contain on or more properties as key value pairs.

SystemProperyFile hashed_known_hosts.ini
known_hosts=/home/gollum.sos/.ssh/known_hosts

Example

Description 
  • 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 protocol_fragment_sftp@sftp-uk.sos and protocol_fragment_sftp@sftp-japan.sos.

YADE Settings

 

YADE Settings system_property_files
[globals]
history                             = /home/test/sos-berlin.com/jade_client/logs/jade_history.csv
system_property_files               = /home/test/sos-berlin.com/jade_client/configurations/hashed_known_hosts.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

[protocol_fragment_sftp@sftp-japan.sos]
protocol                            = sftp
host                                = japan.sos
user                                = tokyo
ssh_auth_method                     = publickey
ssh_auth_file                       = ${HOME}/.ssh/id_rsa

[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

 

YADE System Property Configuration

 

References

Change Management References

YADE-400 - Getting issue details... STATUS

 

  • No labels