The client most definitely doesn't want a security hole opened up with a SVRCONN (the channel type you get by default when you don't specify the channel property at all on the MQ connection factory).
Is there a secure bi-directional communication alternative between ActiveMQ and WMQ, or is the only answer for the client to purchase another copy of WMQ and for us to forget about ActiveMQ? The requirement is for our application to use a local messaging server so that the application is completely unaffected by any downtime their WMQ might suffer. Any knowledge of their WMQ is configured within the local messaging server and not within our application. I have no experience with message server integration, let alone with any of the WMQ products. Apologies if I'm straying off course. -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-integration-with-WebSphere-MQ-tp3550031p3563960.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
