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

Compare with Current View Page History

« Previous Version 10 Next »

h1. What protocol and port has to be opened between JADE client & JADE Background Service

What is the purpose of the JADE Background Service?

Ideally JADE Background Service is collecting all the file transfer activities through JADE and archieving it into supported RDBMS Systems i.e. MySQL, PostgreSQL, Oracle etc.

The main components of the JADE Background Service are

  1. SOS JobScheduler running as demon/service on central server
  2. JADE Jobchain running inside the SOS JobScheduler
    #

How to transfer the transfer history data to the JADE Background Service?

There are two possible ways to transfer the JADE trasnfer histroy to the JADE Background Service
JADE writes detail log entries of the all file transfers irspective of there status i.e. success, error in the jade_histroy.log
#Dynamically after the file transfer using TCP/UDP:
#Batch mode as per scheduleded job JADE Background Service in the using file transfer :

TCP Communication

The transfer history can be send to JADE Background Service immedially after the file transfer over TCP or UDP. The JADE Background Service server_name, port etc can be configured in the jade_transfer.ini, which will be used by all the subsiquent profiles.

UDP Communication

The transfer history can be send to JADE Background Service immedially after the file transfer over TCP or UDP. The JADE Background Service server_name, port etc can be configured in the jade_transfer.ini, which will be used by all the subsiquent profiles.

File Transfer

 The JADE Background Service can have scheduled job to collect all the ''jade_histroy.log'' files from different servers. The ''jade_history'' file(s) can be transferd from the JADE Client (server where JADE is running), using FTP, SFTP, FTPS, SCP. Once file is reveived by JADE Background Service files will be automatically processed and transfer history will be imported in the respective Database.
Warning: : syntax error in line 1 near 'ddigraph'
  • No labels