Building Composite Applications Using Standard Tools

8/3/2019 Building Composite Applications Using Standard Tools

http://slidepdf.com/reader/full/building-composite-applications-using-standard-tools 1/18

Building Composite Applications

using Standard Tools

Harald Mueller SAP NetWeaver Composition

22. April 2008



© SAP 2007 / Page 2

Introduction

How to develop Composite Apps?

Simplified Java Memory Analysis

Agenda



© SAP 2007 / Page 3

SAP and Open Standards

SAP and the JCP

Active JSR member since April 2001

Elected to EC in October 2002

Has participated in 67 JSRs

Java SE and Java EE licensee

SAP and other Standards bodies

Eclipse Eclipse 3.3 , WTP 1.5, WTP 2.0 contribution

OSOA SCA, SDO

SPECj SPECjAppServer2007

OASIS WS-BPEL 2.0, WS-Security, ...

OMG, OMA, RosettaNet, W3C, WS-I, WfMC, Liberty Alliance, ...

First Java EE 5 certified

Platform vendor

(September, 2006)

WTP – JEE Tools contribution49% of the changes in 2008

~142 patches provided

Project lead and PMC member

SAP Memory Analyzer

Donated memory analyzer to Eclipsehttp://www.eclipse.org/mat/

SCA and SDO specifications

Leading role and substantial

contributions



© SAP 2007 / Page 4

Insight into NetWeaver Development

NetWeaver Development Team

~ 2.750 employees in NetWeaver and ~1.500 Java developers Global team with locations in: Germany, Israel, Bulgaria, India, USA, ..

Daily production process for NetWeaver

~24 Million Lines of Code and 255k number of Classes

One night build of the NetWeaver Java stack takes ~19 hours and produces 60GB

~70 central servers for source code versioning and build in different locations Optimized Build Tools and Hardware for production

Development process

Toyota Principles: „Takt“ - daily, weekly releases, milestones

Agile project methods: XP, SCRUM, 6σ Layered Development

NetWeaver project plan for 2007: ~200.000 PD

Biggest challenges are dependency and risk management



© SAP 2007 / Page 5

Java App Server

SAP JVM

Robust, enterprise-

class Java EE 5

application server

Eclipse Development

Environment

SAP NetWeaver

Developer Studio: Eclipse

based development andmodeling environment

Selected Improvements With SAP NetWeaver

Composition Environment 7.1.1

P r o c e s s e s

Event Flow / RulesRole

SAP NetWeaver

BPM for process

composition

V i e w s

Portal and Web FormsMobile

and VoiceAnalytics

SAP NetWeaver Visual

Composer for model-

driven UI development

(incl. analytics and voice)

Web Dynpro Java

SAP Interactive Forms

by Adobe

Federated Portal

Network

Enterprise Services

Repository and Registry

(ESR)

Software lifecycle

management and

logistics (NWDI)

B u s

Dataor File

Web Services / Enterprise

Services Connectivity

S e

r v i c e s Service

façadeNew

service

Dataservice EnterpriseserviceBasicservice

SAP Composite

Application

Framework (CAF)

business object

modeling and servicecomposition

New

Graphical, BPMN-based

process composition

Business rules

Improved

CAF performance (no

MMR)

Graphical designer and

developer productivity

New / improved

Full BI & ALV support in

Visual Composer

Web Dynpro components

in VC

VC grid layout / HTML

Flash islands in WD

New

Composite Designer

Eclipse 3.3.x

SAP profiler

New / improved

ESR in CE

NWDI in CE

New

WS-RM & idempotency

Mass configuration

Improved

Java supportability (MC,deployment, logging,

memory analysis)

Performance and failover

http://x/Sven/JAX%2008%20_%20Download%20_%20Sven/Local_Composition/i812460/Local%20Settings/Temp/Boston%20Tour/lightning%20Portal.avi



© SAP 2007 / Page 6

Lifecycle for Building Enterprise SOA-based

