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.
- YADE allows to specify configuration files individually per transfer fragment.
YADE Java Property File Configuration
YADE System Property Configuration
The Java properties configured using System Property Files are global properties available to all protocol fragments. 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.
Following is the example of such a System Property File which contains global properties for multiple data providers. The YADE will apply applicable properties to respective data provider e.g. SFTP properties to JSch data provider and SMB properties to JCifs data provider.
sftp_system_proprieties.ini
SystemProperyFile sftp_system_proprieties.in# SFTP properties known_hosts=/home/gollum.sos/.ssh/known_hosts remote_exec=true
smb_system_proprieties.ini
SystemProperyFile smb_system_proprieties.ini# SMB properties jcifs.smb.client.useExtendedSecurity=false
Example
Description
- The YADE profile has three sections
- Globals section
- ProtocolsFragments section
- Transfer Profiles section
- The system properties files configure under globals section with option
system_property_files
will be available to all the protocol fragments and The YADE will apply applicable properties to respective data provider e.g. SFTP properties to JSch data provider and SMB properties to JCifs data provider. . - In above mentioned 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 Configuration Files Configuration
The ConfigurationFiles are properties available only to the protocol fragments they are assigned. The ConfigurationFile option can be assign a semicolon separated list of property files. The property files can contain on or more properties as key value pairs.
Example
- 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
- 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 two configuration files are created, both of them has configuration properties for the SFTP data provider
sftp-zlip-compression.ini
: effects packet compression during transfer over SFTP.sftp-cipher-aes128-ctr.ini
: effects Cipher used by SFTP data provider.
The
sftp-zlip-compression.ini
is being assigned to the protocol fragmentprotocol_fragment_sftp@sftp-uk.sos
using, thus the packet compression properties will only be applicable to the protocol fragmentprotocol_fragment_sftp@sftp-uk.sos.
Similarly the sftp-cipher-aes128-ctr.ini is being assigned to the protocol fragment
protocol_fragment_sftp@sftp-japan.sos
, thus the Cipher aes128-ctr will only be applicable to the transfers using the protocol fragment protocol_fragment_sftp@sftp-japan.sos.
YADE Settings
References
Change Management References