Colorado Software Summit: October 22 – 27, 2006 ... EBS Customer View ... Colorado Software...

Colorado Software Summit: October 22 – 27, 2006 © Copyright 2006, Oracle Corporation

Bill Jones — Next Generation of SOA Development

Bill JonesOracle [email protected]

Next Generation SOADevelopment



Agenda

SOA and Web Services

Primitive Services

Composite Services

Service Component Architecture

SOA Platform

Conclusions



Service Oriented Architecture

Service model for business functions

Characteristics

Flexibility

• Autonomous services are highly reusable

Non predictive patterns of use

Productivity

• High level of abstraction

Comprehension

• Well-understood system architecture and behavior



Why SOA? – The Cruel Reality

Screen

Scrape

Screen

Scrape

ScreenScrape

ScreenScrape

MessageQueue

Message

Queue

MessageQueue

DownloadFile

DownloadFile

DownloadFile

TransactionFile

Transaction

File

TransactionFile

ORB

ORB

CICS Gateway

CICS Gateway

APPC

APPC

RPC

RPC

Transaction

File

Sockets

Sockets

Message

Message

Application

Application

Application

Application

Application

Application

Application

Application

Application

Application



OracleOracle

FinancialsFinancials

Standard InterfaceStandard Interface

Custom OrderCustom Order

ApplicationApplication


New WebNew Web

Application Application


SiebelSiebel

CRMCRM


Mainframe HRMainframe HR



.NET Inventory.NET Inventory



New Supply Chain Management ApplicationNew Supply Chain Management Application

(Business Process or Composite Application)(Business Process or Composite Application)

Why SOA?Respond to business changes

Address new needs with existing applications

Unlock existing application investments

Support new channels & complex interactions

Support organic business



Web Services

Basic TechnologiesDescribed in WSDL

Accessed with SOAP

Web services emphasize loosely coupledsystems that exchange self-containedmessages

Business functions are modeled as networkedservices

Explicit failure modes

Leverage the ubiquitous protocols of the WebEasy interconnectivity



Web Services and SOA

SOA the goal, Web services an enablingtechnology

Transparent XML payloadsCoarse grained business functionsSOAP/WSDL easily abused

• Externalizing object models problematic

Not only Web servicesHeterogeneity the norm

• One model, multiple protocols

WS* overload unhelpful



Canonical Business Documents

XML type definitions

Broadly understoodShared types

Clear business semantics: accessible tobusiness analysts

Services exchange business documentsthrough meaningful contracts



Transforming Business Processesand Interactions

Today

• Hardcoded inside applications

• Mainly sequential

• Silo-ed (divisional and functional)

• One-size fit all

• Tactical point-to-point integration

• Black boxes

Tomorrow

• Mainly parallel

• Boundary-less

• Wired through events

• Modular

• Continuously optimized

• Highly personalized

• Continuously audited

Your Business is Only as Flexible as Your Technology…

?



SOA (and EDA) Is Emerging asthe Enabling Platform

SAP

Oracle

TOMAX

Developers

Mainframe OutsourcedJava

.NET

Business Process

Optimization

Real-time

Analytics

Data

Integration

SOA Platform

Why Now?

• Network Infrastructure is in place

• Standards (XML, WSDL, WS-*)

• Domain Specific Languages

(BPEL, XSLT, Rules, BAML, CEPQ…)

• Support from Packaged Applications

Requirements

• Business Savvy Developer

• Façade/Leverage Existing Core IT

• Build-to-change

• End-to-end Security

• Management and Monitoring

Functional Analyst

Core IT

Composites



Agenda


Primitive Services

Composite Services


SOA Platform

Conclusions



Primitive Services

Basic building blocks

Adapters

• Tie legacy system into SOA

• Support transformation/translation

• Java Connector Architecture baseline for J2EE

Java/C#

• Service Enablement of existing components



ModelModel

Spring, JPASpring, JPA

ModelModel

EJB 3, JPAEJB 3, JPA

Business Logic



Persistence ServicesO-R & O-XML

Structured DataStructured Data Unstructured DataUnstructured Data

O-RO-R O-XMLO-XML



Agenda


Primitive Services

Composite Services


SOA Platform

Conclusions



Composite Services

BPM model driven by business analysts

BPEL developmentVisual construction of process flow

Heavy emphasis on XML manipulation

Interactions described by SCA metadata

BPEL eases development burdendramatically

Ideal for asynchrony

Automated state management



Composite Services

