SCA Tutorial Part1 Asia-Updated

SCA
Service Component Architecture

(SCA) Tutorial : Part 1
Mike Edwards - IBM
Anish Karmarkar – Oracle
Jim Marino – BEA
OSOA Collaboration | 30th May 2007 | SOA Roadmap

SCA
Service Component Architecture

A model for building components, assembling them into
applications, and deploying them to various runtime
environments
Components can be built from new or existing code using
SOA principles
vendor-neutral – supported across the industry
language-neutral – components written using any language
technology-neutral – use any communication protocols and
infrastructure to link components
OSOA Collaboration | SOA Roadmap

SCA
Part 1 Outline
Composite example
Implementation using Java component implementation
Introduction to SCA concepts
Advanced composition – nested composites
Packaging and deployment
Extension points
Component Implementation types
Spring Framework
BPEL
Demonstrations

SCA
Part 2 Outline
Bindings
Web service binding
JMS binding
EJB session bean binding
Policies – Intents and Policy Sets

Security
Reliable Messaging
Transactions

SCA
AccountsComposite
Example SCA assembly External
Banking
Payment Payments
Reference
Service Component
Order
Processing OrderProcessing
Component
Service Accounts
Ledger
Component
EventLog
Component
External
WarehouseComposite Warehouse
Reference
Warehouse
Warehouse Warehouse
Broker
Service Component
Component
EventLog
Reference

SCA
Simple Example
bigbank.accountcomposite
Reference
StockQuote
Service
Service AccountService
AccountService Component
AccountData
Service
Component

SCA
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0" XML Representation

name="bigbank.accountcomposite" >
<service name="AccountService“ promote=“AccountServiceComponent”>

<interface.java interface="services.account.AccountService"/>
<binding.ws port="http://www.bigbank.com/AccountService#
wsdl.endpoint(AccountService/AccountServiceSOAP)"/>
</service>
<component name="AccountServiceComponent">
<implementation.java class="services.account.AccountServiceImpl"/>
<property name=“currency”>EURO</property>
<reference name="accountDataService" target="AccountDataServiceComponent"/>
<reference name="stockQuoteService"/>
</component>
<component name="AccountDataServiceComponent">
<implementation.java class="services.accountdata.AccountDataServiceImpl"/>
</component>
<reference name="StockQuoteService“ promote=“AccountServiceComponent/stockQuoteService”>

<interface.java interface="services.stockquote.StockQuoteService"/>
<binding.ws port="http://www.quickstockquote.com/StockQuoteService#
wsdl.endpoint(StockQuoteService/StockQuoteServiceSOAP)"/>
</reference>
</composite>

SCA
Java Implementation Example:

Service Interface
Interface is callable
package org.example.services.account; remotely
eg. as a Web service
@Remotable
public interface AccountService {
public AccountReport getAccountReport(String customerID);

}

SCA
Java Implementation Example – Implementation (part 1)

package org.example.services.account;
import org.osoa.sca.annotations.*; Defines the

service interface
@Service(AccountService.class)
public class AccountServiceImpl implements AccountService {
private String currency = "USD";

private AccountDataService accountDataService; Defines a property
private StockQuoteService stockQuoteService; “currency”
public AccountServiceImpl(
@Property("currency") String currency,
@Reference("accountDataService") AccountDataService dataService,
@Reference("stockQuoteService") StockQuoteService stockService) {
this.currency = currency;
this.accountDataService = dataService;
this.stockQuoteService = stockService;
} // end constructor
Defines references
“accountDataService”
and
“stockQuoteService”

SCA
Java Implementation Example – Implementation (part 2)
public AccountReport getAccountReport(int customerID) Get the basic account

throws AccountDataUnavailableException { report using the
account data service
AccountReport accountReport =
accountDataService.getAccountReport(customerID);
List<Stock> stocks = accountReport.getStocks(); Obtain up to date
stock values using the
List<StockValues> stockValues = stock quote service
stockQuoteService.getValues( stocks, currency );
accountReport.setStockValues( values );
return accountReport;
} Update the account
} // end class report with the latest
stock values

SCA
SCA Java Implementation principles

