SAP NetWeaver Gateway - Gateway Service Consumption

SAP NetWeaver Gateway
Gateway Service Consumption
May 2012

A Branded Service provided by SAP Customer Solution Adoption

Objectives

At the end of this chapter, you will understand:
 The general principles of consuming a Gateway Service
 Creation of OData proxy objects
 Creating an iPhone Application to Consume a Gateway Service

© 2012 SAP AG. All rights reserved. 2

Agenda

 Gateway Service Consumption Overview
 Creating OData Proxy Objects
 Using the Gateway Developer Tool for XCode – Building an iPhone App
 Demo


Agenda

 Demo


My Gateway Service Works… Now What?

Once you’ve built a working Gateway Service,
the next step is to create an application that can
consume this service.

OK, so how do I that?

There are many possibilities.
For instance, you could develop an application for a mobile
client using the Sybase Unwired Platform (SUP),
or you could use a wide variety of programming languages
and freely available OData libraries.


Gateway Service Consumption – Where to Start?

Since the application that consumes a Gateway Service executes outside the scope
of an SAP system, you will first need to choose a programming environment.

You are free to choose any programming environment with which you are
comfortable… SAP places no restrictions on how Gateway services are to be
consumed.
In this course, we will focus on two possible consumption options:
• Java Server Pages
• JavaScript (using the SAPUI5 libraries)

Gateway Service Consumption – General Principles

No matter what programming
language you choose, you
should obtain at the very
least, an OData SDK for your
chosen language.
Many OData SDKs are
available from the developers
section of the odata.org
website.
However, SAP offers some
proxy generation tools that
help accelerate application
development.


Agenda

 Demo


Gateway Service Consumption – Proxy Generation

Six different tools are available for creating OData proxy objects, five of which are
written by SAP.
Language Tool Shipped As Proxy Object Created
Java Oracle Eclipse plug-in Manually at design time
PHP PHP Eclipse plug-in Manually at design time
Group
Visual C# Microsoft Visual Studio 2010 project template Manually at design time
Objective C Apple Stand alone tool Manually at design time
JavaScript ECMA Object within SAPUI5 library Implicitly at runtime
Flash Adobe Flash Builder plug-in from Adobe Manually at design time
The generated OData proxy object acts as the interface to the SAP NetWeaver
Gateway system, and hides many of the lower level details of the OData protocol.
All of these plug-ins can be downloaded from the SAP Community Network page
http://scn.sap.com/community/netweaver-gateway  Developer Tools
The SAPUI5 JavaScript library can also be downloaded from SCN.


Gateway Proxy Generation – Eclipse (Java or PHP)

SAP NetWeaver
Gateway

In Eclipse Helios (3.6) or Indigo (3.7), a Gateway proxy object is created by
selecting a project of type “SAP NetWeaver Gateway”  “Proxy Generation” at
design time.
This functionality is installed as a plug-in for Eclipse.

Gateway Proxy Generation – Visual Studio 2010 (C#)

SAP NetWeaver
Gateway

In Visual Studio 2010, a Gateway proxy object is created by selecting project of type
“SAP Web Application” at design time.
This functionality is installed as a plug-in for Visual Studio.


Gateway Proxy Generation – Flash Builder ≥4.5 (MXML)

SAP NetWeaver
Gateway

In Flash Builder ≥4.5, a Flex Project is created and then you select Data 
“Connect to Data/Service Type”  “SAP Gateway”.
This functionality is installed as a plug-in for Flash Builder.


Gateway Proxy Generation – XCode (Objective C)

Generated
XCode Project

SAP NetWeaver
Gateway

The SAP NetWeaver Gateway developer tool for XCode is a stand-alone tool that
connects to a Gateway server and generates an XCode project.
This project is then opened in XCode and can be edited as required.


Gateway Proxy Generation – SAPUI5 (JavaScript+HTML5)

SAP NetWeaver
Gateway

At design time, you create an sap.ui.model.odata.ODataModel object.
At runtime, the OData object is created automatically.
This functionality is contained both in plug-ins and libraries referenced by your
SAPUI5 Project.

Agenda

 Demo


Creating a Basic iPhone Application – 1/11

When you run the SAP NetWeaver Gateway developer tool for XCode, you are first
asked whether you want to create just a proxy object, or a proxy object wrapped in
a basic application.
The demo application being built here will show first a list of Airports.
The user then selects an airport and will be shown a list of flights departing from
that airport.
Finally, the user can select an individual flight to see its bookings.



Before using the proxy generator tool, you must first configure it to point to the

Press ⌘, (Command comma) to display the configuration screen.
installed OData SDK and at least one Gateway server.



Enter the application name and press Browse



Once you have selected a system, a list of available Gateway services will be
displayed. Press OK, to use the selected service, then Next.



We now must construct the screens the application will use.
Give the first screen a title (“Airports” in this case) and press the plus sign in the
bottom right corner to add fields to this screen.



Knowing that our application will start by providing a list of Airports, we choose
this entity set from the drop down list.
We then choose the appropriate fields from this entity set that we wish to display.
GeoCoordinates is omitted because it is based on a Complex Type.


Now add a second page by clicking on the plus sign in the bottom left corner.
The second page will show only those flights departing from the airport selected on
the first screen.



Notice now that the dropdown list no longer displays entity sets. This is because
the first screen uses the Airports entity set; therefore, we can only use fields
available from the navigation paths belonging to Airports.
In this case, we are interested in the DepartingFlights navigation path.


As with the Flights page, a third page is added for Bookings and fields are added
as seen earlier.
This completes the design process for the screen fields, so we can now press
Finish.


After defining where you want the generated XCode project to be stored, you now
use XCode to open that project.
At this point you could simply run the application or you use the coding as the
starting point for your own custom application.


The application can then be run in the iOS simulator within XCode.


Agenda

 iPhone App Creation
 Demo


Summary

You should now understand:
 The general principles of consuming a Gateway Service
 Creation of OData proxy objects
 Creation of an iPhone Application to Consume a Gateway Service


SAP NetWeaver Gateway - Gateway Service Consumption

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to SAP NetWeaver Gateway - Gateway Service Consumption

Similar to SAP NetWeaver Gateway - Gateway Service Consumption (20)

More from SAP PartnerEdge program for Application Development

More from SAP PartnerEdge program for Application Development (20)

SAP NetWeaver Gateway - Gateway Service Consumption