ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General Discussion » WAS V6 - ESB - JetStream? , death of the messagebroker?

Post new topic  Reply to topic
 WAS V6 - ESB - JetStream? , death of the messagebroker? « View previous topic :: View next topic » 
Author Message
Michael Dag
PostPosted: Fri Feb 18, 2005 5:40 am    Post subject: WAS V6 - ESB - JetStream? , death of the messagebroker? Reply with quote

Jedi Knight

Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)

I know the subject of this post is a bit confusing, but may be we can all put our heads together and shed some light on this...

More then a year ago the mysterious name JetStream appeared and we had some discussion on it see:
http://www.mqseries.net/phpBB2/viewtopic.php?t=12270&highlight=esb

Then the words ESB came up more and more and is on the top of Gartners hype cycle including SOAs.

So we have basic transport with WebSphere MQ, which can act as a JMS provider,
then WAS V5 came with embedded MQ, which could be linked to WebSphere MQ but could not co-exist on the same machine,
now WAS V6 is out with Messaging Resources (=MR from now): a Messaging Engine combined with Service Integration Bus

Reading the article below:
http://www-106.ibm.com/developerworks/websphere/techjournal/0501_reinitz/0501_reinitz.html
and related resources in the article
it turns out this Service Integration Bus in WAS V6 can 'talk' to almost anything, route messages and transform them.

From what I have read sofar the routing and transformations are not based on WBIMB / WBIEB technology i.e. using ESQL, but rather so called mediations written in Java. To the best of my knowledge this comes closer to the way WICS works, but then again there is no mention of this technology coming from the WICS domain.

from a positioning point of view this becomes a little confusing:

Transport: WebSphere MQ, WAS V6 MR
Routing : WebSphere MQ + WBIEB or WAS V6 MR
Transformation: WebSphere MQ + WBIMB or WAS V6 MR or WICS

There have already been debates whether to use WBIMB or WICS and sure they can work together and can share adapters and WBIMB can be considered to be predominantly a stateless router and transform engine and WICS is more into colaborations and process choreography

so I would position WAS V6 MR in between, but what would be the decisive factor to make me choose between WBIMB and WAS V6 MR?

is it ESQL versus Java, is pure performance versus ease of use?

your thoughts please!
_________________
Michael



MQSystems Facebook page
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
Michael Dag
PostPosted: Fri Feb 18, 2005 7:55 am    Post subject: Reply with quote

Jedi Knight

Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)

found some more information:

basically WAS V6 implements Service Data Objects (SDO) a standard jointly developed by IBM and BEA which basically is the 'intermediate' between let's say and inbound webservice and a database object or for that matter a JMS message mapped to a WebSphere MQ message.
I think this is how the 'any' to 'any' works.

WAS V6 embedded messaging implements JMS 1.1 spec, but for persistency uses the embedded database called Cloudscape.
This however is a configurable option as you can use DB2, Oracle, etc via JDBC drivers.
Maybe this explains also why embedded messaging is now fully interoperable with WebSphere MQ and can co-exist...
_________________
Michael



MQSystems Facebook page
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
bower5932
PostPosted: Fri Feb 18, 2005 8:08 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA

I have WAS6 and WMQ 5.3 CSD 7 installed on my system. I haven't played much with WAS6, but I did get interoperabilty working between the two. WAS6 has a concept of a WebSphere MQ Link that acts like a channel to a regular WMQ. You can then put messages from WMQ and have them go over the link to WAS6 and vice versa. There are instructions in the infocenter on how to get it setup:

http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp

and search for 'websphere mq link sample configuration'.
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General Discussion » WAS V6 - ESB - JetStream? , death of the messagebroker?
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.