| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Restrictions with Multiple SOAP Input Nodes in Message Flow |
« View previous topic :: View next topic » |
| Author |
Message
|
| Pegazus |
 Posted: Tue May 10, 2011 10:31 am Post subject: Restrictions with Multiple SOAP Input Nodes in Message Flow |
 |
|
Novice
Joined: 10 Aug 2006
Posts: 16
|
I am trying to use 2 SOAP Input nodes in my message flow, but I get an error on deployment saying, Vector out of range error. The error as such is not clear.
From what I understand, when you use multiple soap input nodes, the URI cannot be the same, although the base URL can be same.
If anyone has experience using multiple soap input nodes in WMB 7 and aware of the restrictions, pls. let me know. The Manual is not very clear on this.
Here is what I read from developerworks
http://www.ibm.com/developerworks/webservices/library/ws-soapnode3/
Each SOAPInput node is configured by a single WSDL file. If you need to implement several versions of the same WSDL, you can configure multiple SOAPInput nodes in the same flow as long as each node uses a different Uniform Resource Identifier (URI). The SOAPInput nodes can share a single SOAPReply node if required; this may improve the readability of the flow. |
|
| Back to top |
|
 |
| harish_td |
| Posted: Tue May 10, 2011 7:13 pm Post subject: Re: Restrictions with Multiple SOAP Input Nodes in Message F |
|
|
Master
Joined: 13 Feb 2006
Posts: 236
|
| Pegazus wrote: |
| If anyone has experience using multiple soap input nodes in WMB 7 |
We use multiple SOAPInput Nodes (using different WSDL files) in certain flows. No such issues during deployment.
Using two SOAP Nodes with the same URI would perfectly work too (Research Only). But you have no say on which input node received the message. You can verify this by running the command
| Code: |
| mqsireportproperties BROKER -e EG_NAME -o HTTPConnector -r |
Ensure your toolkit and run time are up to date with the latest fixpac levels.
Can you Validate the WSDL that you are using in the toolkit?
Try to generate the skeleton flow that is auto-generated when you drag and drop a Deployable WSDL to your Message Flow Canvas
On a related note, i do not like the idea of having multiple starting/entry points in my flow and avoid them as much as possible. If you use a single WSDL for multiple operations, that need similar kinds of processing, then i would use a combination of 1 SOAPInput and SOAPExtract nodes to route the operations. |
|
| 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
|
|
|
|
