Details
-
Fix
-
Status: Released (View Workflow)
-
High
-
Resolution: Fixed
-
1.12.12, 1.13.4
Description
Current Situation
- A YADE Client transfer can be configured in a settings file or via the YADE Client Command Line Interface directly.
- When the YADE Client not uses a settings file then the YADE transfer functionality is broken:
- The Source/Target Host and Protocol settings are ignored by the YADE Client.
- Jump host
- When YADE Source/Target fragment uses a JumpFragment then the YADE client installed on a server in the DMZ (jump host) should in a first step transfer files between the source server and the jump host and in a second step perform the transfer to the target host.
- This functionality is broken:
- the YADE client installed an a server in the DMZ (jump host) ignores the Source/Target Host and Protocol settings and tries to transfer the files beetween a Source and target directory on the same jump host via local file system.
- This functionality is broken:
- When YADE Source/Target fragment uses a JumpFragment then the YADE client installed on a server in the DMZ (jump host) should in a first step transfer files between the source server and the jump host and in a second step perform the transfer to the target host.
Test instructions
- see Fix Version/s
- YADE Client CLI
- Not use a settings file but running the YADE Client from the command-line arguments
- example:
<YADE Client>/bin/jade.(cmd|sh) -file_spec=".*\.txt" -transactional="true" -operation="copy" -source_protocol="sftp" -source_host="<sftp server>" -source_port="22" -source_user="<sftp user>" -source_password="<sftp user password>" -source_ssh_auth_method="password" -source_dir="/tmp/source" -target_protocol="local" -target_host="localhost" -target_dir="C:/tmp/target"
- Check the Banner Source/Target output (Protocol entry should not be empty)
- Check the execution results
- example:
- Not use a settings file but running the YADE Client from the command-line arguments
- YADE Jump
- See attached test_jump.xml
configuration
- copyToInternet - copy from a source server via jump host to a target server
- copyFromInternet - copy from a target server to a source server via jump host
- moveFromInternet - copy from a target server to a source server via jump host and delete the files on the target server
- getListFromInternet - connect to a target server via jump host and print the file list to the stdout
- removeFromInternet - connect to a target server via jump host and delete the files on the target server
- See attached test_jump.xml