Building Web Services with ABAP and SAP Web - … Webservice with...Building Web Services with ABAP and SAP Web Application Server Timm Falter Project Manager Web Services / SAP AG

SAP TechEd ‘03 Basel

© 2003 SAP AG Session ID, Speaker 1

Building Web Services with ABAP and SAP Web Application Server

Timm FalterProject Manager Web Services / SAP AG Walldorf

Martin HuvarProduct Manager Enterprise Services / SAP AG Walldorf

SAP AG 2003, TechED_Basel / OSI202, Timm Falter / Martin Huvar / 2

Learning Objectives

As a result of this lecture, you will be able to:

Comprehend the main ideas of SAP’s Web Service definition

Understand the architecture of the Web Service Framework

Understand what Virtual Interfaces, Web Service Definitions, Web service Configurations and other concepts of the Web Service Framework are




Agenda

Web Service OverviewWhat are Web services?Why do we need them?

SAP NetWeaver Web Service Technology

SAP Web Application Server 6.40Providing Web Services Consuming Web Services

Summary


Web Services Definition

Web Services are

application functionalities

supporting direct interaction

by responding to service requests

based on open Internet Standards




The nature of Web Services

Web Services

act like a black-box that may require input and deliver a result

are modular, self-contained and self-describing

work on top of any communication technology stack

can be published, discovered and invoked based on opentechnology standards

work in synchronous and asynchronous scenarios

facilitate integration within an enterprise as wellas cross enterprises


UDDI

Web Service Paradigm

3ServiceExecution

2

Service Requestor

ServiceDiscovery

Service Provider

Service Directory

1

ServicePublication

WSDL/XSD

XML/SOAP

http




Web Services: Examples

Intelligent product catalog search

Product availability check

Pricing inquiry

Customer credit check

Order status check

Vendor managed inventory Demand forecasts, stock replenishment …

Dynamic auctioning and bidding

Publish and analyze financial reports (XBRL based)

Electronic bill presentment and payment

Matching vacancies and job applicants profiles

Postal service address check

UDDI registration and discovery services

Automated web searches (Google)


Demo

DemoWeb ServiceExample




Example: Web Service Szenario Credit Limit Check

CRM

Order CreateOrder

CreditManagementSystem

Credit Limit Check

Financial

ProcessOrder

CreditlimitOK?

Credit standingDatabase

History

Database

OKrejected

= Web Service

Customer Company Service Provider


Credit Limit Check Example: Architecture

RFC Function Module(External Id -> Internal ID)

R/3 Enterprise 4.7

Session Enterprise Java BeanSAP Web

AS 6.30 (Java) SAP JCo Proxy SAP JCo Proxy

RFC Function Module(Credit Limit Check)

Virtual Interface Virtual Interface

SAP Web AS 6.30 (Java)

Cell Phone ShopWeb Application (JSP)

Microsoft Excel XP / 2003 Beta

Credit Limit CheckCompany Worksheet

Web Service Web Service

Web Service ProxyWeb Service Proxy




Fundamental Elements of the complete Web Service Solution

Web ServiceTechnology

Open Technology Standards for Web

ServicesWeb ServiceTechnology

Referentto business semantics

SAP NetWeaver

RosettaNet,Spec2000,HR-XML,

XBRL, IFX,papiNet,

....

XML, WSDL, SOAP, UDDI, WSI


Agenda




Summary




Providing Web services based on Open Standards

UDDI

SOAP Processing

Bus

ines

s A

pplic

atio

n

Web Service Configuration

UDDI Publishing

WSDL Generation

DevelopmentEnvironment

Web Service Consumer

Web ServiceConfiguration

Web

Ser

vice

Inte

rfac

esR

FCB

API

IDoc

EJB

SAP Web Application

Server

Extensible Runtime

Pluggable Features

Security

Transactions

Protocols

WSDL

SOAP


Consuming Web services based on Open Standards

UDDI

SOAP Processing

Bus

ines

s A

pplic

atio

n

UDDI based Web Servicediscovery

Web Service ProxyGeneration

Proxy Configuration

DevelopmentEnvironment

ProxyConfig.

Web

Ser

vice

Prox

ies

SAP Web Application

Server

Extensible runtime

Pluggable features

Security

Transactions

Protocols

WSDL

SOAP

Web Service Provider




Exchange Infrastructure & Web Services

