|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Environment Tree |
« View previous topic :: View next topic » |
Author |
Message
|
Sam Uppu |
Posted: Tue Oct 12, 2010 11:05 am Post subject: Environment Tree |
|
|
 Yatiri
Joined: 11 Nov 2008 Posts: 610
|
Hi Guys,
I have a requirement where I need to store the request message in a queue.
Initially I am storing it in Environment Variable and then I am copying it to outputRoot(SET OutputRoot = Environment.Variable.State) to drop it to a queue.I see the message of length zero is written to queue.
When I copy the Environment tree to Output Tree like below, I see message in queue.
SET OutputRoot.Properties = Environment.Variable.State.Properties;
SET OutputRoot.MQMD = Environment.Variable.State.MQMD;
SET OutputRoot.XMLNS = Environment.Variable.State.XMLNS;
Can you guys throw some light on this.
Thanks |
|
Back to top |
|
 |
Vitor |
Posted: Tue Oct 12, 2010 11:40 am Post subject: Re: Environment Tree |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Sam Uppu wrote: |
Can you guys throw some light on this. |
A message is more than just data on a queue. If it doesn't have an MQMD it doesn't count. WMB & the MQOuput node can build one for you if coded to, but just putting your data into the bitstream & expecting it to work won't.
You're also moving your data to OutputRoot, effectively deleting the Properties section of the message tree that WMB uses to describe the message internally. If you'd used CopyMessageHeaders then SET OutputBody = etc might have worked for you. Or SET OutputRoot.XMLNSC = etc
(Because you use XMLNSC for all new development don't you??)
But the 2nd way you describe is the correct way. There are many, many subtle design variations of this and I doubt any is the "right" one. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Oct 12, 2010 12:01 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You're also moving your data from trees that have parsers assigned to them to trees that don't, and then back again.
As previously discussed. |
|
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
|
|
|
|