It will help understanding the concept of finding applications automatically because it is simply uses a supply chain example. Pleas take a look.
IBM Dynamic process is a suite contains a set of collaborative, role-based capabilities that enable customers to model, simulate, execute, rapidly change, monitor and optimize core business processes. Any business Function needs an interface. Interfaces are defined using WSDL. If you take a look at UDDI technology, a provider usually publish its WSDL in the UDDI registry. The convention for publishing WSDL-based web services in a UDDI registry can make UDDI effective for doing dynamic discovery of web services at runtime. There have been attempts to define specifications for web services discovery. WS-Inspection and WS-ServiceGroup. IBM is a key player behind all web services standards and its implementation. All the best Ashraf Galal On Wed, Dec 3, 2008 at 3:48 PM, Michael Poulin <[EMAIL PROTECTED]> wrote: > I am not sure how WS-I Basic Profile helps in finding applications in > the Net but recent release of IBM's Dynamic Process Edition certainly does. > The process' actions specify only required business functionality (not the > WSDL) and the Edition looks-up in the Service Registry/Repository for > particular service meeting the requirements, on the fly. > > Actually, this is the same way, at last, that CORBA Trading Object Service > used 11 years ago. The UDDI's solution for this task was quite bad from the > very beginning. > > - Michael > > ------------------------------ > *From:* A W <[EMAIL PROTECTED]> > *To:* [email protected] > *Sent:* Wednesday, December 3, 2008 7:32:57 PM > *Subject:* Re: [service-orientated-architecture] Gartner note on WOA > (Web-Oriented Architecture) just published > > This is common on different application such supply chain magenta. > Please visit the WS-I profile for More details > > All the best > Ashraf Galal > > On Fri, Nov 28, 2008 at 12:35 PM, Nick Gall <[EMAIL PROTECTED] com<[EMAIL > PROTECTED]> > > wrote: > >> On Wed, Nov 26, 2008 at 4:12 PM, A W <[EMAIL PROTECTED] com<[EMAIL >> PROTECTED]>> >> wrote: >> > It is great but how an application can find another application in the >> Net >> > without having a WADL (the equivalent for WSDL in WS-*)? >> >> I've never seen an application (X) find and use another application (Y) >> that X didn't already know about. I know that UDDI originally offered this >> vision of a "yellow pages" where one app could "discover" a service and its >> associated service provider by some category scheme, then "discover" how the >> service's API worked by analyzing its WSDL, then "negotiate" with the >> service provider to use the API -- all completely automatically. >> >> It never came close to happening. So perhaps if you could provide a bit >> more detail about, and an example or two of successful implementations of, >> this concept of "how an application can find another application in the >> Net", then I could describe ways in which it can be accomplished with WOA. >> >> -- Nick >> >> > > >
