+ All Categories
Home > Documents > Comp 104

Comp 104

Date post: 03-Jun-2018
Category:
Upload: koizak
View: 219 times
Download: 0 times
Share this document with a friend
27
8/12/2019 Comp 104 http://slidepdf.com/reader/full/comp-104 1/27 COMP104 Using SCA for Modular Application Development  Iliyan Nenov, SAP NetWeaver Product Management Peter McNulty, SAP NetWeaver Product Management
Transcript
Page 1: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 1/27

COMP104

Using SCA for

Modular Application Development 

Iliyan Nenov,SAP NetWeaver Product Management

Peter McNulty,SAP NetWeaver Product Management

Page 2: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 2/27

Goal

© SAP 2008 / SAP TechEd 08 / COMP104 Page 3

>GOAL 

Learn about the concepts of Service Component

 Architecture and see some practical use cases for how

it can be used for modular based development.

Page 3: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 3/27

© SAP 2008 / SAP TechEd 08 / COMP104 Page 4

1. Introduction

1.1. Business Value

1.2. Technical Overview

2. Use-Cases Where SCA Can Fit2.1. Bottom-Up Composition

2.2. Top-Down Composition

2.3. Heterogeneous Assembly

2.4. Implementation Reuse

2.5. Flexible Deployment3. SCA at SAP

4. Questions and Answers

Agenda

Page 4: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 4/27

SCA Business Value

© SAP 2008 / SAP TechEd 08 / COMP104 Page 5

 Simplification Easy breakdown of complex problems into set of component interfaces

 Integration of complex middleware technologies via a common, simplified model

 Development Productivity Single model leads to less training

 Decreased design time work more focus on business logic

 Business Agility Faster composition, decreased time-to-market

 Increased flexibility in accessing business logic via different protocols

For SAP, the business value in SCA is in the ability

to implement flexible business processes.

Page 5: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 5/27

© SAP 2008 / SAP TechEd 08 / COMP104 Page 6

Supporters of Service Component Architecture

Page 6: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 6/27

© SAP 2008 / SAP TechEd 08 / COMP104 Page 7

1. Introduction

1.1. Business Value

1.2. Technical Overview

2. Use-Cases Where SCA Can Fit2.1. Bottom-Up Composition

2.2. Top-Down Composition

2.3. Heterogeneous Assembly

2.4. Implementation Reuse

2.5. Flexible Deployment3. SCA at SAP

4. Questions and Answers

Agenda

Page 7: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 7/27

SCA Assembly

 –  Deployment Descriptors “on Steroids” 

© SAP 2008 / SAP TechEd 08 / COMP104 Page 8

 An SCA assembly is basically a bag of components, connected by wires 

Configure the SCA aspects (@Reference’s and @Property’s) 

SCA assembly defined using XML, SCDL (pronounced „skiddle“) 

Composite A 

Component A Service 

Component B 

Wire Promote Promote 

Reference 

Property setting 

Properties 

Page 8: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 8/27

SCA Technical Overview

 –  Basic Concepts

© SAP 2008 / SAP TechEd 08 / COMP104 Page 9

component

bindingbinding

interface interface

Implementation Types

 Abstraction of Service Component Implementation

Define rules for Component Type derivation

Composites

Provide grouping and encapsulation

Built-in implementation type (recursive assembly)

Used in deployment and modularization

Policies

Govern interaction and implementation contract

Deployment

 Abstraction of packaging (contribution)

Domain-level assembly

composite

comp2comp1

component

domain composite

Contribution 1

deployment composite

composite

comp2comp1

component

Contribution

n

...

component

Service Components

Services, References, and Properties Interfaces and Bindings

Implementation

component

bindingbinding

interface interface

implementation

policy

Implementation

component

bindingbinding

interface interface

interaction

policyinteraction

policy

Page 9: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 9/27

SCA is the Scale-Out Model for Java EE

© SAP 2008 / SAP TechEd 08 / COMP104 Page 11

 We want to scale-out from JavaEE, not break it!

 Preserve investment in Java EE technology and Java EE platform knowledge

 The programming model is only part of the story!

 Tools

 Infrastructure for lifecycle management

 Monitoring

 Administration

 Therefore:

Evolutionary (not revolutionary) approach, starting with Java EE, and adding

