Untangle Your Enterprise: Leverage SOA

1
Untangle Your Enterprise Leverage SOA !

• Sal Campana
• sal.campana_at_oracle.com
• Oracle Corporation

2
Agenda

• Integration and Automation Challenges
• Standards and Service Oriented Architecture
• Benefits Summary
• Best Practices

3
Middleware Defined

• Benefits
• Portable and simpler development
• Scalability
• Horizontal scaling, simplified
• Performance
• Threading, connections pools
• Messaging / Interoperability
• Security
• Tooling / wizards (RAD)
• Standards-based, minimize vendor lock-in

Applications
Upper Middleware Integration, Security,
Portals, etc.
Classic Middleware (App Servers J2EE, .NET)
Database
Operating System
Hardware
4
Heterogeneous Environment
Wireless / Mobile
Portal
3rd Party
Batch Processing
Data Aggregation/Synch
BAM
Mainframe
Warehouse
Database
5
Enterprise Challenges
Process Automation
Simplified Integration

• How do we
• Leverage existing systems
• Move from manual/batch processing ? real-time
  information
• Enable IT to efficiently implement new initiatives

• How do we streamline interactions
• Across departments
• With Federal Govt
• Do more with less
• Quality of service

6
Process Automation Requires Integration

• Processes do not stand alone
• Require constant interaction with and validation
  from
• Applications
• People
• Data sources
• IT Administrators
• Various, disparate systems and need to be linked
  to complete a process, but
• Should avoid hard-coded one-off solutions
• Should leverage new standards to enable
  painless integration

Customer Preferences
Customer Look-Up
Product Availability
Production Scheduling
Exception Management
Logistics Tracking
7
Heterogeneous Environment
Wireless / Mobile
Portal
3rd Party
Middleware
Batch Processing
Web services
Data Aggregation/Synch
BAM
Mainframe
Warehouse
Database
8
Heterogeneous Environment
Wireless / Mobile
Portal
3rd Party
Batch Processing
Data Aggregation/Synch
BAM
Mainframe
Warehouse
Database
9
Heterogeneous Environment
Wireless / Mobile
Portal
3rd Party
Middleware
Batch Processing
Web services
Data Aggregation/Synch
BAM
Mainframe
Warehouse
Database
10
Middleware Benefits

• Simplified and Centralized
• Integration / Automation
• Administration
• Security
• Total visibility
• Enable runtime changes
• Standards-based plugplay
• Web Services SOA

11
What is Service-Oriented Architecture?

• Two basic concepts
• Services also known as components, business
  functions, or web services
• Examples
• Create Invoice
• Delete Account
• Orchestration the combining of services into
  business processes
• Advantages
• Build and integrate quickly - without software
  coding/development
• Handle errors easily and elegantly
• ? GOAL Make IT more efficient -- focus on adding
  business value

12
SOA Comparison
Service Oriented Architectures
Traditional Architecture
?
Designed for change re-use
Inflexible
?
Synchronous Asynchronous
Synchronous
?
Loosely Coupled, Coarse-grained
Tightly Coupled
?
True Interoperability (Std-based)
Application Silos
?
Process Oriented
Functionality Oriented
?
Message Oriented
Object Oriented
Re-use Friendly !
13
Service-Oriented Architecture Benefits

• More flexible
• Business process drives application flow, not the
  other way
• Leverage plug and play standards
• Respond to changing requirements faster
• Lower cost
• Re-use across/among organizations dont reinvent
  the wheel
• Use less expensive resources
• Lower risk
• Test component once, use many times
• Less complexity, more manageable
• Handle error situations easily
• Allows IT to focus on adding business values

14
Key SOA Standards
Management Fuels Change
More Adaptable
ERP/ Legacy Apps
Custom Apps Services
Process Flow Logic
PKI Dashboards
Web services
PROCESS ORCHESTRATION
MONITORING
BAM
BPM
JMX
BPEL
XSLT/XQuery
15
What is Business Process Management?

• Focus is on Business Not Technology
• Tools
• Architecture
• Drives Process Improvement

16
The BPM Lifecycle

• BPM is about
• Process Modeling, Execution and Management
• Continuous Process Improvement
• Business and IT working together to achieve
  business objectives
• Making IT more responsive to changing business
  needs and conditions

Business Process Analysis (BPA)
17
BPM Key Users Stakeholders

• Both business and IT people
• Process owners responsible for the business
  process
• Business analysts for modeling and analyzing
  processes
• IT Architects and Developers for building,
  deploying and administering processes
• Business Users for operating and monitoring
  processes

Business Analyst
Process Architect
LOB Process Owner
Business Process
Application / Integration Developer
Business End User
Process Administrator
18
SOA and BPMPerfect Together!
19
Example Process Orchestration

• Service Update State Debarred/Restricted Vendor
  list
