SERVICE ORIENTED

ARCHITECTURE
(EID364)
EID364: SERVICE ORIENTED ARCHITECTURE
(Elective) LTPC 3003

Module I :(FUNDAMENTALS OF SOA): Introduction, defining

SOA, evolution of SOA, service oriented enterprise, comparing SOA to
client server and distributed internet architectures, basic SOA
architecture concepts, key service characteristics, technical benefits,
business benefits.

Module II COMBINING SOA AND WEB SERVICES: Web services

, service descriptions , messaging with soap ,message exchange patterns,
web service platform, service contract, service level data model, service
discovery, service level security, service level interaction patterns,
atomic and composite services, service enabling legacy system,
enterprise service bus pattern
. Module III 10 hours MULTI CHANNEL ACCESS AND WEB SERVICES
COMPOSITION: SOA for multi, channel access, business benefits, tiers, business
process management, web service composition, BPEL, RESTFUL services,
comparison of BPEL and RESTFUL services.

Module IV 10 hours JAVA WEB SERVICES: SOA support in J2EE , java API for
XML, based web services(JAX,WS), java architecture for XML binding (JAXB) , java
API for XML registries(JAXR), java API for XML based RPC (JAX,RPC), web
services interoperability, SOA support in .NET , ASP.NET web services, case studies,
web services enhancements (WSE).

Module V 8 hours WEB SERVICES SECURITY AND TRANSACTION: Meta

data management, advanced messaging, addressing , reliable messaging, policies, WS-
policy, security, WS- security, notification and eventing, transaction management.
Text Book(s)
1. Eric Newcomer, Lomow, Understanding SOA with Web Services,
Pearson Education, 2005.
2. 2. James McGovern, Sameer Tyagi, Michael E Stevens, Sunil
Mathew, Java Web Services Architecture, Elsevier, 2003.

References

1. Thomas Erl, Service Oriented Architecture, Pearson Education,

2005. 2. Sandeep Chatterjee, James Webber, Developing Enterprise
Web Services, An Architect's Guide, Pearson Education, 2005.

3. Dan Woods and Thomas Mattern, Enterprise SOA: Designing IT

for Business Innovation, O'REILLY, 1/e, 2006.

4. Frank Cohen, FastSOA, Elsevier, 2007. 5. Jeff Davies, The

Definitive Guide to SOA, Apress, 2007
 Module I
FUNDAMENTALS OF SOA
Introduction
Defining SOA
Evolution of SOA
Service oriented enterprise
Comparing SOA to client server and distributed internet
architectures
Basic SOA architecture concepts
key service characteristics
Technical benefits
Business benefits
Introduction:
Hotel and services

So in order to order a item from a hotel you need the three

logical departments / services to work together (counter,
kitchen and waiter).

In the same manner in software world these services are

termed as business services.
.
Ex:- ‘order system’ shows a simple ordering system which is
achieved by different services like payment gateway, stock system
and delivery system coming together
Definition: Business service: – It’s a logical
encapsulation of self contained business
functionality.
What is a service in SOA?
A service is a self-contained unit of software that performs a specific
task . It has three components: an interface, a contract, and
implementation.

Interface  utilize common communication standards in such a way

that they can be rapidly incorporated into new applications without
having to perform deep integration each time
Contract ---how the service provider and the service consumer should
interact

Implementation ---- actual service code itself.

Service Oriented Architecture:

“It is a style of software design where services are

provided to the other components by application
components, through a communication
protocol over a network”

Informal:---Functionality provided by vendor over a network/internet

for a cost or no cost
Service oriented Terminology
Properties:
A service has following properties according to one of
many definitions of SOA:
1. It logically represents a business activity with a specified
outcome.
2. It is self-contained and exist alone logically(loosely
coupled).
3. It is a black box for its consumers, meaning the
consumer does not have to be aware of the service's
inner workings.
4. It may consist of other underlying services
5.SOA services are maintained in a central
repository
Principles of SOA Design:

Standardized Service Contract

Loose Coupling
Service Abstraction
Service Reusability
Service Autonomy(independent)
Services should have control over the logic they
encapsulate.
Service Statelessness
Ideally, services should maintain min information or
stateless.
Service Discoverability
Services can be discovered (usually in a service registry).
Service Composability
Services break big problems into little problems.
Evolution of SOA:

Procedural Programming
Object Oriented Programming
Service Oriented Programming:
 This SOA designs infrastructure architecture around
services rather than applications.
 In this emphasis is on creating components called