as much SCA as justified by the use-case

 No new packaging to be introduced

Page 10: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 10/27© SAP 2008 / SAP TechEd 08 / COMP104 Page 12

1. Introduction

1.1. SCA Business Value

1.2. What is SCA

2. Use-Cases Where SCA Can Fit2.1. Bottom-Up Composition

2.2. Top-Down Composition

2.3. Heterogeneous Assembly

2.4. Implementation Reuse

2.5. Flexible Deployment3. SCA at SAP

4. Questions and Answers

Agenda

Page 11: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 11/27

Bottom-Up Composition

© SAP 2008 / SAP TechEd 08 / COMP104 Page 13

Select a set of existing componentimplementations for building the newcomposite 

services  references 

For each component: configure thebehavior to match the uniquerequirements of the composite 

 Hand off the composite tothe Deployer

Composite

 Configure references. Drawinternal wires

properties   Wrap the components in a

composite and configure

external services, etc.

Page 12: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 12/27

Composite

Service

Properties

Top-Down Composition

© SAP 2008 / SAP TechEd 08 / COMP104 Page 14

Start with gathering requirements forthe high-level composite

Define the services/references and

properties for the composite

Break down the composite intoindividual components and

wires between them

Recursively break down

each component

Hand off the individual component

contracts to developers for

implementation

Page 13: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 13/27

Heterogeneous Assembly

© SAP 2008 / SAP TechEd 08 / COMP104 Page 15

Complex composites often involve assembly ofheterogeneous components (e.g. EJB, BPEL, C++, PHP, …) 

 Lifecycle of all components is managed together

Properties of wires between components are managed

together (e.g., change all wires to use security, logging)

Page 14: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 14/27

Implementation Reuse

© SAP 2008 / SAP TechEd 08 / COMP104 Page 16

 Select an existing component implementation(code, not service) for reuse

 Configure its behavior (via setting props,

refs) to match the requirements of some

high-level scenario

E.g., configure multiple instances of product pricingcomponent, each with different currency, tax rate,

discount charts, etc.

Component

…  … 

Services

References

Properties

Implementation

- Java

- BPEL

- Composite

Deploy the component implementation

Multiple instances of the same implementation

may be running simultaneously

Page 15: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 15/27

Flexible Deployment

© SAP 2008 / SAP TechEd 08 / COMP104 Page 17

Services

References

Properties

SOAP/HTTPWS Binding

JMS

BindingJCA Binding

 Developer creates componentimplementation for reuse

WS

Clients

JMS

Clients

ERPService

 Deployer chooses and configures middleware for

component access to match the unique requirements

of a set of clients

  Assembler configures the implementation

with business properties and service/refs

Page 16: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 16/27© SAP 2008 / SAP TechEd 08 / COMP104 Page 18

1. Introduction

1.1. SCA Business Value

1.2. What is SCA

2. Use-Cases Where SCA Can Fit2.1. Bottom-Up Composition

2.2. Top-Down Composition

2.3. Heterogeneous Assembly

2.4. Implementation Reuse

2.5. Flexible Deployment3. SCA at SAP

4. Questions and Answers

Agenda

Page 17: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 17/27

Roadmap for

SAP NetWeaver Composition Environment

2007

Lean, standards-based

environment for composite

applications

2008/09

Composite process

flexibility with full

lifecycle support

Beyond

Composite application

agility by design Consumption and

provisioning of enterprise

services

Reuse of SOA and

composite assets

Decoupled ESR and registry

NWDI integration

Supportability (logging,

tracing, debugging)

Java EE 5 and WS*

standards

Eclipse, WTP adoption

Lean and fast installation

and start-up   S   t  a  n   d  a  r   d  s

  a  n   d

  s   i  m  p   l   i  c   i   t  y

   E  n   t  e  r  p  r   i  s  e

   S   O   A

   C  o  m  p  o  s   i   t  e

   l   i   f  e  c  y  c   l  e

  m  a  n  a  g  e  m  e  n   t

Enhanced business process

modeling

Service adaptation

Built-in extensibility support

Enhanced supportability andfast error diagnostics

Development infrastructure

and logistics enhancements

Translation support

Java and WS* standards

Full Eclipse adoption

Reusable building blocks

Extended re-factoring

Situational composites

Extended support of

