5. August 28, 2015 5
What is SOA?
SOA – Service Oriented Architecture
SOA is an architectural
approach, centered around the
concept of services…
6. August 28, 2015 6
Business
And
IT
synchronized
to capitalize
on change
What is SOA?
How does HP define Service Oriented Architecture?
SOA is an architectural approach, centered around the
concept of services, to designing, building and
managing distributed computing infrastructure that an
enterprise requires to execute its business strategy and
achieve its business goals. This approach promotes the
use of loosely-coupled, reusable services, with
standards-based well-defined service specifications that
enable them to be discovered and consumed by
independent service consumers.
SOA permits organizations to link business and IT
services together, and establish stability, predictability,
security, and manageability in a highly distributed and
dynamically changing business environment.
7. August 28, 2015 7
SOA - An Analogy
Internet:
• Standards – html & http so anyone
with a browser can access
information
• Integration – hyperlink allow for ease
of integration
• Metadata – the Internet is metadata
driven. Google creates indexes, plus
provides other services like page
ranking, identifying related products,
etc. You get more than just a list of
sites.
SOA:
• Standards - WSO, WSDM, UDDI.
These allow an SOA to expose
information about services
• Integration – SOAs make
integration of components very
easy, fast and cheap.
• Metadata – If you stopped with
just standards and linkages, the
internet would be nearly useless.
Google makes the Internet
valuable. Likewise, metadata turns
simple Web services into SOA.
Let’s take a look at
The Internet, and SOA share 3 critical principles
8. August 28, 2015 8
Web Services make implementing
SOA easier, but they aren’t the same
9. August 28, 2015 9
Composite Applications
Business
Logic
Legacy ERP CRM Finance
Business
Logic
Business
Logic
Business
Logic
Business Services
Service Infrastructure
What does an SOA look like?
Business Process Layer
10. August 28, 2015 10
Characteristics of a Service
• Meaningful and articulating
− Meaningful levels of granularity
− Flexibility across functional and technology layer
− Makes use of standards and promotes reuse
• Contract based
− Consumer/producer are aware of their obligations
• Self contained and modular
− Coarse grained cohesive, composable, atomic
• Loosely coupled
− Interfaces independent of implementation
− Should not contain technology assumptions
• Locatable
− Distributed using registry and metadata/semantics
− Can be discovered
− Not simply point-to-point
Simplification
Standardization
Modularity
Integration
11. August 28, 2015 11
SOA Technology and Web Services
• One of the key reasons for the today’s focus upon
SOA is the emergence of supporting technologies.
• SOA is an architectural approach, centered
around the concept of services
• SOA ≠ Web Services
− SOA can exist without Web Services
− Web Services can be utilized without an SOA
− Using web services can significantly enhance our ability
to implement SOA
A common source of confusion
12. August 28, 2015 12
Why Web Services for SOA?
Web Services:
• Are (mostly) standardized
• Promote loose-coupling
• Are platform independent and vendor independent
• Provide integration at service level
• Include service description mechanisms
• Include service catalogue mechanisms
14. August 28, 2015 14
Web Service model
Service Registry
Service Consumer Service Provider
Find Publish
Bind
ServiceClient
15. August 28, 2015 15
SOAP
What is it?
• Lightweight XML-based messaging format
• Key components of the specification
− Messaging specification
− Set of encoding rules
− Convention for invocation
• Benefits of using SOAP
− Vendor, platform, and language independence
− HTTP is firewall friendly
16. August 28, 2015 16
SOAP
How does it look like?
• A unit of communication
− Envelope
− Header
− Body
• Error handling through SOAP faults
• Extensibility through custom headers
• Mechanism for representing abstract data
• Invocation styles
− RPC
− Document
22. August 28, 2015 22
Monitoring WS with OVIS
Stock Quote example
SOAP
probe
StockApp
WS
Server
OVIS HP OV
Operations
SOAP
Request
SOAP
Response
WSDL
getQuote
metrics
messages
23. August 28, 2015 23
Monitoring WS with OVIS
Stock Quote example – SOAP and WSDL
SOAP Request:
SOAP Response:
Stock sample WSDL:
27. August 28, 2015 27
SOA Manager
WSM Features
Interposed Management
Performance and availability
monitoring
Security
Auditing
Content monitoring
Automation
Discovery and Deployment
Support for
SOAP over HTTP
XML over HTTP
SLA report
Customizations
Brokered services
Advanced management (handlers)
Message routing
Authorization & Policy/Rules
and beyond
View IT environment in the context of
business metrics
Manage IT according to business
priorities
Link management layers:
business, configuration, and resource
levels
Publish management models to UDDI
Manage change effectively
Embrace heterogeneity
28. August 28, 2015 28
SOA Manager Components
• Network Services
Server
(Business Service Explorer
console)
• WSM Broker
(Broker Configurator console)
• OVO Integration Tool
• WSM J2EE Agent
(optional, WebLogic Server)
• WSM .NET Agent
(optional, .NET Framework)
• Identity Management
(optional, Select Access)
34. August 28, 2015 34
SOA Manager / OVO integration
• Frontend subagent
− Responsible for
communicating with SOA
Manager
− Gathers management
data
• Backend Service
− Receives management
data from frontend
subagent
− Updates OVO service
model
− Submits OVO messages
36. August 28, 2015 36
Configuration
UnderpinningOperations
Management
Business
ITSM Service Model
Checking
Account
Customer
Vault
Credit Risk
Credit Risk
WS
App Srv OS
HP-UX 11.23
Customer
Vault WS
Server
Management
UNIX Server
Management
Web Service
Management
Hardware
Maintenance
HP Server
Manages
Uses
Supports
Manages
Uses
Uses Parent-Child
Underpinned by
Uses
Checking
Account WS
Uses
37. August 28, 2015 37
Business service model
Presentation in Service Navigator
• Shows the business
services
• Maps business services
to web services
• Links the infrastructure to
web services
• Enables impact and root
cause analyses
38. August 28, 2015 38
Summary
SOA Monitoring
OVIS
SOAP
probe
WS
Checking
account
Credit
Risk
Customer
Vault
WSM
broker
WSM
agent
WSM
agent
SOA
manager
OVIS
Server
OVO
Server
Messages
Service model
Messages
Service model
WS WS
Probes:
synthetic end to end
response –
characterize service
availability
“Am I Ready?”
Client monitoring:
real end to end –
characterize service
quality
“How Am I Doing?”