Code only to business interfaces
“Don’t program to SCA, just program…”
Use Java idioms
Minimal middleware APIs used only in special cases
Principles apply to other languages
Components declare both the services they offer and references

to other services they need
Injection of required service References and Property values

via constructor
via setter methods
via direct field injection
Java annotations for SCA elements

services, references, properties
+ more advanced features such as intents, bindings
SCA
SCA Concepts: Component

Properties
Implementation
Services configuration attribute
Business function
provided to clients
through an interface
contract
Component
…
…
References
Implementation
dependency on an
Implementation external service
The implementation code
for the component. In any
one of many languages,
eg. Java, BPEL, C++, PHP,
Composite….

SCA
SCA Concepts: Wire, Interface, Binding

Wire
Connects services to references
Component Component
…
Interface Binding
Description of business functions of services Access mechanism used by services and
& references. For example, Java interface, references. For example, Web services binding,
WSDL 1.1 portType, WSDL 2.0 interface JMS binding, EJB Session bean binding

SCA
Bigbank Composite - multiple components,

service, reference & property
Reference
StockQuote
Service
AccountData
Service
Component

SCA
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
targetNamespace="http://example.org"
<service name="AccountService" promote="AccountServiceComponent">

<binding.ws port="http://www.example.org/AccountService#
wsdl.endpoint(AccountService/AccountServiceSOAP)"/>
</service>
<reference name="StockQuoteService"/>
<reference name="AccountDataService"
target="AccountDataServiceComponent/AccountDataService"/>
<property name="currency">EURO</property>
StockQuote
</component>
Reference
StockQuote
Service
<component name="AccountDataServiceComponent"> AccountService Component
AccountData
<implementation.bpel process=“QName"/> Service
Component
<service name="AccountDataService">
<interface.java interface="services.accountdata.AccountDataService"/>
</service>
</component>
<reference name=“StockQuoteService" promote="AccountServiceComponent/StockQuoteService">

<binding.ws port="http://example.org/StockQuoteService#
wsdl.endpoint(StockQuoteService/StockQuoteServiceSOAP)"/>
</reference>
<composite>
SCA
Reuse in SCA
Inclusion
Recursive composition
Implementation reuse through configurable components
Reusable services through composite references

SCA
ComponentType
Describes component implementation type details
Services
References
Properties
Extensibility elements
Can be introspected from the implementation or specified in

an XML sidefile
Typically will be introspected from the implementation
Component implementations may use annotations to specify
componentType information
• eg Java

SCA
Java Implementation Example: componentType
<componentType xmlns="http://www.osoa.org/xmlns/sca/1.0"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<service name="AccountService">
</service>
<reference name="accountDataService">
</reference>
<reference name="stockQuoteService">
</reference>
<property name="currency" type="xsd:string"/>
</componentType>

SCA
Top-Down Design: constrainingType

constrainingType
Implementation independent
Specifies the shape -- constraints in terms of
services/references/properties
composites, components, componentType and implementations can
be constrained using the “constrainingType” attribute
Allows an architect to specify constrainingTypes which can be used
by developers as a template
SCA provides runtime validation of artifacts with its constrainingType

SCA
constrainingType Example
<constrainingType name=“myCT” ... >
<service name="MyValueService">
<interface.java interface="services.myvalue.MyValueService"/>
</service>
<reference name="customerService">
<interface.java interface="services.customer.CustomerService"/>
</reference>
<property name="currency" type="xsd:string"/>
</constrainingType>
<component name="MyValueServiceComponent" constrainingType="myns:myCT” >

<implementation.bpel process=“..."/>
<service name=“MyValueService”>
<interface.java interface="services.myvalue.MyValueService"/>
<binding.jms .../>
</service>
<reference name="customerService" target="CustomerService">
<binding.ws ...>
</reference>
</component>

SCA
Recursive Composition
Composites and Implementations look the same
services
references
properties
composites have associated ComponentType
“Recursive composition” = nesting of composites

composite can be a component implementation in a higher level
composite
promotes reuse of assemblies
<implementation.composite../> as component implementation
component can be implemented by “atomic” implementation or by
composite

SCA
Implementing AccountDataService Using A

