HANA SPS07 Studio Development Perspective
Download as PPTX, PDF•0 likes•2,904 views
This document provides an overview of new features and enhancements to the SAP HANA Studio Development Perspective between SPS 06 and SPS 07. Key highlights include: - Integration of standard Eclipse projects and team provider interface for storing objects in the SAP HANA repository. - Enhancements to HANA-specific editors, debugger, and support for server-side JavaScript (XSJS). - Planned additions and improvements to the repository interface, repository browser, synchronization view, project explorer, new artifact templates, and ability to run artifacts directly from the studio. - Support for inactive testing to allow multiple developers to work on the same content simultaneously. - Introduction of a change manager
HANA SPS07 Studio Development Perspective
- 1. What´s New? SAP HANA SPS 07 SAP HANA Studio Development Perspective (Delta from SPS 06 to SPS 07) SAP HANA Product Management November, 2013
- 2. SAP HANA Studio Development Perspective Goal: Provide an extensible and integrated development environment supporting all development artifacts necessary for building a HANA application, covering development, testing, debugging, supportability and lifecycle management. As new and existing technologies are being integrated into HANA, a seamless integration of the corresponding external tools in the HANA Development Workbench should be possible. Target customer: HANA Application Developer (Internal and external developers). Including content development scenarios. © 2013 SAP AG. All rights reserved. Public 2
- 3. SAP HANA Studio Development Perspective • Utilizes standard Eclipse projects – HANA Specific, General SAP Projects, and even 3rd party ones • Standard Eclipse Team Provider interface for storing all objects into the SAP HANA Repository © 2013 SAP AG. All rights reserved. Public 3
- 4. SAP HANA Studio Development Perspective • HANA Specific Editors and Debugger Enhancements (for example: XSJS – Server Side JavaScript) © 2013 SAP AG. All rights reserved. Public 4
- 5. SAP HANA Studio Development Perspective: Roadmap – Planned for SPS 07 Native Repository interface implementation Repository Browser Enhancements Synchronization View Project Explorer Enhancements New Artifact Templates Run Artifacts from the Studio Inactive Testing SAP HANA Text Editor Mass Activation Change Manager CDS Graphical Editor © 2013 SAP AG. All rights reserved. Public 5
- 6. Native repository interface implementation • Removal of dependencies upon REGI and the HANA Client; simplify installation and setup • Improved performance by batching operations; better tolerance for high latency connections between HANA Studio and Server • Dependencies during activation are considered for multiple object operations © 2013 SAP AG. All rights reserved. Public 6
- 7. Repository Browser enhancements • Edit package contents from the Repository browser • Remove From Client – essentially undo a Check Out operation without risk of deleting content within the Repository • Regenerate – force runtime regeneration without the need to go through activation • Better handling of deletion of content via activation within the Repository browser © 2013 SAP AG. All rights reserved. Public 7
- 8. Synchronization View • Integration of HANA Repository tools into the standard Eclipse Synchronization tool • View pending deletions on the server after the content is gone from the client • Compare differences between local Repository Workspace and server side Repository content © 2013 SAP AG. All rights reserved. Public 8
- 9. Project Explorer enhancements • Projects contain both Catalog and Repository nodes under the System Library • Additional Team menu options: © 2013 SAP AG. All rights reserved. Public 9
- 10. New artifact templates • Wizards for the creation of the majority of all development artifacts • Enforce naming rules and automatically apply file extensions to greatly reduce common development errors © 2013 SAP AG. All rights reserved. Public 10
- 11. Run Artifacts from the Studio • Test XSJS, XSODATA and HTML content directly from the Project Explorer • Run in your default web browser in a separate window © 2013 SAP AG. All rights reserved. Public 11
- 12. 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 12
- 13. 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 13
- 14. SAP HANA text editor • Generic text editor for all textual based HANA artifacts without their own specific editor • Default mapping in HANA Studio now uses this editor • Always displays HANA System ID, Editing User, HANA Hostname, and HANA Instance Number in editor header • Creates a foundation for future artifact specific features © 2013 SAP AG. All rights reserved. Public 14
- 15. Mass activation • New activation dialog displays all inactive objects across all projects for the same repository workspace • New activation option under Team menu to Activate All © 2013 SAP AG. All rights reserved. Public 15
- 16. Change manager • Automatic recording of changes to a change list • The ability to release changes for just a sub-set of objects within a package • Supports multiple streams of development on the same package(s) in parallel with reduced risk of accidentally transporting unwanted changes © 2013 SAP AG. All rights reserved. Public 16
- 17. Development model 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 17
- 18. 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 18
- 19. 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 19
- 20. CDS/HDBDD Graphical Editor • Added graphical representation of the HDBDD Entities and their associations • Graphical mode is ready only. All changes made to the source code editor • Navigation into the source editor from the graphical display © 2013 SAP AG. All rights reserved. Public 20
- 21. 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 21
- 22. Thank you Contact information Thomas Jung SAP HANA Product Management [email protected] To get the best overview of what’s new in SAP HANA SPS 07, read this blog.
- 23. © 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 23
- 24. © 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 24
Editor's Notes
- #18: 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.