MQ interface using JadeMessaging framework

[ConvertFromOldNGs]

by Alan >> Wed, 22 Jul 2009 1:08:15 GMT

We are currently interfacing from our Jade system to IBM MQ using the JadeMessaging framework. The MQ we are connecting to is on a remote machine - everything works fine - great interface.

Have a question from our architects - Are there any production Jade sites that are configured to use a local MQ connected to via a message channel agent to another MQ? The architects are after some confirmation that this will work prior to implementing a change aimed at reducing potential data loss due to network / remote hardware failures.

I would expect that this is transparent from a JadeMessaging framework point of view - can anyone, who has actually implemented the described target architecture, confirm this?

[ConvertFromOldNGs]

by Dean Cooper >> Thu, 23 Jul 2009 11:26:06 GMT

Assuming you mean the following:

MACHINE 1
[JADE] -- client connection -- [WMQ QueueMgr1]

[some channel between QueueMgr 1 & 2]

MACHINE 2
[WMQ QueueMgr2]

Then everything from the client connection onwards is standard WebSphereMQ stuff, so the fact that the client program is JADE should not be relevant. If you have some specific WMQ questions/concerns then you could perhaps try a WebSphere forum? We don't know of anyone using this configuration in a JADE system.

Dean.