Composite
Reference
StockQuote
Service
AccountData
Service
Component
implements
bigbank.accountdata
Service
AccountData Logging
AccountDataService

SCA
bigbank.AccountData Composite
name="bigbank.AccountData" >
<service name="AccountDataService" promote="AccountData">

<interface.java interface="services.accountdata.AccountService"/>
</service>
<implementation.bpel process=“..."/>
<reference name=“LoggingService"
target=“LoggingServiceComponent"/>
</component>
<component name=“LoggingServiceComponent">
<implementation.spring location=“..."/>
</component>
<composite>

SCA
AccountDataService ComponentType
<componentType>
<interface.java
interface="services.accountdata.AccountDataService"/>
</service>
</componentType>

SCA
bigbank.account Composite (recursion)

<service name="AccountService" promote="AccountServiceComponent">
<binding.ws port="http://..."/>
</service>
<reference name="StockQuoteService"/>
<reference name="AccountDataService"
target="AccountDataServiceComponent/AccountDataService"/>
</component>
<implementation.composite name=“bb:bigBank.AccountData"/>
<implementation.bpel process=“QName"/>
</service>
</component>
<reference name="" promote="AccountServiceComponent/StockQuoteService">

<binding.ws port="http://..."/>
</reference>
<composite>
SCA
Packaging and Deployment: Domains

Composites deployed, configured into SCA Domain
Defines the boundary of visibility for SCA
Typically an area of functionality controlled by single
organization/division
• E.g.: accounts
Configuration represented by virtual composite

potentially distributed across a network of nodes
contains components, services, references, wires
configured using composites
Composites make deployment simpler

individual composites created, deployed independently
may contain only wires or components or externally provided
services or references
Abstract services provided for management of the domain

SCA
Packaging and Deployment: Contributions

Contributions hold artifacts available for use in the Domain
Package containing artifacts necessary for SCA
SCA defined artifacts
• E.g.: composites, constrainingType, etc
Non-SCA defined artifacts
• E.g.: WSDL, XML schema, Java classes, object code etc
Packaging must be hierarchical
Metadata included in the “META-INF” directory
<contribution xmlns=http://www.osoa.org/xmlns/sca/1.0>
<deployable composite="xs:QName"/>*
<import namespace="xs:String" location=”xs:AnyURI”?/>*
<export namespace="xs:String"/>*
</contribution>
Interoperable packaging format: ZIP

Other formats possible: filesystem directory, OSGi bundle, JAR file

SCA
SCA Runtime Example Runtime Topology
SCA JEE Containers SCA Java Containers SCA CPP Containers

…
SCA PHP Container SCA BPEL Container
Assigned to be
hosted by SCA
Deployment Java container Assigned to be
hosted by SCA
Mapping CPP container
SCA Domain
bigbank.accountmanagement
bigbank.stockquote
Service Compositions

SCA
Extensibility in SCA
Designed for extensibility
Extensible artifacts:
Implementation types
• <implementation.*>
Interface types
• <interface.*>
Binding types
• <binding.*>

SCA
Assembly: Summary
SCA Assembly models systems composed of reusable services
A model for service-based system:
construction
assembly
deployment
Heterogeneity
Multiple languages
Multiple container technologies
Service access methods
Metadata driven
SCA
Component Implementation Types

SCA supports a number of programming models and technologies
for authoring components
The SCA Java Implementation type based on POJOs

Spring
EJB
BPEL
C++
PHP
In the future, potentially others

SCA
Spring Framework Component Implementation

SCA = integration at coarse-grained level
Spring = integration at fine grained level
Spring application context used as component implementation
SCA component implemented by a collection of Spring beans
Two ways:
1. No SCA-related metadata in Spring
2. SCA-related metadata specified as Spring beans
• sca:service
• sca:reference
• sca:property
Uses <implementation.spring ...”/>
<implementation.spring location="/spring/application-context/"/>
...
</component>

SCA
Bigbank implementation using Spring

