1. WEB SERVICES OrangeScapeTechnologies Write Once, Cloud Anywhere.

2. Ordering at a restaurant

3. What is Web Service? Application Programming Interfaces (API) Allows different application from different sources to communicate Integration 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 & software Accessibility of applications through firewalls using Web protocols Cross-platform, cross-language data model (XML)

5. Calling a Web service diagram

6. Web services framework

7. UDDI UDDI defines the operation of a service registry: Data structures for registering SOAP Access API Rules for the operation of a global registry businessEntity businessEntity businessEntity Rosetta-Net businessService businessService BASDA Simple.Buy Schemas, Interchange specification bindingTemplate bindingTemplate InstanceDetails InstanceDetails categoryBag SIC CODE NAICS keyedReference keyedReference identifierBag DUNS Numbers keyedReference keyedReference Thomas Registry ID Web Service

8. WSDL Provides functional description of network services: IDL description Protocol and deployment details Platform independent description. Extensible language. Used in combination of XML & SOAP Service Port (e.g. http://host/svc) Port Binding (e.g. SOAP) Binding portType operation(s) ageinMes outMessage

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. SOAP Relies on XML for messaging Messaging framework: SOAP processing model SOAP extensibility mode SOAP underlying protocol binding SOAP message construct

11. SOAP format <SOAP-ENV:Envelope xmlns="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 tools Basic unit- WSDL Tightly coupled

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

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

17. Web service , Mashups and API’s Mashups 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 - SOAP Expose a service Easy generation of WSDL. Default services. User defined services. Consume a Service Easy 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. Conclusion The 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…