| Author |
Message
|
| Michael Dag |
 Posted: Fri Sep 02, 2005 9:00 am Post subject: Article: ESB with WAS V6 and MQ |
 |
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2602
Location: The Netherlands (Amsterdam)
|
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Fri Sep 02, 2005 11:26 am Post subject: Re: Article: ESB with WAS V6 and MQ |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
Michael == It has nothing to do with confusing or not.
The word is ESB and the reliability needed with the ESB.
The model on which the ESB messaging engine is based is radically different from the Embedded MQ model.
It allows for reliable and assured delivery even in client mode and multiple phase commit, a true feature for an ESB.
Enjoy  |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Sep 02, 2005 11:53 am Post subject: Re: Article: ESB with WAS V6 and MQ |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2602
Location: The Netherlands (Amsterdam)
|
| fjb_saper wrote: |
Michael == It has nothing to do with confusing or not.
|
Well I just want to know the details and without any introduction,
simply calling something I 'know' differently is adding to the confusion
| fjb_saper wrote: |
The word is ESB and the reliability needed with the ESB.
|
I know IBM wants to move to ESB as it is a hot topic, so IBM's ESB is called SIBus now?
| fjb_saper wrote: |
The model on which the ESB messaging engine is based is radically different from the Embedded MQ model.
|
In WAS V5 there was embedded MQ which was not MQ itself, now in WAS V6 the embedded MQ stuff is rewritten to the ESB model and cannot be called embedded MQ I understand that!
Is there another place where the difference between the 'old' embedded MQ and the new SIBus is discussed or explained?
| fjb_saper wrote: |
It allows for reliable and assured delivery even in client mode and multiple phase commit, a true feature for an ESB.
|
hhhhmm for the ME (Messaging Engine) this sounds a lot like good old MQ with a new coat 
MQ also has bridges and interfaces to other messaging systems, so what makes this new SIBus ME so special and/or will it replace MQ itself one day? (just asking...)
| fjb_saper wrote: |
Enjoy |
I do
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 02, 2005 12:28 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
The Messaging Engine is a completely different beast.
It is not a rewrite of MQ.
It's a full service JMS provider, that gateways to MQ if necessary.
In addition, there is support for a standard set of message schemas and protocols... which turns the whole thing into an ESB - an ESB is more than just the bus!
The "si" comes from the name of standard set of the schemas/protocols - which is a JSR I think.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JLRowe |
| Posted: Fri Sep 02, 2005 11:11 pm Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
The messaging engine (akin to a queue manager) stores the queue/topic contents in a database as opposed to directly in the file system with MQ.
Together with the high availability features in WAS 6, high availability becomes a *lot* easier to do. If the server that hosts a messaging engine dies, then it can pop up on another server within the cluster and resume the processing of messages. |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Thu Sep 08, 2005 11:36 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2602
Location: The Netherlands (Amsterdam)
|
| JLRowe wrote: |
The messaging engine (akin to a queue manager) stores the queue/topic contents in a database as opposed to directly in the file system with MQ.
Together with the high availability features in WAS 6, high availability becomes a *lot* easier to do. If the server that hosts a messaging engine dies, then it can pop up on another server within the cluster and resume the processing of messages. |
this 'looks' like the shared Queuing on the mainframe where CF in combination with DB2 is used.
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Sep 09, 2005 6:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
| Michael Dag wrote: |
| JLRowe wrote: |
The messaging engine (akin to a queue manager) stores the queue/topic contents in a database as opposed to directly in the file system with MQ.
Together with the high availability features in WAS 6, high availability becomes a *lot* easier to do. If the server that hosts a messaging engine dies, then it can pop up on another server within the cluster and resume the processing of messages. |
this 'looks' like the shared Queuing on the mainframe where CF in combination with DB2 is used. |
May be but it should be considerably faster than using the DB2 spill over of the Shared Queues in the Coupling Facility
|
|
| Back to top |
|
|
|
|
