YADE should support to write the file transfer history from an order variable to the reporting database

Current Situation

• YADE can be operated as a JITL job for JobScheduler 1.x and can be executed by its CLI.
• When executed as a JITL job then
  • parallelism of tasks slows down performance,
  • the file transfer history is not supported if YADE is operated with an Agent that has no access to the reporting database.

Desired Behavior

• JobScheduler 1.x
  • Jobs sos.scheduler.jade.JadeJob, sos.scheduler.jade.Jade4DMZJob.
    • Introducing a new boolean job/order parameter async_history (default false).
      • e.g.: <param name="async_history" value="true"/>
  • the FactPlugin should similarly store information from the scheduler history table to the reporting file transfer history tables.
• JS7
  • With YADE-574 an order variable is available that holds the compressed file transfer history.
  • The History Service should consider this order variable and should store its value (in fact the compressed history of files in a given transfer) to the file transfer history tables.

Maintainer Notes

• The functionality is primarily targeted towards use of YADE with JS7.
• It remains to be checked if the functionality can be made available in a similar way for JobScheduler 1.x.

Test Instructions

• Configure a YADE Transfer Job
  • set the job log level to debug9
  • set job/order parameter; <param name="async_history" value="true"/>
• Execute the YADE Job
• Check the log output:
  • find [skip history]async_history=true message
  • no hibernate operations should be found
• Switch to FILE TRANSFERS tab
  • find the current transfer