In This Session - SAPinsider – SAP conferences ... · PDF fileIn This Session •...

1

In This Session

• This session will give an overview of SAP Fiori and demystify the

deployment options for SAP Gateway

• Get practical tips for how to set up your landscape

• See a live demo of Fiori and its architecture

2

What We’ll Cover

• Fiori Overview

• Fiori Components

• Deployment/Architecture Options for Fiori

• Embedded Deployment Pros and Cons

• Central Hub Deployment Pros and Cons

• Configuration Tips and Tricks

• Fiori Demo

• Wrap-up

3

Fiori Fast Facts

• SAP’s UI of the future

Heavy investments made in SAP Fiori and UI5 and providing a next

generation user experience

300+ prebuilt applications that run on ERP, CRM, SRM, GRC, and more

• Run Anywhere

Fiori allows you to run anywhere – Desktop, tablet, and mobile devices

Full security of SAP NetWeaver: Runs on mobile portal, Sybase Unwired

Platform, and Web browser

• Flexibility

Enhancement framework allows for modification to suit customer’s needs

Fiori is built on open source SAPUI5, which gives you the ability to build

fully customized Fiori applications

4

Three Application Flavors

• Transactional

Simplified traditional GUI screens and interaction with existing processes

and solutions

• Analytical

Real-time insight into operations by displaying key figures and statistical

analysis

• Fact Sheets

Provide Key Facts about central objects in business operations

Source: SAP

5

Custom Fiori Applications

• Look and Feel

Will look and feel the exact same as the SAP-delivered

applications

Full theming capabilities including custom CSS

• Any Business Scenario

Ideally contains a scenario not covered by SAP

Can integrate with any system in SAP landscape via Gateway

• Integration with Launchpad

Supports full integration with Fiori Launchpad

Seamless transition for user from standard to custom Fiori

• Open Source Technology

UI5 is well documented and understood

Lots of custom control and functionality exists (less coding!)

6

The New Fiori Launchpad

• Single entry point for all

Fiori applications

• Each tile represents a

Fiori application

• Tile groups and catalogs

can be customized by

the user

• Security is role-based;

standard SAP security

roles are used

7

What We’ll Cover

• Fiori Overview






• Fiori Demo

• Wrap-up

8

SAP UI Add-On

• SAP_UI Components

Fiori Launchpad and Components

SAPUI5 Libraries

SAP Theme Designer

ABAP Team Provider

Note: SAP_UI comes standard with

SAP NetWeaver 7.4

SAP Fiori

9

Fiori Applications

• Fiori Applications

Delivered as add-on to SAP

NetWeaver and SAPUI5

Consumed via BSP (Business Server

Pages)

Recent releases group common

applications together

Source: SAP

10

OData Integration Components

• Components

Delivered as ABAP add-on to SAP

Business Suite

Provides standard integration

between SAP back end and Fiori UI

• Note: For systems < SAP NetWeaver 7.4

IW_BEP must be installed

11

Architecture for Transactional Applications

Source: SAP

• Transactional applications

support any database (HANA

or non-HANA)

• You can connect multiple

back-end systems to a single

Gateway Server

• The Fiori Applications (UI) and

the Launchpad are installed

and consumed directly on the

Gateway Server

• Note: ONLY transactional

applications can be used

externally (outside of the

intranet)

12

Architecture for Fact Sheet Applications

Source: SAP

• Fact Sheet applications

require HANA as the back-

end database

• Web Dispatcher is used as

the entry point for HTTPS

requests into your system –

tools other than Web

Dispatcher are supported

• Using Fact Sheets, you can

navigate to other

Transactional applications or

other UI technologies (i.e.,

SAP GUI for HTML or Web

Dynpro)

13

Architecture for Analytical Applications

Source: SAP

• Analytical applications

require HANA as the back-

end database and the use of

HANA XS for OData requests

• SAP Web Dispatcher selects

the appropriate server for

