11-24-2019
Connect direct - SFTP - List of servers that I can connect
Greetings Experts,
I am working for a bank client and have a question on connect-direct and SFTP.
We are using Linux RedHat servers. We use connect-direct to transfer (NDM) files from one server to another server. At times, we manually transfer the files using SFTP from one server to another server. We have a portal for connect-direct to check the list of nodes/servers configured to send/receive the files on a specific server.
With above given information..
I had a requirement to transfer a file from SIT environment to PROD environment (I know its not correct way, but due to un-avoidable situation did it). I had checked whether the connect-direct is configured between the 2 servers and confirm that they are not configured (verified netmap entries also). As no other alternative, I tried SFTP and transferred the file using SFTP successfully.
I was under the impression that SFTP will be successful between the servers only for which connect-direct is configured (atleast at server-level and not user-id level) between them.
I am not able to understand on below. Can you please help to explain.
Questions:
1. As SFTP successful, how can I know the list of servers I can successfully transfer through SFTP. Is there any file which contains the list of servers that can be connected to. Or is that I can connect to any servers through SFTP without any issues if I have the passwords.
2. Does SFTP also use the public and private keys for connections and transmission.
3. For SFTP, will it refer to both specified user-id home-directories on source and target servers or only on source server or only on target server.
4. Is there any way to restrict the users have SFTP access and allow only the specified users to have SFTP access.
5. Does connect-direct also use the public and private keys for connection establishment.
Thank you for your valuable suggestions and time.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello,
I have a V880 and a 420 running Solaris 9. Each box has more than one NIC card. I'd like to know how to configure the network on the two boxes so that I can directly connect the NIC cards. Meaning, I don't want a switch or router between the two. I just want to run a CAT5 cable to each... (3 Replies)
Discussion started by: agcodba
3 Replies
2. Shell Programming and Scripting
Dear friends,
i need to connect sftp server from my home directory using script .
Please can anyone help me on this. (1 Reply)
Discussion started by: kittusri9
1 Replies
3. Shell Programming and Scripting
Hi,
I have a script in which i'm using ndm connect direct to fetch data from the client server..syntax i'm using is
./con_using_connectdirect /load/nctrl nctrl $xhost
where con_using_connectdirect is the script which establishes connection
load/nctrl is the path from where data... (4 Replies)
Discussion started by: Sheema
4 Replies
4. Solaris
Hi,
I am configuring Connect direct on Solaries 6.0,
but whenever i am giving the below command
cdpmgr -i /export/app/cdunix/ndm/cfg/khello/initparm.cfg
i am getting the message
Component <cdpmgr ndmcmgr ndmsmgr ndmumgr cdstatm> permissions are not set.
Please follow instructions in the... (3 Replies)
Discussion started by: sidd
3 Replies
5. Red Hat
Hi to all,
I've installed IBM Connect:Direct 4.1.00 on Red Hat Enterprise Linux Server release 5.5, but when I try to execute the "direct cli", I obtain the following error:
$ ./direct
***********************************************************
* ... (2 Replies)
Discussion started by: f.vietti
2 Replies
6. Shell Programming and Scripting
Hello all,
I have a requirement to transfer files to mainframe usinf NDM connect:direct. So can anybody provide me a sample shell script on how to call a connect;direct script by providing filename as a parameter please?
Thanks,
Ajay (0 Replies)
Discussion started by: ajaykumar4534
0 Replies
7. Shell Programming and Scripting
I want to connect direct a xml file and a excel file each separately from unix system to another unix system.The size of the xml file and excel file may vary each time.
Below is the possible connect direct script to transfer the files.Please check if it is correct?
Also does DCB parameter... (4 Replies)
Discussion started by: bk_12345
4 Replies
8. Red Hat
I am transfering a file using connect direct from Linux to Mainframe.
Its a point to point transfer but its failing with below error:
**** Error from CONNECT:Direct API - ndmapi_recvresp_c error
Can we do PTP transfers?
code tags for code, please. (1 Reply)
Discussion started by: gerryperillo
1 Replies
9. UNIX for Dummies Questions & Answers
Hi..
We are using connect direct to transfer the files between servers. The CD scripts run on HP UX.
Below is the code using ndmcli.
ndmcli -x << EOJ
submit maxdelay=0 proc1 process snode=$3
step1 ... (1 Reply)
Discussion started by: anijan
1 Replies
10. AIX
i have directly connect AIX pwer 7 to lenovo v3700 v2 without San through fiber card. but i cannot see the WWPN to add AIX as host in management console. (10 Replies)
Discussion started by: khalid khanAIB
10 Replies
LEARN ABOUT MOJAVE
curlopt_connect_to
CURLOPT_CONNECT_TO(3) curl_easy_setopt options CURLOPT_CONNECT_TO(3)
NAME
CURLOPT_CONNECT_TO - Connect to a specific host and port instead of the URL's host and port
SYNOPSIS
#include <curl/curl.h>
CURLcode curl_easy_setopt(CURL *handle, CURLOPT_CONNECT_TO,
struct curl_slist *connect_to);
DESCRIPTION
Pass a pointer to a linked list of strings with "connect to" information to use for establishing network connections with this handle. The
linked list should be a fully valid list of struct curl_slist structs properly filled in. Use curl_slist_append(3) to create the list and
curl_slist_free_all(3) to clean up an entire list.
Each single string should be written using the format HOST:PORT:CONNECT-TO-HOST:CONNECT-TO-PORT where HOST is the host of the request, PORT
is the port of the request, CONNECT-TO-HOST is the host name to connect to, and CONNECT-TO-PORT is the port to connect to.
The first string that matches the request's host and port is used.
Dotted numerical IP addresses are supported for HOST and CONNECT-TO-HOST. A numerical IPv6 address must be written within [brackets].
Any of the four values may be empty. When the HOST or PORT is empty, the host or port will always match (the request's host or port is
ignored). When CONNECT-TO-HOST or CONNECT-TO-PORT is empty, the "connect to" feature will be disabled for the host or port, and the
request's host or port will be used to establish the network connection.
This option is suitable to direct the request at a specific server, e.g. at a specific cluster node in a cluster of servers.
The "connect to" host and port are only used to establish the network connection. They do NOT affect the host and port that are used for
TLS/SSL (e.g. SNI, certificate verification) or for the application protocols.
In contrast to CURLOPT_RESOLVE(3), the option CURLOPT_CONNECT_TO(3) does not pre-populate the DNS cache and therefore it does not affect
future transfers of other easy handles that have been added to the same multi handle.
The "connect to" host and port are ignored if they are equal to the host and the port in the request URL, because connecting to the host
and the port in the request URL is the default behavior.
If an HTTP proxy is used for a request having a special "connect to" host or port, and the "connect to" host or port differs from the
requests's host and port, the HTTP proxy is automatically switched to tunnel mode for this specific request. This is necessary because it
is not possible to connect to a specific host or port in normal (non-tunnel) mode.
When this option is passed to curl_easy_setopt(3), libcurl will not copy the entire list so you must keep it around until you no longer use
this handle for a transfer before you call curl_slist_free_all(3) on the list.
DEFAULT
NULL
PROTOCOLS
All
EXAMPLE
CURL *curl;
struct curl_slist *connect_to = NULL;
connect_to = curl_slist_append(NULL, "example.com::server1.example.com:");
curl = curl_easy_init();
if(curl) {
curl_easy_setopt(curl, CURLOPT_CONNECT_TO, connect_to);
curl_easy_setopt(curl, CURLOPT_URL, "http://example.com");
curl_easy_perform(curl);
/* always cleanup */
curl_easy_cleanup(curl);
}
curl_slist_free_all(connect_to);
AVAILABILITY
Added in 7.49.0
RETURN VALUE
Returns CURLE_OK if the option is supported, and CURLE_UNKNOWN_OPTION if not.
SEE ALSO
CURLOPT_URL(3), CURLOPT_RESOLVE(3), CURLOPT_FOLLOWLOCATION(3), CURLOPT_HTTPPROXYTUNNEL(3),
libcurl 7.54.0 May 20, 2016 CURLOPT_CONNECT_TO(3)