In relation to W3C Web services, the
W3C defined a Web service as: W3C Web Services may use SOAP over HTTP protocol, allowing less costly (more efficient) interactions over the Internet than via proprietary solutions like EDI/B2B. Besides SOAP over HTTP, Web services can also be implemented on other reliable transport mechanisms like
FTP. In a 2002 document, the Web Services Architecture Working Group defined a Web services architecture, requiring a standardized implementation of a "Web service."
Explanation 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. 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
WSDL (Web Services Description Language), which has a .wsdl extension. (Proposals for
Autonomous Web Services (
AWS) seek to develop more flexible Web services that do not rely on strict rules.) A directory called
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.
Automated design methods Automated tools can aid in the creation of a Web service. For services using WSDL, it is possible to either automatically generate WSDL for existing classes (a bottom-up model) or to generate a class skeleton given existing WSDL (a top-down model). • A developer using a bottom-up model writes implementing classes first (in some programming language) and then uses a WSDL generating tool to expose methods from these classes as a Web service. This is simpler to develop but may be harder to maintain if the original classes are subject to frequent change. • A developer using a top-down model writes the WSDL document first and then uses a code generating tool to produce the class skeleton, to be completed as necessary. This model is generally considered more difficult but can produce cleaner designs and is generally more resistant to change. As long as the message formats between the sender and receiver do not change, changes in the sender and receiver themselves do not affect the Web service. The technique is also referred to as
contract first since the WSDL (or contract between sender and receiver) is the starting point. • A developer using a Subset WSDL (SWSDL) (i.e. a WSDL with the subset operation in the original WSDL) can perform Web service testing and top-down development.
Criticism Critics of non-RESTful Web services often complain that they are too complex and based upon large software vendors or integrators, rather than typical
open source implementations. There are also concerns about performance due to Web services' use of XML as a message format and SOAP/HTTP in enveloping and transporting.
Regression testing of Web services Functional and non-functional testing of Web services is done with the help of WSDL parsing.
Regression testing is performed by identifying the changes made to upgrade software. Web service regression testing needs can be categorized in three different ways, namely, changes in WSDL, changes in the code, and selective re-testing of operations. We can capture the above three needs in three intermediate forms of Subset WSDL, Web services testing can also be automated using several test automation tools like
SoapUI,
Oracle Application Testing Suite (OATS), Unified Functional Testing, Selenium, etc.
Web service change management Work-related to the capture and visualization of changes made to a Web service. Visualization and computation of changes can be done in the form of intermediate artifacts (Subset WSDL). is a tool that can identify subset operations in a WSDL file to construct a subset WSDL.
Discovering and Searching for Web Services While UDDI was intended to serve as a service directory and become the means to discovering web services, many vendors discontinued their UDDI solutions or repositories between 2005 and 2008, including Microsoft, SAP, IBM, among others. A key study published in WWW2008 Conference (Beijing, China) presented the state of SOAP-based web services and concluded that only 63% of the available SOAP-based web services at the time of the study were actually active or can be invoked. The study also found that search engines were becoming an ideal source for searching for web services compared to that of service registries like the UDDI due its design complexity. ==See also==