Jeff Gebo, Customer Solution Adoption – Mobility Platform

August 2012

New Features in SAP NetWeaver Gateway SP4

© 2012 SAP. 2

Enterprise Computing for Business Consumers Key Challenges and Desired Outcome

SRM SCM ERP

PLM CRM

SAP Business Suite

Browser Based

Applications

Mobile Devices Enterprise

Software

Consumer

Devices Cloud

Point to Point Solutions

Increase Costs & Complexity

© 2012 SAP. 3

Enterprise Computing for Business Consumers Key Challenges and Desired Outcome

SRM SCM ERP

PLM CRM

SAP Business Suite

Browser Based

Applications

Mobile Devices Enterprise

Software

Consumer

Devices Cloud

SAP NetWeaver Gateway

Sybase Unwired

Platform

OData

Open

Any Environment, Any Platform,

Any Experience

People

Optimized for user interaction scenarios

Timeless

Non-disruptive, any SAP Business

Suite version

Developers

Simple APIs, no SAP knowledge required

Standards

Based on REST and OData/ATOM/JSON

© 2012 SAP. 4

SAP NetWeaver Gateway Planned Architecture

Gateway Core

Technology OData with SAP Annotations

Network

Standards

Data Source

Providers

Tools

SA

P N

etW

eaver

SAP NetWeaver

Gateway

Service

Adaptation

REST

Supportability

Monitoring

Security

SAP Business Suite [ERP,CRM,SRM…]

BAPI RFC …

Data Conn.

IDEs

Plug-ins

Events

Metadata

Repository

Consumer Consumer Consumer

Generators

BOR/RFC/SPI/…

Custom

Dev.

© 2012 SAP. 5

SAP NetWeaver Gateway Service Builder (SEGW)

Developer productivity (low TCD) for ABAP

Developer

The SAP NetWeaver Gateway Service Builder

provides a tool to centrally display and create

the definition of an OData Service.

– Runtime artifacts (model provider class, data

provider class, model and service)

– OData artifacts (entity set, entity type and

properties)

– Used data sources and models

EDMX-Model import

DDIC Import

© 2012 SAP. 6

Demo – SAP NetWeaver Gateway Service Builder (SEGW)

© 2012 SAP. 7

Java Script Object Notation (JSON) Support

Most REST services use JSON

– Simple to use on the UI side

Business data represented in JSON format is

~2.5x smaller than ATOM/XML representation!!!

– Faster to parse on client

– Faster to construct on server

Just add query string parameter

$format=json to the URL of the Gateway

OData service.

© 2012 SAP. 8

Demo – JSON

© 2012 SAP. 9

How To Easily Test Your Services

Query string parameter sap-ds-debug=true

makes it easy to test the QUERY and READ

operations in a browser.

The FireFox RESTClient is a simple and free

plugin for testing REST services

– A tool like this is required for non HTTP Get

method requests.

To test the Create/Update/Delete operations

you need to pass in the x-csrf-token

– Protects from Cross Site Request Forgery

attacks

– Learn more on the Help Portal.

© 2012 SAP. 10

Demo – How To Easily Test Your Services

© 2012 SAP. 11

Multiple Origin Composition

Access data from multiple backend systems

with one service call.

Add multiple aliases to the service in

transaction /IWFND/MAINT_SERVICE.

Add “;mo” to the URL of the service.

– Example:

http://<host name>:<port>/sap/opu/odata/iwfn

d/RMTSAMPLEFLIGHT;mo/

More information on the Help Portal.

© 2012 SAP. 12

And Much Much More…

More features in SP4…

$batch – allows you to pass in multiple operations in a single call

– See How To Guide

$skiptoken support – server side paging

– See Help Portal

$inlinecount – includes entity count returned with results of get_entity_set method.

Integration with SAP HANA – make a connection to SAP HANA and expose HANA data as OData Service

via Gateway

– See How To Guide

And More…See entire list here.

What’s To Come in SP5

Generator integration with the Gateway Service Builder (SEGW)

And Much Much More…

Due out end of August (or early September).

Thank you

Jeff Gebo

Customer Solution Adoption

jeff.gebo@sap.com

© 2012 SAP. 14

Legal Disclaimer

The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of

SAP. This presentation is not subject to your license agreement or any other service or subscription agreement with SAP. SAP

has no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or

release any functionality mentioned therein. This document, or any related presentation and SAP's strategy and possible future

developments, products and or platforms directions and functionality are all subject to change and may be changed by SAP at

any time for any reason without notice. The information on this document is not a commitment, promise or legal obligation to

deliver any material, code or functionality. 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. This

document is for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or

omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent.

All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially

from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as

of their dates, and they should not be relied upon in making purchasing decisions.