| Author |
Message
|
| amitkan2000 |
 Posted: Mon Jun 13, 2011 1:57 am Post subject: Single WSDL for multiple Webservice Message Flows |
 |
|
Novice
Joined: 22 Feb 2010
Posts: 12
|
Hi,
We have a scenario where there are similar type of web service request needs to be integrated from ASP.net to WBI to IMS. We have created one webservice message flow each for one IMS transaction and created the individual WSDL files.
All the message flows are similar in nature for the sake of simplicity it is like -
| Code: |
| SOAPInput --> Compute --> MQOut --> MQGet --> Compute --> SOAPReply |
We have given all the WSDL files to .net team and they have added these WSDL reference as a local copy of WSDL.
The .net team is not happy with the growing no of WSDL, so here is my question -
1. Can we have a single WSDL files for more than one webservice message flows?
2. If yes then what changes we need to do in the WSDL file?
3. How the specific message flow will be triggered in above scenario?
4. If no, can you suggest any alternative way of design?
| Code: |
Environment --
Broker OS - AIX
Broker Version - 6.1
|
Thanks & Regards,
Amit |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Mon Jun 13, 2011 4:27 am Post subject: Re: Single WSDL for multiple Webservice Message Flows |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| amitkan2000 wrote: |
The .net team is not happy with the growing no of WSDL, so here is my question -
1. Can we have a single WSDL files for more than one webservice message flows?
2. If yes then what changes we need to do in the WSDL file?
3. How the specific message flow will be triggered in above scenario?
4. If no, can you suggest any alternative way of design?
|
Sounds like your .net people are not automating their work. Modular design means clear size and scope of project deliverables are useful so that if some change happens, you don't break other things. If you jam all these functions into one WSDL, and make a small change, you potentially break alot of stuff.
Give your .net people some candy. Help them feel better. Socialize the concept that modular design is good design. Also, introduce your .net friends to Hudson. He is a great butler.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| amitkan2000 |
| Posted: Mon Jun 13, 2011 5:04 am Post subject: |
|
|
Novice
Joined: 22 Feb 2010
Posts: 12
|
Your point is valid and well taken 
But in case we need to have this scenario build, I want to understand how the Message Broker will behave.
1. How can I make a single WSDL for more than one message flows?
2. How this WSDL will be imported by .net?
3. How they will send the request to different Message Flows using the same WSDL?
Can you give some pointers pls?
Thanks & Regards,
Amit |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Mon Jun 13, 2011 5:37 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| amitkan2000 |
| Posted: Mon Jun 13, 2011 11:03 pm Post subject: |
|
|
Novice
Joined: 22 Feb 2010
Posts: 12
|
I have gone through the links what you provided the information that I am seeking is not available there.
What I need to understand -
1. Can we share single WSDL file for more than one message flows?
| Quote: |
Message Flow 1 --- CommonWSDL
Message Flow 2 --- CommonWSDL
Message Flow 3 --- CommonWSDL
|
Now my .net client is created based on this CommonWSDL, now I want to understand
| Quote: |
what changes I need to do, in order to specify the webservice request is for Message Flow 1 or Message Flow 2 or Message Flow 3 from the .net client.
|
Regards,
Amit |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jun 14, 2011 4:34 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
The answers to your inquiry are in InfoCenter and taught in the WMB Developers class. Have you taken the class?
In short, import the one WSDL which creates a message set and on the SOAP input node, select that message set in each of your three Message Flows.
How long ago did you take the WMB Developer's class?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 14, 2011 4:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It doesn't make any sense to share wsdls.
It doesn't make any sense to have a single WSDL reflect multiple logical services, with multiple logical operations on those services.
Your .NET team is making noise about things that they don't understand, or they are asking you to do work that properly belongs in their hands.
Presumably your services are architected and designed based on an overall plan, and part of that overall plan included sufficient discussions on service granularity to ensure that the number of services (each of which is defined by a single WSDL) was correct and well-known.
So if the .NET team says "there are too many wsdls", then either they disagree with the architectural decisions or they are complaining just to get someone to pay attention. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jun 14, 2011 4:53 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
The answers to your inquiry are in InfoCenter and taught in the WMB Developers class. Have you taken the class?
In short, import the one WSDL which creates a message set and on the SOAP input node, select that message set in each of your three Message Flows.
How long ago did you take the WMB Developer's class? |
Training! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| khudania |
| Posted: Tue Jun 14, 2011 7:42 am Post subject: Re: Single WSDL for multiple Webservice Message Flows |
|
|
Apprentice
Joined: 30 Nov 2004
Posts: 43
|
| amitkan2000 wrote: |
Hi,
We have a scenario where there are similar type of web service request needs to be integrated from ASP.net to WBI to IMS. We have created one webservice message flow each for one IMS transaction and created the individual WSDL files.
All the message flows are similar in nature for the sake of simplicity it is like -
| Code: |
| SOAPInput --> Compute --> MQOut --> MQGet --> Compute --> SOAPReply |
We have given all the WSDL files to .net team and they have added these WSDL reference as a local copy of WSDL.
The .net team is not happy with the growing no of WSDL, so here is my question -
1. Can we have a single WSDL files for more than one webservice message flows?
2. If yes then what changes we need to do in the WSDL file?
3. How the specific message flow will be triggered in above scenario?
4. If no, can you suggest any alternative way of design?
| Code: |
Environment --
Broker OS - AIX
Broker Version - 6.1
|
Thanks & Regards,
Amit |
From what I have understood from your question, the answer is quite simple. Use as many port types as you like in one wsdl and make a flow for each of the port types.
| Quote: |
portType, which is a set of abstract operations. Each operation refers to an input message and output messages. |
_________________
If the doors of perception were cleansed, everything would appear as it is - infinite |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 14, 2011 9:00 am Post subject: Re: Single WSDL for multiple Webservice Message Flows |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| khudania wrote: |
From what I have understood from your question, the answer is quite simple. Use as many port types as you like in one wsdl and make a flow for each of the port types.
| Quote: |
portType, which is a set of abstract operations. Each operation refers to an input message and output messages. |
|
I'm not sure it makes sense to create a single wsdl that has different port types for logically different services.
You are then moving the identification of the service from the URL into the port. |
|
| Back to top |
|
|
| khudania |
| Posted: Wed Jun 15, 2011 12:41 am Post subject: Re: Single WSDL for multiple Webservice Message Flows |
|
|
Apprentice
Joined: 30 Nov 2004
Posts: 43
|
| mqjeff wrote: |
| khudania wrote: |
From what I have understood from your question, the answer is quite simple. Use as many port types as you like in one wsdl and make a flow for each of the port types.
| Quote: |
portType, which is a set of abstract operations. Each operation refers to an input message and output messages. |
|
I'm not sure it makes sense to create a single wsdl that has different port types for logically different services.
You are then moving the identification of the service from the URL into the port. |
amitkan2000 and his client wants to use only a single wsdl.
_________________
If the doors of perception were cleansed, everything would appear as it is - infinite |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 15, 2011 2:21 am Post subject: Re: Single WSDL for multiple Webservice Message Flows |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| khudania wrote: |
| mqjeff wrote: |
| khudania wrote: |
From what I have understood from your question, the answer is quite simple. Use as many port types as you like in one wsdl and make a flow for each of the port types.
| Quote: |
portType, which is a set of abstract operations. Each operation refers to an input message and output messages. |
|
I'm not sure it makes sense to create a single wsdl that has different port types for logically different services.
You are then moving the identification of the service from the URL into the port. |
amitkan2000 and his client wants to use only a single wsdl. |
one of the development teams at amitkan2000's client want to use a single wsdl.
Whether or not it should be done is a different question. It's akin to saying "we only one to set up a single email mailbox, then give everyone access to it and have them sort out the email by the subject line".
Possible, yes, makes sense, not really. |
|
| Back to top |
|
|
| amitkan2000 |
| Posted: Wed Jun 15, 2011 9:12 pm Post subject: |
|
|
Novice
Joined: 22 Feb 2010
Posts: 12
|
Thanks Khudania and all, I am with you guys on that there is no sense to build the single wsdl, and this we have implementes by having individual wsdl for each message flow services.
But as khudania and mqjeff mentioned I was looking at a possible solution.
I will work on the solution given by khudania and soon post the result. |
|
| Back to top |
|
|
|
|