Human Workflow

Business Rules

Sub Process

Automated Activity

Notification

Business Event

Studio

Full

BPA

Outliner

Share

d M

odel



ESB in a Nutshell

Loan

Process APR

Rule

Manager

Review

Task EBS

Customer

View

Enterprise Service Bus

UDDIRegistry

MDS

HTTP

RESTJMS

SOAP

HTTP

SOAP

.NET

Payment

Calculator

Core Features

Rich Set of Adapters(technology and applications)

Transformation

Reliable Message Delivery

Content-based Routing

Publish and Subscribe

Service URL Virtualization

Value-Added FeaturesRequest/Response and Event DrivenInteractionsMulti TransportRich Monitoring ConsoleNative XML and Web ServiceSupportMetadata RepositoryUDDI RepositoryExternalized Process FlowsReal Time Activity Monitoring

In

Memory



Agenda


Primitive Services

Composite Services


SOA Platform

Conclusions



SCA in a Nutshell

SCA models the “A” in SOA – for systemscomposed of reusable services

model for service-based system:

• service construction

• service assembly

• deployment

Heterogeneity – supports components from

• multiple languages

• multiple container technologies

• multiple service access methods

0.9 Level specification published in November 2005



SCA – High Level PointsUnified declarative model describing serviceassemblies

dependency resolution and configurationdeclarative policies for infrastructure services

• Security, Transactions, Reliable messaging

Business-level model for implementing servicesservice components with service interfaces

Binding model for multiple access methodsWSDL, SOAP over HTTPbut also: JMSTM/messaging, JavaTM RMI/IIOP…JavaTM interfaces are good, as are WSDL portTypes



Service Assembly Model

Unified, language-independent way to exposeimplementations as services

• JavaTM, BPEL, PHP, other languages (including .NET)

Technology independent modelling andcomposition of service networks

• Service dependencies

• Resolution through wiring

Facilities for dynamic service configuration• Properties / Protocols / Qualities of service

• Profiles

Design time and deployment time configuration



Assembly Model Concepts

Design Time Assembly

Composite

Implementation

Component

Service

Reference

Wire



Composite

Composite

External Web Service

System

Service Assembly ModelModel for assembling tightly coupled code (Composites)

Model for assembling loosely coupled services (Systems)



Composite



SCA Composite Example<?xml version="1.0" encoding="ASCII"?><composite xmlns="http://www.osoa.org/xmlns/sca/0.9" name="bigbank.accountcomposite" >

<service name="AccountService"> <interface.bpel process="AccountService"/> <binding.ws port="http://www.bigbank.com/AccountService#

wsdl.endpoint(AccountService/AccountServiceSOAP)"/> <reference>AccountServiceComponent</reference></service>

<component name="AccountServiceComponent"> <implementation.java class="services.account.AccountServiceImpl"/> <property name=“currency”>EURO</property> <reference name="accountDataService" target="AccountDataServiceComponent"/> <reference name="stockQuoteService" target="StockQuoteService"/></component>

<component name="AccountDataServiceComponent"> <implementation.java class="services.accountdata.AccountDataServiceImpl"/></component>

<reference name="StockQuoteService"> <interface.java interface="services.stockquote.StockQuoteService"/> <binding.ws port="http://www.quickstockquote.com/StockQuoteService#

wsdl.endpoint(StockQuoteService/StockQuoteServiceSOAP)"/></reference>

</composite>



Agenda


Primitive Services

Composite Services


SOA Platform

Conclusions



Architecture GoalsSOA Technology Requirements Evolving

Service Integration to Orchestration to Composite

Assemblies

Enable more adaptive enterprise applications

Through more extensible business processes

Simplify integration between enterprise

applications

Through declarative, metadata-based design &

customization



All SOA Platforms Are NOT Equal

“Lipstick on a Pig”(proprietary)

Hot-pluggable or Not

Monolithic versus Modular

Slew of disjoint tools

Silo-ed Security

Breath of Lifecycle Support

Metadata RepositoryStrategy

Message Bus ESBnew

Process EngineHuman Workflow

Portal

sec

sec

sec

sec

Tool

Tool

Tool

Tool

BPA

Adapters



SOA Evolution

PublishServices

IntegrateServices

OrchestrateFlows

AssembleComposites

Packaged

Applications

Java

.NET

Mainframe

A B

Service Bus

A

BPEL

B C A

BPEL

B C

rules BI

BAM

Service Bus Service Bus