requests – either the

Gateway Server or HANA XS

• Unlike the other two

application types, Fiori

OData content is installed

directly in HANA XS

14

What We’ll Cover

• Fiori Overview






• Fiori Demo

• Wrap-up

15

Embedded Deployment

Source: SAP

SAP Gateway IW_BEP

SAP

Gateway

Server

16

Fiori Installs for Embedded Deployment

Components SAP NetWeaver 7.4

Older Versions of SAP NetWeaver

IW_FND X

GW_CORE X

IW_BEP X

SAP_GWFND X

SAP_UI X

17

Central Hub Deployment

Source: SAP

SAP

Gateway

Server

SAP Gateway IW_BEP

18

Fiori Installs for Central Hub Deployment

Gateway Server



IW_FND X

GW_CORE X

SAP_GWFND X

SAP_UI X

Backend System



IW_BEP X

SAP_GWFND X

19

SAP’s Recommended Architecture

Source: SAP

20

What We’ll Cover

• Fiori Overview






• Fiori Demo

• Wrap-up

21

Embedded Deployment

• Advantages

Reduced cost to implement/maintain due to a single landscape

Less configuration = Faster implementation time

• May be appropriate for a single SAP landscape (i.e., only ECC)

22

Embedded Deployment (cont.)

• Disadvantages

Not Scalable – Only applicable to embedded system

Limited by back-end system version

The version of Gateway will be dependent upon updates to the

back end

23

Embedded Deployment Use Case

• May be appropriate if you want to install Gateway in a demo or

lab environment

• Embedded deployment may be used if you are on a single SAP

Landscape (i.e., only ERP)

• Your version of SAP NetWeaver is a recent one – i.e., SAP

NetWeaver 7.4

• This architecture could be used if you want to test Fiori as a

“pilot” scenario. When moved to productive scenario it is

recommended to switch to the Central Hub environment.

24

What We’ll Cover

• Fiori Overview






• Fiori Demo

• Wrap-up

25

Central Hub Deployment

• Advantages

Non-invasive installation – No downtime in back-end system

Scalable

No dependencies on back-end system version –

recommendation is to install SAP NetWeaver 7.4

Clear separation between UI and Business Logic

* SAP recommended deployment

26

Central Hub Deployment (cont.)

• Disadvantages

Higher TCO with a separate landscape and possibly more

maintenance

27

Central Hub Use Case

• The adoption of SAP Fiori has been accepted and will be used in a

productive environment

• Your SAP environment contains multiple backend systems (i.e.,

ECC and CRM)

• Your SAP NetWeaver release is older (< SAP NetW7eaver 7.4)

28

What We’ll Cover

• Fiori Overview






• Fiori Demo

• Wrap-up

29

Considerations for Embedded Deployment

• You must consider the version of SAP NetWeaver in your back-

end system. With an older version you will be limited on the Fiori

applications available.

• SAP_BASIS must be higher than SAP NetWeaver 7.31 SP05 to

meet Gateway prerequisites

• If your back-end system is less than SAP NetWeaver 7.4, you

must manually install all UI add-on components. These

components are included with SAP NetWeaver 7.4.

30

Installation Steps for an Embedded Deployment

1. Install SAP Gateway in your back-end system

2. If your version of SAP NetWeaver is less than 7.4, you must install

the SAPUI5 libraries and tools: SAP_UI and the latest support

packs

3. Install the Fiori OData Services in your back-end system (will be

dependent upon the Fiori applications being installed)

Components NetWeaver 7.31 NetWeaver 7.4

GW_FND X

IW_FND X

IW_BEP X

GW_CORE X

IW_PGW X

31

Installation Steps for an Embedded Deployment (cont.)

4. When activating the Gateway Services (IWFND/MAINT_SERVICE)

you must setup a Local RFC

