This document provides an overview of key concepts in service-oriented architecture (SOA) including service component architecture (SCA), business process execution language (BPEL), and SOA infrastructure components like the service bus. It discusses how SOA can help businesses by enabling loose coupling, adaptability, agility, and business-driven IT enablement through composition of reusable services.

1. By Abhilash

2. Introduction
SOA Foundation Standards
Service Component Architecture (SCA)
SOA Infrastructure
BPEL
BPM
Service Bus
Phases of a SOA Project

3. Web discoverable application components
Foundation standards:
Foundatio
n
Standards

4. Find-Bind-Invoke paradigm

5. - Business Agility through Decoupling
- Adaptability
- Business Driven IT enablement
- Composition of Services
- Architecture style
SERVICE ORIENTED ARCHITECTURE
(SOA)

7. Close the gap between business and IT
Loose coupling
Agility
DT @ RT – Design Time at Runtime
Natively Interoperable with heterogeneous
systems
Cross-platform support through open WS
standards
Reliable
Secure
Scalable
Vendor independent

10. Business Process Execution Language, BPEL, is
an executable modeling language. Through
XML it enables code generation.
Traditional Approach BPEL Approach
Hard-coded decision logic Externalized decision logic
Designed by IT Modeled by business analysts
Developed by IT Developed by IT
Maintained by IT Maintained by policy managers
Managed by IT Managed by IT
Dependent upon custom logs Automatic logs and process
capture
Hard to modify and reuse Easy to modify and reuse

11. • SOA is all about Services
• Services are building blocks to SOA solution
Services should be:
• Granular – Finding balance between coarse
grained and fine grained service
• Atomic – atomic to service-consumer
• Idempotent – have no side affects
• raiseSalaryByX Vs. setSalaryAtX()
• Stateless – Less footprints to promote
repeated reuse
• Event aware
• Bound to Service Level Agreement (SLA)
Granular IdempotentAtomic Stateless

12. Technical/Utility Services
◦ Exception Handling, Transformations, Logging,
Address Checker, Emailer, SNMP Traps
Elementary Services
◦ For claims – Matching, Pricing, Eligibilities
Business Services
◦ Caters the business needs like
Process a claim
Adjust a claim
Retrieve claims history of a subscriber
◦ Composed of one or more Elementary services or
Utility services
◦ Business process are exposed as a service
◦ Examples: Claim Engine, Billing, Provider, SMS

13. SOAP & WSDL
◦ SOAP & WSDL interactions are strongly typed
◦ Consumer knows what to expect from a service
WS-*
RESTful Services
◦ REST seems primarily useful for data integration
between web clients and servers, not so much for
enterprise SOA

14. WS-Addressing
WS-Policy
WS-Security
WS-SecureConversation
WS-Trust
WS-ReliableMessaging
WS-Coordination
WS-AtomicTransaction
Etc…
Collectively referred
as WS-*

15. Service Component Architecture (SCA)
◦ Set of specifications to model applications using Service-
Oriented Architecture
UDDI Directory, Enterprise Repository, Registry
(YellowPages for webservices)
◦ Dynamic lookups of services to promote reuse
Specifications per different industry verticals
◦ Healthcare uses HL7 for message formats
◦ Financials use XBRL for financial reporting
◦ E-commerce (B2B) uses EDI, ebXML, RosettaNet, etc…

16. A programming model
Basic building block for SCA is a component
Component abstracts business logic

17. A deployable unit – a business solution
Consists of components, services, references
and wires that connect them
Composite can be viewed as component from
integration point of view.

20. Open Standard to orchestrate discrete
services into an end-to-end process flow
Specs driven by OASIS (oasis-open.org)
Follows SCA programming model
Scopes, Fault Handling, Compensation
Handlers, Correlation sets
Sync/Async, JCA Adapters, Activities, Events
Integrates with Rules, Human Workflows, SOA
Governance

22. Business strategy implementation
Graphical representation called as Business
Process Model
Business Process Modeling Notation (BPMN)
BPM Life Cycle:

24. A business perspective - Viewing a business
as a set of processes that can be explicitly
defined, optimized, and managed
A technical (and SOA-oriented) perspective –
Development using software designed for
implementing, executing, and monitoring
process logic

25. Endpoint virtualization
Content based Routing
Transformations
Validation
Auditing
Messaging
Synchronous/Asynchronous adaptation
Composition

30. Centralized library for security policies
Security enforcement, Validation rules are externalized
Improved visibility for the services
Design Time @ Runtime support
Leverages Application Server infrastructure like WebLogic, JBoss
And of course, Decoupling
Complex message flows can be composed using these decoupled services in very
short time
REST-ful WS support

31. Dynamic nature of markets requires RAD and
reduce time-to-market
Identify Business Processes based on business
areas
Top-Down approach
◦ Business Strategy translated into SOA app(s)
Bottom-Up approach
◦ Strategy driven, but existing apps are composed as SOA
apps
◦ Keeping Security, Management as centralized as possible

32. Select
Application
Build
Service
Portfolio
Service
Bus
Business
Process
User
Interface
Dashboard
Security
Scalability