Group Members:-

Gurdeep Kansal(071265)
Raman Kumar(071313)

Project Guide:-
 Mr. Yashwant Singh
 Group No. 47
Overview
 Web services involve many technologies:
 WSDL to learn about web service
 to call: proxy objects, SOAP, XML, HTTP and .ASMX pages

web service

WSDL
client app obj
obj

method call obj

method call

.asmx
proxy
Web server
SOAP msg (XML)

HTTP request
 Web Services Basics
 Web services are applications, available over the
Internet, that provide some kind of service, either
programmatic or informative, to other applications.
Web services differ from Web applications in that they
generally involve application-to-application
communication, and are not intended to be accessed
via a Web browser
Example
 Google

 A great search engine

 www.google.com
 but what if I want my own GUI?
 Google web service
 Google offers a web service that performs searches for
you
 Why?
 clients can build custom GUIs
 google.com can make money!

// ask google to search for us...

google = new GoogleSearchService();
result = google.doGoogleSearch("4a8/TvZQFHID0WIWnL1CMmMx0sNqhG8H",
txtSearch.Text, 0, 10, false, "", false, "", "", "");

// display resulting URLs...

foreach (ResultElement re in result.resultElements)
lstURLs.Items.Add(re.URL);
Web Services Discovery
Challenges
 Who provides Web services?
 How are they implemented?
 Where are they exposed?
 What are they for?
 What is their behavior?
 How do I incorporate run-time interaction?
 How do I publish my Web service?

6
 Underlying Standards
 XML - Extensible Markup Language
 SOAP – exchanging XML messages on a network
 WSDL – describing interfaces of Web services
 UDDI – managing registries of Web services

--By following these standards services can dynamically

interact with one another
 Web services with SOAP
 “Simple Object Access Protocol”
 Actually used to communicate with the Web Service
 Both the request and the response are SOAP messages
 The body of the message (whose grammar is defined
by the WSDL) is contained within a SOAP “envelope”
 “Binds” the client to the web service
Simple structure of web services

Application 1 Application 2

XML

To picture this we have two applications communicating over the internet using an
agreed message format – encoded as XML.
Working with web services
 Two steps:

1. build a web service

2. build clients to use it
Building a web service
 Start by creating a project of type “ASP.NET Web
Service”
A web service is…
 One or more objects that respond to web-based
method calls
 there is no GUI design to a web service
public class
 only raw Service1
classes : System.Web.Services.WebService
with methods…
{
.
.
.
}
Building a client
 Start by creating a client…
 WinForm, WebForm, console-based, anything you
want!
 for fun, let's use VB…
Reference the component
How?

 project references, right-click, Add web reference…

 type URL for web service, e.g.

 http://localhost/WebService/Service1.asmx

web service class

server name name
Front page of website
Administrator Page
Admin creates packages
Admin Manages Flights
Customer can take HOLIDAY PACKAGES
Payments by a Customer
Payment options
references
 Our Project Guide – Mr. Yashwant singh
 Web Services: Concepts, Architecture and
 Applications
 G. Alonso, F. Casati, H. Kuno, V. Machiraju
 Springer Verlag 2004
 Anders Møller & Michael I. Schwartzbach
© 2006 Addison-Wesley
 Addison Wesley
 Web Services- Markus Mitterer | Mathias Willburger