Exchange Infrastructure

mySAPComponent

mySAPComponent

mySAPComponent

mySAPComponent

NON SAPComponentNON SAP

ComponentNON SAP

ComponentNON SAP

Component

SOAP

Adapter

NativeProtocol

NativeProtocol

SAP Web Application Server

SOAP

SOAP

SOAP

Web Services InfrastructureWeb Services Infrastructure

Business ProcessEngine

Business ProcessEngine

RoutingRouting

MappingMappingInte

grat

ion

Run

time

Integration Repository &

Directory

Integration Repository &

Directory

RMIRMI ......

PersistencyPersistencyRFCRFC

Adapter


Enterprise Services: Runtime View

SAP Web AS as client SAP Web AS as server

App

licat

ionA

pplication

XI

IntegrationServer

Outbound Proxy

Mediated Executionvia Web Services

Web Service Infrastructure W

eb S

ervi

ce In

fras

truc

ture

Inbound Proxy

Standard Web Service Execution (P2P)

IntegrationRepository& Directory




Agenda



SAP Web Application Server 6.40Providing Web ServicesConsuming Web Services

Summary


Web Service within SAP Web Application Server

The Web Service capability within SAP Web AS is

the foundation for all mySAP.com solutions

a scalable, reliable Web application infrastructure that delivers high-performance Web Services

offering Web Service functionality for the ABAP and J2EE personality with a common architecture

allowing to expose existing functionality (BAPIs, RFMs, IDOCs, EJBs, Java Classes, XI Server Proxies) as Web Service

easily allowing to consume Web Service from any source

requiring only configuration (no coding)




Benefits

Web Service interfaces provide a ‚virtual‘ abstraction from the implementation layer

Fully integrated into development environment

Full fledged UDDI capabilities UDDI server implementation UDDI client functionality

Standard compliant WSDL generation

Support of client proxy generation for ABAP and J2EE

Extensible SOAP Runtime

Pluggable FeaturesSecurityProtocols....


SAP Web Services Infrastructure- Role-based Approach -

Provider-side

Web Service Developerdefines design time information of a Web Service

Web Service Configuratordefines runtime information of a Web service

Consumer-sideWeb Service Client Developer




Agenda




Summary


The Web Service Creation Wizard- Background -

Creating a Web Service in less than 1 minute

- The Web Service Creation wizard

proves that Web services are easy and out-of-the-box

allows to expose an existing endpoint as a Web Service with few mouse-clicks

Only shows the most important settings in the wizardDefault values for other settings

hides technical details

implicitly creates all necessary objects




Steps for the Web Service Wizard

Implement Business Logic1

UDDI

Start Web Service Wizard2

Publish Web Service (optional)3a

Deploy Web Service3

VirtualInterface

WebService

Definition

WebServiceConfig.

generate


Demo

DemoWeb Service Creation Wizard




Step 1 – Implement Business Logic


Step 2 – Start Web Service Wizard




Step 2 – Web Service Wizard (1)














Web Service Wizard Results

All necessary files are created

Virtual InterfacesWeb service DefinitionWeb Service Configuration

Enterprise Application Project (optional)




The Web Service Homepage

The Web Service Homepage

is available for each activated Web Service

shows the documentation for the Web Service

allows to retrieve WSDL descriptions in different styles

offers testing capabilities


Demo

DemoWeb Service Homepage




Invoke Web Service Homepage


Homepage - Overview




Homepage – WSDL View


Homepage – Test View (1)











The Step-by-Step approach

Create all objects by hand

Full flexibility and options

More expenses

… but still configuration only


The Step by Step Approach

Implement Business Logic1

UDDI

Define Virtual Interface (VI)2

Create Web Service Definition (WSD)3

Publish Web Service (optional)5a

Publish WSD (optional)3a

Activate Web Service5

Configure Web Service4





The Step-by-Step approach

Create all objects by hand

Full flexibility and options

More expenses

… but still configuration only


Support for Web Service Developers (1)- Background -

The Web Service developer

knows/defines the application logic

knows/defines the Web Service Interface which should be accessible for clients

knows/defines the “behavior” of the Web Servicee.g. “Stateless / Stateful”, Security requirements, etc.

does not need to have detailed knowledge abouttechnical protocols which implement abstract behaviorconcrete application servers on which the Web Service will be running

Defines Design-Time information of a Web Service




