From SAP NetWeaver to the Business Process Platform: Preparing for the Evolution from Web Services to Enterprise

Services
Franklin Herbas
SAP Labs

Web Services and Web Service Technology Overview Developing Web Services Web Services vs. Enterprise Services Developing Enterprise Services Consuming Enterprise Services Summary

Web Services and Web Service Technology Overview Developing Web Services Web Services vs. Enterprise Services Developing Enterprise Services Consuming Enterprise Services Summary

Web Services Definition

WEB SERVICES are SELF-CONTAINED and SELF-DESCRIBING APPLICATION FUNCTIONALITIES that can be PROCESSED through OPEN INTERNET STANDARDS
SAP AG 2006, 4

Web Services Paradigm 2

Web Service Directory Stores WSDL Reference

UDDI UDDI Service Directory

3
Discover Web Service Develop Client App
Direct WSDL Exchange

Create Web Service Create WSDL Publish WSDL (opt.)

WSDL Document

WSDL Document Web service

Web Service Client

SOAP

Bus. Functionality Web Service Execution Web Service Provider

4
SAP AG 2006, 5

Open Integration Based on Standards

Examples of supported standards in SAP NetWeaver
W3C SOAP 1.1 WSDL 1.1 XML Schema XML Signature XSL BPML CIM OASIS SAML UBL UDDI 2.0/3.0 WSRP WS-Security XML.org Wf-XML WS-I Basic Profile 1.0 XMLA UDDI4J JAX-RPC JAXM and many others

SAP NetWeaver is based on open standards SAP NetWeaver supports standards on technology, framework, and business levels Built on a consistent technology and application stack

SAP AG 2006, 6

Providing Web Services Based on Open Standards

Development Environment

UDDI UDDI Registry

WSDL

Web Service Meta Data WS Client

XI Server Proxy

Virtual Interface

SOAP Web Service

Web Service Runtime

BAPI RFC EJB

Java Class

SAP Web Application Server

SAP AG 2006, 7

Business Application

Standard Interfaces

IDOC

Consuming Web Services Based on Open Standards

Development Environment

WSDL

UDDI UDDI Registry

Web Service Meta Data

Web Service Client Application

Web Service Proxy

Web Service Runtime

SOAP

Web Service

Bus. Functionality Web Service Provider

SAP Web Application Server

SAP AG 2006, 8

Value-Added Web Services with SAP NetWeaver XI

Mediated Web services with routing, mapping, and BPM

Adapter

Third Party

Web Service Client

SOAP

SAP NetWeaver XI Integration Server

Adapter
XI Protocol or SOAP

SAP System

Web Service Client

SOAP

SAP WebAS 6.40

Point-to-Point Basic Web Services

SAP AG 2006, 9

Web Services and Web Service Technology Overview Developing Web Services Web Services vs. Enterprise Services Developing Enterprise Services Consuming Enterprise Services Summary

Creating a Web Service In Less Than ONE Minute

1
Implement Business Application
No Web service-specific programming New or existing applications Defines standard interfaces Well-known programming models

WS Configuration WS Definition Virtual Interface

Generate Web Service

2
Wizard-based approach Based on preconfigured profiles Based on abstract behavior Available for ABAP and Java

3
Activate/ Deploy Web Service
Deployment in Java Activation in ABAP

SAP AG 2006, 11

Demo: Web Service Creation Wizard

Web Service Creation Wizard

SAP AG 2006, 12

The Web Service Creation Wizard Background

Out-of-the-box Web services enablement of SAP solutions Allows you to expose an existing endpoint as a Web service with few mouse clicks Only shows the most important settings in the wizard
Default

values (profiles) for other settings

Hides technical details Implicitly creates all necessary objects

SAP AG 2006, 13

Demo: Web Service Homepage

Web Service Homepage

SAP AG 2006, 14

Creating a Web Service Step-by-Step for Individual Needs 1

Implement Business Application
No Web service-specific programming New or existing applications Defines standard interfaces Well-known programming models

2
Virtual Interface

Create Virtual Interface

Abstraction from implementation

3
WS Definition

Create Web Service Definition

Defines abstract behavior

WS Configuration

Configure Web Service

