Web services allow different applications from different sources to communicate using common standards like XML, SOAP, WSDL and UDDI. They enable interoperability between distributed applications across diverse hardware and software. Web services use a common data model (XML) and can access applications through firewalls using web protocols. There are different styles of using web services including RPC, SOA and REST. OrangeScape's web services platform makes it easy to both expose and consume web services.

1. WEB SERVICESOrangeScapeTechnologiesWrite Once, Cloud Anywhere.

2. Ordering at a restaurant

3. What is Web Service?Application Programming Interfaces (API)Allows different application from different sources to communicateIntegration of Web application include standards: XML - Extensible Markup Language SOAP - Simple Object Access Protocol WSDL - Web Services Description Language UDDI - Universal Discovery Description and Integration

4. Why Web Service?Interoperability among distributed applications – diverse hardware & softwareAccessibility of applications through firewalls using Web protocolsCross-platform, cross-language data model (XML)

5. Calling a Web service diagram

6. Web services framework

7. UDDIUDDI defines the operation of a service registry:Data structures for registering SOAP Access API Rules for the operation of a global registrybusinessEntitybusinessEntitybusinessEntityRosetta-NetbusinessServicebusinessServiceBASDASimple.BuySchemas,Interchange specificationbindingTemplatebindingTemplateInstanceDetailsInstanceDetailscategoryBagSIC CODENAICSkeyedReferencekeyedReferenceidentifierBagDUNS NumberskeyedReferencekeyedReferenceThomas Registry IDWeb Service

8. WSDLProvides functional description of network services: IDL descriptionProtocol and deployment detailsPlatform independent description. Extensible language.Used in combination of XML & SOAPServicePort(e.g. http://host/svc)PortBinding(e.g. SOAP)BindingportTypeoperation(s)ageinMesoutMessage

9. Structure of WSDL<definitions><types> definition of types........</types><message> definition of a message....</message><portType> definition of a port.......</portType><binding> definition of a binding....</binding></definitions>

10. SOAPRelies on XML for messagingMessaging framework:SOAP processing model SOAP extensibility mode SOAP underlying protocol binding SOAP message construct

11. SOAP format<SOAP-ENV:Envelopexmlns="http://schemas.xmlsoap.org/soap/envelope/"> < SOAP-ENV:Header> ... </ SOAP-ENV:Header> < SOAP-ENV:Body> ... </ SOAP-ENV:Body> ...</ SOAP-ENV: Envelope>

12. Architecture

13. Style of use

14. RPC“Remote Procedure Call”First web service toolsBasic unit- WSDLTightly coupled

15. SOA“Service Oriented Architecture”Basic unit of communication is message“Message-oriented” serviceLoosely coupled

16. REST“Representational State Transfer”Constrains interface to a set of well know operationsDescribed in context of HTTP

17. Web service , Mashups and API’sMashups is any web feature that builds on services provided by other sites.API contains classes and Interfaces just like a program.A web service is a form of API (Application Programming Interface). Embedding a URL to google maps, a webservice? a mashup? Or a API ?

18. Web Services in OrangeScape 3.0

19. Style of Use - SOAPExpose a serviceEasy generation of WSDL.Default services.User defined services.Consume a ServiceEasy to configure.

20. Consuming a Web Service

21. Style of use – REST ( Representational State Transfer) URL with HTTP methods( PUT,POST,GET & DELETE ).Data is passed using query string.

22. ConclusionThe Web services framework is being defined, standardized and supported by the industry at a record pace.Broad industry acceptance and standard compliance will make it ubiquitous.Will bring an unprecedented level of interoperability to Web applications.Integration with any application is now very easy with OrangeScape’s web services.The benefits of Web services, however, are not limited to the Web!

23. Questions…..

24. Thank you…