It 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.
 

John Clemens
IT Specialist, Software
IRMS
Veterans Affairs Medical Center (662)
4150 Clement Street
San Francisco, CA  94121
Phone:  415.221.4810 x4540 (Tu,Wed,Thu)

Cell phone Mon and Fri (7:30-4:00 Pacific)
650.464.7585
Digital Pager:415.303.0388 ( Mon,Fri)
Fax: 415.750.2177
 
[EMAIL PROTECTED]
 
 

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gregory Woodhouse
Sent: Tuesday, December 06, 2005 7:59 AM
To: [email protected]
Subject: Re: [Hardhats-members] Setting up HL LOGICAL LINKs problem - No response


On Dec 6, 2005, at 2:01 AM, Usha wrote:

After changing the TCP/IP SERVICE TYPE of Server A from MULTI LISTENER to SINGLE LISTENER and restarting the links, PING worked.
 
Though I have no idea why it did not work as MULTI LISTENER..........
 
Regards
Usha 

Single listeners work entirely in the VistA environment, but multi-listeners require some setup at the OS level. In this case, the daemon doesn't run in the MUMPS environment, but is a program that calls MUMPS to handle messages when they arrive.

===
Gregory Woodhouse

"The most profound technologies are those that disappear."
--Mark Weiser




Reply via email to