HANA SPS07 Extended Application Service
Download as PPTX, PDF1 like3,392 views
- Guides user through creation of a new application - Collects key information about the application - Creates initial Delivery Units and Packages - Sets up namespaces and permissions - Sets up initial structure and metadata - Reduces manual setup effort © 2013 SAP AG. All rights reserved. Public 30 SAP HALM: Transport Templates • Pre-defined transport templates - Specify standard transport configurations - E.g. transport all objects in a Delivery Unit - Or transport specific Packages only • Simplify and standardize transports - Users just select template rather than configuring transport
HANA SPS07 Extended Application Service
- 1. What´s New? SAP HANA SPS 07 SAP HANA Extended Application Services (XS) & Content Lifecycle Management (Delta from SPS 06 to SPS 07) SAP HANA Product Management December, 2013
- 2. Contents SAP HANA Extended Application Services (XS) Overview What’s New for XS in SPS 07 SAP HANA Native Content Lifecycle Management Overview What’s New for SAP HANA Native Content Lifecycle Management in SPS 07 SAP HANA User Interface Integration Services: Overview and What’s New © 2013 SAP AG. All rights reserved. Public 2
- 3. Overview: SAP HANA Extended Application Services (XS)
- 4. SAP HANA Extended Application Services (XS) Introduction What: Small footprint application server / web server / basis for an application development platform inside SAP HANA Rationale: Enable application development and deployment while minimizing architectural “layers” Create apps that have an http-based UI (browser, mobile apps) Apps run directly on SAP HANA, w/o additional external servers or components -> simplified system architecture = low TCO Tight integration w/ SAP HANA DB -> best possible performance Scope: wide range of apps Lightweight small web-based applications Complex enterprise business applications © 2013 SAP AG. All rights reserved. Public 4
- 5. Development model for SAP HANA based native applications SAP HANA extended application services offer Easy access to SAP HANA database via HTTP-based consumption Attractive, dynamic HTML5 UI applications via OData services or by writing native application-specific code that runs in SAP HANA context Built-in web server to access static content stored in SAP HANA repository …and much more Application development following a layered approach UI rendering completely in the client (browser, mobile apps) Server-side procedural logic in JavaScript All artifacts stored in the SAP HANA repository © 2013 SAP AG. All rights reserved. Public 5
- 6. SAP HANA Extended Application Services – Overview Front-end Technologies http/s HTML5 / SAPUI5 Client-side JavaScript Control Flow Technologies OData Server-Side JavaScript XMLA Client: Browser or Mobile Presentation logic SAP HANA XS Control flow logic Data Processing Technologies SQL / SqlScript Calculation Engine Functions Application Function Library (AFL) © 2013 SAP AG. All rights reserved. Data Calculation logic Public 6
- 7. Development Model Overview UIS SAPUI5 CDS – Core Data Services • Data Definition Language • Query Language • Expression Language XSODATA XSJS XSXMLA InA HDBRole HDBTable CDS SQLScript SQL Views © 2013 SAP AG. All rights reserved. AFL Public 7
- 8. What’s New for XS in SPS 07
- 9. CDS/HDBDD Syntax Changes - Associations • Associations define relationships between Entities (tables) • Not yet integrated into the catalog/SQL but can be referenced when defining views within the same CDS object © 2013 SAP AG. All rights reserved. Public 9
- 10. CDS/HDBDD Syntax Changes - Views • CDS syntax expands to include the definition of views • Views can utilize the defined associations between entities • Join type automatically determined from association definition of the entity © 2013 SAP AG. All rights reserved. Public 10
- 11. Inactive Testing • Ability to execute the inactive version of xsjs, xsodata, xsjslib, or any static web content • Better support multiple developers working on the same content at the same time as they can test just their localized changes • Requirements: • • Server must be running in developer_mode On the client side set a cookie name sapXsDevWorkspace to the name of your Repository workspace © 2013 SAP AG. All rights reserved. Public 11
- 12. Inactive Testing (continued) • Ability to execute the inactive version of xsjs, xsodata, xsjslib, or any static web content • Better support multiple developers working on the same content at the same time as they can test just their localized changes • Prerequisites: • • Server must be running in developer_mode On the client side set a cookie name sapXsDevWorkspace to the name of your Repository workspace © 2013 SAP AG. All rights reserved. Public 12
- 13. OData CRUD XSJS Exits UIS SAPUI5 XSODATA • Low coding OData REST service generation framework XSODATA XSJS XSXMLA • Based upon existing tables and views • CRUD (Create, Read, Update, Delete) operations support with SQLScript exits InA HDBRole HDBTable CDS • New for SPS 07: Create, Update, Delete exits support XSJS © 2013 SAP AG. All rights reserved. SQLScript SQL Views AFL Public 13
- 14. OData JavaScript Exits • Processing exits can reference xsjslib files and specific JavaScript functions • The database connection and temporary tables with the before and after values are passed to this function • Particularly useful for server-side validations (but open for other use cases too) © 2013 SAP AG. All rights reserved. Public 14
- 15. Other Miscellaneous OData Features New in SPS 07 • Annotations: e.g. sap:label, sap:unit, sap:text – available for use with texts for analytic views • Associations between parameterized CalcViews • Access to translatable parts of arbitrary runtime objects - support for translatable texts © 2013 SAP AG. All rights reserved. Public 15
- 16. Job Scheduling • HANA now contains a Job Scheduler which can run XSJS and SQLScript • New Development artifact: XSJOB • Extension to the Admin tool to maintain job definitions and view job logs © 2013 SAP AG. All rights reserved. Public 16
- 17. Job Scheduling – XSCRON syntax • CRON-like syntax for controlling job timings and repetitions © 2013 SAP AG. All rights reserved. Public 17
- 18. Job Scheduling – XSJS API • New Job extension to the XSJS APIs • Ability to programmatically create and cancel jobs © 2013 SAP AG. All rights reserved. Public 18
- 19. Authentication for XS: New Options for SPS 07 XS Authentication Options: - Basic Authentication - Form-based authentication - SSO (Single-Sign On) via SAP Logon Tickets - SSO via X.509 (standard for Public Key Infrastructure) - SSO via SAML 2.0 (Security Assertion Markup Language) - SSO via SAML2 also for XHR (ajax) - NEW for SPS 07 - SSO via Kerberos - NEW for SPS 07 - Outbound SSO via SAP Assertion Tickets - NEW for SPS 07 © 2013 SAP AG. All rights reserved. Public 19
- 20. Other Miscellaneous XS New Features in SPS 07 XS JavaScript / XS Layer: • Last-Modified header for static resources • HTTP Compression © 2013 SAP AG. All rights reserved. Public 20
- 21. Overview: SAP HANA Native Content Lifecycle Management
- 22. Content lifecycle management in SAP HANA Managing “content” in SAP HANA SAP HANA content defined: Not part of the core SAP HANA DB installation itself Is delivered by SAP as part of SAP HANA optimized solutions Is created in SAP HANA-based development projects (partner, customer) Sometimes called “objects” or “artifacts” Content comprises all kinds of objects, for example: Schemas and table definitions Attribute views, analytic views and calculation views Procedures and privileges SQLScript, JavaScript and HTML Roles and permissions © 2013 SAP AG. All rights reserved. Public 22
- 23. Content lifecycle management in SAP HANA The repository The repository and lifecycle management of objects Native feature of SAP HANA providing “backend” functionality for content lifecycle management Used to manage various types of design time objects (Content) During deployment/activation the design time objects become runtime objects (Catalog) SAP HANA Studio Modeling Perspective run time Key functions provided by the repository: Object versioning Namespace concept Support for server-based development design time SAP HANA content © 2013 SAP AG. All rights reserved. Public 23
- 24. Content lifecycle management in SAP HANA Transport of changes in a typical basic transport landscape SAP HANA Development System SAP HANA QA/Test System SAP HANA Productive System Delivery Unit Delivery Unit Delivery Unit Packages Packages Packages Views, Procedures, P rivileges, etc. Views, Procedures, Privileges, etc. Views, Procedures, P rivileges, etc. © 2013 SAP AG. All rights reserved. Public 24
- 25. SAP HANA Application Lifecycle Management (HALM) Use cases New SAP customers without ABAP-footprint SAP customers with the need for a lightweight transport management © 2013 SAP AG. All rights reserved. Simple and easy Constraints Native SAP HANA transport tool, which can be used without additional systems Lightweight and easy-to-use tool Easy setup and minimal configuration effort No central management of extended system landscapes No transport synchronization to non-HANA content No integration in SAP process tools (ChaRM, QGM) Public 25
- 26. What’s New: SAP HANA Native Content Lifecycle Management
- 27. Change Tracking • Optional mode for managing content in a promote-to-production system landscape (activate in HALM) • Automatic recording of changes to a change list • Allows a developer (or team) to work on a development artifact and release the “change” only when the artifact is ready to promote to the test system • Provides more precise control over which objects get transported from the development system © 2013 SAP AG. All rights reserved. Public 27
- 28. SAP HANA Application Lifecycle Management: Home Screen • Usability enhancement • Easy navigation to key features • Quick overview of transport information © 2013 SAP AG. All rights reserved. Public 28
- 29. SAP HANA Application Lifecycle Management: Dependency Viewer • Graphical tool to display dependencies between Delivery Units • Graphical depiction is interactive – can be rotated and shifted around to provide different perspectives • Useful for determining which Delivery Units should be transported together • Useful for detecting unwanted dependencies, in order to clean them up © 2013 SAP AG. All rights reserved. Public 29
- 30. SAP HALM: Create Application Wizard • Wizard to expedite key initial steps in application development • Creates design-time content artifacts automatically © 2013 SAP AG. All rights reserved. Public 30
- 31. More New HALM Features in SPS 07 • Tool support for transport of SAP HANA Changes (Change Tracking) • Transport of SAP HANA products (all relevant Delivery Units and product definition) • Improved system management (without additional logon) • Object preview during plain file import • Easier assignment for packages to Delivery Units • HALM integration into SAP HANA Studio • HALM integration into Web IDE (just a link) © 2013 SAP AG. All rights reserved. Public 31
- 32. Other Miscellaneous Content LM New Features in SPS 07 Content Lifecycle Management: • CTS+: exposing the contained object lists © 2013 SAP AG. All rights reserved. Public 32
- 33. Overview and What’s New: SAP HANA User Interface Integration Services
- 34. SAP HANA UI Integration Services Overview With SAP HANA UI Integration Services, developers and designers can easily make use of standardized UI services to be leveraged in their standalone HANA applications or - in addition - create and design application sites based on SAP HANA applications using consistent UI patterns to support end-to-end business scenarios with harmonized user experience across applications. Provides end users a state-of-the-art user experience to seamlessly integrated HANA native applications Enables designers to easily organize applications and widgets into sites via an intuitive design environment Gives developers a simple way to use standardized services for creating application sites and widgets, integrated in the SAP HANA Developer Studio © 2013 SAP AG. All rights reserved. Public 34
- 35. SAP HANA UI Integration Services Key Capabilities SAP HANA UI Integration Services provide a set of UI services and UI patterns on top of HANA XS allowing the easy re-use of those services as well as the aggregation of wrapped XS applications into shell experiences The SAP HANA UI Integration Services are fully integrated into the SAP HANA Developer Studio and provide wizards and a visual design time environment for creating those shell experiences Examples of services provided by SAP HANA UI Integration Services: o Sites and page building: state-of-the-art design environment for managing sites, page navigation, layout and content o Personalization and property persistence: persistency of widget properties on user level o Publish-Subscribe: eventing mechanism allowing cross-widget data interchange o Context: stable URL allowing bookmarking and sharing © 2013 SAP AG. All rights reserved. Public 35
- 36. SAP HANA UI Integration Services Development Environment SAP HANA UI Integration Services are tightly integrated into the SAP HANA Studio – the development environment for SAP HANA Native applications The creation of UI Integration Services related objects is supported by dedicated wizards Editor for using UI services API in your code Application site Widget Developers enjoy the full life cycle support of SAP HANA Creation wizard for application sites and widgets © 2013 SAP AG. All rights reserved. Public 36
- 37. SAP HANA UI Integration Services What’s new in SAP HANA SPS 07 Enhanced Catalog Services allowing to retrieve non-widget content Widget Directory leveraging the new catalog service enhancements New permissions mechanism on Application Sites Introduction of a new navigation service Supporting the Golden Reflection Theme and the new Blue Crystal Theme Demo content available as part of the SHINE demo package © 2013 SAP AG. All rights reserved. Public 37
- 38. 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 intentionally or grossly negligent. © 2013 SAP AG. All rights reserved. Public 38
- 39. Thank you Contact information Ron Silberstein SAP HANA Product Management AskSAPHANA@sap.com To get the best overview of what’s new in SAP HANA SPS 07, read this blog.
- 40. © 2013 SAP AG. All rights reserved. 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. National product specifications may vary. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP 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 other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices. © 2013 SAP AG. All rights reserved. Public 40
- 41. © 2013 SAP AG. Alle Rechte vorbehalten. Weitergabe und Vervielfältigung dieser Publikation oder von Teilen daraus sind, zu welchem Zweck und in welcher Form auch immer, ohne die ausdrückliche schriftliche Genehmigung durch SAP AG nicht gestattet. In dieser Publikation enthaltene Informationen können ohne vorherige Ankündigung geändert werden. Einige der von der SAP AG und ihren Distributoren vermarkteten Softwareprodukte enthalten proprietäre Softwarekomponenten anderer Softwareanbieter. Produkte können länderspezifische Unterschiede aufweisen. Die vorliegenden Unterlagen werden von der SAP AG und ihren Konzernunternehmen („SAP-Konzern“) bereitgestellt und dienen ausschließlich zu Informationszwecken. Der SAP-Konzern übernimmt keinerlei Haftung oder Gewährleistung für Fehler oder Unvollständigkeiten in dieser Publikation. Der SAP-Konzern steht lediglich für Produkte und Dienstleistungen nach der Maßgabe ein, die in der Vereinbarung über die jeweiligen Produkte und Dienstleistungen ausdrücklich geregelt ist. Keine der hierin enthaltenen Informationen ist als zusätzliche Garantie zu interpretieren. SAP und andere in diesem Dokument erwähnte Produkte und Dienstleistungen von SAP sowie die dazugehörigen Logos sind Marken oder eingetragene Marken der SAP AG in Deutschland und verschiedenen anderen Ländern weltweit. Weitere Hinweise und Informationen zum Markenrecht finden Sie unter http://www.sap.com/corporateen/legal/copyright/index.epx#trademark. © 2013 SAP AG. All rights reserved. Public 41
Editor's Notes
- #8: The Core Data Services comprise a family of domain-specific languages (highlighted in the illustration above) which serve as a common core model for all stacks on top:The Data Definition Language (DDL) for defining semantically rich domain data models which can be further enriched through Annotations. The Query Language (QL) for conveniently and efficiently reading data based on data modelsas well as for defining views within data models. The Expression Language (EL) for specifying calculated fields, default values, constraints, etc.within queries as well as for elements in data models Besides these DSLs, Core Data Services also comprise advanced means for writing data, handling transactions, access control – yet these services are not yet specified in details as of now. Core Data Services focus on providing functional services independent of any programming language and language paradigms. They don't specify nor make assumptions on how to add application logic and behavior using general-purpose programming languages and services of application containers.Further background – not necessarily for presentation:The CDS data definition language supports for example: Definition of reusable structured typesStructured fields (instead of flat tables)Calculated fieldsAssociations between entities, that can be used to explicitly model the structural relationships between data. This information can be used when writing queries in the CDS query language. Since path expressions can be used instead of SQL joins, queries are much easier to write and understand. A modification-free extension mechanism that can be used by add-on developers, partners or customers to add fields to entities and views, for example.Annotations for defining different types of metadata. CDS Core annotations are available for example for metadata describing hierarchies, for translatable field labels to be shown in user interfaces, for hints for compilers and generators, and in the future also metadata for analytical clients (attributes, measures, hierarchies, default aggregation). In addition, domain-specific annotations will be available. Domain-specific annotations can, for example, be used to annotate a field of a business entity with information about the kind of data it contains, for example whether it is a URL, a name, an amount, or a quantity. Such metadata can be used by user interfaces to adjust the display and interaction accordingly. CDSviews based on existing tables (created by previous releases or via replication) to make the data available in the CDS world and to model additional semantics such as associations. Reflection. It is planned to give applications access to metadata using the CDS query language.