W8/WP8 App Dev for SAP, Part 1B: Service Generation with NetWeaver Gateway Frameworks
•
1 recomendación•820 vistas
Agenda: Redefine services based on Easy Query MDX GENIL SPI Gateway Services
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a W8/WP8 App Dev for SAP, Part 1B: Service Generation with NetWeaver Gateway Frameworks
Similar a W8/WP8 App Dev for SAP, Part 1B: Service Generation with NetWeaver Gateway Frameworks (20)
Más de SAP PartnerEdge program for Application Development
Más de SAP PartnerEdge program for Application Development (20)
Último
Último (20)
W8/WP8 App Dev for SAP, Part 1B: Service Generation with NetWeaver Gateway Frameworks
- 2. Introduction
- 3. © 2012 SAP AG. All rights reserved. 3 SAP NetWeaver Gateway Service Builder 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 Models can be created based on EDMX-Modeling. The modeling environment follows a project based approach, all relevant data is consolidated in this projects.
- 4. © 2012 SAP AG. All rights reserved. 4 Service Generation Gateway Service Builder - development flow Service Definition Data Model Definition Service Implementation (Code based or mapping) Gateway Backend (SEGW) Service Registration and Hub Activation Gateway Server (/IWFND/MAINT_SERVICE)
- 5. © 2012 SAP AG. All rights reserved. 5 Gateway Service Builder - development flow in detail OData Service Definition in SEGW Declarative Model Definition* Import Data Model (EDMX) Import DDIC/ RFC/BOR Interface* Redefine Data Source Service (GenIL, SPI, BW Easy Query, MDX)Code-Based Implementation* Code-Based Extensions* Data Model Definition (MPC) Service Implementation (DPC) Map RFC/BOR Operation* Service Registration and Hub Activation Service Maintenance Include Gateway Service* * Repeatable within one service Service Generation Data Model Definition Service Implementation (Code based or mapping)
- 6. © 2012 SAP AG. All rights reserved. 6 Agenda Redefine services based on Easy Query MDX GENIL SPI Gateway Services
- 8. © 2012 SAP AG. All rights reserved. 8 Gateway Service Builder – Code generation based on existing business objects in SAP PLM, EAM, … OData Service Definition in SEGW Declarative Model Definition* Import Data Model (EDMX) Import DDIC/ RFC/BOR Interface* Redefine Data Source Service (GenIL, BOL, SPI, BW Easy Query, MDX)Code-Based Implementation* Code-Based Extensions* Data Model Definition (MPC) Service Implementation (DPC) Map RFC/BOR Operation* Service Registration and Hub Activation Service Maintenance Include Gateway Service* * Repeatable within one service
- 9. © 2012 SAP AG. All rights reserved. 9 Gateway Service Builder – redefine existing services Subtitle Step1: Generate a “technical” service which calls the BW Step2 Beautification” of the external names Example Generate services from existing business objects from (for example) PLM and EAM CRM BW HANA Generate services based on existing Gateway services
- 10. © 2012 SAP AG. All rights reserved. 10 SAP NetWeaver Gateway – Analytical Integration SRM SCM ERPPLMCRM SAP Business Suite SAP NetWeaver Gateway HANA Consumer / Channel specific infrastructure OData Sync SAP NetWeaver BW Easy Query MDX
- 11. © 2012 SAP AG. All rights reserved. 11 Service generation – SAP Business Warehouse SAP NetWeaver Gateway enables SAP BW content for light weight consumption via OData. This happens by providing generators for - Easy Query - MultiDimensional eXpresions (MDX)
- 12. © 2012 SAP AG. All rights reserved. 12 Service generation – based on SAP HANA Via the new SAP NetWeaver Gateway with SAP HANA integration capability it is now possible to connect to SAP HANA. Currently only Read-Only access is supported. The following information models can be exposed as an OData Service: Attribute Views Analytic Views Calculation Views
- 13. © 2012 SAP AG. All rights reserved. 13 Service generation based on SPI
- 14. © 2012 SAP AG. All rights reserved. 14 What is the Service Provider Interface – SPI ?
- 15. © 2012 SAP AG. All rights reserved. 15 Service Provider Enhancements - Overview Some SPI objects do not offer a query method. Solution:
- 16. © 2012 SAP AG. All rights reserved. 16 Gateway Service Builder – Gateway service mashup OData Service Definition in SEGW Declarative Model Definition* Import Data Model (EDMX) Import DDIC/ RFC/BOR Interface* Redefine Data Source Service (GenIL, BOL, SPI, BW Easy Query, MDX)Code-Based Implementation* Code-Based Extensions* Data Model Definition (MPC) Service Implementation (DPC) Map RFC/BOR Operation* Service Registration and Hub Activation Service Maintenance Include Gateway Service* * Repeatable within one service
- 17. © 2012 SAP AG. All rights reserved. 17 Mashup Gateway services Example To create a sales order you need two types of master data “Customer” and “Products”. Reuse of existing Gateway services for Customer and Products Leverage analytical read-only services from BW and Hana in CRUD-style service
Notas del editor
- Value Proposition / Theme = (why should a customer care)
- Noit‘s time toactivatetheservice
- The following enhancements simplify and accelerate the implementation process using the OData ChannelGenerators for Frameworks:Service Provider Interface (SPI) is the name of an internal framework used in the WebDynpro-based version of SAP PLM or SAP EAM and several other modules GENIL / BOL (SAP CRM)
- GW-runs-with-HANA: Access from a GW Hub to a HANA system. Reading Metadata from HANA. Either enriching GW objects by HANA Query results as property value or binding HANA Objects into a GW objects tree /Servcie document.Productization planned for SP3 with a likeliness to be distributed over SP3 and SP4
- Value Proposition / Theme = (why should a customer care)
- Value Proposition / Theme = (why should a customer care)
- What is SPI ?The Service Provider Infrastructure (SPI) is an application and UI technology independent layer for business data exposure which is used across the whole Business Suite to build timeless software. It works as the backbone for different feeder technologies like GUIBBs, POWLs and Adobe Forms and offers an FPM integration. Comment: Here Web Dynpro is meantThe SPI handles huge amounts of data with a great performance and no additional buffering while being minimal invasive to the underlying implementation (arbitrary data repositories can easily be connected). Every application that is using the SPI can – out of the box – either run the UI and the backend on the same system or run the UI on a system in the DMZ and the backend on a second system behind the firewall, which is needed in an internet collaboration scenario. Also dynamic backends can be accessed via the SPI, which for example do not have a static DDIC representation of their data structures or which even change their metadata at runtime.Furthermore the SPI offers a central enhancement spot which can be used by customers or partners to enhance the application backend modification free.Source: https://wiki.wdf.sap.corp/wiki/display/SPI/Service+Provider+Infrastructure+%28SPI%29 It is important to highlight that the SPI framework allows to implement DMZ scenarios where for example an “empty” PLM system is placed in the DMZ that talks to the productive PLM system in the intranet.What comes with Gateway:With Gateway for all SPI objects Odata services can be generated
- The BAdI offers following enhancement possibilities: Ø handling of own (new) nodes and/or actions Ø modifying/enhancing SAP implementations (e.g. enriching node data) Ø replacing SAP Service Provider implementation with own logic/coding