SOA Demystified

1
SOA Demystified
Krishna Kumar
2
SOA Demystified
Agenda

• ESOA Introduction and benefits
• Trends and Paradigm shifts
• Modeling a Sample scenario
• Differentiate a web service and an Enterprise
  service

3
ESOA
The Buzz word Enterprise Service-Oriented
Architecture Enterprise service-oriented
architecture (enterprise SOA) - business-driven
software architecture - Share and reuse services
within your company and strategic
partners Business functionality
transformation - Smaller process steps -
Software modeled as reusable enterprise
services - Monolithic applications
re-engineered - Business change with increased
adaptability, flexibility, and cost efficiency.
4
What is possible?
With enterprise SOA You can
Compose new business processes for business
innovation Enterprise services, including
those from strategic business partners can be
created, combined and rearranged to compose new
business processes to support innovative business
strategies. Modify business processes to achieve
operational excellence When change is required,
you only need to modify the enterprise service
for a particular process step, so the IT
organization can respond more quickly and cost
effectively to changing business
requirements. Automate processes to empower
information workers You can use enterprise
services to automate many process steps that
currently require human intervention. With
automated processes information workers spend
less time on routine tasks, freeing them to
contribute to the strategic goals of your
business.
5
Current Pressures in the industry
Complexlandscapes

• Next generation
• Platform approaches
• Canonical landscape
• Collaborations
• Shared sourcing

Changingbusiness

• Homemade world
• Home-grown architecture
• Limited collaboration
• Tightly coupled

Multiple playersand new sourcing
6
SOA - Go to Market Multiple Steps to Win
Customers and Partners
Building networks
Create standards(IVN)
Composition
Convincing customers
Provisioning
Banking Services
Innovate new sales channels
Createecosystem
Convincing analysts
7
Paradigm Shift - 1

• Shift from application-centric to
  process-centric approach
• Application is a set of processes
• Think beyond a transaction
• Business Processes span multiple LUWs and time
• Business Processes act and feed on Business
  Events (BEN)
• Loose-coupling
• Component Independency
• The Granularity Trade-off
• Your Component should be replaceable
• Asynchronous Communication
• Asynchronous is the way to go
• Distributed Objects Separation of
  responsibilities
• Data-disjunctive

Are We prepared?
8
Paradigm Shift - 2

• Prepare internal architecture for process
  architecture
• Decouple business objects according to process
  component boundaries
• Replace direct calls by message-based
  communication
• Separate process logic from business logic
• What is typically process logic?
• Process relevance
• Process persistence evaluation (choreography,
  restart, monitoring)
• Condition / responsibility determination
• Separate integration logic from business logic
• What is typically integration logic?
• Partner agreements
• Message assembly
• Proxy call and logging

Are We prepared?
9
Paradigm Shift 3(Loose coupling and
Communication)

• Asynchronous
• Uni-Cast / Fire and Forget
• Request Response
• Publish / Subscribe
• Data Consistency
• Forward Recovery
• Business Rollback not just a DB Rollback
• Independence from technical locks, other parallel
  business processes
• Accept some imbalances
• e.g., Stock and Delivery
• Design message interface so that inconsistency
  does not arise
• e.g., Credit/Debit Posting
• Avoid the need for serialization, if possible
  (dependent messages)
• Use Synchronous only as a last step!

Are We prepared?
10
New Paradigms
Design principles

• Outside in Design
• Modeling and Meta data
• Start with the scenario, variant, process,
  process step
• Identify the BOs, Services, Events and Messages
  and choreography
• Follow governance throughout!
• Separation of Logic
• UI and business logic
• process logic and business logic
• integration logic and business logic
• Structural design
• Use Layering
• Service Provision/Consumption, Business
  Application, Persistency
• Group the Service Adaptation (proxies into
  facades)

Lets prepare !
11
Industry Standard Services with Enterprise
Processes
12
Four Elements of Enterprise SOA

• Composition Platform
• Integrated composition environment
• Flexibility for consumption of services
• Composite Applications on top

Composition
Provisioning

• Enterprise Service Repository
• Enterprise Modeling
• One unified central repository

Banking Services

• Provisioning Platform
• Decoupled, configurable functionality
• Breaking up the product silos
• Reusable business transactions
• Flexible deployment
• Collaboration through openess

• Platform Infrastructure
• Modeling environment
• Process integration Service orchestration
• Delivering technology innovations tools
• Openness interoperability

13
SOA transformation example
Enterprise SOA for Banking
Banking Software
Composition
Provisioning
Banking Services
Banking Services 6.0
14
Web Vs Enterprise services

• What is a WebService?
• Answer 1
• Answer 2

.txt

• Then Why Enterprise Services?

15
Enterprise SOA transformation lifecycle

