| Author |
Message
|
| albitkw |
 Posted: Wed Mar 24, 2010 7:18 am Post subject: Transform MRM to XMLNS to Add a DOCTYPE XML Declaration |
 |
|
Novice
Joined: 02 May 2005
Posts: 15
Location: Pittsburgh, PA
|
 I must use a mapping node for some major mapping operations using two complex message sets. I beleive this requires that the messages be defined as MRM. Output messages, however, must have XML declaration statements that contain DOCTYPE attributes.
The input message contains repeating rows, so an intial compute node is used to break them into individual messages required by the mapping node target message set.
After mapping, is it possible to transform the MRM messages into XMLNS format so that I can use the XML.XMLDecl functions?
If this cannot be done in a single message flow, should I use two: the first for MRM mapping and the second for adding custom XML declarations? |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Mar 24, 2010 7:53 am Post subject: Re: Transform MRM to XMLNS to Add a DOCTYPE XML Declaration |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| albitkw wrote: |
The input message contains repeating rows, so an intial compute node is used to break them into individual messages required by the mapping node target message set.
|
why do you need this, if you could do everything in one Compute Node
| albitkw wrote: |
After mapping, is it possible to transform the MRM messages into XMLNS format so that I can use the XML.XMLDecl functions?
If this cannot be done in a single message flow, should I use two: the first for MRM mapping and the second for adding custom XML declarations? |
you are un-necessarily making it so complex 
its so simple if you use 1 or 2 compute nodes and complete the full flow.
or use JCN to do the same.
Message broker is really a good tool don't contaminate
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Mar 24, 2010 7:59 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| I must use a mapping node for some major mapping operations using two complex message sets. I beleive this requires that the messages be defined as MRM. |
Please read this: http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/ad10280_.htm
I would recommend that any non-trivial message flow should have a message set that describes the formats that it deals with. It is recommended practice, and makes the toolkit work better in loads of ways.
| Quote: |
After mapping, is it possible to transform the MRM messages into XMLNS format so that I can use the XML.XMLDecl functions?
|
Don't use MRM for XML messages. Don't use XMLNS unless you have a good reason. Use XMLNSC throughout your message flow, as recommended in the infocenter. |
|
| Back to top |
|
|
| albitkw |
| Posted: Wed Mar 24, 2010 8:43 am Post subject: |
|
|
Novice
Joined: 02 May 2005
Posts: 15
Location: Pittsburgh, PA
|
If MRM is not used, does that mean all mapping must be done in ESQL and Compute nodes?
My source and target message sets are derived from XML schemas. The source is relatively flat, but the target Message Set is based on two XML schmas, where one references fields defined in the other, which has multiple levels. My understanding is that mapping nodes can only be used with MRM messages.
Sorry if I seem to have little experience with XML and message sets. My responsibilities only include one or two message sets every 4 years. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 24, 2010 8:52 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| albitkw wrote: |
| My understanding is that mapping nodes can only be used with MRM messages. |
Your understanding is false, as is your reading of kimbert's post. He's talking about message sets, which can and should be used to model XML messages.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Mar 24, 2010 9:10 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| My understanding is that mapping nodes can only be used with MRM messages. |
A long time ago, the MRM parser was the only parser that used message sets at runtime. As far as I remember, the Mapping node has always used message sets.
In all recent versions of the product, *all* of the toolkit uses message sets to make your development experience easier. Create them and use them in every flow that you design.
| Quote: |
| If MRM is not used, does that mean all mapping must be done in ESQL and Compute nodes? |
No. You could have found that out in 5 minutes by reading the infocenter.
| Quote: |
| My responsibilities only include one or two message sets every 4 years. |
As a responsible developer, you should be aiming to produce maintainable message flows. That usually means using message sets. |
|
| Back to top |
|
|
| albitkw |
| Posted: Wed Mar 24, 2010 4:41 pm Post subject: |
|
|
Novice
Joined: 02 May 2005
Posts: 15
Location: Pittsburgh, PA
|
Thanks for your help. Unfortunately, we're still at version 6003, so I guess that's working on a system from a long time ago. There is a big difference between the version 7 "XML parsers and domains" artical you referenced and the version 6 artical from my version 6 HELP.
My MQ Input nodes only allow message set entries for the MRM domain. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Mar 25, 2010 12:18 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| we're still at version 6003 |
That's the first time you've mentioned it
| Quote: |
| My MQ Input nodes only allow message set entries for the MRM domain. |
I know. That fact does not change any of the advice given above. |
|
| Back to top |
|
|
|
|
