Downloaded 530 times
![Web Service Client Example
package com.soapwebtest.service;
import java.rmi.RemoteException;
import java.util.Arrays;
import java.util.List;
public class OTPClient {
public static void main(String[] args) throws RemoteException {
OTPGenerator service = new OTPGeneratorProxy();
List<Subscriber> ll = Arrays.asList(service.getAllSubscriber());
for (Subscriber subscriber : ll) {
System.out.println(subscriber.getEmail());
}
}
}](/proxy?url=https%3A%2F%2Fimage.slidesharecdn.com%2Fwebservices-140608115513-phpapp01%2F75%2FWeb-services-A-Practical-Approach-30-2048.jpg)
Uploaded byMadhaiyan Muthu
Web services - A Practical Approach
The document explains web services, highlighting their role in enabling machine-to-machine interaction over the internet using protocols like SOAP and REST. It covers the definitions, terminologies, and technologies involved, including WSDL for describing web services and UDDI as a directory service. The content also provides examples of implementing web services, such as an OTP service for authentication, along with architecture and client development using Java.
In this document
Powered by AI
Introduction to web services, definition by W3C, and examples including Facebook and e-commerce platforms.
Use case presented with multiple application servers interacting through methods like bookTicket() and cancelTicket().
Interface design criteria emphasizing platform independence, and natural language request/response.
Explanation of SOAP, WSDL, UDDI, REST, and HTTP including their roles and importance in web services.
Comparison between SOAP and REST web services, highlighting differences in architecture, communication methods, and data formats.
Visual comparison of SOAP and REST service data handling and communication characteristics.
Overview of service flow in web applications involving WSDL and HTTP communication protocols.
Disadvantages including difficulty in consuming SOAP services and issues with security and UI changes.
Illustration of improved web service flow with centralized control and security through OAUTH.
Benefits of actual flow including centralized control, authorized access, and no UI change requirements.
Examples of practical web services like GeoIP and OTP services.
OTP generation service details, usage scenarios, and functionalities like validation.
Overview of an application architecture integrating web services for healthcare portal functionalities.
List of needed software and technologies for developing web services including Java and PostgreSQL.
Code snippet for OTP generator web service, showcasing methods for generating and validating OTP.
Presentation on how WSDL provides a structured interface for web services.
Java interface example for web service highlighting input and output methods.
High-level WSDL components including definitions, types, messages, and operations.
Explanation of namespace uniqueness and data types used in web service communication.
Brief discussion on XML Schema Definition (XSD) used in web services.
Details about SOAP binding styles, including document and RPC styles.
Explanations of document style binding characteristics and implications.
Differences between RPC binding and document style in web services.
Discussion of service structure including services, ports, and operation messages.
Description of the overall WSDL structure used for web services.
Role of web service clients and differences among various client types.
Steps to create a Java client using wsimport and Eclipse IDE based on WSDL.
Java client code example for consuming OTP service and retrieving subscriber information.
Final overview of complete application architecture integrating web services.
Technology stack for developing a web application with SOAP client integration.
Overview of how Tomcat serves web applications with request and response handling.
Key servlet concepts including HttpRequest, HttpResponse, HttpSession, and more.
Explanation of serialization and its importance in web services.
Illustrative example of serialization process in client-server communication.
Practical example demonstrating serialization in a web service scenario.
Course outline covering topics related to web services, Java, WSDL, SOAP, and more.
Open floor for questions and discussions following the presentation.
Closing remarks and gratitude for participation.
More Related Content
Similar to Web services - A Practical Approach
![Web services and SOA [Modified]](/proxy?url=https%3A%2F%2Fcdn.slidesharecdn.com%2Fss_thumbnails%2Fwebservicesandsoa-100901124018-phpapp01-thumbnail.jpg%3Fwidth%3D640%26height%3D640%26fit%3Dbounds)
Web services - A Practical Approach
- 2. What is WebService? • Services are available in the Web. • Communication between the two system over network. • Software system designed to support interoperable machine-machine interaction over the network (w3c definition). • Real-time Example: – Facebook, Google, Twitter, e-commerce sites, and irctc.
- 3. Simple Use case ApplicationServer-1 bookTicket() IRCTC- Ticket Service DB Dealer site1 (makemytrip.com) Struts Application Server-2 Dealer site2 (cleartrip.com) .NET/RUBY Application Server-3 cancelTicket() Interface
- 4. Criteria for interfaceand request/response • Interface should be platform independent. So what is the format? And why? • Request and response should be language natural. So what is the format? And why?
- 5. Web Service Terminologies •SOAP – Simple Object Access Protocol. – Envelope for soap request/response. • WSDL – Web Service Description Language. – Interface for SOAP web service • UDDI – Universal Description, Discovery and Integration. – Repository/yellow pages of web services • REST – REpresentational State Transfer. – Architecture style of communication to the services • HTTP – Hypertext Transfer Protocol. – Stateless protocol and used for transport
- 6. Different Types ofWeb Services SOAP REST JAX-WS standard JAX-RS standard Required WSDL interface for expos as web service No Interface. It uses HTTP methods (GET,POST,PUT,DELETE) XML should be communication medium for request and response Both XML and JSON used for request and response. Maintain session state Stateless (fire and forget) It uses SOAP protocol to transfer data over HTTP Uses only HTTP Not human readable Human readable Client – server communication heavy weight like BLOB Simple client-server communication and light weight.
- 7. SOAP vs REST ClientServerData SOAP Standard Huge Data+ = <=> SOAP Client ServerData <=> Sending data as its REST *REST are mostly used in industry
- 8. Web service Flow-I HTTP HTTP WebBrowser Mobile WSDL SOAP REST DB Web services Application Server Not Applicable for Real time and it FALSE one for SOAP.
- 9. Disadvantage of flow-I •Consuming SOAP services from Java Scripts is tedious and time consuming task. • Some browser will not support build in Jquery functions for SOAP.(Browser compatibility) • Security validation is needed for every service. Because anybody can access any service. • No centralized controlled. • UI change to be needed for every Web service enhancements like URL for version update.
- 10. Web service Flow-II(Actual) Web Browser Mobile (Toolkit) Java Web service Client DB WSDL SOAP REST DB Web Server/application server Web/Servlet application Web services Application Server HTTP HTTP Client for Web service Client for Web App
- 11. Advantage of Flow-II •Centralized control. • Only authorized users/vendors can consume web services. • No UI changes needed. • Can use OAUTH/APIGEE for security. • Standard industry model
- 12. Examples • GeoIP service –http://www.webservicex.net/ws/WSDetails.aspx? WSID=64&CATID=12 • One Time Password(OTP) service – Our own service
- 13. Web Service -OTP • OTP(One-Time-Password) Generator. – This web service will generate OTP for authentication for more security. – Used in banking site, e-commerce site for every transactions. • Functionality – Generate OTP and send to mail. – Validate OTP. – Get registered user. – Get all registered users.
- 14. Complete Application architecture (HealthCarePortal) Generate OTP Validate Get All Subscriber Get Subscriber DB WSDL SMTP Mail Server (GMAIL) Application Server (Glassfish) Java .Net Ruby Web Server (Tomcat) Servlets End User SOAP Client JDBC ORM (Hibernate)
- 15. Setup environments • Requiredsoftware – JDK 1.6 – IDE (Eclipse/NetBeans) – Application server (GlassFish) – Mail API – Database (postgresql DB) • Technology used – Java – XML – JDBC
- 16. Service Development package com.soapwebtest.service; importjava.util.List; import java.util.Random; import javax.jws.WebMethod; import javax.jws.WebService; import com.soapwebtest.service.model.Subscriber; @WebService public class OTPGenerator { @WebMethod public boolean generateOtp(String email) { return false; } public boolean validate(String mail, String otp) { return false; } public Subscriber getSubscriber(String mail) { return subscriber. } public List<Subscriber> getAllSubscriber() { return List<Subscriber> } }
- 17. OTP service –WSDL interface
- 18. Compare WSDL withjava Interface package com.testapp.webservice //package name Public interface Calculatore{ //interface name int add(int a, int b); // method name, input and output parameters int multiply(int a, int b); Math add (Math math); //Object }
- 19. WSDL high levelelements -<definition> +<types> //input and output types reference +<message> // inputs and outputs (one for input and one for output) -<portType> -<operation> //method name of webservice <input> // all input and output are message (one for input and one for output) <output> </operation> +<binding> //information about how webservices accepts its input and output via http (literal via http) +<service> //list of ports and each port has address location. port consist of operations -</definition>
- 20. Name Space andtypes • Name space represent the package name of service. • Name space should be unique. • Types represents what kind of data type to passed to service input and output over HTTP. • Types will be applicable only for document style binding. Not for RPC.
- 21.
- 22. SOAP binding style JAX-RPCDocument no XSD XSD document as an input and output easy to read complex to read no validation validates inputs (ex : minoccurs) Note: Document style binding is default SOAP binding represents what kind of communication and data passed to request and response for the service.
- 23.
- 24.
- 25. Service, portType andmessage • Service consist of ports and each port will have address location URL. • portType has operations of service which exposed on the particular port. • Each operation has input/output which represent as messages.
- 26.
- 27.
- 28. Web service client •One who consume web service is called web service client. • Client needs only WSDL interface. • Different Types of Clients: – Java – .Net – Ruby – Python
- 29. Steps to createjava client • Use wsimport – Wsimport –keep –s <src> <wsdl> • Use Eclipse-IDE – Create java project. – Create Web service client. – Specify the WSDL and Validate. – Generate required classes using Axis.
- 30. Web Service ClientExample package com.soapwebtest.service; import java.rmi.RemoteException; import java.util.Arrays; import java.util.List; public class OTPClient { public static void main(String[] args) throws RemoteException { OTPGenerator service = new OTPGeneratorProxy(); List<Subscriber> ll = Arrays.asList(service.getAllSubscriber()); for (Subscriber subscriber : ll) { System.out.println(subscriber.getEmail()); } } }
- 31. Complete Application architecture (HealthCarePortal) Generate OTP Validate Get All Subscriber Get Subscriber DB WSDL Mail Server (GMAIL) Application Server (Glassfish) Java .NET Ruby Web Server (Tomcat) Servlets End User SOAP Client JDBC ORM (Hibernate)
- 32. Developing Web Applicationand Integrate SOAP Client • Required Software: – Hibernate – Postgresql(Database) – Tomcat (web server) – SOAP Client • Technology – HTML – JSP – Servlets – Java – XML (web.xml)
- 33. Tomcat Web Server Browser Tomcat Request Response WebApplication Web Application Web Application Login Servlet Web.xml / annotation
- 34. Servlet Terminologies • Http-Stateless protocol • HttpRequest – scope will be only on request • HttpResponse- scope will be only on response • HttpSession – scope on particular browser/user • ServletConfig- Scope on particular servlet • ServletContext – Scope for all servlet and every browser/user.
- 35. Serialization • Process ofstoring object state for streaming called serialization. • Every java class should implements serializable interface • What is object state? • Why should we store object state?
- 36.
- 37.
- 38. Syllabus • Web Services:JAX-RPC-Concepts-Writing a Java Web Service-Writing a Java Web Service Client-Describing Web Services: WSDL- Representing Data Types: XML Schema- communicating Object Data: SOAP Related Technologies-Software Installation-Storing Java Objects as Files-Databases and Java Servlets.
- 39.
- 40.