The document provides an overview of web service implementation using ASP.NET. It defines web services as software components that can be published, located, and run over the Internet using XML. The key points covered include: how web services work by allowing client applications to request and use classes and methods hosted on a web server; the technologies that power web services including the web, XML, and service-oriented architecture (SOA); how to create a basic web service in ASP.NET and test it using a client application.

1. Web Service Implementation
Using ASP.NET
T.Ponraj ,
Research Assistant,
Pondicherry University,
Puducherry.

2. Web services
 Definition:
 Software components that can be published,
located, and run over the Internet using
Extensible Markup Language (XML).
 A web service is a software application that
works over the internet.
 A web service is service-oriented application that
communicates over the web using messages
 We can test the web service by using the local
web server.

3. Working of web service
The web service is also a software, with its own class
and methods .
 A request by the client application constitutes
construction and sending a SOAP request using HTTP to
the web server.
 For a web service to work, the computer has to be
connected to the internet.
 The web server hosts the class and its methods of a web
service, for a client computer to request and use.
 Any client computer located any where in the world, with
an internet connection can request and use the class and
its methods of the web service.

4. Web Service technologies
A web service is service-oriented
application that communicates over the web
using messages.
 The Web
 XML
 SOA

5. 1 . The Web
 A Web service is a Web resource. It
communicates over the internet using standard
Web protocols. Leveraging the Web yields
universal connectivity and pervasiveness.
 A web service is also hosted on a web server.
We can access a web service programmatically,
only programmatically and not by a browser.

6. 2 . XML
 XML is a language for electronic documents and
messages. It provides a universal, self-describing data
format that can be interpreted, processed, and
transformed by any application running on any platform.
 Each bit of information in a document is defined by tags
without overload of formatting present in HTML.
 This type of representation is suitable for application to
application communication.

7. 3 . SOA
 SOA stands for service-oriented architecture.
 SOA is a concept and describes a set of well-
established patterns.
 Each pattern represents a mechanism to describe a
service, to advertise and discover a service, and to
communicate with a service.
 Web services rely on these patterns and client
applications connect to a service using these patterns.

8. 3.1.Basic Roles
 Service provider :-
Who develops or supplies the service.
 Service consumer :-
Who uses the service.
 Service broker :-
Facilitates the advertising and discovery process.

9. 3.2.Operation
 Register :-
The service provider registers the service with a
service broker.
 Find :-
The service broker gives the service consumer
directions on how to find the service and its service
contract .
 Bind :-
The service consumer uses the contract to bind the
client to the service, at which point the client and service
can communicate.

10. 3.3 . Standard
 WSDL :-
WSDL provides a mechanism to describe a Web
service.
 UDDI :-
UDDI provides a mechanism to advertise and
discover a Web service.
 SOAP:-
SOAP provides a mechanism for clients and
services to communicate.

11. 3.3.3.SOAP
Simple Object Access Protocol (SOAP) is an XML
protocol. It is used by client applications to communicate
with Web services.
SOAP implements an envelope for sending an XML
message. We put an XML message into an envelope
and send it across the networks.
A SOAP envelope is transported by various
communication protocols. But, the most common way to
transfer SOAP messages is to use HTTP. Other Web
protocols commonly used are SMTP and FTP.

12. SOAP Message
A SOAP message consists of two parts.
 SOAP header :-
It includes system level
information.
 SOAP body :-
It contains the message
the information that is
being sent.

13. Functional SOA
FIND

14. Reason for why we use Web Services
 Web Services operate on a service-based model
architecture .
 Web Services allow us to communicate among all
different entities without affecting their existence.
 It is written separately from the application logic.
 They improve the information flow between applications.
 web services use text based protocol that all
applications can understand.
 Web services reduce licensing costs.
 They do not rely on special protocols.

15. Case Study

16. Create a Web Service

17. Service.cs

18. Service.asmx

19. Web service Test #1

20. Web service Test #2

21. Web service Test #3

22. Web service Test #4

23. Add Web Reference

24. Select web Service

25. Link to Service

26. Add localhost to client application

27. After additing to solution Explorer

28. Create Client Application

29. Join.aspx

30. Join.aspx.cs

31. Output # 1

32. Output # 2

33. References
 http://www.dotnetissues.com/search/label/ASP.NET%20
WebService
 http://msdn.microsoft.com/en-us/library/ba0z6a33.aspx
 http://www.codeproject.com/KB/webservices/
 http://www.vkinfotek.com/webservice/whycreatewebservi
ce.aspx
 http://oreilly.com/catalog/9780596002503/
 http://www.c-
sharpcorner.com/UploadFile/puranindia/324/

34. Thanks