SAPUI5 & Fiori – Where ABAP-Er Meets Javascript
. SAPUI5 & Fiori – Where ABAP-er Meets JavaScript Igor Barbarić Content • Web@ABAP - History • SAPUI5 & Fiori – Key Features, Architecture • SAPUI5 vs Fiori • OpenUI5 vs SAPUI5 • Development Environments • Learning Content • Personal Experience: First Project Content • Web@ABAP - History • SAPUI5 & Fiori – Key Features, Architecture • SAPUI5 vs Fiori • OpenUI5 vs SAPUI5 • Development Environments • Learning Content • Personal Experience: First Project Web@ABAP – History 1. Business Server Pages (BSP, 2002) = • Not responsive HTML + ABAP-script • SAP Web Server only 2. WebDynpro (2003 Java, 2004 ABAP) = • ABAP/Java-only (no HTML, CSS, Script) SAP backend only • Performance issues 3. SAP Web Client (2007) = BSP + Dev Worbkench + GenIL Model • No (difficult) theming / branding 4. SAPUI5 & Fiori (2013) = BSP + SAPUI5 + HTML5 + CSS + JavaScript Content • Web@ABAP - History • SAPUI5 & Fiori – Key Features, Architecture • SAPUI5 vs Fiori • OpenUI5 vs SAPUI5 • Development Environments • Learning Content • Personal Experience: First Project Fiori – SAP’s Strategic Direction • “Over time, we plan to move all SAP solutions in this direction.” (support.sap.com SAP Product Strategy) SAP Fiori – Design Award Winner gartner.com red-dot.sg SAPUI5 & Fiori – Key Features • HTML5 + JavaScript + CSS3 + jQuery • Models: JSON, XML, OData • Stateless • Extendable • Flexible design (Theming, Branding, Corporate Identity) • Client-side libs & rendering (server performance!) • Any web server (SAP ABAP, SAP HANA, Tomcat, Jetty...) • Any backend (also non-SAP) • Any device / client (responsiveness) • Open source (OpenUI5) • No need for SAP NW server to play with SAPUI5/Fiori Architecture Client (Web Browser): SAPUI5 Views with “sap.m” Views with lib “sap.ui.commons” lib Models (JSON, XML, Controllers OData) Server No SAP system! UI5 Fiori UI5 Fiori SAPUI5 BSP Fiori SAP Web BSP Lchpd XS Engine BSP Lchpd XS Engine Web Page Launchpad Gateway Server, e.g.
[Show full text]