www oasis-open org SCA Overview Sanjay Patil

www. oasis-open. org SCA Overview Sanjay Patil – SAP Mike Edwards - IBM Open. CSA Member Section – Service Component Architecture 1

Agenda n n n A little history SCA and SOA SCA scenarios SCA specifications OASIS SCA TCs l n major challenges Related & future work Open. CSA Member Section – Service Component Architecture 2

A little history n n n “…once upon a time, some programmers thought it would be good to have a programming model to support Service Oriented Architecture…” That model is SCA Industry collaboration grew from just 2 companies to 18 today l n published 1. 0 SCA specifications, March 2007 SCA specifications now ready for standardization in OASIS Open. CSA Member Section – Service Component Architecture 3

Open. CSA Member Section – Service Component Architecture 4

Other Standards Bodies SCA V 0. 9 SDO V 1 SCA V 0. 95 SCA V 1. 0 SDO V 2. 01 Finalization of further SCA Specs Further complementary incubation SDO V 2. 1 Nov 2005 July Press 2006 Announcement of Project Launch New Partners Announced March 2007 Specs 1. 0 Submission for Standardization Early Adopters SDO TC SCA TC’s System Vendors ISVs Customer Value Adoption Time Line Summary Open. CSA Member Section – Service Component Architecture 5

Standardization n n OASIS to guide the standardization of Specifications from the collaboration in the Open. CSA Member Section Structure l n n 6 Technical Committees (TCs) to address one or more Specifications from the collaboration SDO V 2. 1 for Java will be completed in the JCP as JSR 235 Specification development to continue within OSOA collaboration for technologies not yet ready for standardization Open. CSA Member Section – Service Component Architecture 6

Agenda n n n A little history SCA and SOA SCA scenarios SCA specifications OASIS SCA TCs l n major challenges Related & future work Open. CSA Member Section – Service Component Architecture 7

What are SCA and SDO? n Service Component Architecture l l n an executable model for building service-oriented applications as composed networks of service components “how to build composite service applications” Service Data Objects l l a unified model for the handling of (service) data irrespective of its source or target “how to handle data in a services environment” Open. CSA Member Section – Service Component Architecture 10

Service Component Architecture (SCA): Simplified Programming Model for SOA n n model for: building service components assembling components into applications deploying to (distributed) runtime environments l l Service components 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 Open. CSA Member Section – Service Component Architecture 11

Key benefits of SCA n Loose Coupling: components integrate without need to know how others are implemented n Flexibility: components can easily be replaced by other components n Services can be easily invoked either synchronously or asynchronously n Composition of solutions: clearly described n Productivity: easier to integrate components to form composite application n Heterogeneity: multiple implementation languages, communication mechanisms n Declarative application of infrastructure services n Simplification for all developers, integrators and application deployers Open. CSA Member Section – Service Component Architecture 12

SCA assembly RMI/IIOP Accounts. Composite Payment Service Order Processing Service Payments Component External Banking Reference Order. Processing Component Accounts Ledger Component SOAP/HTTP Java EE BPEL Multi-level composition External Warehouse Reference Warehouse. Composite Warehouse Service Warehouse Broker Component Mixed: - technologies - app locations Warehouse Component JMS C++ Open. CSA Member Section – Service Component Architecture Shipping Reference 13

Agenda n n n A little history SCA and SOA SCA scenarios SCA specifications OASIS SCA TCs l n major challenges Related & future work Open. CSA Member Section – Service Component Architecture 14

Bottom-up Composition Select a set of existing component implementations for building the new composite Configure the component properties Composite Draw internal wires Wrap the components in a composite and configure external services/references Hand off the composite to Deployer Open. CSA Member Section – Service Component Architecture properties services references 15

Properties Top-down Composition Start with gathering requirements for the top-level composite Composite Ref Service Define the services/references and properties for the composite Ref Break down the composite into individual components and wires between them Recursively break down each component Hand off the individual component contracts to developers for implementation Open. CSA Member Section – Service Component Architecture 16

