| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message set |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bartez75 |
 Posted: Mon Aug 25, 2008 7:12 am Post subject: Message set |
 |
|
Voyager
Joined: 26 Oct 2006
Posts: 80
Location: Poland, Wroclaw
|
I want to have one message set that can handle 2 different messages.
First is: 12345Name1Address189
Second is: 12345Naaammmee2Address289
They start with the same record name but their length is different (whole length of msg). Second is longer then first. They don't have any delimiters, they are fixed length.
Is it possible to have them designed in one message set? They will never be send together to broker.
I thought about TDS, with type TaggedFixedLength but they have the same first field.
I tried also FixedLength but then when I sent second msg broker tried to put it in the first one which definition is for the shorter message.
I want to have them in one message set because then I can use only one flow for transformation.
If it is not that easy to do I will create two message sets and 2 flows. |
|
| Back to top |
|
 |
| sourdas2 |
| Posted: Mon Aug 25, 2008 11:20 am Post subject: |
|
|
Voyager
Joined: 21 Apr 2006
Posts: 90
Location: Kolkata,India
|
You no need to create two different message sets. You can simply create two message defination file under the message set or one message defination file with two different message.
Also, you no need to create two different flows. In Input Node, the any message can be taken as Blob and then in compute node, it could be converted to any logical tree (tree1 or tree2) using PARSE clause.
_________________
Thanks and Warm Regards
Sourav |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Aug 25, 2008 12:28 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| Is it possible to have them designed in one message set? They will never be send together to broker. |
You need to parse two different messages. The logical structure of both messages is the same, but the physical format is different.
You should do this:
- Create one message set
- Create one message definition
- Create two TDS physical formats ( e.g. 'TDS1' and 'TDS2', but you can probably come up with better names than those )
- In TDS1, set the length of 'Name' to 5. In TDS2 set it to 10
Now you have to decide how to pick TDS1 or TDS2. If the messages are arriving at the same input node, and without an RFH2 header, then you will have to
- parse as BLOB in the input node
- pick TDS1 or TDS2 based on the length of the message
- Use a ResetContentDescriptor node ( or CREATE...PARSE ) to re-parse using the MRM TDS parser.
If the mesages are arriving at different input nodes, or they have an RFH2 header with an mcd folder, then the task is much simpler.
btw, this scenario would be ideal for a message broker training course. Message broker always separates the logical structure of a message from its physical format. Most users do not properly understand that concept. |
|
| 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
|
|
|
|
