YADE Job - handling settings and profile parameters

Current Situation

• the settings and profile parameters are not mandatory:
  • A YADE Job can be configured without the settings and profile parameters.
  • All another parameters such as source_host, file_spec etc can be directly defined in an YADE Job or Order.
• when the settings or profile parameters are not set, they will not appear in the YADE banner.
• when settings parameter is set
  • settings file does not exist
    • .xml file - job execution is terminated and an error message (file not found) is logged
    • .ini file - will be ignored
      • YADE Job is executed and terminated later with the error message SOSVfs-E-0000: one of these parameters must be specified: 'file_path', 'source_dir', 'File_List_Name'
  • profile parameter not set
    • Behavior like above for .ini file
  • profile parameter is set but does not exist
    • Job execution is terminated, an error message (profile not found) is logged
• when profile parameter is set
  • settings parameter not set
    • Behavior like above for .ini file

Desired Behaviour

• the settings and profile parameters should be always displayed in the YADE banner to make it clear that they are set or not.
• .ini file does not exist
  • similar to .xml case - Job execution should be terminated and an error message (file not found) should be logged
• settings parameter is set but profile is not set
  • Job execution should be terminated, an error message (missing profile parameter) should be logged
• profile parameter is set but settings is not set
  • Job execution should be terminated, an error message (missing settings parameter) should be logged
• implementation for the YADE Job with and without jump host