XML, WSDL XSLT, WS-Policy BPEL SCA



Data LayerService LayerUI Layer

BPEL

C

rules

BI

BAM

A

EJB3

ADF

BC

JAX-

WS

JSF Page

JSF Page

ESB

Adaptive Business Applications



The SOA Platform

Modular and Extensible Enterprise Service Bus

SCA Framework

Process

Packaged Solutions

Human

Task

Business

Rule

Business

Event

Service

Registry

IDE

SLA

Monitoring

Management

Security

300+

Application

Adapters

Java

.NETWeb

ServicesData Hubs

Portal

B2B

Business

Editor

Analytics

Metadata

Web 2.0 Office Mobile

BAMCEPQ



Service FabricSCA, ESB, Micro Kernel

JMSJMSSOAPSOAP

HTTPHTTPSOAPSOAP

TransformsTransforms

Service Service EnginesEngines

Pluggable

Loan ServiceLoan ServiceProviderProvider

ApprovalApprovalRuleRule

BusinessBusiness Rules Rules

HTTPHTTPRESTREST

RoutingRouting



Service OrchestrationBPEL & Workflow

JMSJMSSOAPSOAP

HTTPHTTPSOAPSOAP

BPELBPEL

WorkflowWorkflow

HTTPHTTPRESTREST

RoutingRouting


ManagerManagerApprovalApproval

Financials Financials GL ProcessGL Process



Business Events

New

Order

Event

Order

Capture

Process

Order

Fulfillmen

t

Process

Stock

Forecast

er

High

Demand

Alert

Raise

Subscribe

Raise

CEPQ

BAM

Dashboard

Why?

• Integration Points between

Business Activities

• Foundation of Real-Time

Analytics

• Higher Affinity with Business

Modeling

What is Needed?

• Event Definition Language

• CEP Query Language

• Event Extensions to SCA



Business

RulesBPEL BAM

Human

Task… CEPQ Scheduler

Loan

Process APR

Rule

Manager

Review

Task

EBS

Customer

View

Monthly

Activation

UDDI

Meta

Data

HTTP

SOAP

.NET

Payment

Calculator

JCA

Adapters

SDO

ADF/BC

Service/Event Delivery API

Policy Enforcement Point

SCA Composite

Policy Enforcement



Policy Management



Service SecurityWS-Security, WS-Trust, SAML

JMSJMSSOAPSOAP

HTTPHTTPSOAPSOAP

AccessAccessControlControl

HTTPHTTPRESTREST

AuthenticateAuthenticate


SecuritySecurityMonitoringMonitoring

EncryptionDecryption

Signature Verification

IntrusionIntrusionDetectionDetection

IdentityManagement



JMSJMSSOAPSOAP

HTTPHTTPSOAPSOAP

FailoverFailoverPolicyPolicy

HTTPHTTPRESTREST

QOS PolicyQOS Policy


SecuritySecurityPolicyPolicy

Service ManagementWS-Policy, Web Services Management



BPEL PM with Business Rules

BPEL Process Manager and Rules together enableagile and adaptive business processes

Key benefits:

Complementary technologies

• BPEL for orchestration of services, systems, people & partners

• Rules focus on decision making and policies

Declarative specification of constantly changing businesspolicies and regulations

Enables business users to participate in businessprocesses

Centralized policy management across the organization



PORTAL

BPEL + RulesPORTAL

Web S

erv

ices

Inte

rface:

XM

L,

SO

AP,

WSD

L,

WSIF

Worklist

Application

Approval Task

DecisionService

RulesEngine

Rule Author

Credit RatingRules

LOAN FLOW BPEL PROCESS

receive

getPhone

invoke

select

receive

review

Auto Loan

end

5-15 min

getRating

invoke

DecisionService

RulesEngine

Loan AdvisorRules



SOA Platform IDE


Bill Jones — Next Generation of SOA Development Page 46

Agenda


Primitive Services

Composite Services


SOA Platform

Conclusions



Conclusions

SOA marks transition to higher level ofabstraction for

System language programmers

Business process developers

IT Administrators

Challenges

Policy in a heterogeneous world

Trend toward simplicity despite multipletechnologies



AQ&Q U E S T I O N SQ U E S T I O N S

A N S W E R SA N S W E R S

Colorado Software Summit: October 22 – 27, 2006 ... EBS Customer View ... Colorado Software...

Documents

Transcript of Colorado Software Summit: October 22 – 27, 2006 ... EBS Customer View ... Colorado Software...