PAPER PRESENTATION ON WEB SERVICES PRESENTED BY B.SUSHMAJA (CSE) sushmaja.naninani@gmail.com EKATHRA ID: EK115454 B.ANKAMMA (CSE) borraankamma@gmail.

com EKATHRA ID: EK115528 SRI PADMAVATHI MAHILA VISWAVIDYALAYAM (WOMENS UNIVERSITY) SCHOOL OF ENGINEERING &TECHNOLOGY R.USHARANI (CSE) usharani.raavi@gmail.com EKATHRA ID: EK115470

ABSTRACT
Web Services is a technology applicable for computationally distributed problems, including access to large databases. It is a method of communication between two electronic devices, and a "solution logic" that can be exposed over worldwide web. The W3C (World Wide Web Consortium, is the main international standards organization for the World Wide Web) defines a

"web service" as "a software system designed to support described interoperable in a machine-to-machine format interaction over a network. It has an interface machine-processable (specifically Web Services Description Language WSDL). Other systems interact with the web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards. The W3C also states, "We can identify two major classes of Web services, REST-compliant Web services, in which the primary purpose of the service is to manipulate XML representations of Web resources using a uniform set of "stateless" operations; and arbitrary Web services, in which the service may expose an arbitrary set of operations. The term Web services Web API: It is a development in web services where emphasis has been moving away from SOAP based services towards Representational State Transfer (REST) based communications. Its services do not require XML, SOAP, or WSDL service-API definitions. Web APIs allow the combination of multiple web services into new applications known as mashups. When used in the context of web development, Web API is typically a defined set of Hypertext Transfer Protocol (HTTP) request messages along with a definition of the structure of response messages, usually expressed in an Extensible Markup Language (XML) or JavaScript Object Notation (JSON) format. When running composite web services, each sub service can be considered autonomous.

describes a standardized way of integrating Webbased applications using the XML, SOAP, WSDL and UDDI open standards over an Internet protocol backbone. XML is used to tag the data; SOAP is used to transfer the data. WSDL is used for describing the services available and UDDI (XML based registry) is used for listing what services are available. Keywords: SOAP (Simple Object Access Protocol) Protocol specification for exchanging structured information in the implementation of Web Services, XML (Extensible markup language) data description language, WSDL (Describes the Web Service and defines the functions that are exposed in the Web Service), UDDI (Universal Description, Discovery and Integration). The user has no control over these services. Also the web services themselves are not reliable; the service provider may remove, change or update their services. Reliability and fault tolerance is not well supported; faults may happen during the execution. Exception handling in the context of web services is still an open research issue. Remote procedure calls (RPC): RPC web services present a distributed function call interface. The basic unit of RPC web services is the WSDL operation.

Figure 1: Architectural elements involved in XML-RPC.

Representational state transfer (REST): REST attempts to describe architectures which use HTTP or similar protocols by constraining the interface to a set of well-known, standard operations (like GET, POST, PUT, DELETE for HTTP). An architecture based on REST can use WSDL to describe SOAP messaging over HTTP.

Qworum

services

return

XML

results

like

conventional RPC services. In addition they can interact with the end-user through web pages during the call, and they can call other Qworum services. REST SOAP UDDI Web Processing Service (WPS) WSDL WSFL - Web Services Flow Language. WSCL Language XINS Standard Calling Convention - HTTP parameters in (GET/POST/HEAD) POX out. XLANG - XLANG-Specification. XML-RPC - XML Remote Procedure Calls. WPS: The OGC Web Processing Service (WPS) Interface Standard provides rules for standardizing how inputs and outputs (requests and responses) for invoking geospatial processing services, such as polygon overlay, as a web service. The WPS standard defines how a client can request the execution of a process, and how the output from the process is handled. It defines an interface that facilitates the publishing of geospatial processes and clients discovery of and binding to those processes. The data required by the WPS can be delivered across a network or they can be available at the server. WPS can describe any calculation including all of its inputs and outputs, and trigger its execution as a Web Service. It supports simultaneous exposure of processes via HTTP GET, HTTP POST, and SOAP, thus allowing the Web Services Conversation

