On Dec 6, 2005, at 8:15 AM, Clemens, John wrote:

t occurs to me that the option name, "Ping (TCP Only)" is confusing in this setting. That option is really for use between two VISTA HL7 implementations only. It was a useful tool for VA to test that another VA site was operational. Rather than telnet'ing to a site at port 5000 and quitting, it tested connectivity through to HL7 Package and application response, indicating that Vista HL7 is actually listening on the port defined. It works for both single and multi-listener configurations. As Greg mentioned, it sounds like the multi-listener issue was setup being OS-specific.
 

Yes, I've gotten a number of questions from people thinking it is something like a network level ping. HL7 PING uses a non-standard extensions to VistA HL7 and serves to ensure that the process to which you are connecting does run VistA HL7. The ping utility in Unix/Linux is used to establish low level network connectivity, and has nothing to do with TCP. In fact it works by sending an ICMP ECHO_REQUEST. Internet Control Message Protocol (or ICMP) is a control protocol you usually don't have to deal with directly. But, for example, if you ever tried to connect to a system and saw a message like "No route to host", then you've seen ICMP in action. Your system knows this is the problem because it's received an ICMP message to that effect.

===
Gregory Woodhouse

"Design quality doesn't ensure success, but design failure can ensure failure."

--Kent Beck


Reply via email to