services which are called services that provides a
specific functionality and can be reused in every
application.
CIO….
Chief Information Officer Serves as the company’s top
technology infrastructure manager.
Collaborates and manages vendors that supply
infrastructure solutions
Aligns the company’s IT infrastructure with business
priorities
Developers strategies to increase the company’s
bottom line (profitability)
Has to be a skilled and organized manager to be
successful the organization’s internal IT operations
CTO.. Chief Technology Officer
Serves as the company’s top technology architect
Runs the organization’s engineering group
Uses technology to enhance the company’s product offerings
Focuses on external customers (buyers)
Collaborates and manages vendors that supply solutions to
enhance the company’s product(s)
Aligns the company’s product architecture with business
priorities
Develops strategies to increase the company’s top line (revenue)
Has to be a creative and innovative technologist to be successful
Enterprise Architect has to contemplate the basic
design from the standpoint of strength, functionality
and placement of resources
Service-Oriented Architect’s job is to bring specific
services (utilities) online and ensure their operation
Enterprise Architecture is like the OS which organizes,
drives everything, and provides stability to the entire
machine.
SOA on the other hand, is akin to a browser OS, which
can be used to deliver and manage new services and
apps. Both systems of control are needed in order to
ensure that a business operation is fundamentally
sound from an operational standpoint as well as a
technological one.
Extra:
In enterprise architect looks at the overall construction of
the enterprise. SOA is a particular construction technique
that can be used to build enterprise IT.
INTRODUCTION
"Enterprise architect is a newer skill that's emerged on
our platform over the past, increase in the number of
job postings for 'enterprise architect,' particularly
among large enterprise organizations who are adopting
service-oriented architecture (SOA) and those who
are instigating technology and business process change
within the organization," Pearson says.
Service-oriented architecture as a solution..
Service-oriented architecture presents an approach for
building distributed systems that deliver application
functionality as services to either end-user applications
or other services. It is comprised of elements that can
be categorized into functional and quality of service.
A service is generally implemented as a course-
grained, discoverable software entity that exists as a
single instance and interacts with applications and
other services through a loosely coupled, message-
based communication model.
Service-oriented terminology:
Applications or Services
Service Locator
Service Broker
Service Provider
Service Consumer
Services: Logical entities, the contracts defined by one or more
published interfaces.
 Service provider: The software entity that implements a service
specification.
 Service consumer (or requestor): The software entity that calls
a service provider. Traditionally, this is termed a “client”. A
service consumer can be an end-user application or another
service.
 Service locator: A specific kind of service provider that acts as a
registry and allows for the lookup of service provider interfaces
and service locations.
 Service broker: A specific kind of service provider that can pass
on service requests to one or more additional service providers
Service oriented Terminology
CIO….
Chief Information Officer Serves as the company’s top
technology infrastructure manager.
Collaborates and manages vendors that supply
infrastructure solutions
Aligns the company’s IT infrastructure with business
priorities
Developers strategies to increase the company’s
bottom line (profitability)
Has to be a skilled and organized manager to be
successful the organization’s internal IT operations
CTO.. Chief Technology Officer
Serves as the company’s top technology architect
Runs the organization’s engineering group
Uses technology to enhance the company’s product offerings
Focuses on external customers (buyers)
Collaborates and manages vendors that supply solutions to
enhance the company’s product(s)
Aligns the company’s product architecture with business
priorities
Develops strategies to increase the company’s top line (revenue)
Has to be a creative and innovative technologist to be successful
Enterprise Architect has to contemplate the basic
design from the standpoint of strength, functionality
and placement of resources
Service-Oriented Architect’s job is to bring specific
services (utilities) online and ensure their operation
Enterprise Architecture is like the OS which organizes,
drives everything, and provides stability to the entire
machine.
SOA on the other hand, is akin to a browser OS, which
can be used to deliver and manage new services and
apps. Both systems of control are needed in order to
ensure that a business operation is fundamentally
sound from an operational standpoint as well as a
technological one.
Let’s highlight some of the key aspects of SOA common principles here:

• Loose coupling—Services maintain a relationship that minimizes dependencies

and only requires that they retain an awareness of each other.

• Service contract—Services adhere to a communications agreement, as defined

collectively by one or more service descriptions and related documents.

• Autonomy—Services have control over the logic they encapsulate.

Abstraction—Beyond what is described in the service contract, services hide logic
from the outside world.

• Reusability—Logic is divided into services with the intention of promoting

reuse.
• Composability—Collections of services can be coordinated and assembled to
form composite services.
• Statelessness—Services minimize retaining information specific to an activity.
• Discoverability—Services are designed to be outwardly descriptive so that they
can be found and assessed via available discovery mechanisms.

•
Technical Benefits
Efficient development
More reuse
Simplified maintenance
Incremental adoption
Graceful evolution
More resue
Meaningful to the service requester
Well-defined service contracts published in a service
repository
Dynamic, discoverable, meta driven
Loose process coupling
Loose technology coupling
Open, standards based
Predictable service-level agreements
Design for multiple invocation styles
Design service contracts with related services in mind
Business Benefits
Increased business agility
Better business alignment
Improves customer satisfaction
Improved ROI of existing IT assets
Reduced integration costs
Reduced vendor lock-in and switching costs
What is an enterprise architect?
As more enterprises tackle digital transformation and recognize
the value of aligning their IT strategy, technology and processes
with broader business goals, there's a growing need for talented
pros who can reduce complexity, establish solid technology
processes and ensure tech's used consistently across business
units and functional areas.

Increasingly that role is filled by an enterprise architect: someone

who can translate a company's business strategy into concrete
solutions, design and execute an IT systems architecture blueprint
to support that strategy, says Rich Pearson, senior vice president
of marketing and categories at technology skills marketplace
Upwork.
businesses are dealing with two fundamental concerns:
The ability to change quickly, and the need to reduce
costs.
With a service-oriented architecture, we can realize
several benefits to help organizations succeed in the
dynamic business landscape of today:
Leverage existing assets.

Easier to integrate and manage complexity.

More responsive and faster time-to-market.

G
POWER