AccountService component
<beans>
<bean id=“FirstBean”>
<property name="aPropertyName" ref=“SecondBean"/>
</bean>
<bean id=“SecondBean">
<property name="SQRef" ref="StockQuoteService"/>
<property name="ADRef" ref="AccountDataService"/>
</bean>
<sca:service name="AccountService"
type="bigbank.account.AccountService" target=“FirstBean"/>
<sca:reference name="StockQuoteService"
type="bigbank.account.StockQuoteService"/>
<sca:reference name="AccountDataService"
type="bigbank.account.AccountDataService"/>
<beans>
SCA
BPEL Component Implementation

SCA and BPEL are complementary
BPEL provides business sequencing & orchestration of services
SCA provides a compositional view of interconnection of service components
Supports WS-BPEL 1.1 and 2.0
Uses WSDL interfaces
SCA service = partnerLink with single role belonging to the BPEL process
SCA reference = partnerLink with single role belonging to partner
When partnerLink defines two roles, directionality defines whether it is a service

or a reference

SCA
BPEL Component Implementation (cont.)

SCA extensions for BPEL (not mandatory)
Attribute “sca:property” on a variable declaration defines a property
Element “sca:multiReference” on a variable declaration defines a multivalued
reference (multiple partners for one partnerLink, called in sequence)
Uses <implementation.bpel process=“bpel-process-QName”/>
<implementation.bpel process=“myns:Process1"/>
...
</component>

SCA
Summary
SCA models systems built using a Service Oriented

Architecture
supports Service Implementation, Service Assembly
open to many kinds of service implementation
open to many types of service access
declarative intent & policy approach to application of

Security & Transaction

SCA
Demonstrations
IBM Demo:
HelloWorld sample with a callback (SCA V0.95)
Oracle Demos:
Oracle Fusion Middleware (SCA 0.95) Overview
Simple SayHello Example Using Jdeveloper (Synchronous)
Simple HelloWorld Example (Asynchronous)
OrderBooking Application
BEA Demo
Based on the Fabric3 open source SCA implementation
(www.fabric3.org)
Component provisioning in distributed SCA domain across multiple
JVMs
Java SCA 1.0 programming model support

SCA
IBM Demo: HelloWorld Sample with Callback

Service
WSDL PortType
HelloWorldWSClient
JSP
HelloWorldService
Component Reference
Hello Service
Implementation
Binding - Java
Web Service
Service
Implementation WSDL PortType

- Java
HelloWorldWS
HelloWorldService
Service Component
Hello Service
Binding
Web Service

SCA
IBM Demo: HelloWorld Sample with Callback - Client

xmlns:system="http://tuscany.apache.org/xmlns/system/1.0-SNAPSHOT"
name="helloworldwsclient">
<component name="HelloWorldServiceComponent">
<implementation.java class="helloworld.HelloWorldServiceComponent"/>
<reference name="helloWorldService">HelloWorldService</reference>
</component>
<reference name="HelloWorldService">
<interface.wsdl xmlns:wsdli="http://www.w3.org/2006/01/wsdl-instance"
interface="http://helloworld#wsdl.interface(HelloWorld)"
callbackInterface="http://helloworld#wsdl.interface(HelloWorldCallback)"
wsdli:wsdlLocation="http://helloworld wsdl/helloworld.wsdl" />
<binding.ws endpoint="http://helloworld#
wsdl.endpoint(HelloWorldService/HelloWorldSoapPort)"
location="wsdl/helloworld.wsdl" />
</reference>
</composite>

SCA
IBM Demo: HelloWorld Sample with Callback - Service

xmlns:wsdli="http://www.w3.org/2006/01/wsdl-instance"
name="helloworldws">
<service name="hwwsasync">
<interface.wsdl xmlns:wsdli="http://www.w3.org/2006/01/wsdl-instance"
interface="http://helloworld#wsdl.interface(HelloWorld)"
callbackInterface="http://helloworld#wsdl.interface(HelloWorldCallback)"
wsdli:wsdlLocation="http://helloworld WEB-INF/wsdl/helloworld.wsdl" />
<binding.ws endpoint="http://helloworld#
wsdl.endpoint(HelloWorldService/HelloWorldSoapPort)"
location="WEB-INF/wsdl/helloworld.wsdl" />
<reference>HelloWorldServiceComponent</reference>
</service>
<component name="HelloWorldServiceComponent">
<implementation.java class="helloworld.HelloWorldImpl" />
</component>
</composite>

