MQSeries.net :: View topic - Accessing the properties of an HL7 node in eSQL

jrsetters · Posted: Tue Jul 31, 2012 7:08 am Post subject:

The GenericHL7Output node in the healthcare pack has three terminals:

1) Failure
2) Out
3) Retry

When a messages is successfully sent and an acknowledgment is received from the client, the Acknowledgment message is propagated to the Failure terminal. I am able to take this output and cast it along with some of its properties to a BLOB output that is sent to a text log file. This is our first source of verification for message connectivity.

When an ACK is propagated to this terminal it carries the TCPIP connectivity information as part of the LocalEnvironment variables and I am able to grab this and place it in my log file.

For instance: TIMESTAMP '2012-07-30 10:30:02.961398' ** ACK RECEIVED FROM 10.1.1.18:0731 - MSG 378346 **

Before the HL7 node I use a flow order to throw a copy of the original message into the same subflow that creates the timestamp so that every successful message has a sending timestamp followed by the original message, then an ACK timestamp followed by the text of the ACK.

This is great for a lot of support purposes.

However when the message fails through 1 of 2 scenario - the receiving port is not accessible, or the message times out waiting for the acknowledgement, the HL7 node propagates the message to either the OUT or RETRY terminals respectively. I am able to capture these in my Log sublfow and label my time stamp appropriately, but in neither case are the TCPIP properties from the HL7 node contained in the local variables. So in those cases I cannot specify the IP and Port it was attempting to send to.

I am wondering if there is some way to extract the configurable properties of the HL7 node when they aren't included automatically as local variables in the message flow. Ideally, I'd like to place the TCPIP address and Port number the node is sending to as text in each of the message send attempts. Basically the contents of the field 'Connection details' below:

[/img]