Heterogeneous Assembly PHP BPEL Java Legacy C++ Components in the same composite share a common context for many aspects such as installation, deployment, security settings, logging behavior, etc. Open. CSA Member Section – Service Component Architecture 17

Implementation Reuse – By Configuration Select an existing component implementation Properties Configure its behavior (via setting props, refs) to match the current requirements Open. CSA Member Section – Service Component Architecture … Deploy the component implementation - Multiple instances of the same implementation may be running simultaneously … E. g. Configure multiple instances of product pricing component, each with different currency, tax rate, discount charts, etc. Services References Component Implementation - Java - BPEL - Composite 18

Deployment Flexibility Deployer chooses and configures communication mechanisms for services/references without having to modify the component implementation WS Clients SOAP/HTTP WS Binding Properties References Services JMS Clients JMS Binding Open. CSA Member Section – Service Component Architecture ERP Service JCA Binding 19

Abstract policy decleration Developer Deployer 1 SCA Assembly 2 Policy Administrator 3 4 5 0 Repository SCA Runtime SCA policy. Sets 0. 1. 2. 3. 4. 5. Registry Policy Administrator authors SCA policy. Sets with concrete policies Developer specifies intents on SCA assembly Developer hands over SCA assembly to Deployer configures SCA assembly by assigning SCA policy. Sets (could be automated) Deployer deploys configured SCA Assembly to SCA Runtime Deployer updates Registry Open. CSA Member Section – Service Component Architecture 20

Agenda n n n A little history SCA and SOA SCA scenarios SCA specifications OASIS SCA TCs l n major challenges Related & future work Open. CSA Member Section – Service Component Architecture 21

SCA Technology How do I define, use and administer policies for nonfunctional aspects (Qo. S, etc)? SCA Policy Framework Spec SOAP/ HTTP How do I define, configure and assemble components to create composites? SCA Assembly Spec Composite Component JMS How do I configure SCA services/references to use SOAP/HTTP or JMS or JCA, … SCA WS Binding Spec, … Open. CSA Member Section – Service Component Architecture JCA How do I develop SCA components in BPEL? Or in Java? Or C++, PHP, … SCA BPEL Client & Impl Spec, … 22

The SCA Specifications Assembly Policy Framework Implementation Languages Bindings Security Java JEE Web services RM Spring BPEL JMS Transactions Open. CSA Member Section – Service Component Architecture C++ JCA 23

Agenda n n n A little history SCA and SOA SCA scenarios SCA specifications OASIS SCA TCs l n major challenges Related & future work Open. CSA Member Section – Service Component Architecture 24

OASIS SCA Technical Committees n Open. SCA Member Section l l l SCA Assembly TC SCA Bindings TC SCA Policy TC SCA J TC SCA C-C++ TC SCA BPEL Open. CSA Member Section – Service Component Architecture 25

Work of the SCA TCs n Produce OASIS standard versions of SCA specifications l l l n conformance statements mandatory vs optional portability, interoperability Test suites l define test suites to check conformance Open. CSA Member Section – Service Component Architecture 26

Challenges n What is a good test suite for SCA? n Coordination between TCs Open. CSA Member Section – Service Component Architecture 27

Agenda n n n A little history SCA and SOA SCA scenarios SCA specifications OASIS SCA TCs l n major challenges Related & future work Open. CSA Member Section – Service Component Architecture 28

Possible Future work n n n C specification COBOL specification REST binding(s) l JSON, ATOM, … Open. CSA Member Section – Service Component Architecture 29

Related Work n OASIS SDD n Management l WSDM, SML, … n WS-* specifications n OASIS SOA RM l other RM’s Open. CSA Member Section – Service Component Architecture 30

Summary n OASIS SCA l l l n an exciting challenge major effort over the next year aim to appeal to a very wide audience 6 SCA TCs to run & coordinate! Open. CSA Member Section – Service Component Architecture 31