4
Individual configuration of security, session, etc.

5
Activate/ Deploy Web Service
Deployment in Java Activation in ABAP

SAP AG 2006, 15

Two Basic Ways of Developing an Interface Inside-Out

Start of implementation in the back-end system Interface semantics predefined and directly reflect implementation (virtual interfaces allow some viewlike mappings)

Outside-In
Central design of interfaces that make business sense in SAP NetWeaver Exchange Infrastructure integration repository Using global data types Reference to governance process for PIC Generation of proxies from abstractly modeled interface Implementation of glue code between proxy and business function Implementation can be changed without changes in interface

SAP AG 2006, 16

Web Services and Web Service Technology Overview Developing Web Services Web Services vs. Enterprise Services Developing Enterprise Services Consuming Enterprise Services Summary

Current SAP Focus Areas

Business Suite

SAP Composite Apps (including UI and analytics)

ISV/Customer Composite Apps (including UI and analytics)

Enterprise Services Repository

SAP NetWeaver Business Process Platform

Legacy/ Partner Services

Legacy/ rd Party 3 Third-party

ISV Components

SAP Non-platform Components

OEM Platform Components

Process Process Components Components

Service Enablement refers to the process of providing enterprise functionality in the form of well-defined services
SAP AG 2006, 18

ServiceEnabling

What Are Enterprise Services?

Enterprise Services provide business functionality

with enterprise quality in scalability, robustness, security, manageability, supportability, etc.

ERP

ERP

ERP

ERP

ERP

ERP

CRM

ERP

ERP

D&B

S&P

D&B

S&P

D&B

S&P

Traditional
Proprietary protocols Hard-coded logic

SAP AG 2006, 19

Web Services
Standard protocols Various semantics

Enterprise Services
Web services tech. Standardize semantics Business rules

Enterprise Services Architecture

Business Processes and User Interaction

Abstraction and Integration
Enterprise Services

Enterprise Applications

SAP AG 2006, 20

Enterprise Services Are Defined Centrally within the ESR The Enterprise Services Repository (ESR) is the designtime repository of Enterprise Services

SAP AG 2006, 21

Web Services and Web Service Technology Overview Developing Web Services Web Services vs. Enterprise Services Developing Enterprise Services Consuming Enterprise Services Summary

Process Integration and ESA Enterprise Services Architecture

PEOPLE PRODUCTIVITY

SAP NetWeaver
PEOPLE INTEGRATION Multi-channel access Composite Application Framework Portal Collaboration

ANALYTICS/REPORTING

INFORMATION INTEGRATION Bus. Intelligence Master Data Mgmt. Knowledge Mgmt. Lifecycle Mgmt..

SERVICE COMPOSITION AND ORCHESTRATION

PROCESS INTEGRATION
Integration Broker Business Process Mgmt.

SERVICE ENABLEMENT

Enterprise Services Repository

SAPs Enterprise Services

Partner Services

APPLICATION PLATFORM J2EE ABAP

Bus. Partner Legacy

Business Objects, Components, and Engines

DB and OS Abstraction

LIFECYCLE Mgmt.

SAP AG 2006, 23

Process Integration and ESA/Service Enablement Enterprise Services Architecture

PEOPLE PRODUCTIVITY

Enterprise Services Repository SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI) Integration Repository as the foundation for a central services repository New/enhanced objects:

ANALYTICS/REPORTING

SERVICE COMPOSITION AND ORCHESTRATION

SERVICE ENABLEMENT

Enterprise Services Repository

SAPs Enterprise Services

Partner Services

Business objects Services (SAP/non-SAP)

Business Objects, Components, and Engines

Bus. Partner Legacy

LIFECYCLE Mgmt.

SAP NetWeaver XI interfaces and data types are naturally part of ESR Leverage existing investment

SAP AG 2006, 24

Global Data Types: Building Blocks for Interfaces

Global Data Types are company-wide defined data types with business content, as found in standards or should be found in standards or which are structured in accordance with standards

Global Data Types (GDTs) are:

