| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message flow: SOAPRequest validation option management |
« View previous topic :: View next topic » |
| Author |
Message
|
| bazzaa |
 Posted: Wed Feb 03, 2010 8:13 am Post subject: Message flow: SOAPRequest validation option management |
 |
|
Novice
Joined: 29 Sep 2009
Posts: 18
|
Hi all,
Is it possible to manage validation state (none/content and value, etc) for all applicable nodes in message flow (especially SOAPRequest) during .bar deployment?
I'm working with messages in XMLNSC domain and noticed that performance is increased drastically (not on production but on test environment, CentOS 5.4 under VirtualBox) when validation is off, that's why I'm wondering is it possible to change this value during deployment.
Thanks! |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Feb 03, 2010 11:45 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Well, the validation switch is on each input node, on RCD nodes and Compute nodes ( all flavours ). So you should have the control you require in the deployed artifacts.
I'm interested to hear that validation makes a large difference to performance in your flow. Normally, validation has a fairly low overhead ( <25% ) in XMLNSC. If you're prepared to open a PMR and supply your schemas you might find that the cost of validation can be significantly reduced. |
|
| Back to top |
|
|
| bazzaa |
| Posted: Thu Feb 04, 2010 3:39 am Post subject: |
|
|
Novice
Joined: 29 Sep 2009
Posts: 18
|
Hi Kimbert,
| kimbert wrote: |
| Well, the validation switch is on each input node, on RCD nodes and Compute nodes ( all flavours ). So you should have the control you require in the deployed artifacts. |
Ok, so you should always have a sources and redeploy a flow after changes are applied?
Another issue, as I understand a value of Input node's validation property is inherited upon the flow. So in order to disable validation (actually, set it to "none") for each flow node (if applicable) I just need to set Input node's validation property to "none". Am I correct?
| Quote: |
| I'm interested to hear that validation makes a large difference to performance in your flow. Normally, validation has a fairly low overhead ( <25% ) in XMLNSC. If you're prepared to open a PMR and supply your schemas you might find that the cost of validation can be significantly reduced. |
<25%
25% of what? CPU time of node execution? Overall execution time? And where this value is taken from? Any proof? 
Well, yes, performance overhead for SOAP extraction/validation is minimal and easily could be neglected running a flow on some real server environment. But if I run broker on virtual machine with, say, Linux on the board and host has 2GB RAM and 1 CPU 2GHz... The flow that consists of 3 SOAPRequest nodes and some minimal response merging logic using ESQL is sometimes 3(!) and even more times faster when validation is off... In my case, for instance, 3(off) vs 11(on) seconds. |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Feb 04, 2010 4:09 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| 25% of what? CPU time of node execution? Overall execution time? And where this value is taken from? Any proof? |
Fair question. I was talking about CPU usage. I based that comment on some performance tests which were done a long time ago ( when v6.1 XMLNSC was under development ).
I would be interested to know a little more about your scenario. Things like average message size / style of schema ). Hence my suggestion about a PMR. |
|
| 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
|
|
|
|