Support for Web Service Developers (2)- Tasks of a Web Service Developer -

Step 1: Implementing the business logic

Supported by the standard IDE

Takes place in “Endpoint-specific” standard ToolsJava: SAP NetWeaver Developer Studio ABAP: SE80



Step 2: Definition of Virtual Interface

Web Service Interface = Interface visible to clients (via WSDL, UDDI, … )

Supported by the Web Service Infrastructure via Virtual Interface Editor

A Virtual Interfaceprovides abstraction from concrete implementation (=endpoint)

allows to publish a “view” on existing implementations as Web Service Interfaces

i.e. renaming, hiding of parameters/methods, default values

allows to define how the Web Service Interface is represented in the SOAP message




Virtual Interfaces

VirtualInterface

ImplementationLayer

i_creditsegment (I)

i_partner (I)

e_score (O)FSCM_Cr_Limit_Check e_limit

(O)e_currency

(O)e_valid_to

(O)

<SOAP-ENV:Envelope><SOAP-ENV:Body>

<ns1:creditLimitCheck><ns1:idNumber>1001</ns1:idNumber>

</ns1:creditLimitCheck></SOAP-ENV:Body>

</SOAP-ENV:Envelope>


<rpl:creditLimitCheckResponse><rpl:Response>

<tns:score>980</tns:score><tns:creditLimit>500000.00</tns:creditLimit><tns:limitCurrency>USD</tns:limitCurrency><tns:validTo>2005-01-01</tns:validTo>

</rpl:Response></rpl:creditLimitCheckResponse>

</SOAP-ENV:Body></SOAP-ENV:Envelope>

idNumber (I)

score (O)

creditLimit (O)

limitCurrency (O)

valid To (O)

creditLimitCheck

Request

Default Value: BUP001

Response


Virtual Interfaces

VirtualInterface

ImplementationLayer

i_creditsegment (I)

i_partner (I)


(O)e_currency

(O)e_valid_to

(O)










idNumber (I)

score (O)

creditLimit (O)

limitCurrency (O)

valid To (O)

creditLimitCheck

Request


Response

Rename Methods




Virtual Interfaces

VirtualInterface

ImplementationLayer

i_creditsegment (I)

i_partner (I)


(O)e_currency

(O)e_valid_to

(O)










idNumber (I)

score (O)

creditLimit (O)

limitCurrency (O)

valid To (O)

creditLimitCheck

Request


Response

Rename Parameters


Virtual Interfaces

VirtualInterface

ImplementationLayer

i_creditsegment (I)

i_partner (I)


(O)e_currency

(O)e_valid_to

(O)










idNumber (I)

score (O)

creditLimit (O)

limitCurrency (O)

valid To (O)

creditLimitCheck

Request


Response

Hide parameters and / or provide default

values




Demo

Demo

Virtual Interfaces


Virtual Interface Editor - Creation of a „default“ Virtual Interface -




Virtual Interface Editor - Rename operation -


Virtual Interface Editor - Parameter Mapping -

Rename Parameter

Type mapping

Define default value

Hide parameter




Virtual Interface Editor - Type Mapping (1) -








Virtual Interface Editor Type Mapping (4)

Rename Field

Copied Type











Original type



Choose new type





new type assigned

Type mappings applied



Step 3: Creation of Web Service DefinitionWeb Service Definition = Assignment of behavior to a Web ServiceInterface via features

Motivationa Web Service is not only described by its interface but also by its behaviorwith respect to

stateless/stateful communication, transactional behavior, security requirements, …

Idea:describe this kind of behavior via abstract featuresleave it to the Web Service Configurator to assign technical protocols to these abstract featuresExample:

Feature: Stateful

Technical Protocols: Stateful via HTTP-Cookies, Stateful via URL-Extensions





Benefits

The same Web Service definition can be activated on various systems which may differ in their technical capabilitiesWeb Service Client implementations do not depend from technical server information

Clients are generated based on implementation-independent Web Service definitionsTechnical details are configured separately in the Web Service Client Runtime

Supported by the Web Service Infrastructure viaWeb Service Definition EditorUDDI Publication of Web Service DefinitionsWSDL Generation for Web Service Definitions


Demo

DemoWeb Service Definition




Web Service Definition- General Properties -


Web Service Definition- Feature Configuration -




Web Service Definition- UDDI Publishing -

Start UDDI publishing


