SAP Fiori Toolkit. Marc Anderegg, RIG, SAP February, Provided by Rapid Innovation Group (RIG)

Transcription

1 SAP Fiori Toolkit Marc Anderegg, RIG, SAP February, 2014 Provided by Rapid Innovation Group (RIG)

2 Agenda SAP Fiori Toolkit Overview SAP Fiori Extensibility Concept Overview Demo Useful Links

3 SAP Fiori Application Types Transactional Task-based Access Access to tasks like change, create, or entire processes with guided navigation Analytical Insight to Action Visual overview over a complex topic for monitoring or tracking purposes Factsheet & Contextual Navigation Search and Explore View essential information about an object and contextual navigation between related objects Runs on any DB and HANA Runs on HANA 3

4 Fiori Building Blocks Design Time Eclipse / SAP Fiori Toolkit Fiori App Fiori App Fiori App Fiori App Fiori App Fiori App Fiori App SAP Fiori Launchpad SAP UI5 Run Time OData OData Service OData Service OData Service OData Service OData Service OData Service OData Service OData Service SAP NetWeaver Gateway SAP HANA XS Design Time NW Gateway Service Builder SEGW / ABAP Workbench SE80 HANA Studio 4

5 SAP Fiori Toolkit Motivation Simplify the standard SAP Fiori Application development process and increase developer productivity by providing a starting point for a developer who wants to create a new application Simplify the development process of extending delivered standard applications 5

6 SAP Fiori Toolkit SCN Page The page contains: ZIP download Documentation Short installation instructions Links to other relevant pages Prerequisites: Eclipse Juno 4.2 SAP Development Tools for Eclipse GWPA SP1 6

7 SAP Fiori Toolkit High Level Architecture SAP NetWeaver Gateway Productivity Accelerator (GWPA) GWPA extension Eclipse Plug-In (Framework) Search & Exploration capabilities Starter application templates Android Toolkit ios Toolkit Java SE Toolkit More... SAP Fiori Toolkit 7

8 SAP Fiori Toolkit Pre-required knowledge Mandatory: Eclipse UI5 Familiar with SAP NetWeaver Gateway OData protocol Fiori apps (for Fiori extensions) Optional: GWPA Fiori apps development Development of OData services using SAP NetWeaver Gateway Service builder (SEGW) + SE80 8

9 SAP Fiori Toolkit Features Overview Part 1 Creation of Fiori extension project o The extension project is a separate project. It contains all extensions to the delivered standard Fiori application. Both manually developed extensions and extensions created by SAP Fiori Toolkit. o The project defines a custom (extension) application which is extending the delivered standard application. OData Service Replacement o Enables the custom application to use a different service than the delivered standard application. Usually this is a service which extends the service used in the delivered standard application. (For example: a new property added in the new service and a new UI field will display this property in the custom application) Starter Fiori Application project o Creates a Starter Application (Fiori Transaction Application) which is using an OData service 9

10 SAP Fiori Extensibility Concept Overview

11 Fiori Extensibility Concept overview Fiori Extensibility Documentation on SAP help portal: 176d/content.htm?frameset=/en/38/265c f2de a44176d/frameset.htm Provides documentation on: Extending the UI Layer Extending the SAP NetWeaver Gateway Layer (OData Extensibility) Extending the SAP HANA Layer Extending the Search Model Layer 11

12 Fiori Extensibility Concept overview Extending the SAP NetWeaver Gateway Layer (OData Extensibility) You can achieve modification-free extensibility by using the Redefine Gateway Service function. For more information, see Redefining OData Services (GW) For OData Extensibility for Fiori, see documentation on SAP help portal: 34/235c f2de a44176d/content.htm?fram eset=/en/38/265c f2de a44176d/framese t.htm By extending an OData service you are creating a custom OData service, or OData project, that redefines an SAP-delivered one. This is done using SAP NetWeaver Gateway Service Builder (transaction SEGW). Example of redefinition of SAP-Delivered OData Project The property NetAmount is added in the custom OData project. 12

