| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Soap Input Node handling multiple WSDLs |
« View previous topic :: View next topic » |
| Author |
Message
|
| pottas |
 Posted: Mon Jun 30, 2008 1:54 am Post subject: Soap Input Node handling multiple WSDLs |
 |
|
Disciple
Joined: 27 Oct 2005
Posts: 185
Location: South Africa
|
As an addition to the post I did some while back on 'Version Control in Message Broker',
http://www.mqseries.net/phpBB2/viewtopic.php?t=44057&highlight=
I need some kind of way to handle different versions of WSDLs in Message Broker.
A SoapInput Node can handle one(...and only one) deployable WSDL. So that means if I introduce another version of the WSDL, I would have to have another SoapInput node. Firstly, is this correct?
So my question is, design-wise, what would be my options to handle different versions of the WSDL in the same flow, firstly with the least impact to the existing flows, and secondly without having to have a number of SoapInput Nodes in the Message flows each with its own endpoint and own WSDL?
Thanks
Jacques |
|
| Back to top |
|
 |
| francoisvdm |
| Posted: Mon Jun 30, 2008 2:19 am Post subject: |
|
|
Partisan
Joined: 09 Aug 2001
Posts: 332
|
Jacques
I've solved a similar problem where customer wants to "call only one" remote URL by accepting "XMLNS" as the input on HTTP Input node. Then I look at the data and "RouteToLabel". Luckily every distinct "call" had a "header" portion with some unique information in there. Very crude, I know, but it worked for me.
Have fun
Francois
_________________
If you do not know the answer or you get the urge to answer with "RTFM" or "Search better in this forum", please refrain from doing so, just move on to the next question. Much appreciated.
Francois van der Merwe |
|
| Back to top |
|
|
| pottas |
| Posted: Mon Jun 30, 2008 2:51 am Post subject: |
|
|
Disciple
Joined: 27 Oct 2005
Posts: 185
Location: South Africa
|
Thanks Francois,
Yes, I figured that I can use an HTTPInput Node, with the XMLNSC parser. The problem with this is that we want to use WS-Adressing and WS-Security and then we will have to go for a Soap Input Node. The other option is to use an HTTPInput node and after that route to a SoapInput Node, but that's also a bit too messy to my liking. |
|
| Back to top |
|
|
| mgk |
| Posted: Mon Jun 30, 2008 7:57 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi.
You are correct in assuming you need multiple SOAPInput nodes in this scenario as the SOAPInput node can only handle one WSDL file at a time. However, there is no reason that you cannot have multiple SOAPInput nodes in the same flow, with a single SOAPReply node servicing all the SOAPInput nodes in that flow.
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| Paul D |
| Posted: Mon Jun 30, 2008 11:54 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
Would the best approach in this situation be to use the URL selector on the SOAP node to help manage your routing to the different WSDL's for the different versions in the same flow? Is it safe to say that the number of SOAP Input nodes you have in a flow won't negatively effect performance. It looks like they all share a common thread listening on 7800, so there's some internal selector that routes a request to the corrrect SOAP Input node given the URL.
Also seems like another approach to versioning is to use different operations and "add on" to the same WSDL for different versions. I'dassume a "minor version" in this case, not a "major one". Major may take a new WSDL.
I would like to hear others comments on this as web services, and versioning interfaces in web services, is new to me.
_________________
Thanks!!!
Paul D |
|
| Back to top |
|
|
| mgk |
| Posted: Mon Jun 30, 2008 12:50 pm Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Hi Paul.
What you say is correct. Minor versions could be handled by new operations in the WSDL if that suits your environment. However, if you do use a new WSDL (so multiple SOAPInput nodes) then you must use the URLSelector is ensure that the inbound message ends up at the correct SOAPInput node. Having multiple SOAPInput nodes in a flow should not unduly affect performance.
Regards.
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| 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
|
|
|
|