SCA
Oracle Demo: Fusion (SCA 0.95) Overview
Service Engines
Scheduler
BPEL Routing Rules
…
Bindings
SCA Runtime MDS

HTTP (Fusion Middleware)
Normalized message bus
JMS Component lifecycle management
Inter-component “wiring”
Policy enforcement (binding UDDI
JCA independent)
… Monitoring
J2EE + Spring

SCA
Oracle Demo: SayHello Example

(Synchronous)
<componentType ...>
<service name="client">
Service <interface.wsdl
WSDL PortType interface="http://xmlns.oracle.com/SayHello#
wsdl.interface(SayHello)"/>
</service>
</componentType>
SayHello
<composite name="SayHello“ ... >
<service name="SoapService1">
Service SayHello <interface.wsdl
SoapService1 Component
interface="http://xmlns.oracle.com/SayHello#
wsdl.interface(SayHello)"/>
<binding.ws
port="http://xmlns.oracle.com/SayHello#
wsdl.endpoint(SoapService1/SayHello_pt)"/>
</service>
<component name="SayHello">
<implementation.bpel src="SayHello.bpel"/>
</component>
Binding
Web Service
<wire>
<source.uri>SoapService1</source.uri>
<target.uri>SayHello/client</target.uri>
Implementation </wire>
- BPEL </composite>
SCA
Oracle Demo: HelloWorld Example

(Asynchronous)
<componentType ...>
Service <interface.wsdl
WSDL PortType interface="http://samples.otn.com/helloworld#
wsdl.interface(HelloWorld)"
callbackInterface="http://samples.otn.com/helloworld#
wsdl.interface(HelloWorldCallback)"/>
</service>
</componentType>
HelloWorld
<composite name="HelloWorld“ ...>
HelloWorld <interface.wsdl
Service
SoapService1 Component interface="http://samples.otn.com/helloworld#
wsdl.interface(HelloWorld)"
callbackInterface="http://samples.otn.com/helloworld#
wsdl.interface(HelloWorldCallback)" />
<binding.ws port="http://samples.otn.com/helloworld#
wsdl.endpoint(HelloWorld/HelloWorld)"/>
</service>
<component name="HelloWorld">
<implementation.bpel src="HelloWorld.bpel"/>
Binding </component>
Web Service <wire>
<source.uri>client</source.uri>
Implementation <target.uri>HelloWorld/client</target.uri>
- BPEL </wire>
</composite>
SCA
Oracle Demo: OrderBooking Application binding.jca
ApproveOrder OrderFulfillment Order

Component Component
.
.
. Implementation.workflow Implementation.mediator .
OrderProcessor
Component .
.
EventLogger SelectManufacturer
Component Component Implementation.bpel
binding.ws
ApprovalRequired
Implementation.eventAgent Component Implementation.decision

SCA
<composite name="OrderProcessing" ...>

<service name="Client">
<interface.wsdl interface="http://www.globalcompany.com/ns/OrderBooking#
wsdl.interface(SOAOrderBooking)"/>
<binding.ws port="http://www.globalcompany.com/ns/OrderBooking#
wsdl.endpoint(OrderBooking/OrderBookingPort)"/>
</service>
<component name="OrderFulfillment">
<implementation.mediator src="OrderFulfillment.mplan"/>
</component>
<component name="ApproveOrder">
<implementation.workflow src="ApproveOrder.task"/>
</component>
<component name="ApprovalRequired">
<implementation.decision src="DecisionService.decs"/>
</component>
<component name="SelectManufacturer">
<implementation.bpel src="SelectManufacturer.bpel"/>
</component>
<component name="EventLogger">
<implementation.eventAgent
className="oracle.integration.platform.blocks.event.agent.LoggingEventAgent"/>
<business-events>
<subscribeAll consistency="guaranteed"/>
</business-events>
</component>
<reference name="Order">
<interface.wsdl interface="http://xmlns.oracle.com/pcbpel/adapter/db/Order/#
wsdl.interface(Order_ptt)"/>
<binding.jca config="OrderService_db.jca"/>
</reference>
...
</composite>
SCA
BEA/Fabric3 Demo
Open source CodeHaus Foundation project (www.fabric3.org)
Apache Licensed
Built around a small embeddable kernel that is highly extensible
Less than 1MB
Extension ecosystem, e.g. Spring, OpenJPA
Focused on
Implementation quality
SCA 1.0 support
“Agile” development experience and SDK
Management of distributed SCA domains
Federated deployment to multiple runtime types
WebLogic
Manage and provision Cluster
components
Servlet
SCA Domain Engine •Domains are heterogenous
Controller
•Fabric3 may be embedded in a
OSGi variety of containers
Other
Containers

