Q: I need to receive a high volume of HL7 messages, how FAST can the UltraPort Listener receive HL7 messages?
A: Message volume (or throughput) is a very important consideration for anyone exchanging HL7 messages over TCP/IP, and for the VAST majority of users it's also a question that can be answered very easily. The answer depends on your definition of high volume. For example, if you need an HL7 Listener that can receive/write/log up to 200,000 HL7 messages per day the answer is really simple, no problem, the UltraPort HL7 Listener in any configuration should suit your needs without any thought whatsoever. If your requirement/expectation is that you need to process greater than 200,000 HL7 messages per day then the answer can be very complex, not just for our UltraPort Listener but for ANY HL7 Listener product. For this reason we created a special topic in the help devoted to helping you determine your HL7 volume/speed/throughput needs. See Listener Volume for more information.
Q: My Application just shuts down or won't start?
A: Remember that the UltraPort Listener uses TCP/IP socket communication. Although unlikely, this can trigger DEP or be blocked by firewalls and network security programs (like Norton's or Symantec's). The most common experience is with users on Microsoft Windows Server 2003 or greater who have DEP blocking all applications by default. UAC is a much more likely culprit here.
Q: Can I have 2 listener profiles "listen" on the same Port?
A: No. Never. Only one listener application (of any kind) can bind to a particular port at any given time. Here's a real world example. A lot of people don't realize this but Microsoft SQL Server (and Oracle for that matter) is just a Listener application. By default SQL Server "Listens" on port 1433 (unless you specifically change it). If you have SQL Server running on your computer AND try to configure a listener profile (or the Global Monitor Port) to listen on port 1433 one of two things will happen. If SQL Server is running, then your listener will fail to start because it can't bind to port 1433 OR if SQL is not running, the listener will start successfully BUT if you then try to start SQL Server it will fail to start.
Q: Can I have a listener profile listen on the same Port as a 'Proxy' application running on the same computer?
A: No. Never. As in the answer aboce Only one listener application (of any kind and this includes Proxy applications built with the UltraPort Listener Proxy Toolkit) can bind to a particular port at any given time.
Q: Can I have multiple listener profiles deliver HL7 messages to the same Data Folder?
A: Yes. Absolutely. There are even scenarios where you need to do this specifically because of limitations of the client sending HL7 to you. Some clients may require that different feeds go to different ports whereas you may wish to have ALL HL7 data consolidated into one location.
Q: Can I have multiple listener profiles forward HL7 messages to the same Proxy Application on the same port?
A: Yes. Absolutely.
Q: Can I have 1 listener profile deliver HL7 messages to multiple Data Folders?
A: No. Each listener profile can only deliver messages to a single data folder. However, if you need to have 1 inbound message delivered to multiple destination folders then we do have a solution for you. The UltraPort HL7 Postmaster was designed for just this type of scenario. Click here for more information. Another alternative would be to create a Proxy Toolkit application in Microsoft Visual Studio which could then save HL7 messages wherever you wish.
Q: I have a computer running the UltraPort Listener. I've purchased a single port license. Can I upgrade that license to 2 ports? 10 ports? 50 ports? 100 ports?
A: Yes. Absolutely. In version 1 licenses are available for up to 500 ports on a single computer. Contact HermeTech customer service US#254-549-0825 or email info@hermetechnz.com for more information and pricing. You're only limited by your computer's physical resources (memory, processor, storage).
