| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Changing node properties from ESQL |
« View previous topic :: View next topic » |
| Author |
Message
|
| umaneesh |
 Posted: Sun Jun 28, 2009 8:58 am Post subject: Changing node properties from ESQL |
 |
|
Novice
Joined: 13 Apr 2009
Posts: 24
|
Hi,
Is there any ESQL way to change properties in node[MQInput Node, OutputNode, etc] ... In certain scenarios, instead of using RCD's i would like to go with ESQL..
Hope I have one way of doing this, by ASBITSTREAM/PARSE options. Not sure, how far this is useful for MRM, TDS formats as i have used this only for XML's.
May be now I am limited to msg properties. But, would like to know changing any nodes property in an ESQL way 
Pls advice.
Thanks |
|
| Back to top |
|
 |
| rekarm01 |
| Posted: Sun Jun 28, 2009 12:55 pm Post subject: Re: Changing node properties from ESQL |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 1415
|
| umaneesh wrote: |
| Is there any ESQL way to change properties in node [MQInput Node, OutputNode, etc] ... |
No. Node properties are configurable at deploy time, but not run time.
| umaneesh wrote: |
In certain scenarios, instead of using RCD's i would like to go with ESQL..
Hope I have one way of doing this, by ASBITSTREAM/PARSE options. |
The ESQL SET can directly modify fields in the Root.Properties sub-tree.
The ESQL CREATE statement and ASBITSTREAM function supports a PARSE clause to control parsing and serializing of message data.
Consult the documentation for more details. |
|
| Back to top |
|
|
| LazyBoy |
| Posted: Mon Jun 29, 2009 7:16 am Post subject: |
|
|
Voyager
Joined: 04 May 2006
Posts: 78
|
Hi umaneesh,
You can parse the incoming message from MQinput node as blob and then parse the blob message using CREATE PARSE Statement.
| Quote: |
| Hope I have one way of doing this, by ASBITSTREAM/PARSE options. Not sure, how far this is useful for MRM, TDS formats as i have used this only for XML's. |
CREATE Parse works the same as parsing on input node, so dont worry abt parsing using this statement it works fine.
The output message to output node is serialized against the message set value set in outputroot.properties.messageset , you can set this value in the esql. |
|
| 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
|
|
|
|
