| Author |
Message
|
| murdeep |
 Posted: Fri Feb 29, 2008 10:23 am Post subject: MQInput Node Input Message Parsing promited property issue |
 |
|
Master
Joined: 03 Nov 2004
Posts: 211
|
Hi, WMB runtime V6.0.0.5, tooling support is up to date.
I am trying to develop a message flow where I configure the MQInput node Input Message Parsing message values (domain, set, type format) at deploy time.
I promote these properties but when I add the flow to my bar these promoted properties do not appear so I cannot set them at bar build time.
Is this a bug or are there certain properties of nodes that can't be promoted. I searched the doc but didn't see anything stating these can't be promoted.
Can someone verify if they can promote these and set set them at bar build time. |
|
| Back to top |
|
 |
| murdeep |
| Posted: Fri Feb 29, 2008 10:44 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
Ok, I thought I'd look into the RCD node and I see in the doc that the values I mention are NOT configurable in the RCD node. So I assume the same is true for the MQInput node but can't find the doc that explicitly states this.
So, now my question is morphing into: does anyone know a way where I could set say UDPs at deploy time and then maybe force a reparse of the input message?
I'm thinking that if I can set my UDPs at deploy time and then do a reparse in a compute node then maybe I can get around this.
Any ideas? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Feb 29, 2008 2:10 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Not all properties are configurable in the bar file.
You don't need to use an RCD node to change these, you can just set them in the Properties tree.
These values on MQInput are suggestions anyway... if the Broker can identify the message on it's own, it will do so and parse it that way.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| murdeep |
| Posted: Sun Mar 02, 2008 10:44 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
| Jeff, so if I wire a compute node after my MQInput node, configure the MQInput node to use the BLOB domain and then in the compute node set the properties to reflect the values I provided in UDPs for messge domain (MRM), set, type etc then the broker will be able to subsequently parse the message? I assume if in compute node A I set the properties then I'll need another compute node B after compute node A where I can then reference InputRoot.MRM? |
|
| Back to top |
|
|
| vsr |
| Posted: Mon Mar 03, 2008 7:38 am Post subject: |
|
|
Centurion
Joined: 04 Apr 2006
Posts: 104
|
| You can do that within a single compute node using 'CREATE ... PARSE' using a MsgSet . Like you said, you can promote msg set type and format to the flow. No need for 2 compute nodes. |
|
| Back to top |
|
|
| murdeep |
| Posted: Tue Mar 04, 2008 8:16 am Post subject: |
|
|
Master
Joined: 03 Nov 2004
Posts: 211
|
| For my interest does anyone know why specifically MQInput node Input Message Parsing values can't be promoted? |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Mon Jul 21, 2008 11:09 pm Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
| murdeep wrote: |
| For my interest does anyone know why specifically MQInput node Input Message Parsing values can't be promoted? |
I would like to know too and if there is a list of properties that can not be promoted...
I was trying to promote a messageset ID to the flow (that worked) and then wanted to set it at bar level, but no luck and
a lot of time spent scratching my brains... 
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
|
|
