ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Process Server (WID/WPS/WAS+) » WSDL Interface with multiple operations ?

Post new topic  Reply to topic
 WSDL Interface with multiple operations ? « View previous topic :: View next topic » 
Author Message
venky
PostPosted: Tue Jul 26, 2011 2:39 pm    Post subject: WSDL Interface with multiple operations ? Reply with quote

Master

Joined: 08 Jul 2003
Posts: 205

Hi All,

We have 4 different business processes that we will be developing and each has its own functionality.

The question I have is - is it a best practice to have one big WSDL interface with 4 operations in it and implement the respective operation in the 4 different business processes ?

in this case we will have 1 URL that can be exposed to the calling applications.

(or)

Have separate WSDL interfaces (4 different interfaces) one for each operation and implement the 4 business processes ?

In this case we will have 4 separate URLs.

Which one of the above is a best practice ?

Please Advice.

Thanks,
Balaji Subbru.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Jul 27, 2011 4:31 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

The best practice is to make one WSDL for each logically connected set of operations.

So if one of your operations is something like "Add Item to shopping cart", and two of them are things like "Change address" and "Change name", and one of them is "track shipment", then that's three WSDLs.

But if they're all operations for the same kind of task, it's one WSDL and one business process.
Back to top
View user's profile Send private message
venky
PostPosted: Wed Jul 27, 2011 10:41 am    Post subject: Reply with quote

Master

Joined: 08 Jul 2003
Posts: 205

Thanks, Jeff.

Is there a technical/logical justification as to why using one WSDL for each logically connected operations is the best practice.?

I know using one WSDL for all operations is possible technically, but also, I understand that is not a good practice. I am trying to come up with a reason/justification as to why 'one WSDL for each logically connected operations' is the best practice.

V.
Back to top
View user's profile Send private message
mqjeff
PostPosted: Wed Jul 27, 2011 11:06 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

venky wrote:
Is there a technical/logical justification as to why using one WSDL for each logically connected operations is the best practice.?


Because that's what the word "service" means - a set of logically connected operations.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Process Server (WID/WPS/WAS+) » WSDL Interface with multiple operations ?
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.