JADE S2S implementation details

Server to Server (S2S) is unique key feature of JADE. It provides possiblity to setup number of transfers with installing clients/agents on each source/tearget server, from Single Sever.

JADE Implementation Architecture

JADE Implementation Architecture Details

JADE have following main components

1. JADE Engine
2. Options Engine
3. JADE Engine Interface
4. VFS (Virtual File System) Interface (Data Provider)
   • FTP
   • SFTP
   • FTPS
   • WebDAV
   • CIFS
   • Local (native copy)

JADE Server-to-Server File Transfer

JADE can transfer files using intermediate server from Source Server to Target Server (S2S) without touch down on intermediate server. S2S implementation details.

1. JADE uses "Streams" (or common terminology pipe) to transfer file from Source to Target.
2. JADE opens an input stream from source server and
3. output stream with target server.
4. JADE can use different Data provider as Source and Target for S2S operation.
5. By default JADE transfer 32Kb chunks from input to output stream. One can increase the buffer size by setting buffer_size parameter, but bigger buffer size may not result in higher transfer speed.
6. JADE can process the content of the buffer during transfer
   1. Calculate Hashes
   2. Reserved for further development
      1. Filtering
      2. Encoding/Decoding
      3. Encryption/Decryption
7. JADE transfers files from source server to target server without "touch down" means, during transfer file is never written to the intermediate server (where JADE is running). JADE's key unique feature is "in memory" transfer. During transfer JADE do not copy entire file in the memory, but only chunks, size defined as with parameter buffer_size.

For more information about JADE Server to server transfer configuration see link JADE server to server transfer
JADE has a generic implemantation for Virtual file System or Data Provider, which make it easy to implement new Protocols.