• Required development steps
• Identify and consolidate services
• Model and design (the Gov process)
• Define content in Enterprise Service Repository
• Create documentation
• Generate and implement proxy
• Generate Web service for synchronous operations

Asynchronous A2A B2B
Runtime (integration server) Eg. SAP NetWeaver XI

• Third-party application
• Composite app
• External system

Middle ware eg. XI
Back end Software
WSDL proxy
6
4
16
Transaction Patterns - SOA
Sender
Receiver
Synchronous or asynchronous
Query
Response
Database update
Request
Confirmation
Asynchronous only
Notification
Information
A transaction pattern describes an atomic dialog
between service consumer and service provider.
It characterizes the kind of information
exchanged, and it specifies the expected reaction
from the service provider.
17
Basic pattern for Request/Confirmation
Request
Provider
MsgHeader
Request (atomic transaction)
Application proxy
Consumer
Proxy Method Implementation
Confirmation
MsgHeader
Confirmation
MsgLog
18
Synchronous Operation
Request
Consumer
Provider
Consumer process
MsgHeader
Request (atomic transaction)
XI/WS runtime
Appl. proxy
wait
1 communication channel
Confirmation
MsgHeader
Commit work
Confirmation
MsgLog
19
Asynchronous Operation
Request
Consumer
Provider
Consumer process
MsgHeader
XI inbound queue
Outbound queue (optional)
Request (atomic transaction)
XI runtime
Application proxy
XI outbound queue
status update
Commit work
2 communication channels
Confirmation
XI runtime
MsgHeader
Inbound queue (optional)
Confirmation
Consumer process
MsgLog
20
Enterprise Service Repository Technical View
Modeling (ARIS)
Business Process Components
Business Objects
Interfaces
11
Operations
Message Types
Data Definition
ESR content
Technology Platform
Data Types
21
A sneak preview into modeling
22
Modeling a process - ARIS sample
Integration scenario Model
Process component model
Process component interaction model
23
Definition of Message Interfaces in a Service
Repository
Message Interface
Message Type
Data Type
X3R
24
Proxy Implementation in Backend System eg. SAP
R/3
Wizard to generate WebService
SPROXY
25
Generation of Web Service in Backend System
WSADMIN
26
ESOA Governance

• The primary goals of governance of services are
• Consistency of semantics across development units
• Re-use wherever possible
• Similar treatment of similar objects (customer
  invoice supplier invoice)
• Homogenous modeling and documentation rules
• Minimizing effort for composite development due
  to compatible services
• Compatible services require consolidation across
  the different solutions
• High quality (from a conceptual viewpoint)
• Out side in perspective standardizes
• the Governance Process, e.g. for Services,
  Interfaces, Message Types, Data Types,
• Provides Guidance for Identification, Design and
  maintenance, e.g. for Services, Interfaces,
  Message Types, Data Types,
• Defines roles, tasks, milestones and design rules

27
Recap A2X, A2A, B2B
UI / Composite
A2X
Customer Application
B2B
Application 1
Application 2
A2A
28
Recap Service types

• B2B
• Message communication with partners and customers
• Integration of eco systems
• Especially suited for industries with high
  integration of partners and customers (e.g.
  chemicals)

• A2A
• Integration of heterogeneous applications needed
• Existing applications loosely coupled with
  standard applications from vendors
• Especially suited for industries with high
  integration of heterogeneous applications (e.g.
  banking

• A2X
• Make or buy composites on top of platform
  solution
• UI to back end communications

28
29
Recap A2X, A2A, B2B

• Consumer Model Patterns
• Composite_01 CC Create Change
• Composite_02 RPAU Read Process Approve Update
• Composite_03 ARA Analyze Read Action
• Provider Model
• A2A_01Request_Confirmation
• A2A_02Notification
• A2A_03 Synchronous Reservation
• A2A_04 Specific Query
• A2A_05 Replication
• A2X_01 Manage BPO
• A2X_02 Manage MDO
• A2X_03 Query BO
• A2X_04 Query Fixed Values
• A2X_05 Specific Value Help for BO
• A2X_06 BO Action
• A2X_08 Query Configuration Object

30
Enterprise Service repositories offer more than
Service DefinitionsThey are Process Models
MODEL DESIGN FOR A FULLY SERVICES BASED PLATFORM
31
Conclusion

• WebService is
• self descriptive
• callable function
• standardized communication

What is a Webservice? What is an Enterprise
Service?

• An Enterprise Service is
• a WebService
• harmonized amongst all Enterprise Services
• guantees interoperability
• describes context easy to use

31
32
(No Transcript)
33
Enterprise SOA by Design Technology Topics
34
Recap A2X, A2A, B2B
We have a lot to achieve !! , Let's make things
better Together we will prevail in this eco
system
34