-----
Original Message -----
Sent: Tuesday, December 06, 2005 2:32
PM
Subject: [Hardhats-members] Setting up HL
LOGICAL LINKs problem - No response
Hi all
We want to have connection between two VistA
systems, so that they can exchange patient data between themselves. According
to the manuals, the first step is to establish a connection between them using
the HL7 links. The specification of the two systems is
Server A (TCP server)
1. IP address is 192.168.1.31
2. Cache on NT
3. Following is the entry added to HL LOGICAL
LINK file
NUMBER:
210
NODE: ZVISTA
INSTITUTION: ZZ.EHR OFFICE
LLP TYPE: TCP
DEVICE TYPE: Multi-threaded
Server
STATE: Reading
TIME STOPPED: DEC 06, [EMAIL PROTECTED]:22:51 SHUTDOWN LLP ?:
NO
QUEUE SIZE:
100
ACK TIMEOUT: 600
TCP/IP ADDRESS:
192.168.1.31
TCP/IP PORT: 5000
TCP/IP SERVICE TYPE: MULTI
LISTENER PERSISTENT: YES
STARTUP NODE:
EHR:CACHEWEB
SAY HELO: YES
Server B (TCP client)
1. IP address is 192.168.1.201
2. GT.M on Linux
3. Following is the entry added to HL LOGICAL
LINK file
NUMBER:
194
NODE: ETL2
INSTITUTION: ZZ.EHR
OFFICE LLP
TYPE: TCP
DEVICE TYPE: Persistent
Client
STATE:
Idle
AUTOSTART:
Enabled
TIME STARTED: DEC 06,
[EMAIL PROTECTED]:47:56 TIME STOPPED: DEC 06,
[EMAIL PROTECTED]:47:56
SHUTDOWN LLP ?: NO
QUEUE SIZE:
100
ACK TIMEOUT: 600
TCP/IP
ADDRESS:
192.168.1.31
TCP/IP PORT: 5000
TCP/IP SERVICE TYPE: CLIENT
(SENDER) PERSISTENT: NO
STARTUP NODE:
ROU:local
SAY HELO: YES
On running PING (TCP only) option from Server B, the message displayed is
"No response". And the STATE of ZVISTA link on Server A is READING.
The HL7 Site Manager and Developer Manual says "No response" means "VISTA HL7 was able to get a connection, but failed
to get a response. In this case, a listener is running on the target system,
but something else is wrong: the listener is a foreign listener (e.g., the RPC
Broker), or the link entry for the listener on the receiving system is not
defined correctly."
Can someone help detect the possible problem?
Regards
Usha
