Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Similar to SAP NetWeaver Gateway for the Uninformed at #sitnl
Similar to SAP NetWeaver Gateway for the Uninformed at #sitnl (20)
Recently uploaded
Recently uploaded (20)
SAP NetWeaver Gateway for the Uninformed at #sitnl
- 1. SAP NetWeaver Gateway for the Uninformed at #sitnl Fred Verheul, NL for Business November 2011
- 2. SAP NetWeaver Gateway for the Uninformed Chris Whealy, Customer Solution Adoption, EMEA November 2011
- 3. Disclaimer This presentation outlines our general product direction and should not be relied on in making a purchase decision. This presentation is not subject to your license agreement or any other agreement with SAP. SAP has no obligation to pursue any course of business outlined in this presentation or to develop or release any functionality mentioned in this presentation. This presentation and SAP's strategy and possible future developments are subject to change and may be changed by SAP at any time for any reason without notice. 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 assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP being intentionally or grossly negligent. © 2011 SAP AG. All rights reserved. 3
- 5. Enterprise Computing for Business Consumers Key Challenges and Desired Outcome From Black Box to Open Any Environment, Any Platform, Any Experience From Business Process Centric to People Centric Optimized for user interaction scenarios Browser Based Mobile Devices Enterprise Consumer Applications Software Cloud Devices From Version Specific to Timeless Non-disruptive, any SAP Business Suite version From SAP Developers to Non-SAP Developers Point to Point Solutions No SAP knowledge required Increase Costs & Complexity From complex APIs to Standards & Simple Based on REST and OData/ATOM SAP Business Suite From IT nightmare to IT control Manage IT complexity with no comprise to IT audit & compliance while deploying innovations CRM SRM SCM PLM ERP From High TCO to Low TCO Consumption pricing model © 2011 SAP AG. All rights reserved. 5
- 6. SAP NetWeaver Gateway Open Experiences Any Device, Any Experience, Any Platform People Sybase Unwired Optimized for user interaction scenarios Enterprise Web Platform Social Software Timeless Non-disruptive, any SAP Business Suite SAP NetWeaver Gateway version Developers SAP Business Suite Simple consumption API – no SAP knowledge required Standards CRM SRM SCM PLM ERP Based on REST and OData/ATOM © 2011 SAP AG. All rights reserved. 6
- 7. © 2011 SAP AG. All rights reserved. 7
- 8. What is the Open Data Protocol (OData)? OData is a Microsoft developed extension to the Atom Publishing and Atom Syndication standards, which in turn, are OData for SAP based on XML and HTTP(S). OData It was designed to provide database-like access to server-side resources. Hence, OData has been described as: Atom Publishing “ODBC for the Web” Atom Syndication It can be used freely without the need for a license or contract. XML OData is also extensible. This allows SAP to supplement the data types used by OData with extra information from the ABAP HTTP(S) Data Dictionary. © 2011 SAP AG. All rights reserved. 8
- 9. Development Paradigms in SAP NetWeaver ® Gateway
- 10. Development in the Gateway Server Life Cycle Management Web Sybase Unwired Platform Enterprise Software Social Development on Gateway Server Service generators for specific data sources (BAPI/RFC/Dynpro Screens*) Design Gateway Core Requirements SAP NetWeaver SAP NetWeaver Time Runtime & Screen Scraping: OData Library Backends must be based on NW 7.00 SP14 or higher + AddOn: IW_SCS Gateway Custom RFC/BAPI & Custom Dev: Dev. Data Source Prov. Backends must be based on 4.6C or Data Conn. higher Generators BAPI RFC Scr. Recommendation Partners/Customers with Backend < ECC 6.0 EHP 0 IW_SCS Gateway AddOns not installed in SAP Business Suite IW_BEP Backend Systems Custom [ERP,CRM,SRM…] Dev. Use of code generators preferred over custom coding © 2011 SAP AG. All rights reserved. 10
- 11. Development in the Gateway Server Life Cycle Management Web Sybase Unwired Platform Enterprise Software Social Development on Gateway Server Service generators for specific data sources (BAPI/RFC/Dynpro Screens*) Design Gateway Core Requirements SAP NetWeaver SAP NetWeaver Time Runtime & Screen Scraping: OData Library Backends must be based on NW 7.00 SP14 or higher + AddOn: IW_SCS Gateway Custom RFC/BAPI & Custom Dev: Dev. Data Source Prov. Backends must be based on 4.6C or Data Conn. higher Generators BAPI RFC Scr. Recommendation Partners/Customers with Backend < ECC 6.0 EHP 0 IW_SCS Gateway AddOns not installed in SAP Business Suite IW_BEP Backend Systems Custom [ERP,CRM,SRM…] Dev. Use of code generators preferred over custom coding © 2011 SAP AG. All rights reserved. 11
- 12. Development in the Backend System – OData Channel Life Cycle Management Web Sybase Unwired Platform Enterprise Software Social Development in the SAP Backend Gateway Server: Configuration only Requirements Design Gateway Core Backends must be based on SAP NetWeaver Time SAP NetWeaver Runtime & NW 7.00 SP18 or higher and need OData Library AddOn: IW_BEP Recommendation Gateway Custom Dev. Data Source Prov. Used by SAP for Standard Software Data Conn. Development Generators Most flexible since it allows access BAPI RFC Scr. to all backend resources and not only to remote enabled interfaces. IW_SCS SAP Business Suite IW_BEP Custom [ERP,CRM,SRM…] Dev. © 2011 SAP AG. All rights reserved. 12
- 13. Development using the OData Channel
- 14. Gateway Service Architecture – 1/5 A Gateway Service is built from 2 different ABAP classes. Contains the implementation of the Gateway Service’s functionality Data Provider Class Model Provider Class Defines the Gateway Service’s interface (Metadata) © 2011 SAP AG. All rights reserved. 14
- 15. Gateway Service Architecture – 2/5 These classes are not required to have any direct programmatic communication with each other. They are combined in to a Gateway Service by means of configuration. Service Group Data Technical Model Provider Object Class Model A Service Group is a Provider configuration wrapper for the Class Data Provider Class A Technical Model Object is a configuration wrapper for the Model Provider Class © 2011 SAP AG. All rights reserved. 15
- 16. Gateway Service Architecture – 3/5 The Service Group contains the definitions for the internal and external names of your Gateway Service. Service Group Data Technical Model Provider Object External Service Class Model Name Provider Internal Class Service Name IMPORTANT! The value entered for the External Name should be meaningful to the end user and is case-sensitive! © 2011 SAP AG. All rights reserved. 16
- 17. Gateway Service Architecture – 4/5 A Gateway Service is created by associating the Technical Model Object with the Service Group. Service Group Data Technical Model Provider Object External Service Class Model Name Provider Internal Class Service Name Gateway Service © 2011 SAP AG. All rights reserved. 17
- 18. Gateway Service Architecture – 5/5 The final configuration step is to activate the Gateway Service. The service is now accessible from outside the SAP NetWeaver system. Service Group Data Technical Model Provider Object External Service Class Model Name Provider Internal Class Service Name Gateway Service Direct access to a Gateway service from a device or browser is only one of several connection possibilities. © 2011 SAP AG. All rights reserved. 18
- 20. Consumption of SAP NetWeaver Gateway Services Q: What’s the best way to consume a Gateway service? A: Well you could use… If fact, you can use any technology with which you are comfortable… © 2011 SAP AG. All rights reserved. 20
- 21. © 2011 SAP AG. All rights reserved. 21
- 22. Next steps • Gateway docu on SDN: http://www.sdn.sap.com/irj/sdn/gateway • Please do the tutorials of Chris Whealy. They can be found via the link above or directly at: • Part 1: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/109c15ed-d8a3-2e10-7c9f-dcb1168aa1ff • Part 2: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/50ad7227-68a9-2e10-b191-905cb9b6c31a • More tutorials available on help.sap.com: • http://help.sap.com/saphelp_gateway20sp02/helpdata/en/56/d0cc05b564411e841141f68294e29f/frameset.h tm • More on OData: http://www.odata.org/developers/protocols/overview • Read the HTTP spec: http://www.w3.org/Protocols/rfc2616/rfc2616.html © 2011 SAP AG. All rights reserved. 22
- 23. Q&A © 2011 SAP AG. All rights reserved. 23
Editor's Notes
- Gateway is open and provides access to SAP Business Suite Data for multiple devices, experiences and platforms.In addition to mobile devices, the interfaces provided by Gateway can be accessed by any Web based applications as well as Enterprise Software and social platforms.Gateway services are optimized for user interaction scenarios. They are not targeted for A2A or B2B scenarios and are thus not intended to be a replacement for the existing Enterprise Services.Gateway supports the timeless principle since it offers non-disruptive access to any SAP Business Suite version.No internal knowledge of an SAP system is required before a developer can consume a Gateway service. The only prerequisite understanding is they are familiar with the OData protocol.
- The Open Data Protocol (OData) is a web protocol for querying and updating data. It has been referred to as “ODBC for the Web”.OData is based on HTTP(S) communication and the Atom Publishing Protocol (AtomPub).For more detailed information, please refer to http://www.odata.orgService DocumentA Service Document is a URL lists all the resources available from a particular service.For instance http://services.odata.org/OData/OData.svcEntity Sets represented as Atom FeedsAn Entity Set is a resource that can be acted upon in some way. Entities are typically represented as Atom Entries and a Collection of typed Entries where an Entry is a record with a:KeyList of properties (primitive and/or complex types)Service OperationsA Service Operation is a verb that performs some task on the resource.Service Operations can accept zero or more input parameters and return entriesService Metadata Document A Service Metadata Document is a self-describing set of metadata that provides an external software system with all the information necessary to consume the particular OData service.The metadata description can be obtained by adding the keyword $metadata to the end of the Service Document URL.For instancehttp://services.odata.org/OData/OData.svc/$metadata
- Technical Use CasesConsumption of well defined SAP Netweaver Gateway objects, e.g. Duet Enterprise or Alloy for connected application systemsConsumption of centrally deployed application contentBenefitsGateway enables routing for Alloy/DUET /Mobile scenarios against multiple backendsDecoupled lifecycle of consumer apps from application backendCentral management of routing & connectivity with application systems SAP Gateway capabilities need to be deployed only once within the landscapeSeparate SAP Gateway system can be implemented in DMZ for external accessIndependent innovation speed of SAP Gateway and connected application systemsConsiderationsSAP Gateway enabling component has to be installed in each application systemCreation of new SAP Gateway objects requires high effortYou can only call coding from the server that is remote enabled like RFC's, BAPI's or Web ServicesThere is always the need for some kind of adaptation between the backend logic and the data model which exposes this logic through OData services with SAP Annotations.This adaptation can be defined either on the Gateway or on the backend which is discussed in the next slideGateway offers support to generate an adaptation against some backend without modifying the backend. With SAP NetWeaver Gateway 2.0 the adaptation of BOR Objects, RFC Function Modules and Screen Scraping are supported. The Tooling is based on model driven development.Alternatively adaptation can be coded in ABAP on the Gateway Server.If the interfaces for data provisioning on a backend already match the requirements, e.g. the RFCs exist, a complete adaptation on Gateway is feasible. Basically, the adaptation wraps remote calls to the backend and converts data between the RFC’s tables and the Gateway API. If However the required remote interfaces do not exist, adequate RFCs for data provisioning would have to be developed.In such a case it would be better to perform the adaption on the backend directly and one should go for the Odata Channel which is described in the following slide.
- Technical Use CasesConsumption of well defined SAP Netweaver Gateway objects, e.g. Duet Enterprise or Alloy for connected application systemsConsumption of centrally deployed application contentBenefitsGateway enables routing for Alloy/DUET /Mobile scenarios against multiple backendsDecoupled lifecycle of consumer apps from application backendCentral management of routing & connectivity with application systems SAP Gateway capabilities need to be deployed only once within the landscapeSeparate SAP Gateway system can be implemented in DMZ for external accessIndependent innovation speed of SAP Gateway and connected application systemsConsiderationsSAP Gateway enabling component has to be installed in each application systemCreation of new SAP Gateway objects requires high effortYou can only call coding from the server that is remote enabled like RFC's, BAPI's or Web ServicesThere is always the need for some kind of adaptation between the backend logic and the data model which exposes this logic through OData services with SAP Annotations.This adaptation can be defined either on the Gateway or on the backend which is discussed in the next slideGateway offers support to generate an adaptation against some backend without modifying the backend. With SAP NetWeaver Gateway 2.0 the adaptation of BOR Objects, RFC Function Modules and Screen Scraping are supported. The Tooling is based on model driven development.Alternatively adaptation can be coded in ABAP on the Gateway Server.If the interfaces for data provisioning on a backend already match the requirements, e.g. the RFCs exist, a complete adaptation on Gateway is feasible. Basically, the adaptation wraps remote calls to the backend and converts data between the RFC’s tables and the Gateway API. If However the required remote interfaces do not exist, adequate RFCs for data provisioning would have to be developed.In such a case it would be better to perform the adaption on the backend directly and one should go for the Odata Channel which is described in the following slide.
- Technical Use CasesEnable applications to be consumed by popular devices via application specific contentScenarios not requiring any routing across different backendsBenefitsDirect local access to metadata and business data Less runtime overheadNo content merge for different applications requiredNo additional separate SAP Gateway system requiredConsiderationsInnovation speed of SAP Gateway and application system need to be in syncDevices need to be integrated with application system on a point-to-point baseDedicated SAP Gateway content not availableIn general we cannot eliminate the backend component since its very task is to expose new tailored interfaces for consumption through SAP NetWeaver Gateway.However, we can eliminate the adaptation component on the Gateway Server. Conceptually, this is achieved by moving the adaption logic to the backend.The resulting concept code is called OData Channel.Hence, the corresponding Gateway API for data and metadata provisioning will be on the backend.This is achieved through interfaces that are provided by the ABAP AddOn IW_BEP that has to be installed in the backend system.Complete adaptation in a backend component leads to significant simplifications in development, maintenance, and deployment.This is because the OData Channel enables the lifecycle of content and metadata to be within one software component in the backend system.
- The configuration screen asks you to enter the internal service name and then uses this value as the external service name.Be careful to enter the name here that you want the end user to see.There is no need to start the internal service name with a Z character, and remember that the value you enter is case-sensitive.
- The activation of a Gateway service takes place in whichever SAP system has the GW_CORE component. This may well be a different system than the one in which you developed the Gateway Service.
- The activation of a Gateway service takes place in whichever SAP system has the GW_CORE component. This may well be a different system than the one in which you developed the Gateway Service.