Table of Contents | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Questions:
- Can JADE handle 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 securely, without it being in plain text?
Answer:
UNC to UNC server transfers
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 I: Using UNC Names in JADE:
Code Block |
---|
[Copy_Local2Local_UNC]
source_protocol = local
source_dir = //8of9.sos/c/temp
target_dir = //r2d2.sos/share/nobackup/junittests/testdata/JADE
target_protocol = local
log_filename = $\{TEMP\}/test.log
file_spec = ^.*\.(txt|dot)$
operation = copy
remove_files = false
|
This is a profile (section) of a configuration file. Just start with
Code Block |
---|
jade.cmd -settings=settings-file-name -profile=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.
Example II: Using UNC Names and the "net use" command:
Note that it is possible to define the "net use" or any other os command directly in the profile:
Code Block |
---|
[Copy_Local2Local_UNC_withNetUse]
include=Copy_Local2Local_UNC
preTransferCommands=net use //8of9.sos/c;net use //r2d2.sos/share
|
...
See also Transfer to Multiple Destinations.
Securely Specifying Transfer Credentials
It is possible to securely specify transfer credentals, so that they are not visible in plain text.
Getting the pw from a script
For a transfer where a password is required (e.g. (s)FTP(S)) you can get the password by specifing the name of a shell script (in backticks) which will return the value of the password.
Code Block |
---|
password=`get.password.sh`
|
The script itself will be executed as a separate process.
The content of </code>stdout</code> created by the script will be used as the value for the password.
private/public key usage
For sFTP you can use PPK authorisation. JADE uses JSch (JCraft) and alternatively Trilead for SSH.
windows: net command
For UNC names you can use, for example on Windows systems, a .net command before you start the JADE client.
Code Block |
---|
Example: Net Use \\yourUNC\path /user:uname password
|
...
If credentials are a big issue, we recommend the use of sFtp with PPK whenever possible, which, of course depends on the configuration of the server.
Further Information
See also our JadeParameterReference
.
...