Editing Web service (section)

===Explanation===
[[File:Webservices-en.svg|thumb|right|Web services architecture: the service provider sends a WSDL file to UDDI. The service requester contacts UDDI to find out who is the provider for the data it needs, and then it contacts the service provider using the SOAP protocol. The service provider validates the service request and sends structured data in an XML file, using the SOAP protocol. This XML file would be validated again by the service requester using an XSD file.]]

The term "Web service" describes a standardized way of integrating Web-based applications using the [[XML]], SOAP, WSDL and UDDI open standards over an [[Internet Protocol]] backbone. XML is the data format used to contain the data and provide metadata around it, SOAP is used to transfer the data, WSDL is used for describing the services available and UDDI lists what services are available.

A Web service is a method of communication between two electronic devices over a network. It is a software function provided at a [[network address]] over the Web with the service ''always-on'' as in the concept of utility computing.

Many organizations use multiple software systems for management.{{citation needed|date=August 2015}} Different software systems often need to exchange data with each other, and a Web service is a method of communication that allows two software systems to exchange this data over the Internet. The software system that requests data is called a ''service requester'', whereas the software system that would process the request and provide the data is called a ''[[service provider]]''.

Different software may use different programming languages, and hence there is a need for a method of [[data exchange]] that doesn't depend upon a particular programming language. Most types of software can, however, interpret XML tags. Thus, Web services can use XML files for data exchange.

Rules for communication with different systems need to be defined, such as:
* How one system can request data from another system.
* Which specific parameters are needed in the data request.
* What would be the structure of the data produced. (Normally, data is exchanged in XML files, and the structure of the XML file is validated against a .xsd file.)
* What error messages to display when a certain rule for communication is not observed, to make [[troubleshooting]] easier.

All of these rules for communication are defined in a file called [[Web Services Description Language|WSDL]] (Web Services Description Language), which has a <code>.wsdl</code> extension. (Proposals for '''Autonomous Web Services''' ('''AWS''') seek to develop more flexible Web services that do not rely on strict rules.{{efn|1=Compare: {{harvnb|Oya|2008}}, "Under the current Web Services, […] stakeholder systems must follow the predefined rules for a particular business service including those about business protocols to send/receive messages and about system operation. […] More flexible mechanism is desired where freely built and autonomously running systems can exchange business messages without pre-agreed strict rules. We call it Autonomous Web Services (AWS) and proposed the framework called Dynamic Model Harmonization (DMH) with its algorithm, which dynamically adjusts different business process models between systems […]."<ref>
{{cite book | last1 = Oya | first1 = Makoto | chapter = Autonomous Web Services Based on Dynamic Model Harmonization | editor1-last = Oya | editor1-first = Makoto | editor2-last = Uda | editor2-first = Ryuya | editor3-last = Yasunobu | editor3-first = Chizuko | title = Towards Sustainable Society on Ubiquitous Networks: The 8th IFIP Conference on E-Business, E-Services, and E-Society (I3E 2008), September 24 – 26, 2008, Tokyo, Japan | url = https://books.google.com/books?id=__WWduWBk7IC | series = IFIP Advances in Information and Communication Technology | volume = 286 | publisher = Springer Science & Business Media | publication-date = 2008 | page = 139 | isbn = 9780387856902 | access-date = 2015-08-19 | date = 2008-09-02 }}</ref>}})

A directory called [[Universal Description Discovery and Integration|UDDI]] (Universal Description, Discovery, and Integration) defines which software system should be contacted for which type of data. So when one software system needs one particular report/data, it would go to the UDDI and find out which other systems it can contact for receiving that data. Once the software system finds out which other systems it should contact, it would then contact that system using a special protocol called [[SOAP]] (Simple Object Access Protocol). The service provider system would first validate the data request by referring to the WSDL file, and then process the request and send the data under the SOAP protocol.