| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| WTX replacing Message Broker? |
« View previous topic :: View next topic » |
| Author |
Message
|
| zpat |
 Posted: Wed Feb 04, 2009 3:47 am Post subject: |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5867
Location: UK
|
The aix menu says something like
| Quote: |
Websphere Message Broker 6.0 provides message processing facilities Yes
Transformation Broker Services extends capabilities of the broker Yes
|
So it should really say Websphere Event Broker? Bit confusing. |
|
| Back to top |
|
 |
| shanson |
| Posted: Wed Feb 04, 2009 4:20 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
| Event Broker is gone from 6.1 onwards. |
|
| Back to top |
|
|
| joebuckeye |
| Posted: Thu Feb 05, 2009 7:03 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 365
Location: Columbus, OH
|
We use WTX maps in WMB flows where I work.
One thing we would like to see is the ability to import a WTX type tree and create a WMB Message Set from it.
We have over 100 WTX maps and having no easy way to create a Message Set from the type trees has limited our design options.
It has been awhile since we looked into this so I don't know if it has been added recently or not. |
|
| Back to top |
|
|
| shanson |
| Posted: Thu Feb 05, 2009 7:28 am Post subject: |
|
|
Partisan
Joined: 17 Oct 2003
Posts: 344
Location: IBM Hursley
|
This facility does not exist today.
Even if it did, you end up with the WTX map using the type tree, and the rest of the flow uses the message set. The MRM owned tree must be serialised prior to the WTX map node, and the WTX map then re-parses the bitstream using the type tree. And reverse on output. It's not very efficient. And it's a double maintenance headache.
New in 8.2.0.3 is an alternative. Create your models only as message sets. Then use the facility in WTX maps to use an xsd/mxsd instead of a type tree when building a card. If the broker message tree is owned by XMLNSC or MRM domains, the WTX map node walks the broker tree, instead of serialising/re-parsing. More efficient. You should definitely be building WTX maps for XML processing this way anyway (XML modelling in type tree is ugly). But it's good for non-XML data too - MRM does the parsing, the WTX map works off the logical data in the message tree. The disadvantage is that you can't use such a map for non-XML data when it runs outside broker. |
|
| Back to top |
|
|
| joebuckeye |
| Posted: Thu Feb 05, 2009 10:19 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 365
Location: Columbus, OH
|
Our main problem was that these were existing WTX maps that were being migrated into a WMB infrastructure. So type trees is what we had to work with.
We basically limited ourselves to working with the messages after they came out of the WTX node (the maps were basically turning various input formats into a common format) and created a message set for this common format by hand. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