Based on the International Standard UN/CEFACT CCTS (Core Component Technical Specification)* SAP-wide approved with reference to the Governance Process for Process Integration Content (embedded within the SAP Standard Application Integration and Interfaces) Defined in the central Integration Repository using XML Schema Well-documented according to the Document template Semantic building blocks for interfaces (reuse)
* UN/CEFACT CCTS is a methodology for developing a common set of semantic building blocks that represent the general types of business data in use today
SAP AG 2006, 25

Design Paradigm One service infrastructure for:

Uniform definition, implementation, and usage of services All types of integration (for UI, A2A/B2B, etc.) All relevant interaction models (sync./asynchronous, etc.) Based on Web services standards

Enterprise Services
Service definition based on business semantic Enable a business modeloriented service orchestration UI and business logic based on same set of standardized core services

Model-driven development
Process model Data model UI model

SAP AG 2006, 26

ESA Elements of the ESI Architecture

Implementation Tools
Dev Tools (ABAP Workbench/ NetWeaver Developer Studio/ Visual Composer) ES/ES-related Tools

UI Service Consumption
SAP Front-end Server (UI consumer side) UI Configuration
(including provider system)

Central ES Repository

UI Core Service Consumer Interface (Typed Proxy or Generic) Consumerrelevant Meta Data

ES Builder and Repository

ESI

Application Service Consumption

SAP Web AS (application consumer side)

(extended XI Integration Builder and Repository)

y Data Types y Business Object Model y Operations and Interfaces

Provider Side
SAP Web AS (provider side)

Application Service Consumer Proxy

ESI Consumerrelevant Meta Data ESI SAP XI Integration Directory

ESI Providerrelevant Meta Data

Core Service Compound Service

Non-SAP Web Service Provider

Non-SAP

Non-SAP Web Service Consumer

SAP AG 2006, 27

Demo: Enterprise Service Development

Developing Enterprise Service

Outside-In
Central design of interfaces that make business sense in the SAP NetWeaver Exchange Infrastructure integration repository Using Global Data Types Reference to governance process for PIC Generation of proxies from abstractly modeled interface Implementation can be changed without changes in interface

SAP AG 2006, 28

Design
Integration Builder Integration Repository
Scenario Editor Process Editor Mapping Editor Condition Editor Business Scenarios Business Processes Mappings Context Objects Message Interfaces
Message Types

Pre-delivered integration content for mySAP solutions Open for collaboration knowledge of non-SAP systems, using open standards (e.g., WSDL) Provision to enhance SAP NetWeaver XI design-time objects by customers/partners Java-based graphical tools

BPEL XSLT Java XPath WSDL

Data Type Editor

Data Types (XSD)

System Software Component Version Landscape Software Component Directory

SAP AG 2006, 29

SAP WebAS

J2EE/ ABAP Proxies

Modeling Services Namespace

SAP AG 2006, 30

Modeling Services Input Type

SAP AG 2006, 31

Modeling Services Output Type

SAP AG 2006, 32

Modeling Services Message Type

SAP AG 2006, 33

Modeling Services Message Type (cont.)

SAP AG 2006, 34

Modeling Services Interface

SAP AG 2006, 35

Modeling Services Activate Change List

SAP AG 2006, 36

Modeling Services Activate Change List (cont.)

SAP AG 2006, 37

Modeling Services Generate ABAP Proxy

SAP AG 2006, 38

Modeling Services Generate ABAP Proxy (cont.)

SAP AG 2006, 39

Modeling Services Implement Proxy

SAP AG 2006, 40

Modeling Services Implement Proxy (cont.)

SAP AG 2006, 41

Enterprise Services Browser

The Enterprise Services Browser allows you to browse the business objects and service interfaces in the ESR and generate proxies for these objects. The WSDL descriptions of the objects are retrieved from the ESR and form the basis for the generated proxies (outside-in programming model).

SAP AG 2006, 42

Web Services and Web Service Technology Overview Developing Web Services Web Services vs. Enterprise Services Developing Enterprise Services Consuming Enterprise Services Summary

ESA as the Convergence Point of Business and IT

Purchaser Production Planner Accountant Portals that help people do their work

Composite Applications SAP NetWeaver People Integration Information Integration Process Integration SRM PLM ERP SCM CRM

Business Engineering The business is the starting point and drives the IT landscape, not vice versa Flexibility is the key to growth and survival Few companies can provide complete (industry) business solutions