SOAP::LITE:
Soap is an open protocol specification defining a uniform way of performing RPCs using HTTP as the underlying communications protocol with XML for the data serialization. It is a collection of modules and are loaded automatically when needed. Supports SOAP 1.1 specification All methods can be used for both setting and retrieving values: If you provide no parameters, you will get current value, and if parameters are provided, a new value will be assigned to the object and the method in question will return the current object (if not stated otherwise) which is suitable for stacking these calls like: $lite = SOAP::Lite -> uri (openBQS') -> proxy ('http://industry.ebi.ac.uk/soap/openBQS'); List of web service protocols: BEEP - Blocks Extensible Exchange Protocol E-Business XML Hessian JSON-RPC Qworum - Defines the concept of Qworum services, which are building blocks for web applications.

client to choose the most appropriate interface mechanism. Although WPS was designed to work with spatially referenced data, it can be used with any kind of data. WPS makes it possible to publish, find, and bind to processes in a standardized and thus interoperable fashion. Theoretically it is transport/platform neutral, but in practice it has only been specified for HTTP. WPS defines three operations: 1. GetCapabilities returns service-level metadata. 2. DescribeProcess returns a description of process including its inputs and outputs. 3. Execute returns the output(s) of a process. WPS operations are invoked by submitting XML or URL-encoded requests to an Online Resource URL. When requesting an Execute operation the HTTP request identifies the inputs, the name of process to be executed, and the form of output to be provided. WPS properties: Inputs can be web-accessible URLs or embedded in the request. Outputs can be stored as web-accessible URLs or embedded in the response. For a single output such as a GIF image, WPS can return the output directly, without any XML wrapper. It supports multiple input and output formats. It supports long-running processes. It supports SOAP and WSDL. A WPS is usually not invoked directly. More often, it is invoked by a client application that provides the user with interactive controls. This client application may or may not be web-based.

WEB SERVER: It can be referred to as either the hardware (the computer) or the software (the computer application) that helps to deliver content that can be accessed through the Internet. A web server is what makes it possible to be able to access content like web pages or other data from anywhere as long as it is connected to the internet. The hardware houses the content, while the software makes the content accessible through the internet. The most common use of web servers is to host websites but there are other uses like data storage or for running enterprise applications. There are also different ways to request content from a web server. The most common request is the Hypertext Transfer Protocol (HTTP), but there are also other requests like the Internet Message Access Protocol (IMAP) or the File Transfer Protocol (FTP). The primary function of a web server is to deliver web pages on the request to clients. This means delivery of HTML documents and any additional content that may be included by a document, such as images, style sheets and Java Scripts. A client, commonly on a web browser or web crawler, initiates communication by making a request for a specific resource using HTTP and the server responds with the content of that resource or an error message if unable to do so. The resource is typically a real file on the server's secondary memory, but this is not necessarily the case and depends on how the web server is implemented. While the primary function is to serve content, a full implementation of HTTP also includes ways of receiving content from clients. This feature is used

for submitting web forms, including uploading of files. Many generic web servers also support serverside scripting, e.g., Apache HTTP Server and PHP. This means that the behavior of the web server can be scripted in separate files, while the actual server software remains unchanged. Usually, this function is used to create HTML documents "on-the-fly" as opposed to returning fixed documents. This is referred to as dynamic and static content respectively. The former is primarily used for retrieving and/or modifying information from databases. The latter is, however, typically much faster and more easily cached. Web servers are not always used for serving the world wide web. They can also be found embedded in devices such as printers, routers, webcams and serving only a local network. The web server may then be used as a part of a system for monitoring and/or administrating the device in question. This usually means that no additional software has to be installed on the client computer, since only a web browser is required (which now is included with most operating systems). Common features: Virtual hosting to serve many Web sites using one IP address. Large file support to be able to serve files whose size is greater than 2 GB on 32 bit OS. Bandwidth throttling to limit the speed of responses in order to not saturate the network and to be able to serve more clients.

Server-side scripting to generate dynamic Web pages, still keeping Web server and Web site implementations separate from each other.

Figure 2: The World's First Web Server

Figure 3: The inside and front of a DellPowerEdge Web Server.

Figure 4: Web Services Architecture.

Advantages of web services:

 Web services provide interoperability between various software applications running on disparate platforms/operating systems. Web services use open standards and protocols. By utilizing HTTP, web services can work through many common firewall security measures without requiring changes to the firewall filtering rules. Other forms of RPC may more often be blocked. Web services allow software and services from different companies service. Web services allow the reuse of services and components within an infrastructure. Web services are loosely coupled thereby facilitating a distributed approach to application integration. Web services standards features such as transactions are currently nonexistent or still in their infancy compared to more mature distributed computing open standards such as CORBA. PACKAGING LAYER: Simple Object Access Protocol (SOAP) is a lightweight protocol designed for the exchange of information. Defines a modular packaging model and the encoding mechanisms for encoding data within module. SOAP ATTACHMENTS: Large quantities or binary data may not fit well into a XML SOAP message. In which case it can be sent out of band by attaching it to a SOAP message and locations to be combined easily to provide an integrated

Web

services

may

suffer

from

poor

performance compared to other distributed computing approaches such as RMI, CORBA, or DCOM. Web Services Architecture:

Web Services involve three major roles

Service Provider. Service Registry. Service Consumer. 3 major operations surround web services Publishing making a service available. Finding locating web services. Binding using web services. SOAP Faults: SOAP errors are handled using a specialised envelope known as a Fault Envelope A SOAP Fault is a special element which must appear as an immediate child of the body element <faultcode> and <faultstring> are required.

Analogy: email attachments. How does XML differ from HTML??? HTML is a presentation markup language provides no information about content. There is only one standard definition of all of the tags used in HTML. XML can define both presentation style and give information about content.XML relies on custom documents defining the meaning of tags

What is a Schema??? A schema is the definition of the meaning of each of the tags within a XML document. Analogy: A HTML style sheet can be seen as a limited schema which only specifies the presentational style of HTML which refers to it. Example: in HTML the tag <strong> predefined. In XML you would need to define this in the context of your document. Valid And Well formed: A correct XML document must be both valid and well formed. Well formed means that the syntax must be correct and all tags must close correctly (eg < > </>). Valid means that the document must conform to some XML definition ( a DTD or Schema). Using Name Spaces in XML:

More technologies of distributed architecture will collaborate. The better standards we have the better results well get. Web Services is not a new hype but a trend to follow WS are easier to deploy because of their firewall-friendliness. WS are quite well marketed (both from IT companies and Open Source projects). user sessions are less standardised. many parts yet-to-be-done (notification, transactions, security, etc.).

The programming effort and maintainability is similar to other distributed technologies.

REFERENCES:
1. Benslimane, Djamal; Schahram Dustdar, and Amit Sheth (2008). "Services Mashups: The New Generation of Web Applications". IEEE Internet Computing, vol. 12, no. 5. Institute of Electrical and Electronics Engineers. pp. 1315. 2."Mashup Dashboard". ProgrammableWeb.com. 2009. 3. "Web Services Description Language (WSDL) Version 2.0 Part 2: Adjuncts". 4. Gray, N. A. B. (2005). "Performance of Java Middleware - Java RMI, JAXRPC, and CORBA". University of Wollongong. pp. 3139. Retrieved January 11, 2011. "The results presented in this paper show that the nature of response data has a greater impact on relative performance than has been allowed for in most previous studies."

To fully qualify a namespace in XML write the namespace:tag name. eg. <my_namespace:tag> </my_namespace:tag>

In a globally declared single namespace the qualifier may be omitted. More than one namespace: <my_namespace:tag> </my_namespace:tag> <your_namespace:tag> < /your_namespace:tag> can co-exist if correctly qualified.

CONCLUSIONS:

Distributed computing is inevitable. More accesses by programs than by clicking on hyperlinks.