Monday, March 22, 2010

Configuring the C:D Requester


Day 2

Before we get into the configuring of Lee’s Connect:Direct Windows, I’d like to just give few more details about testing the connectivity to the remote Connect:Direct node. The possible outcomes from the “telnet” test are “refused”; probably a firewall not configured appropriately. “failed” means that there was nothing listening on that port, probably because the remote Connect:Direct node was not running. “Timeout” means that no route to the remote address was found. If you get this then you will probably want to perform a “tracert” and see where the connection is being held up. It could be a router or even a routing rule on the server depending on where the “tracert” shows where the problem is. 

The outcome you are looking for is when the “telnet” program actually connects on the port you gave it. This shows that something at that address was listening on the said port and accepted your connection request. If this happens you won’t see anything useful in the “telnet” screen so just kill the command prompt window.

It was also be a good idea for someone at the remote node to perform a similar exercise to prove that the network connectivity is actually in place before troubleshooting the Connect:Direct configuration.
For configuring Connect:Direct Windows we will be using the Connect:Direct Requester program that you should be able to find after clicking the start menu button then “Programs” and then “Sterling Commerce Connect:Direct ...” and then click on “C:D Requester”. Hopefully you will see something similar to the image below:

 


If you installed Connect:Direct Windows or if you have previously configured the C:D Requester to point to your Connect:Direct node then you should see your node name in the left hand panel in the nodes tab. In the above picture you can see my node name NICKE. If you don’t have any nodes listed there then you will have to look in the “Node | Connection Settings | Insert Node” menu and configure your connection to your local node. 

When you have something like the left panel above then we can configure the connection to the remote node.

No comments: