| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ vs JMS and WAS Clustering |
« View previous topic :: View next topic » |
| Author |
Message
|
| jboller001 |
 Posted: Wed Feb 14, 2007 8:36 am Post subject: MQ vs JMS and WAS Clustering |
 |
|
Apprentice
Joined: 31 May 2006
Posts: 40
|
I have the following environment:
Server 1: Message Broker 6.0, WebSphere MQ 6.0
Server 2: Message Broker 6.0, WebSphere MQ 6.0
Server 3. WebSphere Application Server ND 6.0, WebSphere MQ 6.0
Server 4. WebSphere Application Server ND 6.0, WebSphere MQ 6.0
The queue managers on all four servers are clustered.
The code for the Message Broker is the same on both servers.
The same application is being run on both WAS servers.
Messages are sent from another application, where they are transformed and routed to the WAS servers using MQ. The queues on the application server are clustered, which allows for load balancing.
The following question has been raised: Would it be possible to replace the WebSphere MQ Queue Managers on the application servers with the application server's native JMS engine? Could I get the same clustering / load balancing using JMS that I get with MQ?
Thanks, |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Feb 14, 2007 9:57 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's possible.
There are several different ways to do it - for example switch to using JMS* nodes in Broker. The JMS provider in WAS 6 also bridges to MQ, and provides it's own internal load balancing - MQ would likely see all the WAS machines as a single qmgr, and the was provider would load balance on it's own.
If you've already paid the licenses for MQ on the WAS machines, though, it's of questionable benefit - that may depend on who you ask.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jboller001 |
| Posted: Wed Feb 14, 2007 10:46 am Post subject: |
|
|
Apprentice
Joined: 31 May 2006
Posts: 40
|
Initially we had WAS and the broker on the same servers, which allowed us to use a single MQ license. We were thinking that we would have to double our licenses now that we're moving those components to their own servers. We don't use MQ client connections.
By using the JMS nodes in the broker, are you saying that we can publish a message to a topic that's being subscribed to by MDBs on different servers?
Licensing costs aside, are there any architectural drawbacks to using JMS instead of MQ? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Feb 14, 2007 11:18 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You wouldn't need to use the JMS nodes in broker to publish or subscribe.
You'd just have to link the broker into the WAS JMS network as a foreign broker, and publish/subscribe only on that, rather than the internal. I think.
Licensing costs aside, there's a variable amount of risk in using the WAS JMS provider, which has been under development for less than a few years, and MQ which has been under development and widely used for many many years.
In addition, it's a different skill set for your administrators, and different configurations for monitoring toolds, and there are some different architectural considerations for laying out the network and etc.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