5. Install the Fiori UI components in your back-end system (will be


32

Considerations for Central Hub Deployment

• The Gateway Server should be SAP NetWeaver 7.4. This

installation will include the UI and Gateway Components and will

allow for ALL Fiori applications and application types.

• If Gateway is not installed in your back-end system (or you are not

on SAP NetWeaver 7.4), you must install IW_BEP

33

Installation Steps for Central Hub Deployment

1. Install and configure a new SAP NetWeaver 7.4 instance. This will

include SAP Gateway 2.0 and the SAPUI5 tools (SAP_UI).

2. If your back-end system is less than SAP NetWeaver 7.4, you

must install IW_BEP

3. Install the Fiori OData Services in your back-end system (will be


34

Installation Steps for Central Hub Deployment (cont.)

4. When activating the Gateway Services (IWFND/MAINT_SERVICE)

you must set up a trusted RFC

Step-by-Step Guide: Trusted RFCs

http://help.sap.com/fiori_bs2013/helpdata/en/ee/805652f4c27

22de10000000a44176d/frameset.htm

5. Install the Fiori UI components in your front-end (Gateway) server

(will be dependent upon the Fiori applications being installed)

http://help.sap.com/fiori_bs2013/helpdata/en/ee/805652f4c2722de10000000a44176d/frameset.htm




35

What We’ll Cover

• Fiori Overview






• Fiori Demo

• Wrap-up

36

Fiori Demo and Architecture Overview

37

What We’ll Cover

• Fiori Overview






• Fiori Demo

• Wrap-up

38

Where to Find More Information

• http://help.sap.com/fiori_bs2013/helpdata/en/ee/805652f4c2722de10000000a44176d/fram

eset.htm

Connect SAP Gateway to SAP Business Suite (Trusted RFC) on the SAP Help Portal

• www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e03be70d-68fb-3010-c6a0-

ff56889c2c81?QuickLink=index&overridelayout=true&58652073478233

“SAP Fiori – Architecture Overview” (SAP, 2013).

• http://help.sap.com/saphelp_fiorierpx1_100/helpdata/en/4c/ca4152fc94b610e10000000a4

4176d/content.htm?frameset=/en/1f/b9e9522806b267e10000000a441470/frameset.htm&c

urrent_toc=/en/40/1b675374bc6655e10000000a423f68/plain.htm&node_id=66

SAP documentation on deployment options, installation, and SAP recommendations

on the SAP Help Portal

• http://help.sap.com/fiori_bs2013/helpdata/en/ec/a941524a6b6760e10000000a423f68/cont

ent.htm

SAP Fiori App Types and Database Requirements on the SAP Help Portal




http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e03be70d-68fb-3010-c6a0-ff56889c2c81?QuickLink=index&overridelayout=true&58652073478233










http://help.sap.com/saphelp_fiorierpx1_100/helpdata/en/4c/ca4152fc94b610e10000000a44176d/content.htm?frameset=/en/1f/b9e9522806b267e10000000a441470/frameset.htm&current_toc=/en/40/1b675374bc6655e10000000a423f68/plain.htm&node_id=66




http://help.sap.com/fiori_bs2013/helpdata/en/ec/a941524a6b6760e10000000a423f68/content.htm



39

7 Key Points to Take Home

• Accelerate Fiori adoption by understanding the application types

and capabilities of each

• Know the different deployment options available and the pros and

cons of each

• Understand the architecture required for each Fiori application

type

• Understand the considerations and configuration differences

between Central Hub and Embedded Deployment

• Have a list of the required installation components for Fiori

• Valuable information provided in the live demo of Fiori, the

Launchpad, and the architecture for both Embedded and Central

Hub Deployments

• Review the step-by-step guidance for both deployment options

41

Disclaimer

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or

an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective

companies. Wellesley Information Services is neither owned nor controlled by SAP SE.

In This Session - SAPinsider – SAP conferences ... · PDF fileIn This Session •...

Documents

Transcript of In This Session - SAPinsider – SAP conferences ... · PDF fileIn This Session •...