UDDI Publishing – Authentication




UDDI Publishing – Name of Service Definition


UDDI Publishing – Categories




UDDI Publishing – Service Definition Details


UDDI Publishing – Result View




Support for Web Service Configurators (1)- Background -

The Web Service Configurator

knows the technical protocols which implement the abstract features

knows the System Landscape

knows the Web Service capabilities of the single Application Servers

Defines Runtime information of a Web Service


Support for Web Service Configurators (2)- Tasks of a Web Service Configurator -

Step 1: Technical configuration and Activation of a Web Service Definition

Assignment of technical protocols to the abstract features based on the Web Service capabilities of the Application Server

Configuration of additional Web Service Runtime featuresLogging, Tracing, MonitoringSecurity Roles…

Saving and automatic registration in the Web Service Runtime Registry

Supported by Web Service Infrastructure viaWeb Service Configuration Transaction (WSCONFIG)

Web Service Administration Transaction (WSADMIN)

WSDL Generation for deployed Web Services

UDDI Publishing




Demo

DemoWeb Service Configuration and Administration


Web Service Configuration- Show configurations of Web Service Definition -

Transaction „WSCONFIG“




Web Service Configuration- Create new Configuration (Overall Settings) -


Web Service Configuration- Create new Configuration (Transport Level Config) -

Configure Transport Settings




Web Service Configuration- Create new Configuration (Transport Level Config) -


Web Service Configuration- Create new Configuration (Operation configuration) -

Configure Security Settings




Web Service Administration- List of Available Web Services -

Transaction„WSADMIN“

Display WSDL

Open WS Homepage


Web Service Administration- Configure Web Service -

Configure Logging, Tracing

Start UDDI Publishing




UDDI Publishing – Authentication


UDDI Publishing – Service Publication: Names




UDDI Publishing – Service Publication: Binding Templates


Agenda



SAP Web Application Server 6.40Providing Web ServicesConsuming Web Services

Summary




Support for Web Service Consumers (1)- Background -

The Web Service client developer

implements the client applicationknows how to use the Web Service client proxy in the client application

knows how to get the description of a Web Service(UDDI, WSDL, …)

knows how to generate the Web Service client proxy


Support for Web Service Consumers (2)- Tasks of a Web Service Consumer -

Step 1: Retrieve description of Web ServiceRetrieval of URL of WSDL description

either manually,or using UDDI Browsing

Supported by the Web Service Infrastructure via

Web Service Proxy generationUDDI Client BrowserExchange Infrastructure IFR - browsing




Support for Web Service Consumers (3)- Tasks of a Web Service Consumer -

Step 2: Generate Web Service Client Proxy

Start proxy generator based on imported WSDL Document


Web service Proxy Definition

Step 3: Implementation of Client Application

Use generated client proxies


SAP Development Workbench (SE80)


Demo

DemoWeb ServiceProxy Project




Create Web Service Client Proxy (1)












Display generated Client Proxy (1)- Main properties -


Display generated Client Proxy (2)- Generated entities -




Display generated Client Proxy (3)- Generated structure -


Display generated Client Proxy (4)- Warnings during generation -




Proxy Runtime configuration- Global settings -

Transaction „LPCONFIG“


Proxy Runtime configuration- Global settings -




Proxy Runtime configuration- Operation-specific settings -

Configure Security Settings


Summary

The Enterprise Service Architecture (ESA), SAP’s approach for building services-oriented business applications utilizes Web Services as vital part of its communication and integration strategy

SAP’s rich business functionality, in conjunction withstate-of-the-art technology, enables you to establish cross-company business processes as an integrated part of your development efforts based on Web Services

SAP Web Application Server 6.40 offers an easy, convenient way to build Web services




Q&A

Questions?


Please complete your session evaluation anddrop it in the box on your way out.

Feedback

Thank You !

The SAP TechEd ’03 Basel Team




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®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® 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®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries.

ORACLE® is a registered trademark of ORACLE Corporation.

UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.

Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML 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.

MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One.

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.

Copyright 2003 SAP AG. All Rights Reserved


Corporate Colors for PPT

SAP Blue SAP Gold SAP Gray

You can use these colors with gradations

Remove page for slide show

Documents

Building Web Services with ABAP and SAP Web - … Webservice with...Building Web Services with ABAP and SAP Web Application Server Timm Falter Project Manager Web Services / SAP AG