Page History

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

What is the purpose of the

...

YADE Background Service?

The principle objective of JADE the YADE Background Service is to collect all file transfer activities through JADE YADE and store it into Database System i.ethem to a database, e.g. MySQL, PostgreSQL, Oracle etc.
The stored JADE YADE transfer history can then be used for analysis, compliance, alerting, planning, to measure SLA SLAs etc.

The main components of the JADE YADE Background Service are

1. SOS JobScheduler running as demondaemon/service on central a server
2. JADE Jobchain YADE history import job chain running inside the SOS JobScheduler

How to

...

transmit the transfer history data to the

...

YADE Background Service?

JADE YADE writes detail detailed log entries of the all file transfers irrespective of there status i.e. success, error in their status into the jade_history.csv and jade_history.log.

...

There are two possible ways how to transfer the JADE trasnfer histroy transmit the YADE transfer history to the JADE YADE Background Service:#

• Near Real Time: immediately after

...

• file transfer using TCP/UDP,

...

• the YADE Client initiates the transfer.

...

• Batch Mode: as per scheduled job

...

• of the YADE Background Service using file transfer,

...

• the YADE Background Service

...

• initiates the transfer.

...

TCP/UDP Communication

The transfer history can be send sent to JADE the YADE Background Service immediately after the file transfer over TCP or UDP. The JADE Background Service_server_name, port_etc. required parameters for the YADE Background Service, i.e.ServiceHost, ServicePort, TransferMethod (protocol) etc., can be configured under in the profile _BackgroundService_in of the _jade_settings.ini, which will be used by all the subsequent profiles._ _

_
_[BackgroundService]_
_BackgroundServiceHosh1. 
BackgroundServiceHost=jadebs.sos_
_BackgroundServicePort4210_
_SendTransferHistorh1. true_
_TransferMethodTCP
BackgroundServicePort=4210
SendTransferHistory=true
TransferMethod=TCP

File Transfer

The file name and location of jade_histiry.log and jade_history.csv can be configured by the profile jadeHistory in the file jade_settings.ini, which will be used by all the subsequent profiles. The YADE Background Service will launch tasks (YADE history import job chain_
h3. File Transfer
JADE Background Service have process (SOS Jobscheduler Jobchain) to collect all the _jade_histroyhistory.csv_ files from different servershosts. The _jade_histroy.csv_file(s) files can be PULL/RECEIVED received from different JADE Client(s) (server(s) where JADE YADE Client hosts where YADE isrunning), to the JADE YADE Background Service, using FTP, SFTP, FTPS, SCP. Once file is successfully PULL/RECEIVED by JADE Background Service files will be automatically processed and the files have been successfully received by the YADE Background Service then the files will be processed automatically and the transfer history will be imported in into the respective Database.
h3. database.

[jadeHistory]
log_filename=${TEMP}/jade_history.log
HistoryFileName=${TEMP}/jade_history.csv

Firewall and Port

...

Settings

...

• The YADE Background Service is using TCP/UDP

...

• ports, i.e.

...

• 4440 for the JobScheduler Operation Center GUI and to receive the transfer history (TCP/UDP packets),

...

• therefore firewall rules should

...

• include:
  • allow incoming TCP traffic from YADE Client host to YADE Background Service at port 4440.
  • allow incoming UDP traffic from YADE Client host to YADE Background Service at port 4440.
  • allow incoming TCP traffic from a host accessing the JobScheduler Operation Center GUI and YADE Background Service at port 4440.
• For YADE Background Service to receive 

• jade_history.csv

...

• files from the

...

• YADE Client hosts the respective ports as per

...

• transfer protocol, i.e. FTP 21, SFTP 22, should be allowed by the firewall on YADE Client hosts for the YADE Background Service.

  Firewall on JADE client server(s)