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 in JADE for multiple destinations:
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 |
In this example two commands, defined with the preTransferCommands
parameter, will be executed after connecting and before starting the transfer.
Of course the commands that can be executed depend on the operating system on which the JADE client is running.
See also Transfer to Multiple Destinations.
Securely Specifying Transfer Credentials
It is possible to securely specify transfer credientals, so that they are not visible in plain text.
For a transfer with (s)FTP(S) you can get the password by specifing a shell script (in backticks) which will return the password.
Code Block |
---|
password=`get.password.sh` |
The </code>stdout</code> of the script will be used as a temporary password. The script itself will be executed as a separate process.
For sFTP you can use PPK authorisation. JADE uses JSch (JCraft) and alternatively Trilead for SSH.
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 |
You don't need to specify a drive letter (on Windows).
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 JADE Parameter Reference Document.
Using JADE as an component via the API is described in our JADE API Reference.