Web service implementation
Download as PPTX, PDF1 like216 views
The document discusses web service implementation. It begins by introducing web services and their key components: SOAP, WSDL, and UDDI. It then summarizes the web service implementation lifecycle, which involves requirements, analysis, design, coding, testing, and deployment phases. The document also discusses why businesses need web services to facilitate interoperability and integration between different applications and platforms. It concludes by outlining a web service implementation methodology that takes an iterative, incremental approach through each phase of the lifecycle.
Web service implementation
- 2. Hello!Good Morning all of You… Today we are here because today we are going to give a presentation on Web Service implementation
- 4. Today, companies rely on thousands of different software applications each with their own role to play in running a business. These different software applications run on a wide range of different platforms and operating systems, and they are implemented in different programming languages. As a result, it is very difficult for different applications to communicate with one another and share their resources in a coordinated way. “Web services are open standard (XML, SOAP, HTTP etc.) based Web applications that interact with other web applications for the purpose of exchanging data”. Web Services can convert your existing applications into Web-applications
- 5. • Web services are application components • Web services communicate using open protocols • Web services are self-contained and self-describing • Web services can be used by other applications • XML is the basis for Web services What are Web Services? Web Services, unlike traditional client/server systems, such as browser/Web server systems, are not meant for direct end-user consumption. Rather, Web Services are pieces of business logic, which have programmatic interfaces and it is through these interfaces that developers can create new application systems.
- 6. To summarize, a complete web service is, therefore, any service that: • Is available over the Internet or private (intranet) networks • Uses a standardized XML messaging system • Is not tied to any one operating system or programming language • Is self-describing via a common XML grammar • Is discoverable via a simple find mechanism • The basic Web services platform is XML + HTTP. • The HTTP protocol is the most used Internet protocol. • XML provides a language which can be used between different platforms and programming languages and still express complex messages and functions.
- 8. The basic web services platform is XML + HTTP. All the standard web services work using the following components ◇SOAP (Simple Object Access Protocol) ◇UDDI (Universal Description, Discovery and Integration) ◇WSDL (Web Services Description Language)
- 9. What is SOAP? • SOAP stands for Simple Object Access Protocol • SOAP is for communication protocol between applications • SOAP is a format for sending messages • SOAP is designed to communicate via Internet • SOAP is platform & language independent • SOAP is based on XML • SOAP is simple and extensible
- 10. What is WSDL? WSDL is an XML-based language for describing Web services and how to access them. • WSDL stands for Web Services Description Language • WSDL is written in XML • WSDL is an XML document • WSDL is used to describe Web services • WSDL is also used to locate Web services
- 11. What is UDDI? UDDI is an XML-based standard for describing, publishing, and finding web services. • UDDI stands for Universal Description, Discovery, and Integration • UDDI is a specification for a distributed registry of web services. • UDDI is a platform-independent, open framework. • UDDI uses Web Service Definition Language(WSDL) to describe interfaces to web services.
- 13. Test Phase Coding Phase Design Phase Requirement Phase Analysis Phase Deployment Phase
- 14. The Web Service Implementation Lifecycle describes the phases a typical Web Service would undergo, from the identification of the need of the Web Service to the final deployment and usage by the end-users. The phases identified to be relevant in the Web Service Implementation Lifecycle are: requirements, analysis, design, code, test and deployment. In each of these phases, Web Service specific activities are carried out. These activities, as well as the roles and responsibilities, and the artifacts will be elaborated in the subsequent sub-sections.
- 15. Why need Web Services?4
- 16. Interoperability has highest priority When all major platforms could access the Web using Web browsers, different platforms could interact. For these platforms to work together, Web applications were developed. Web applications are simple applications run on the web. These are built around the Web browser standards and can mostly be used by any browser on any platform. Web services take Web applications to the next level. Using Web services your application can publish its function or message to the rest of the world. Web services uses XML to code and decode your data and SOAP to transport it using open protocols. Connect existing software Web services help solve the interoperability problem by giving different applications a way to link their data. Using Web services you can exchange data between different applications and different platforms.
- 19. • The motivation behind Web Services is to facilitate businesses to interact and integrate with other businesses and clients, without having to go through lengthy integration design and/or to expose its confidential internal application details unnecessarily. • This is made possible by leveraging on the non-platform dependent and non-programming language dependent XML to describe the data to be exchanged between businesses or between the business and its clients. • The Web Service Implementation Methodology is iterative and incremental. • In each iteration, the Web Service would go through all the phases (i.e. requirements, analysis, design, code, testing and finally deployment), thereby developing and refining the Web Services throughout the project lifecycle.
- 20. • The Web Service Implementation Methodology that we define is to promote a systematic approach to Web Service development. • Rather than defining a new software development methodology and expecting software practitioners to forget their own familiar and established methodology to re-learn another, the better alternative is to leverage on what is already available and customize that methodology to incorporate the specifics of Web Services