Applications

Model and

Build

Model business

processes and rules

Model and build UIs Design and model

business objects (BOs)

Build new business logic

and services reusing

existing assets

Compose

and

Orchestrate Compose views by

reusing implemented

services and BO's

Compose and

orchestrate services

and views to

implement new

business process

Manage

and

Optimize

Manage change

and maintain version

(governance)

Monitor service

execution (e.g.performance, availability,

process progress, events)

Integrate

and Deploy

Package and deploy application

Configure runtime (adapt to IT landscape)

Test and validate application Execute application

Analyzes business requirements

Identify needed business objects,

services, and views Discover available enterprise

services in ESR for reuse

Identify missing services

for new business logic

Analyze and

Discover

http://www.flexfs.com/images/molecules.jpg


http://slidepdf.com/reader/full/building-composite-applications-using-standard-tools 7/18© SAP 2007 / Page 7

Business process



BPMN – Standard

Business Processes Modeling Notation



Project Galaxy

The Next Generation of BPM from SAP

Human interaction and system integration

in one model

Handles process flows, events, tasks,

contexts, and roles

Eclipse modeler based on BPM Notation

(BPMN)

Direct path from business view to execution

Strengthened by acquisition of YASU

Technologies for Business Rules Management

Embedded in

SAP NetWeaver Composition Environment

Rule Engine

Rule Builder Web Editor Rule

Management

Rule

Analytics

Process

Composer

Process

Desk

Process Server



DEMO

Sneak PreviewSAP NetWeaver Composition Environment 7.1.1



Scenario: Investment Approval Process

Purchase Requester

Enters purchase request

Business rule

Derives manager for approvalbased on investment volume,exchange rate, and country

Ensures company policies

Purchase Approver Review order, approve or reject

and in case of rejection addreason and propose acceptablesolution

Purchase Requester

Update purchase order or terminate process

Corporate Purchasing

Create PO in ERP includingsupplier integration

Eventing for PO release

Improves process transparency



Motivation for Investment Approval Process

Typical example for a “Before”-process

Compliance regulations

companies are forced to implement e.g. the Sarbanes-Oxley Act (SOX) – changes on

documents must be traceable (who changed when what and why?)

Information can be added not covered by standard processes

Data can be used for later analysis to improve processes even further

Externalize frequently changing company policies

Determination of manager for approval can be dependent on several criteria which most

probably change very often over time

Typical example for a rule-based solution: the correlation of any criteria combination can

easily be modeled and adapted as needed

Implement company policies rapidly

Increase end-to-end process transparency

Bridging the gap between before-process and backend process

Allows for collecting end-to-end process data for further improvements



Java Memory Analysis

Heap

MB

t

IOIOIIIOIIOIOIOIOIIOIIOI

XX:+Heap

DumpOnOutOfMemoryError

Minor Garbage

Collection

Full Garbage

Collection

Memory

utilization

trend

Memory

2 a.m.

High GC activitiy leads to

performance problems

Automatically reads the heap dump

from production and sends an e-mail

with the analysis results

Out Of Memory



Automated Analysis of the Java heap dump

Support staff • Identify problem and responsible• No technical expertise required

Forward the problem to Development

Developer • Which classes are leaking ?

• What is kept by the leak suspect ?Fast identification of the Problem



Thank You



Secondary color palette

100%

Primary color palette

100%

Definition and halftone values of colors

RGB 68/105/125

RGB 96/127/143

RGB 125/150/164

RGB 152/173/183

RGB 180/195/203

RGB 4/53/123 RGB 240/171/0 RGB 102/102/102RGB 153/153/153RGB 204/204/204

RGB 21/101/112

RGB 98/146/147

RGB 127/166/167

RGB 154/185/185

RGB 181/204/204

RGB 85/118/48

RGB 110/138/79

RGB 136/160/111

RGB 162/180/141

RGB 187/200/172

RGB 119/74/57

RGB 140/101/87

