UNIT-2

CLOUD
APPLICATIONS
 INTRODUCTION TO WEB SERVICES &
TECHNOLOGIES
What is a WEB SERVICE?
A service offered by an electronic device to another electronic device,
communicating with each other via the world wide web, a web service
implemented in the particular technologies. 
A Web Service  can be defined by following ways:
 A web service is an application (a package that performs a specific task)
 It is a client server application or application component for
communication.
 A method of communication between two devices over network.
 It is a software system for interoperable machine to machine
communication.
is a collection of standards or protocols for exchanging information between
two devices or application.
Web Service Infrastructure

 ASMX
Invoke
Web Service
methods

ASMX
Web Service Infrastructure

 Web Service Description Language

(WSDL)
–Describe Web Services
–Describes dependencies (e.g.,
DataSets / XSD)
ASMX
WSDL
XSD
Web Service Infrastructure

 Discovery Documents
(DISCO)
–Publish Web Services

ASMX
WSDL
DISCO XSD
WSDL
Web Service Infrastructure

• UDDI(Universal description discovery

language)

ASMX
WSDL
DISCO XSD
UDDI WSDL
DISCO
Technologies required for deployment process:
1.ASMX
2.ASP
3.DISCO

ASMX:
ASMX is known as Active Server Method file. It
is a file type used by microsoft Servers
It invokes the web services methods
ASMx provides the ability to build web services
that send messages using the SOAP
ASPX(Active Server Pages):
It is an open-source server side web application
framework designed for web development to produce
dynamic web pages
It is developed by microsoft

DISCO:
 It is used to discover the url's of XML web services
located on a web server and saves document related to
each XML service on a local disk.
 COMPONENETS OF WEB SERVICES
Major web service components:
1. SOAP
2. WSDL
3. UDDI
4. HTTP
5. XML

SOAP:
1. SOAP is an acronym for Simple Object Access Protocol.

2. SOAP is an XML-based protocol for accessing web services.

3. SOAP is a communication between applications.

4. SOAP is XML based, so it is platform independent and language

independent. In other words, it can be used with Java, .Net or PHP language on
any platform.
WSDL:
1. WSDL is an acronym for Web Services Description
Language.

2. WSDL is a xml document containing information about

web services such as method name, method parameter
and how to access it.

3. WSDL is a part of UDDI. It acts as an interface

between web service applications.
UDDI:
1. UDDI is an acronym for Universal Description,
Discovery and Integration.

2. UDDI is an XML based framework for describing,

discovering and integrating web services.

3. UDDI is a directory of web service interfaces described

by WSDL, containing information about web services.
HTTP:
Full form of http is Hypertext Tansfer Protocol
 HTTP is the World Wide Web standard for
communication over the internet

XML:
Full form of XML is Extensible Markup Language
XML is well known standard for storing and
exchanging data.
DEPLOYMENT:
1. The process of involving a new software or hardware
whether it is working properly in its environment (it
includes installation, configuration, running, testing and
make necessary changes required)

2. It is process of making software available and ready for

use in general.

3. In cloud context, deployment is basically where

software is made available/ running state.
Two Quick Steps to your
first Web Service
 Step 1. Create a project
 Choose your favorite programming language
 Choose the web service project type
 Give it a Name
…Two Quick Steps to your
first Web Service
 Step 2. Add a Web Service to the Project
 Name the Web Service
 Code a Function
 Add an attribute keyword <WebMethod()> to
turn that function into a Web Service method
!!
 That’s it !!
Three Quick Steps to your
first Web Service Client
 Step 1. Create a project
 Choose your favorite programming language
 Choose the correct project type (ASP.NET web
applications)
 Give it a Name
 Step 2. Add a Web Reference to the
Project
 Locating a web service
 Add the reference for the target web service
 And…
…Quick Steps to your first
Web Service Client
 Step 3. Drag and Drop your way to a web
form client (plus a little coding…)
 Use the tool box and drag and drop
elements to the form
 Click on a control (a button usually) to open
the code behind page
 Implement any code to take action (call the
web service!!)
 That’s it !!
Test that Web Service Client

 Run Solution Build

 Right click the aspx page and choose to
view in browser
 Test out the web service through this
web client you built !!
NOTE: In the concern of CSE E2 ALL SECTIONS STUDENTS REGARDING CLOUD COMPUTING
OF TOPIC-DEPLOYMENT PROCESS(STEPS) IS GIVEN IN VISUAL STUDIO.NET (IDE) TO
MAINTAIN UNIFORMITY AMONG ALL SECTIONS IN EXAM POINT OF VIEW PLEASE KINDLY
FOLLOW AND COOPERATE FOR SMOOTH PROCESS
XaaS is a general, collective term that refers to the
delivery of anything as a service. It recognizes the
vast number of products, tools and technologies that
vendors now deliver to users as a service over a
network -- typically the internet -- rather than provide
locally or on-site within an enterprise.
Web service Architecture
Every framework needs some sort of architecture to make sure the entire
framework works as desired. Similarly, in web services, there is an
architecture which consists of three distinct roles as given below

1. Provider - The provider creates the web service and makes it

available to client application who want to use it.
2. Requestor - A requestor is nothing but the client application that
needs to contact a web service. The client application can be a
.Net, Java, or any other language based application which looks for
some sort of functionality via a web service.
3. Broker - The broker is nothing but the application which provides
access to the UDDI. The UDDI, as discussed in the earlier topic
enables the client application to locate the web service.
1.Publish - A provider informs the broker
(service registry) about the existence of the
web service by using the broker's publish
interface to make the service accessible to
clients
2.Find - The requestor consults the broker to
locate a published web service
3.Bind - With the information it gained from
the broker(service registry) about the web
service, the requestor is able to bind, or
invoke, the web service.