Integration Platform Enterprise services will offer flexible integration for inter- and intraenterprise processes Enterprise services platforms will emerge Huge ecosystem will develop and innovate around service platforms

Enterprise Services Architecture (ESA)

SAP AG 2006, 44

Presentation of Enterprise Services Along Processes

select an industry examine the solution map and the business scenario group

read about the business scenario see the list of services and look at the process

go to service description

Made available to customers on a preview system details on SDN

SAP AG 2006, 45

Demo: Consuming Enterprise Services

Consuming Enterprise Services with Visual Composer

SAP AG 2006, 46

UI Building Blocks (UIBBs) Rationale Problems Inconsistent UI behavior

Different UIs for the same user task

Goals Improve UI consistency

Use standardized UIBBs

Training effort for end users

Lot of work for customers to train the users

Improve end-user efficiency

Use standardized UIBBs

Different UI technologies
Poor integration and expensive to maintain

Improve development efficiency

One UI technology (portal and Web Dynpro)

Difficult to adapt
Hard/impossible to adapt to customer needs
SAP AG 2006, 47

Improve adaptability
Enable business experts to build or adapt the UI

Service-Enabled User Interface Service- and Pattern-Based UI Design

SAP NetWeaver Visual Composer

SAP NetWeaver Portal

UI Pattern Framework
VC Models Web Dynpro Pattern Components Web Dynpro UI Components

Web Dynpro UI Runtime

Enterprise Services Repository ABAP Workbench Java Dev Studio

Enterprise Services Infrastructure Service Implementation

DESIGN TIME
SAP AG 2006, 48

RUNTIME

Service Provider

UIBB Hierarchy: Bottom-Up

UI elements: Atomic elements provided by Web Dynpro foundation, such as buttons, text fields, and labels

UI elements

UI patterns: Reusable, task-oriented UIBBs, such as patterns and panes (form, list, and chart panes)

UI patterns

Floor plans: Containers responsible for organizing screen layout and interaction between patterns

Floor plans

SAP AG 2006, 49

UIBBs

iView

UIBB (Floor Plan)

UIBB (Pattern)

Identification Pattern

Object Selection Pattern

Contextual Navigation Pattern

Simple Object Data Pattern

Object Instance Floor Plan

SAP AG 2006, 50

SAP ESA Development Process

Runtime Part Configuration Part
Define which elements of UIBBs application developers can configure

UI Developers

Develop UIBBs using SAP NetWeaver Developer Studio Web Dynpro

Application Developers

Configuration Data

Configure Configure UIBBs UIBBs using using Visual Visual Composer Composer

End Users
SAP AG 2006, 51

Run Run the the application application

Web Services and Web Service Technology Overview Developing Web Services Web Services vs. Enterprise Services Developing Enterprise Services Consuming Enterprise Services Summary

Additional Resources

Public Web
www.sap.com SAP Developer Network: www.sdn.sap.com ESA

Related SAP education/training opportunities

http://www.sap.com/education/ Enterprise Services Architecture booth

Related lectures
Inside SAPs future Enterprise Services Repository and what it means to you, Franklin Herbas ESA in action: Real-world examples and real-world benefits, Paul Kurchina

SAP AG 2006, 53

7 Key Points to Take Home Service-based development can start right now! SAP ESA is based in Web service technology Enterprise services provide business functionality Service-enabling is a focus area in the SAP ESA SAP NetWeaver Exchange Infrastructure (SAP NetWeaver XI) is the foundation of the ESR There are two ways of developing service meta data: The insideout and the outside-in approaches UIBBs are standardized components for creating user interfaces. Instead of programming the UI, you configure UIBBs using SAP NetWeaver Visual Composer.

SAP AG 2006, 54

Questions?

Q&A
SAP AG 2006, 55

Feedback
Please complete your session evaluation Be courteous deposit your trash, and do not take the handouts for the following session

Thank You !

SAP AG 2006, 56

Copyright 2006 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 changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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 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. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains 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. Please note that this document is subject to change and may be changed by SAP at any time without notice. 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 limitation shall 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.

SAP AG 2006, 57

Demo

SAP AG 2006, 58