• Process If debarred1) place vendor on hold
  2) notify interested parties
• 3) update backend systems/applications
• Orchestration/Solution Use simple BPEL GUI to
  build this process
• No coding required !

c
20
Introduction to BPEL

• Markup language for composing a set of discrete
  services into an end-to-end process flow
• 10 years of research and development from
  Microsoft (XLANG) and IBM (WSFL, FDML)
• The best integration solution for XML and Web
  services but also Java, JCA and JMS
• Rich support for async interactions, parallel
  processing and exception management
• Excellent platform for Event-driven architectures
• Leverages XML Schema, XSLT, XML Query,
  WS-Security, WS-Addressing and WSIF
• Composability A process flow is automatically a
  web service

21
BPEL Process
22
SOA Architecture with Bus Topology
23
Ungoverned, Unmanaged SOA
No systematic way to find and re-use existing
services
No checkpoint to control service provisioning in
the SOA, and to validate compliance with service
design policy and best practices
BusinessLogic
BusinessLogic
BusinessLogic
BusinessLogic
No ability to manage services and enforce policy
at run-time
Legacy
ERP
CRM
Finance
No ability to guide what services arebuilt, how
theyre built, and no way to ensure
interoperability
No control over changes to services, or
visibility into dependencies and impact analysis
24
SOA Governance Define, Manage, Enforce Policies
Governance
Design-time
Run-time
Management Agents
Business Process
Composite Applications
Business Services
Web Services
WSDL, XML
Service Registry
ESM, System Management Console
Policy
Policy
BusinessLogic
BusinessLogic
BusinessLogic
BusinessLogic
Business
Operations
Operations, Systems Management
Developers
Legacy
ERP
CRM
Finance
Enable (Assets)
Publish, Discover (Assets, Services)
Manage (Services)
25
Securing Web Services

• Web services are not inherently secure
• Need to protect services from abuse
• Need to comply with regulations and security
  best-practices
• Need to adhere to SLAs
• Take app security out of the hands of developers
• Best-practice used to be declarative security
• Security via deployment descriptors (app-specific
  files)
• New best-practice is policy-based security
• Centralized policy administration console
• Allows powerful combination of centralized
  control with delegated administration

26
SOA Technical Best Practices

• BPEL is good for message orchestration where one
  of the following are true
• State needs to be maintained across more than one
  message/request/reply
• Business or IT process can be modeled
• More than a few flow-steps and/or external
  interactions
• Compensating exception/error-handling logic is
  desirable
• ESBs are good for
• Simple, stateless messaging
• Routing decision criteria may change frequently
  (at run-time)
• Define canonical data schemas for data that must
  be exchanged/transformed to more than one
  destination/application
• Use state-of-the-art transformation capabilities
  rather than hard-coding/hand-coding
• Use XML and WS- standards wherever
  possible/feasible
• But do not assume full interoperability until
  they mature
• Note XML parsing/generation performance has come
  a long way !
• Web services are preferable to adapters, unless
  transactions are required
• Use state-of-the-art tools to develop and manage
  solutions
• Code generation using IDE wizards and standards
• Integrate testing into development/build
  methodology Junit, Cactus, ANT, etc.
• Avoid deploying SOA without management/monitoring
  tools

27
What the Analysts Say
BPEL is the future of the integration space in
my view Why? Because the value is so much
higher when you provide not only a way to
integrate applications, but also a way to create
services from them and put them into business
processes. - John Rymer, Vice President,
Forrester Research, Inc.
28
What the Analysts Say
Business Process Management wins the triple
crown of saving money, saving time, and adding
value. It also spans the business and
technological gap, to create synergy, with proven
results. - Gartner
Gartner believes that BPEL will emerge as the
leading industry standard for Web service
orchestration and coordination of business
processes. - David Smith, Research Vice
President and Fellow, Gartner
29
ROI on SOA Approach to Integration

• Large manufacturer
• 40 ROI on SOA in first year
• Saved 1 Million in re-use value alone
• Large financial institution
• 200 ROI on SOA projects over first year
• Banking institution SOA CRM initiative
• Increased customer retention by 12
• Consumer checking new customer acquisitions up
  19
• Major bank has experienced a 70 improvement in
  ROI when using SOA solely measuring re-use
  value alone
• Not taking things like RAD or centralized
  administration into account
• Financial services company has saved at least
  200 Million on a major SOA-based integration
  project as compared to prior/similar projects

30
Summary Moving from this to
Wireless / Mobile
Portal
3rd Party
Batch Processing
Data Aggregation/Synch
BAM
Mainframe
Warehouse
Database
31
State of the Art
Wireless / Mobile
Portal
3rd Party
SOA BPEL
Batch Processing
Data Aggregation/Synch
BAM
Mainframe
Warehouse
Database
32
(No Transcript)