Unit 4

Service Oriented Analysis

UDDI Basics
UDDI is an XML-based standard for
describing, publishing, and finding Web
services.
UDDI stands for Universal Description,
Discovery, and Integration.
UDDI is a specification for a distributed
registry of web services.
UDDI is a platform-independent, open
framework.
UDDI can communicate via SOAP, CORBA,
Java RMI Protocol.
UDDI uses Web Service Definition
Language(WSDL) to describe interfaces to
web services.

 UDDI has two sections:

=>A registry of all web service's
metadata, including a pointer to the
WSDL description of a service.
=>A set of WSDL port type
definitions for manipulating and
searching that registry.

UDDI: Universal
Description, Discovery, and
Integration

UDDI is a Web service that is

based on SOAP and XML
UDDI registers
tModels: technical descriptions of a
services behavior
businessEntities: describes the
specifications of multiple tModels

Yellow, Green, and White Pages in

UDDI

businessEntity: Information about the

party who publishes information about
a service

tModel: Descriptions of specifications

for services or value sets. Basis for
technical fingerprints

businessEntities contain
businessServices

bindingTemplates contain references

to tModels. These references
designate the interface specifications
for a service

businessService: Descriptive
information about a particular family of
technical services

businessServices contain
bindingTemplates

bindingTemplate: Technical
information about a service entry point
and implementation specs
6

Data
Model for
UDDI

WSDL

WSDL
UDDI

UDDI

Service Implementation
BusinessEntity

<import>
<service>

BusinessService

<port>
<port>

BindingTemplate

BindingTemplate
Service Interface
<types>
<message>
<portType>
<binding>

tModel

3 elements of UDDI
A business or a company can register
three types of information into a
UDDI registry. This information is
contained in three elements of UDDI.
These three elements are:
1. White Pages,
2. Yellow Pages, and
3. Green Pages.

#White Pages
White pages contain:
Basic information about the company
and its business.
Basic contact information including
business name, address, contact
phone number, etc.
A Unique identifiers for the company
tax IDs. This information allows
others to discover your web service
based upon your business
identification.

#Yellow Pages
Yellow pages contain more details about
the company. They include descriptions
of the kind of electronic capabilities the
company can offer to anyone who
wants to do business with it.
Yellow pages uses commonly accepted
industrial categorization schemes,
industry codes, product codes, business
identification codes and the like to
make it easier for companies to search
through the listings and find exactly
what they want.

#Green Pages
Green pages contains technical
information about a web service. A
green page allows someone to bind
to a Web service after it's been
found. It includes:
The various interfaces
The URL locations
Discovery information and similar
data required to find and run the
Web service.

Web Services
A web service is any piece of
software that makes itself available
over the internet and uses a
standardized XML messaging system.
A web service is a collection of open
protocols and standards used for
exchanging data between
applications or systems.

SOAP Web Service

RESTful Web Service

JAX-WS
Java API for XML Web Services (JAXWS), is a set of APIs for creating web
services in XML format (SOAP).
JAX-WS provides many annotation to
simplify the development and
deployment for both web service
clients and web service providers
(endpoints).

JAX-RS
Java API for RESTful Web Services (JAXRS), is a set if APIs to developer REST
service.
JAX-RS is part of the Java EE6, and
make developers to develop REST web
application easily.

Business centric SOA

benefits of introducing service-oriented
principles into the domain of business
analysis. It is easy to ignore serviceoriented business modeling and simply
focus on service-orientation as it
applies to technology and technical
architecture.
The common rationale for this approach
is that whatever business processes
need to be automated can be divided
up into physical Web services as

Benefits
1. Business services build agility into business
models
-Service-orientation brings to business
process models a structure that can
significantly improve the flexibility and
agility with which processes can be
remodeled in response to changes. When
properly designed, business services can
establish a highly responsive IT
environment; responsive in that changes in
an organization's business areas can be
efficiently accommodated through recomposition of both a business process
and its supporting technology architecture
(as expressed by the application services

 In other words, applying service layer

abstraction to both business and
technology ends establishes the
potential for an enterprise to achieve
a form of two-way agility

2. Business services prepare a process

for orchestration
-They lie at core of SOA
- Orchestration is the automated
arrangement, coordination, and
management of complex computer
systems, middleware and services.
3. Business services enable reuse
The creation of a business service
layer promotes reuse in both
business and application services, as
follows:

 By modeling business logic as

distinct services with explicit
boundaries, business process-level
reuse can be achieved. Atomic
By taking the time to properly align
business models with business
service representation, the resulting
business service layer ends up
freeing the entire application service
layer from assuming task or activityspecific processing functions.

4. Only business services can realize

the service-oriented enterprise
Applying business services forces an
organization to view and reinterpret
business knowledge in a serviceoriented manner. Altering the
perspective of how business
processes can be structured,
partitioned, and modeled is an
essential step to achieving an
environment in which serviceorientation is standardized,
successfully consistent, and naturally

Integration Vs Interoperation
-Putting diverse concepts together to
create an integrated whole.
-Making services work together by
sharing messages

Syllabus
Module 2: Roots of SOA [Munindar
Singh]
Module 3: Enterprise Architectures
and SOC Principles [Both]
Module 4: Service Oriented
Analysis [Thomas Erl]