| Author |
Message
|
| broker_new |
 Posted: Wed Jan 13, 2010 9:47 pm Post subject: WMBv6.1->WebService with Multiple operations |
 |
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
Hi Guys,
Have a question on web services.
I have developed a message flow to receive multiple message types, as a result i have defined multiple soapActions for each type and based on the soapAction i route the request to that particular label node and process it.
My question is if there is a change in one particular operation we have to deploy the whole message flow? is there a way to deploy only the modified operation?  |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Thu Jan 14, 2010 12:10 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
So you have developed a huge monolithic flow that handles all sorts of things.
A flow is a complete entity so YES you are going to have to deploy the whole flow again.
This is (IMHO), where the role of the designer comes in. Do you go for your solution or one where there is much more granularity in your flow designs even though there might be a lot of code overlap (via shared projects naturally).
Personally, I'd go for the latter solution.
Develop lots of small bits and use where appropriate.
However you do need to document the dependency tree very well but I think this is a small price to pay for overall development speed and maintainability.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| broker_new |
| Posted: Thu Jan 14, 2010 8:43 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
that is confirmed (deployment of whole flow again), so we have to develop a separate message flow for each operation by keeping things in consideration, any negative impacts as a result of this?  |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 14, 2010 9:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| broker_new wrote: |
| so we have to develop a separate message flow for each operation by keeping things in consideration, any negative impacts as a result of this? |
Probably too many flows to administer successfully IMHO!
As the previous poster said, it's a design question. I agree you don't want one monolithic flow for reasons you've probably discovered (hence your original post) but I doubt you want a 1-1 correlation with operation to flow. You need to strike a balance, and where that balance is will depend heavily on what you're doing and how you're doing it.
For instance, if you have automated deployment processes linked to a source code control system you can probably manage more flows than if you're doing it manually.
Another for instance, you may have written a single flow to get maximum code reuse and breaking the flow will impact this. You'll need to decide where the logical breaks are and if they can be mitigated with common code, sub flows, etc, etc, etc.
These are given simply as examples, there are other considerations, other design straegies and this is my 2 cents.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jan 14, 2010 9:54 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You will need a main flow that handles the WSDL and all of it's operations, and then to dispatch handling of those operations to secondary flows.
Then you can change the secondary flow, and the main flow only changes when the WSDL changes.
You can't configure the SOAP listener to route to different flows based on the operation, just on the URL - at least AFAIK. |
|
| Back to top |
|
|
| broker_new |
| Posted: Thu Jan 14, 2010 10:18 am Post subject: |
|
|
Yatiri
Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
|
| Quote: |
| You will need a main flow that handles the WSDL and all of it's operations, and then to dispatch handling of those operations to secondary flows. |
Interesting....What's the secondary flow..you mean expose the Primary flow as HTTP/SOAP and pass it to MQ and maintain the correlation using the HTTP Request Identifier?....would you please explain how you would design the secondary flow ? |
|
| Back to top |
|
|
|
|