SCA
BEA/Fabric3 Demo
Provision and deploy a Calculator Composite

Calculator service wired to Add, Subtract, Multiply and Divide services
Instantiate components
Provision components 4
on runtime nodes
3 to multiple runtime
nodes Service Node
SCA Domain
Process the composite,
2 resolve wires and
allocate to runtime
nodes
1 Deploy the SCA

composite
SCA Composite

SCA
Thank you!
Questions?
OSOA Collaboration | 30th May 2007 | SOA Roadmap

SCA Tutorial Part1 Asia-Updated

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

SCA Tutorial Part1 Asia-Updated

Încărcat de

Drepturi de autor:

Formate disponibile

SCA

Service Component Architecture

OSOA Collaboration | 30th May 2007 | SOA Roadmap

Service Component Architecture

OSOA Collaboration | SOA Roadmap

OSOA Collaboration | SOA Roadmap

Policies – Intents and Policy Sets

OSOA Collaboration | SOA Roadmap

OSOA Collaboration | SOA Roadmap

OSOA Collaboration | SOA Roadmap

<composite xmlns="http://www.osoa.org/xmlns/sca/1.0" XML Representation

<service name="AccountService“ promote=“AccountServiceComponent”>

<reference name="StockQuoteService“ promote=“AccountServiceComponent/stockQuoteService”>

OSOA Collaboration | SOA Roadmap

Java Implementation Example:

public AccountReport getAccountReport(String customerID);

OSOA Collaboration | SOA Roadmap

Java Implementation Example – Implementation (part 1)

import org.osoa.sca.annotations.*; Defines the

private String currency = "USD";

OSOA Collaboration | SOA Roadmap

Java Implementation Example – Implementation (part 2)

public AccountReport getAccountReport(int customerID) Get the basic account

OSOA Collaboration | SOA Roadmap

SCA Java Implementation principles

Components declare both the services they offer and references

Injection of required service References and Property values

Java annotations for SCA elements

SCA Concepts: Component

OSOA Collaboration | SOA Roadmap

SCA Concepts: Wire, Interface, Binding

OSOA Collaboration | SOA Roadmap

Bigbank Composite - multiple components,

OSOA Collaboration | SOA Roadmap

<service name="AccountService" promote="AccountServiceComponent">

<reference name=“StockQuoteService" promote="AccountServiceComponent/StockQuoteService">

OSOA Collaboration | SOA Roadmap

Can be introspected from the implementation or specified in

OSOA Collaboration | SOA Roadmap

Java Implementation Example: componentType

<property name="currency" type="xsd:string"/>

OSOA Collaboration | SOA Roadmap

Top-Down Design: constrainingType

OSOA Collaboration | SOA Roadmap

<component name="MyValueServiceComponent" constrainingType="myns:myCT” >

OSOA Collaboration | SOA Roadmap

“Recursive composition” = nesting of composites

OSOA Collaboration | SOA Roadmap

Implementing AccountDataService Using A

OSOA Collaboration | SOA Roadmap

<service name="AccountDataService" promote="AccountData">

OSOA Collaboration | SOA Roadmap

OSOA Collaboration | SOA Roadmap

bigbank.account Composite (recursion)

<reference name="" promote="AccountServiceComponent/StockQuoteService">

Packaging and Deployment: Domains

Configuration represented by virtual composite

Composites make deployment simpler

Abstract services provided for management of the domain

Packaging and Deployment: Contributions

Interoperable packaging format: ZIP

OSOA Collaboration | SOA Roadmap

SCA Runtime Example Runtime Topology