Corepoint

• Mobile monitoring/troubleshooting (i.e. cycling interfaces) is a god send.
• We’ve developed complex monitoring and alerting capabilities for our interfaces using Corepoint’s highly customizable alerting framework. In addition to the standard error and queue depth, alert logging, and email notifications, we have some interfaces trigger connection restarts and even e-mail peer vendors’ technical support services upon connectivity loss. All were fairly straightforward to implement and easily managed.
• Monitoring is very easy. Can set up alerts based on connectivity, queue size, etc. as well as errors.

Cloverleaf

• I hear that there are modules that make this process better, but the core engine isn’t the best at monitoring, alerts, etc.
• Quite frankly, we don’t. We create our own. Too expensive. We have looked at these options in the past, but the salespeople don’t understand our needs and are just trying to make a big sale. This is certainly an area of weakness.
• Expensive and there is a learning curve to implement.

Rhapsody

• There are still configurations that you need to learn, but much easier than trying to build something outside of the tool.
• Web services support is very good for SOAP web services. The monitoring of multiple instances needs to be added.
• Complexity varies according to the task, but is mostly due to the complexity of the underlying service rather than the engine’s implementation of it.
• Not difficult, and simpler with these features all in the tool rather than various utilities and applications.

Mirth

• The Mirth interface seems fairly vanilla in terms of additional features.
• Web services are easy, monitoring and security are very hard.
• The open source platform allows for a more robust set of features that are constantly being adding to and approved upon.

Ensemble

• All of these items are doable, but each one comes with their own challenge. Calling web services as a client is rather easy, but setting up a web service server is difficult if the vendor requires us to tweak it for them. Monitoring is great, but if you want to create a role that has limited access it is always possible, but requires you to go very granular.
• Monitoring of interfaces is a crude process of building out additional interfaces and routing messages from each component monitored. It SHOULD be integrated into the software such that a list of ALL interfaces display, giving a choice for monitoring multiple errors and then can be turned on/off at will with a click. Still much to be desired in the monitoring of interfaces. This one thing could be the number two thing currently needing improvement. The ability to build mapping tables is number one. I have not dealt with building/using web services. The security seems adequate.
• The stuff we have done has not been an issue.