enterprise SOA (state, task,

rules, event, and transaction

handling)

Software logistics forcomposite product (e.g.

installer, update manager)

Business configuration for

composites

Synchronized composite-

backend change

management

Java EE 6 and WS*

standards

SCA adoption for

composites

Release to customer

THIS SLIDE WILL BE UPDATED BY 1 SEPTEMBER 2008

Page 18: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 18/27

Business Logic Behind Extensibility

© SAP 2008 / SAP TechEd 08 / COMP104 Page 20

Provide a way for a predefined part (extension point) of a deployed SAP

application to be replaced with a custom implementation

Such concept is available in ABAP since 4.6 (Business Add-Ins)

Page 19: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 19/27

Technical Description of Extensibility

© SAP 2008 / SAP TechEd 08 / COMP104 Page 21

 An EJB should be able to start referring to custom provided

implementation in another application which could appear at a later stage.

This redirecting should be described in a “transportable” artifact (i.e. to

be applied by no manual changes in the SAP NetWeaver Administrator

but by deployment of an application)

 The artifact should be in a unified format for all programming models

(VC, WD, EJB, etc.). Reducing TCO by having common tooling,monitoring, administration, update concept, etc.

Page 20: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 20/27

Extensibility Demo

© SAP 2008 / SAP TechEd 08 / COMP104 Page 22

SAP ApplicationFacadeBean

@EJB(name=“ExtensionPoint”)

@Reference ExtensionPointINterface ext;

public String

getImplementationIdentification() {

return ext.getIdentification();}

DefaultImplBean

@Stateless 

class DefaultImplBean implements

ExtensionPointInterface

@Resource(name=“colour”) 

String envEntry = “default” 

getIdentification() { … } 

Customer Application

CustomImplBean

@Stateless

class CustomImplBean implements ExtensionPointInterface

getIdentification() { … } 

reference

r ef 

 er

 en

 c

 e 

Page 21: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 21/27© SAP 2008 / SAP TechEd 08 / <Session ID> Page 23

DEMO 

Page 22: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 22/27

Questions and Answers

© SAP 2008 / SAP TechEd 08 / COMP104 Page 24

> uestions?

Page 23: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 23/27© SAP 2008 / SAP TechEd 08 / COMP104 Page 25

Further Information

Related SAP Education and Certification Opportunities

http://www.sap.com/education/ 

SAP Public Web:

SAP Developer Network (SDN): www.sdn.sap.com Business Process Expert (BPX) Community: www.bpx.sap.com 

Page 24: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 24/27© SAP 2008 / SAP TechEd 08 / <Session ID> Page 26

Thank you!

Page 25: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 25/27

Fuel your Career with SAP Certification

Take advantage of the enhanced, expanded and multi tier certifications from SAP today!

What the industry is saying  “Teams with certified architects and

developers deliver projects on

specification, on time, and on budget

more often than other teams.” 2008 IDC Certification Analysis

 “82% of hiring managers use

certification as a hiring criteria.” 2008 SAP Client Survey

 “SAP Certified Application

Professional status is proof of quality,

and that’s what matters most tocustomers.”* Conny Dahlgren, SAP Certified Professional 

Page 26: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 26/27

© SAP 2008 / SAP TechEd 08 / COMP104 Page 28

SDN Subscriptions offers developers and consultants like you,an annual license to the complete SAP NetWeaver platformsoftware, related services, and educational content, to keepyou at the top of your profession. 

SDN Software Subscriptions: (currently available in U.S. and Germany) 

 A one year low cost, development, test, and commercializationlicense to the complete SAP NetWeaver software platform

 Automatic notification for patches and updates

Continuous learning presentations and demos to buildexpertise in each of the SAP NetWeaver platform components

 A personal SAP namespace

SAP NetWeaver Content Subscription: (available globally) 

 An online library of continuous learning content to help build skills.Starter Kit

Building Your Business with

SDN Subscriptions

To learn more or to get your own SDN Subscription, visit us at the

Community Clubhouse or at www.sdn.sap.com/irj/sdn/subscriptions 

Page 27: Comp 104

8/12/2019 Comp 104

http://slidepdf.com/reader/full/comp-104 27/27

Please complete your session evaluation.

Be courteous — deposit your trash,and do not take the handouts for the following session.

Thank You

Feedback


Recommended