RGB 161/129/118

RGB 181/156/147

RGB 201/183/176

RGB 100/68/89

RGB 123/96/114

RGB 147/125/139

RGB 170/152/164

RGB 193/180/189

RGB 73/108/96

RGB 101/129/120

RGB 129/152/144

RGB 156/174/168

RGB 183/196/191

RGB 129/110/44

RGB 148/132/75

RGB 167/154/108

RGB 186/176/139

RGB 205/197/171

RGB 132/76/84

RGB 150/103/110

RGB 169/130/136

RGB 188/157/162

RGB 206/183/187

85%

70%

55%

40%

RGB 158/48/57Tertiary color palette100%

85%

70%

55%

40%

SAP Blue SAP Gold SAP Dark GraySAP GraySAP Light Gray

Dove Petrol Violet/MauveWarm RedWarm Green

Cool Green Ocher Warning RedCool Red



Grid



Copyright 2007 SAP AG

All rights reserved

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changedwithout prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned andassociated logos displayed are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This documentcontains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy,and/or development. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitationshall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these

materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages

Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durchSAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden.

Einige von der SAP AG und deren Vertriebspartnern vertriebene Softwareprodukte können Softwarekomponenten umfassen, die Eigentum anderer Softwarehersteller sind.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, Duet, Business ByDesign, ByDesign, PartnerEdge und andere in diesem Dokument erwähnte SAP-Produkte und Servicessowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und in mehreren anderen Ländern weltweit. Alle anderen in diesem Dokument erwähntenNamen von Produkten und Services sowie die damit verbundenen Firmenlogos sind Marken der jeweiligen Unternehmen. Die Angaben im Text sind unverbindlich und dienen lediglich zuInformationszwecken. Produkte können länderspezifische Unterschiede aufweisen.

Die in diesem Dokument enthaltenen Informationen sind Eigentum von SAP. Dieses Dokument ist eine Vorabversion und unterliegt nicht Ihrer Lizenzvereinbarung oder einer anderen

Vereinbarung mit SAP. Dieses Dokument enthält nur vorgesehene Strategien, Entwicklungen und Funktionen des SAP®-Produkts und ist für SAP nicht bindend, einen bestimmtenGeschäftsweg, eine Produktstrategie bzw. -entwicklung einzuschlagen. SAP übernimmt keine Verantwortung für Fehler oder Auslassungen in diesen Materialien. SAP garantiert nicht dieRichtigkeit oder Vollständigkeit der Informationen, Texte, Grafiken, Links oder anderer in diesen Materialien enthaltenen Elemente. Diese Publikation wird ohne jegliche Gewähr, weder ausdrücklich noch stillschweigend, bereitgestellt. Dies gilt u. a., aber nicht ausschließlich, hinsichtlich der Gewährleistung der Marktgängigkeit und der Eignung für einen bestimmten Zwecksowie für die Gewährleistung der Nichtverletzung geltenden Rechts.

SAP übernimmt keine Haftung für Schäden jeglicher Art, einschließlich und ohne Einschränkung für direkte, spezielle, indirekte oder Folgeschäden im Zusammenhang mit der Verwendungdieser Unterlagen. Diese Einschränkung gilt nicht bei Vorsatz oder grober Fahrlässigkeit.

Die gesetzliche Haftung bei Personenschäden oder die Produkthaftung bleibt unberührt. Die Informationen, auf die Sie möglicherweise über die in diesem Material enthaltenen Hotlinkszugreifen, unterliegen nicht dem Einfluss von SAP, und SAP unterstützt nicht die Nutzung von Internetseiten Dritter durch Sie und gibt keinerlei Gewährleistungen oder Zusagen über Internetseiten Dritter ab.

Alle Rechte vorbehalten.

Date post:	06-Apr-2018
Category:	Documents
Upload:	wu-jun
View:	220 times
Download:	0 times

Building Composite Applications Using Standard Tools

Documents