SSH provider - support SSHJ

Desired Behavior

• By default the new data provider SSHJ is not activated, i.e. the data provider JSch is active for compatibility reasons.
• The new data provider can be activated from
  • a command line option -ssh_provider for use with the YADE command line client
    • e.g.: ... -ssh_provider=SSHJ
  • a job/order parameter ssh_provider for use with the YADE JITL job
    • e.g.: <param name="ssh_provider" value="SSHJ"/>
  • an environment variable that applies to both YADE command line client and YADE JITL Job:
    • for JS1: SCHEDULER_VFS_SSH_PROVIDER
    • for JS7: JS7_VFS_SSH_PROVIDER
• The values for the command line option/job/order parameters/both environment variables are the same (case insensitive)
  • JSCH: activates the previous JSch data provider
  • SSHJ: activates the new SSHJ data provider

Test Instructions

• YADE configuration
  • configure a SFTP Fragment
  • configure a Jump Fragment
  • configure Profiles (Copy - for both directions: to/from SFTP, Move, Remove, GetList operations)
  • configure Jump profiles (copy from/to internet)
• JITL-Job configuration
  • configure the sos.scheduler.jade.JadeJob jobs (Copy - for both directions: to/from SFTP, Move, Remove, GetList operations)
  • configure the sos.scheduler.jade.SOSJade4DMZJSAdapter jobs (copy from/to internet)
• YADE standalone client configuration
  • configure jade.cmd|sh calls (Copy - for both directions: to/from SFTP, Move, Remove, GetList operations)
  • configure jade4dmz.cmd|sh calls (copy from/to internet)
• Test YADE JITL-Job
  • Test default JSCH Provider
    • run configured jobs and check the YADE functionality and the YADE job output (find SOSSFTPJCraft)
  • Test SSHJ Provider
    • add a new parameter to all job/order definitions
      • <param name="ssh_provider" value="SSHJ"/>
    • run configured jobs and check the YADE functionality and the YADE job output (find SOSSFTPSSHJ)
      • Note: for Jump (DMZ) jobs check the output of the YADE standalone client on DMZ system
  • Test the environment variable
    • remove <param name="ssh_provider" value="SSHJ"/> parameter from the job definitions
    • configure an environment variable SCHEDULER_VFS_SSH_PROVIDER=SSHJ for all jobs (see How to add environment variables for all jobs)
    • run configured jobs and check the YADE functionality and the YADE job output (find SOSSFTPSSHJ)
    • Test JSCH Provider
      • add <param name="ssh_provider" value="JSCH"/> to one of the jobs
        • run this job and check the YADE job output (find SOSSFTPJCraft)
• Test YADE standalone client
  • Test default JSCH Provider
    • run configured scripts and check the YADE functionality and the YADE output (find SOSSFTPJCraft)
  • Test SSHJ Provider
    • Test the command line option
      • add a new command line option
        • -ssh_provider=SSHJ
      • run configured scripts and check the YADE functionality and the YADE output (find SOSSFTPSSHJ)
    • Test the environment variables
      • remove the -ssh_provider=SSHJ command line option if exists
      • Test for JobScheduler 1.13.10 (SCHEDULER_VFS_SSH_PROVIDER)
        • set the SCHEDULER_VFS_SSH_PROVIDER=SSHJ environment variable in the cmd/sh script
          • run configured scripts and check the YADE output (find SOSSFTPSSHJ)
      • Test for JobScheduler JS7 (JS7_VFS_SSH_PROVIDER)
        • set the JS7_VFS_SSH_PROVIDER=SSHJ environment variable in the cmd/sh script (rename previously configured SCHEDULER_VFS_SSH_PROVIDER variable)
          • run configured scripts and check the YADE output (find SOSSFTPSSHJ)