| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Common Message Model, Different wire formats - Parsing |
« View previous topic :: View next topic » |
| Author |
Message
|
| xprezons |
 Posted: Fri May 13, 2005 8:32 am Post subject: Common Message Model, Different wire formats - Parsing |
 |
|
Novice
Joined: 02 Sep 2004
Posts: 16
Location: UK
|
Hi,
Is it possible to read messages from a *common* queue, wherein the messages have a common message model, but having different wire formats (i.e. CSV, Fixed length format)?
The only way, I can think of is to read the message as a BLOB and then figure out by scanning the message contents and then applying a Reset Content Descriptor to parse the message to the model.
Is there a smarter way of doing this? Appreciate your thoughts on this.
TIA,
Xprezons. |
|
| Back to top |
|
 |
| JLRowe |
| Posted: Fri May 13, 2005 8:41 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
Multipart messages allow you to embed a message format within an envelope message, but I don't think they work across different wire formats.
The only definite way I can think of is to use a BLOB and a RCD. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 13, 2005 8:52 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
As long as the messages are all part of the same message set, and can be reasonably distinguished by the first few bits... the parser may be smart enough to do this for you.
Also, if the message producers can attach an MQRFH2, then they can fully specify what to use to parse the message - and the broker will use that instead of what is on the Input node.
And you could also model one message that contained a single choice element - that contained each different message. Then you wouldn't need the RCD - you'd just need something to use to determine how to resolve the choice, and then your code would force the resolution.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| xprezons |
| Posted: Fri May 13, 2005 11:35 am Post subject: |
|
|
Novice
Joined: 02 Sep 2004
Posts: 16
Location: UK
|
| jefflowrey wrote: |
As long as the messages are all part of the same message set, and can be reasonably distinguished by the first few bits... the parser may be smart enough to do this for you.
Also, if the message producers can attach an MQRFH2, then they can fully specify what to use to parse the message - and the broker will use that instead of what is on the Input node.
And you could also model one message that contained a single choice element - that contained each different message. Then you wouldn't need the RCD - you'd just need something to use to determine how to resolve the choice, and then your code would force the resolution. |
Thank you for your suggestions. The beauty lies in their simplicity 
Shall have to summon a meeting with the message producers  |
|
| 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
|
|
|
|
