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

Compare with Current View Page History

« Previous Version 46 Next »

DAv

Server-to-Server File Transfer (S2S) is a unique key feature of JADE. It provides the possibility to set-up a number of file transfers using a single server without installing clients/agents on each source/target host.

JADE Implementation Architecture

JADE Architecture Components

JADE includes the following main components:

  1. CLI (Command Line Interface) executed at shell level
  2. User Application Programming Interface (API)
  3. JITLJobs scheduling component of JADE
  4. JADE Engine
  5. Options Engine
  6. JADE Engine Interface
  7. VFS (Virtual File System) Interface (Data Provider)
    • FTP
    • SFTP
    • FTPS
    • HTTP/HTTPS FEATURE AVAILABILITY STARTING FROM RELEASE 1.7 (1.7.4 onwards)
    • WebDAV  FEATURE AVAILABILITY STARTING FROM RELEASE 1.8
    • Local (native copy)

JADE Server-to-Server File Transfer

JADE can transfer data using an intermediate server from a Source Server-to-Target Server (S2S) without touchdown on an intermediate server.

S2S implementation details:

  1. JADE uses "Streams" (or in common terminology: pipes) to transfer data from source to target.
  2. JADE opens an input stream from the source server and and output stream to the target server.
  3. JADE can use different data provider as source and target for S2S operation.
  4. By default JADE will transfer 32Kb chunks from input to output stream. You can increase the buffer size by setting the buffer_size parameter, but a larger buffer size may not result in higher transfer speed.
  5. JADE can process the content of the buffer between source and target transfer. By doing in-memory operations, even for multistage processing, JADE dramatically improves the transfer speed.
    1. Calculate Hashes
    2. Reserved for further development
      1. Filtering
      2. Encoding/Decoding
      3. Encryption/Decryption
  6. JADE transfers data from the source server to the target server without touchdown meaning that during transfer the data is never written to the file system on the intermediate server where JADE is running. JADE's key feature is in-memory transfer. During transfer JADE does not copy any data to the memory, but only chunks whose size is defined with the buffer_size parameter.

For more information about JADE Server-to-Server File Transfer configuration see Example for JADE Server-to-Server File Transfer.

JADE provides a generic implementation for Virtual File Systems or Data Providers that makes it easy to implement new protocols.

 

  • No labels