1.
Explain the simple REST interaction between user and server in HTTP specification
with neat diagram.
REST is a software architecture style for distributed systems, particularly distributed
hypermedia systems, such as the World Wide Web.
It has recently gained popularity among enterprises such as Google, Amazon, Yahoo!.
Resource Identification through URIs: The RESTful web service exposes a set of
resources which identify targets of interaction with its clients.
The key abstraction of information in REST Resource Identification through URIs
is a resource.
Any information that can be named can be a resource, such as a document or image
or a temporal service.
A resource is a conceptual mapping to a set of entities.
Each particular resource is identified by a unique name, or more precisely, a
Uniform Resource Identifier (URI) which is of type URL, providing a global
addressing space for resources.
Uniform, Constrained Interface: Interaction with RESTful web services is done via
the HTTP standard, client/server cacheable protocol.
Resources are manipulated using a fixed set of four CRUD (create, read, update,
delete) verbs or operations: PUT, GET, POST, and DELETE.
Self-Descriptive Message: A REST message includes enough information to describe
how to process the message.
This enables intermediaries to do more with the message without parsing the
message contents.
Stateless Interactions: The REST interactions are stateless.
Stateless interaction treats each message independently.
Stateless communications improve visibility.
2. Explain the simple web service interaction among provider, user and UDDI registry
with a neat diagram.
Web service is one of the most common instances of an SOA implementation. web service is a
software system designed to support interoperable machine-to-machine interaction over a
network.
Simple Object Access Protocol (SOAP)
SOAP provides a standard packaging structure for transmission of XML documents
over various Internet protocols, such as SMTP, HTTP, and FTP.
Having such a standard message format, heterogeneous middleware systems can
achieve interoperability.
A SOAP message consists of a root element called envelope, which contains a header
and body.
Header is a container that can be extended by intermediaries with additional
application-level elements such as routing information, authentication, transaction
management,
Body element that carries the payload of the message.
Web Services Description Language (WSDL)
WSDL describes the interface, a set of operations supported by a web service in a
standard format.
It standardizes the representation of input and output parameters of its operations as
well as the service’s protocol binding, the way in which the messages will be transferred
on the wire.
Universal Description, Discovery, and Integration (UDDI)
UDDI provides a global registry for advertising and discovery of web services, by
searching for names, identifiers, categories, or the specification implemented by the
web service.
3. Explain OGSA architecture with a neat diagram.
OGSA is intended to:
• Facilitate use and management of resources across distributed, heterogeneous
environments • Deliver seamless QoS
• Define open, published interfaces in order to provide interoperability of diverse
resources
• Exploit industry-standard integration technologies
• Develop standards that achieve interoperability.
• Integrate, virtualize, and manage services and resources in a distributed,
heterogeneous environment
• Deliver functionality as loosely coupled, interacting services aligned with industry-
accepted web service standards.
Based on OGSA, a grid is built from a small number of standards-based components,
called grid services.
A grid service implements one or more interfaces, where each interface defines a set of
operations that are invoked by exchanging a defined sequence of messages, based on
the Open Grid Services Infrastructure (OGSI).
OGSA services fall into seven broad areas, defined in terms of capabilities frequently
required in a grid scenario. These services are summarized as follows:
Infrastructure Services Refer to a set of common functionalities.
Execution Management Services Concerned with issues such as starting and
managing tasks.
Data Management Services Provide functionality to move data to where it is needed.
Resource Management Services Provide management capabilities for grid resources:
management of the resources themselves.
Security Services Facilitate the enforcement of security-related policies within a
(virtual) organization.
Information Services Provide efficient production of, and access to, information about
the grid.
Self-Management Services Support service-level attainment for a set of services.
4. Explain sematic grid architecture with a neat diagram.
Semantic web is all about automation discovery and integration: adding machine-
processable semantics to data so that computers can understand such information and
process it on behalf of end users.
The Semantic web aims to provide an environment where software agents are able to
dynamically discover, interrogate, and interoperate resources and perform sophisticated
tasks on behalf of humans.
The meaning of web resources is stored in a common data model, the Resource
Description Framework (RDF).
RDF is the first language developed for the Semantic web, using XML to represent
information (including metadata) about resources on the web.
OWL is an expressive ontology language that extends RDF schema.
OWL adds more vocabulary for describing properties and classes: among others,
relations between classes, cardinality, equality, richer typing of properties,
characteristics of properties, and enumerated classes.
Semantic web services describe and annotate various aspects of a web service using
explicit, machine-understandable semantics, facilitating the discovery, execution,
monitoring, and aggregation of resources and web services.
The OWL-S ontology defines the top-level concept of a “Service” and three OWL-S
subontologies:
• Service profile Expresses what a service does in order to enable service advertisement
and discovery.
• Service model Describes how the service works in order to enable service invocation,
composition, monitoring, and recovery.
• Service grounding Specifies the details of how to access the service.
The “semantic grid” or “grid with semantics” aims to incorporate the advantages of the
grid, Semantic web, and web services.
Sematic grid was first articulated in the context of e-science, which is all about scientific
investigation among scientists of various communities such as physicists, biologist, and
chemists.