13 Fiori Extensibility Concept overview UI Extensibility Configuration of Components o Customization is based on the configuration of Components. A special area of their configuration is dedicated to customization information. This configuration is located in a JavaScript file named Component.js (or Configuration.js). Custom extension project o Customization can be performed on a custom application that extends a delivered standard application. The custom application is located in a separate Eclipse project. Both applications contain the Component.js (or Configuration.js) file and the custom application contains all the changes. Modification free o The delivered standard application remains unchanged and hence the extension is considered to be modification free. Custom application o The custom application becomes the start-up project which then launches the delivered standard application with the additional customizing configuration. 13

14 Fiori Extensibility Example SAP Delivered Standard Application Custom Application (Extended) New button New Field New View 14

15 Fiori UI Extension possibilities in the MVC app OData Extension in NetWeaver Gateway data binding Views (XML Views) Models (OData) implementation interface implementation Controllers (JavaScript) View Extension Custom view content in a predefined extension point of the standard view View Modification Modify certain properties, i.e. hide a control in the standard view View Replacement Custom view replacing a standard view Controller Extension Runtime merging of standard and custom controller Add controller customer functions Override standard controller functions 15

16 SAP Fiori Toolkit Features Overview Part 2 - Extensions Extend Controller o Enables to extend or overwrite the functionality of the base controller, the custom application can merge the controller delivered in the standard application with a new controller. Extend View (using an extension point) o Extension points are inserted in the views of delivered standard applications. This will enable extensibility of delivered standard applications by inserting custom content at the location of these extension points. o Enables to define the Fragment which will be inserted at the position where the extension point is defines. Replace View o Enables to provide a new view instead of a view in the delivered standard application. o A new view can be an empty view or a copy of the view from the delivered standard application. Hide UI Control o Enables to change the visible property of a UI control in a view delivered in the standard application to false. 16

17 Fiori Extensibility Concept overview Development Story Steps to extend a delivered standard application: 1. Import the delivered standard application to Eclipse from BSP container 2. Create an Extension Project for the custom application (using SAP Fiori Toolkit) 3. Add extensions to the custom application (manually by coding or using SAP Fiori Toolkit) 4. Deploy the custom application on BSP container 5. Access the custom application URL 17

18 Fiori Extensibility Concept overview Development Story with OData Service Replacement Steps to extend a delivered standard application: 1. Create the custom OData service (using Gateway Service Builder) 2. Import the delivered standard application to Eclipse from BSP container 3. Create an Extension Project for the custom application (using SAP Fiori Toolkit) (During the creation of the extension project select the option to replace OData service) 4. Add extensions to the custom application (manually by coding or using SAP Fiori Toolkit) 5. Deploy the custom application on BSP container 6. Access the custom application URL 18

19 Demo

20 Topics covered in the Demo Creating a new Extension Project o Structure of the project created Creating Extensions Hide Control Extend View (using extension point) Replace View with an Empty View Replace View with a copy of the delivered View + Extend Controller logic o How Component.js file is modified by the toolkit o How the changes reflect in the custom application Creating a new Application Project o How to select a service? (via URL, via catalog) o Structure of the project created 20

21 SAP Fiori Toolkit Features Wrap-up Creation of Fiori extension project Replace a View Extend a View (using an Extension Point) Hide a UI Control in a View Extend a Controller Starter Fiori application project OData service replacement 21

22 Useful Links SAP Fiori Toolkit Information and Download on SCN SAP Fiori Official documentation Additional Related Information to SAP Fiori SAP Web Dispatcher: acc68e a114084/frameset.htm SAP NetWeaver Gateway 2.0: UI5 UI Development Toolkit for HTML5 - Demo Kit (interactive doc on SAPUI5 / OpenUI5): OpenUI5: UI Development with SAPUI5 documentation: de02b150bce3.html SAP HANA Marketplace SCN (SAP Community Network) What is SAP Fiori (provided by RIG): SAPUI5: SAP for Mobile: 22

23 Marc Anderegg RIG, Business Information Technologies Development

24 2014 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. Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iseries, pseries, xseries, zseries, eserver, z/vm, z/os, i5/os, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, 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. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. 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 shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. 24