This alert condition is primarily targeted towards Medical software and hardware that use HL7 to exchange data. If you don't understand the previous sentence this is probably NOT an Alert Condition that you can use. Don't feel bad though, most people that do not work in that industry have ever heard of HL7.
Network Conditions - TCP/IP Listeners
Verify that an HL7 TCP/IP MLLP Listener is working
Scenario: You are using WinScry to support medical software which exchanges HL7 data over a standard HL7 TCP/IP MLLP interface. If the HL7 listener you are sending to is not available OR your HL7 listener is not available for your trading partner then your solution will fail. Solution: Use a TCP/IP Listener condition to monitor an HL7 Listener (local for yours, remote for theirs).
Once configured a TCP/IP Listener condition will query the IP Address and Port Number every 3 minutes by attempting to open and then close a connection. If the operation fails the condition will be Activated. If it continues to fail long enough to pass the trigger threshold the condition will be Triggered.
IMPORTANT NOTE: The open connection / close connection operation described above should have absolutely no adverse effect on any HL7 compliant MLLP Listener software.
How to Create a TCP/IP Listener Alert Condition.
1.In the Network Alert Condition Window under This Alert Condition will monitor... check the A TCP/IP Listener button.
2.Indicate whether the Listener is running on the same computer as WinScry or a remote computer/server. IF running on a remote computer enter the TCP/IP address of that computer.
3.Enter the TCP/IP Port Number which the TCP/IP Listener is listening on. HINT: Click the Test / Verify button () to verify what you entered and do an immediate connect/disconnect action.
4.Set the Trigger Threshold time out.
5.Enable the condition by checking the Enable This Alert Condition box.
6.Click the OK button to save your changes.