| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Question Of Message Definiton Files |
« View previous topic :: View next topic » |
| Author |
Message
|
| satyasheel15 |
 Posted: Fri May 28, 2004 10:38 am Post subject: Question Of Message Definiton Files |
 |
|
Voyager
Joined: 04 Mar 2003
Posts: 86
|
Question:
I have one question on Message Definition Files introduced in the new version of WBIMB V5. As pe the document, it has been mentioned that one message set contains many many message definition files. So if for example I create three message definition files such as:
1. CreditCardRequestMessage.mxsd
2. CreditCardResponseMessage.mxsd
3. MDSRequestMessage.mxsd
And there is one message which contains the all the above mentioned components , then in the MQInput Node properties, which values I should be entering into MessageType properties. And in one compute node, how to access the value of the all the three message definition files.
Please advise. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Jun 01, 2004 2:15 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Message Definition files are a container for storing one or more messages. Nothing more, nothing less.
In the MQInput node properties, fill in the Domain. Set, Type and Format exactly the same way you would for a 2.1 system. Note that the MessageType field should contain the name of the message, because identifiers have been phased out from 5.0 onwards.
Your Compute node will process whatever messages arrive on its input terminal - it does not need to know anything about the message definitions you are using.
You may want to consider putting all three of your messages into one message definition file, if it makes things simpler for you. |
|
| Back to top |
|
|
| waugh |
| Posted: Tue Jun 01, 2004 4:36 am Post subject: |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
satyasheel,
for your question below,
| Quote: |
And there is one message which contains the all the above mentioned components , then in the MQInput Node properties, which values I should be entering into MessageType properties |
Message Domain -- MRM.
Message Set -- once you select MRM in WBIMB, actually you are able to select the message set you created from drop down window.
Message Format -- Is the physical format of the incoming message you created if its XML, the default would be something like XML1..etc., you should be able to select this one from drop down once you select your message set.
Message Type -- no drop down, you need to type -in the message name. for example if message1 contains message2 and message3 then your type would be message1.
the way you access the element is something like
InputRoot.MRM.Message1.Message2.CCNumber
Hope this helps.. |
|
| Back to top |
|
|
| satyasheel15 |
| Posted: Wed Jun 02, 2004 8:34 am Post subject: |
|
|
Voyager
Joined: 04 Mar 2003
Posts: 86
|
The thing is that we have three message definition files. Two of them have headers defined in them. We have defined the headers into separate message definition files, so we could reuse them in other flows. The third msd file contains the actual message definition (the payload).
The question now is:
The message coming into the input queue has header1 followed by header2 followed by message. Currently we are reading this message in as BLOB and then parsing each part separately (by using substring and parse), using each of the message set/type. However we are concerned, if this is the best way to do in terms of efficiency. We are wondering, If we should be defining all the headers and the message in one msd file as one single message. That way we can set this as the message type in the input node.
Hope it is clear. Please let us know if it isn't. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Jun 03, 2004 12:44 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
1. You can have more than one message definition file within the same message set. When you add the message set to a BAR file, all the message definition files are processed, producing the dictionary in the BAR file.
2. A message definition file can include or import another message definition file, thus achieving reuse within a single message set. You may be able to include or import your headers this way.
3. A message can contain other messages. A Complex Type with Type Composition set to 'Message' can contain references to other messages within the same message set. You may be able to use this to model your two-headers-and-a-body structure. On the other hand, it may be simpler to model the headers as global elements, and just refer to them from several different message definitions.
Do you really need to have the headers in a separate message set from the body? If not, you should consider using include or import to re-use the message definition files containing the headers. |
|
| 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
|
|
|
|
