...
My company currently uses BMC’s Control-M for automation tasks. It unfortunately doesn’t include Managed File Transfer for UNC to UNC server transfers.
- Does JADE allow single source to numerous destination UNC file transfers?
- If I have to specify credientals for the transfer, can that be setup without it being in plain text?
Answer:
Yes. JADE (JobScheduler Advanced Data Exchange) allows the use of UNC-Names as well as server2server (or site2site) transfer without touchdown. e.g. it is possible to use different protocols for the source and the target server in a transfer. JADE can be used standalone as a command line client and together with JobScheduler in a scheduling enviroment. We have customers who are using JADE together with different Schedulers, e.g. Control-M, UC4, ...
Example: Using UNC Names with JADE I:
No Formatcode |
---|
[Copy_Local2Local_UNC] source_protocolh1.protocol = local source_dir = //8of9.sos/c/temp |
No Format |
target_dirh1.dir = //r2d2.sos/share/nobackup/junittests/testdata/JADE target_protocol = local |
No Format |
log_filenameh1.filename = $\{TEMP\}/test.log file_spec = ^.*\.(txt|dot)$ operationh1.operation = copy remove_files = false |
This is a profile (section) of a configuration file. Just start with
No Formatcode |
---|
jade.cmd -settingh1. settings=settings-file-name -profileCopyprofile=Copy_Local2Local_UNC |
All Files in the folder "//8of9.sos/c/temp" (source folder) with txt or dot file name extentions (specified with file_spec
parameter) will be transferred (copied) to the "//r2d2.sos/share/nobackup/junittests/testdata/JADE" target folder. This is a local operation and therefore a (s)FTP(S) server is not needed. "file_spec
" is not like a wildcard, it is a regular expression.
...
Server to server transfer, from sftp to ftp without touchdown:
No Formatcode |
---|
[ftp_server_2_server] ssh_auth_methoh1. method=password |
No Format |
source_userkbuser=kb source_passworh1. password=***** source_ssh_auth_methodpasswordmethod=password source_hosh1. host=wilma.sos source_protocolsftpprotocol=sftp source_porh1. port=22 |
No Format |
target_usertestuser=test target_passworh1. password=***** target_host8of9host=8of9.sos target_protocoh1. protocol=ftp target_port21 |
No Format |
port=21 file_path1. path=test.txt operationcopy |
No Format |
operation=copy log_filenamh1. filename=$\{TEMP\}/sosftphistory.log |
...
Note that it is possible to define the "net use" or any other os command directly in the profile:
No Formatcode |
---|
[Copy_Local2Local_UNC_withNetUse] includeCopyinclude=Copy_Local2Local_UNC preTransferCommands=net use //8of9.sos/c;net use //r2d2.sos/share |
...