| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| mapping message from XML to TDS format (WMB6.1) |
« View previous topic :: View next topic » |
| Author |
Message
|
| sapana |
 Posted: Thu Feb 19, 2009 11:46 pm Post subject: mapping message from XML to TDS format (WMB6.1) |
 |
|
Apprentice
Joined: 16 Apr 2007
Posts: 33
Location: Pune
|
Hi,
I created a simple message flow -: MQInput -> Mapping Node -> MQOutput
Input message parsed as :
Message Domain : MRM
Message format : XML
Mapping node was used to transform the input message from XML to TDS format.
The default message domain of the message set project was XMLNSC.
So although I had set the Message Format property to TDS format in mapping node, the output message was still in XML format : OutputRoot - > XMLNSC->message.
And in Message broker documentation it is mentioned :
The parser that is associated with the output message is determined by the Message Domain property of the message set.
(Link : http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp?topic=/com.ibm.etools.mft.doc/ar25245_.htm )
When I changed the default message domain of message set project to MRM, the problem got resolved.And the message was transformed to TDS format (Note, I made no changes to mapping node or the message map)
I request someone to confirm if this observation is correct. If so, how do you deal with the scenario where your message set has different message domain and you need to transform to a different domain? Would ResetContentDescriptor node help in this case?
Sapana |
|
| Back to top |
|
 |
| MQEnthu |
| Posted: Fri Feb 20, 2009 12:31 am Post subject: |
|
|
Partisan
Joined: 06 Oct 2008
Posts: 329
Location: India
|
When you create the message set in the toolkit, in wizard it asks for what kind of documents you will be working with. By default it will be XML documents. And for xml documents, XMLNSC is the default domain in V6.1. And if you choose the documents as binary or text files, the default domain will be set to MRM. If you have not choosen the correct documents type while creating the message set, you will have to chnage the default domain later (as you have done it in your case).
| Quote: |
| how do you deal with the scenario where your message set has different message domain and you need to transform to a different domain? |
I am not sure if I understand you correctly.... You will have to create the message set with appropriate domain as per the requirement of the transformation... For, ex. in your case the outdomain is MRM, and you have to create the message set with MRM domain.
_________________
-----------------------------------------------
It is good to remember the past,
but don't let past capture your future |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Feb 20, 2009 2:35 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I request someone to confirm if this observation is correct |
Confirmed.
| Quote: |
| how do you deal with the scenario where your message set has different message domain and you need to transform to a different domain? Would ResetContentDescriptor node help in this case? |
Your scenario is unusual, because you are using a single message set for two different purposes. Note the following:
- IBM recommends that you have a single physical format per message set.
- The default domain is the domain which the toolkit uses when it provides code assist. So if you added a Compute node and tried to write some ESQL to access fields in InputRoot, then you might get spurious warnings.
It is working for you because:
- Your input message will be parsed using the XMLNSC parser because that is what is specified on the input node. The default domain does not affect message parsing.
- The mapping node chooses the output domain based on the Default Domain of the message set.
The ResetContentDescriptor node can be used to change the domain/set/type/format but it would not help you here. The Mapping node is driven only by the Default Domain of the message set.
If the message flow is going to get more complex, I would recommend that you use two message sets, each having a different Default Domain. |
|
| Back to top |
|
|
| sapana |
| Posted: Fri Feb 20, 2009 3:02 am Post subject: |
|
|
Apprentice
Joined: 16 Apr 2007
Posts: 33
Location: Pune
|
Thanks Kimbert & MQEnthu for the answers. That answers all my questions 
Sapana |
|
| 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
|
|
|
|
