Configuration of SAP Fiori Infrastructure

PDF download from SAP Help Portal:

http://help.sap.com/fiori_bs2013/helpdata/en/25/4a4c52eea9c871e10000000a44176d/content.htm
Created on July 10, 2014

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

2014 SAP SE or an SAP affiliate company. 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 SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE 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 SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 7

Table of content
1 Configuration of SAP Fiori Infrastructure
1.1 Setup of SAP Fiori Launchpad
1.1.1 Activate OData Services for SAP Fiori Launchpad
1.1.2 Activate SICF Services for SAP Fiori Launchpad
1.1.3 Assign Administrator Role for SAP Fiori Launchpad to Administrat
1.1.4 Assign Role with Launchpad Start Authorization to End Users
1.1.5 Configure a Logout Screen for the SAP Fiori Launchpad (Optional)
1.1.6 Create RFC Connection for Back-End Transactions (Fact Sheets)
1.2 Setup of SAP Fiori Search

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 7

1 Configuration of SAP Fiori Infrastructure

To be able to install single apps in your SAP Fiori system landscape, you have to configure the SAP Fiori infrastructure.

1.1 Setup of SAP Fiori Launchpad

The SAP Fiori launchpad is the entry point to the apps, from desktop and mobile devices. You need to configure the SAP Fiori launchpad so that users can
access those apps that have been assigned to their respective role.
For detailed information about the configuration tasks for the Fiori launchpad, see the following documentation:
For SAP NetWeaver 7.31, see SAP Library for User Interface Add-On 1.0 on SAP Help Portal at http://help.sap.com/nw-uiaddon Application Help
SAP Library
SAP Fiori Launchpad Initial Launchpad Configuration .
For SAP NetWeaver 7.4, see SAP Help Portal at http://help.sap.com/nw74 Application Help
UI Technologies in SAP NetWeaver UI Frameworks
based on HTML5, JavaScript and CSS SAP Fiori Launchpad Initial Launchpad Configuration .

1.1.1 Activate OData Services for SAP Fiori Launchpad

The activation of the OData services and of the ICF services are required to initially set up the SAP Fiori launchpad and the SAP Fiori launchpad designer. SAP
Gateway provides the infrastructure for the OData services used by the SAP Fiori launchpad, and the Fiori apps. An OData service has to be enabled in SAP
Gateway which establishes a mapping between the technical OData service name and the corresponding back-end service.

Procedure
1. Run transaction Activate and maintain services (/IWFND/MAINT_SERVICE) on the front-end server.
2. Use the system alias of your local system when activating the following services:

Note
Do not activate the /UI2/LAUNCHPAD service. This service is not relevant for SAP Fiori.
The service names listed below are concatenations of the namespace /UI2/ and the technical names of the individual services. Enter these
concatenations when adding new services in transaction /IWFND/MAINT_SERVICE. When searching for services, you need to search either by
namespace or by technical name.
/UI2/PAGE_BUILDER_CONF
/UI2/PAGE_BUILDER_PERS
/UI2/PAGE_BUILDER_CUST
/UI2/INTEROP
/UI2/TRANSPORT
The services are activated in your customer namespace, with the following technical names, for example:
ZINTEROP
ZPAGE_BUILDER_CONF
ZPAGE_BUILDER_CUST
ZPAGE_BUILDER_PERS
ZTRANSPORT
3. Call each service once by selecting it in transaction Activate and maintain services (/IWFND/MAINT_SERVICE), then choosing Call Browser in the
screen area ICF Nodes . Select the OData node, not the SDATA node.
You have called a service successfully when an XML document is displayed without any error messages.

Note
When you call a service, a hash key is generated in the background. The hash key is required for the generation of authorization profiles under Assign
Administrator Role for SAP Fiori Launchpad to Administrator User.
You can verify the hash key generation in table USOBHASH in transaction Data Browser (SE16). In the selection screen, specify the following:
R3TR in the PGMID field
IWSG in the Object field
The technical service name in the OBJ_NAME field
The hash key should be displayed in the NAME column of the results table.

1.1.2 Activate SICF Services for SAP Fiori Launchpad

In addition to the ICF services that correspond to the OData services you have to activate the following ICF services manually.

Procedure
1. Run transaction Maintain Services (SICF) on the front-end server.
2. In the menu under

Service/host

Activate

, activate the services under the following subtrees:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 7

Note
In the Activation of ICF Services dialog box, choose Yes with the hierarchy icon to activate all child nodes under a service.
/default host/sap/bc/ui2/nwbc/
/default_host/sap/bc/ui2/start_up
/default_host/sap/bc/ui5_ui5/sap/ar_srvc_launch
/default_host/sap/bc/ui5_ui5/sap/ar_srvc_news
/default_host/sap/bc/ui5_ui5/sap/arsrvc_upb_admn
/default_host/sap/bc/ui5_ui5/ui2/ushell
/default_host/sap/public/bc/ui2
/default_host/sap/public/bc/ui5_ui5

1.1.3 Assign Administrator Role for SAP Fiori Launchpad to

Administrator User
You copy the administrator role for the SAP Fiori launchpad delivered by SAP and assign it to your administrator user. The administrator is then authorized to use
the SAP Fiori launchpad designer.

Prerequisites
You have created an administrator user who needs extensive authorizations, such as S_SERVICE, S_DEVELOP, /UI2/CHIP, and S_CTS_SADM. If applicable,
create the user with the ID the user already has in the back end.

Procedure
1. Run transaction Role Maintenance (PFCG) to copy the role SAP_UI2_ADMIN_700 to your customer namespace.
2. On the Menu tab, open the menu of the pushbutton for adding objects (+ button). Select the object type Authorization Default .
3. Choose TADIR Service from the menu for the Authorization Default . Specify the following values:
Program ID: R3TR
Object Type: IWSG
4. In the table, enter the names of your activated services in the form <technical name>_<four-digit version number with leading
zeros>, for example ZINTEROP_0001 and ZPAGE_BUILDER_CONF_0001. For the list of the activated services, see Activate OData Services for SAP
Fiori Launchpad.
5. On the Authorizations tab, choose Propose Profile Name next to the Profile Name field.
6. Choose Change Authorization Data and then Generate .
You have generated a role with five IWSG authorizations and five IWSV authorizations. The IWSV authorizations are included in the role delivered by SAP,
so they are not in your customer namespace.
7. Assign the new role to your administrator user.

1.1.4 Assign Role with Launchpad Start Authorization to End

Users
SAP delivers a predefined role with start authorizations for the SAP Fiori launchpad.

Prerequisites
You have created a user in transaction SU01, using the same user ID as on the back-end server.

Procedure
1. Run transaction Role Maintenance (PFCG) to copy the role SAP_UI2_USER_700 to your customer namespace.
2. On the Menu tab, open the menu of the button for adding objects (+ button). Choose the object type Authorization Default .
3. Choose TADIR Service from the menu for the Authorization Default . Specify the following values:
Program ID: R3TR
Object Type: IWSG
4. In the table, enter the following services:
ZINTEROP_0001
ZPAGE_BUILDER_PERS_0001
5. On the Authorizations tab, choose Propose Profile Name next to the Profile Name field.
6. Choose Change Authorization Data and then Generate .
7. Assign the new role to your test user.

1.1.5 Configure a Logout Screen for the SAP Fiori Launchpad

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 7

1.1.5 Configure a Logout Screen for the SAP Fiori Launchpad

(Optional)
After users log out from the SAP Fiori launchpad, the browser displays a generic logout screen.
You can configure a custom HTML page that is displayed as logout screen.

Procedure
1. On the SAP Fiori front-end server that runs the SAP Fiori launchpad, start transaction Maintain Services (transaction sicf).
2. On the start screen, choose External Aliases .
3. Select a host in the hierarchy that you want to be the root node of the alias, and choose Create New External Alias .
4. Enter the following data:
External Alias : /sap/public/bc/icf/logoff
Trg Element : /sap/public/bc/icf/logoff
On the
Error Pages
5. Save your entries.

Logoff Page

tab page: In Redirect , enter the URL of the logout page in HTML format.

More Information
For SAP NetWeaver 7.31, see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw731 Application Help
Function-Oriented
View Application Server Application Server Infrastructure Connectivity
Components of SAP Communication Technology
Communication Between
ABAP and Non-ABAP Technologies
Internet Communication Framework
Development Server-Side Development Creating and Configuring ICF
Services
External Aliases .
For SAP NetWeaver 7.4, see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw74 Application Help
Function-Oriented View
Application Server Application Server Infrastructure Functions and Tools of SAP NetWeaver Application Server Connectivity
Components of SAP
Communication Technology
Communication Between ABAP and Non-ABAP Technologies
Internet Communication Framework
Development ServerSide Development Creating and Configuring ICF Services
External Aliases .

1.1.6 Create RFC Connection for Back-End Transactions (Fact

Sheets)
From fact sheets, you can access the back-end server and start transactions there (in SAP GUI or Web Dynpro). To enable this, you need to establish a
connection between the SAP Fiori launchpad and the back-end system. Perform the following steps on the front-end server:

Note
From mobile devices or tablets, you cannot access SAP GUI or Web Dynpro transactions through the SAP Fiori launchpad.

Procedure
1. Identify the system alias for the back-end transactions as follows:
1. Run transaction Overview of Launchpads (LPD_CUST) on the front-end server.
2. Select the relevant role with Instance TRANSACTIONAL and double-click it.

Note
There is a role for each front-end application. Select the front-end application that corresponds to the back end for which you want to define the
RFC connection. Example: You want to establish an RFC connection that enables users to run the transaction Display Purchase Order in the
SAP SRM back-end system. In this case, you need to select the role corresponding to the SAP SRM front-end application.
3. In the left-hand screen area, select a row where Transaction is displayed as the Application Description . The system alias is displayed in the righthand screen area.
2. Create an RFC connection of type H (HTTP connection) in transaction Configuration of RFC Connections (sm59).
Use the system alias identified under 1. as the RFC Destination .
3. Enter the Target Host under Technical Settings in transaction Configuration of RFC Connections (sm59).

1.2 Setup of SAP Fiori Search

You can use the SAP Fiori Search to find apps and central business objects. To enable the SAP Fiori search in the SAP Fiori launchpad, perform the steps
described below.
The search for business objects is enabled through corresponding search models. You can find an up-to-date list of the search models delivered for SAP
Business Suite in SAP Note 1999463.

SAP Fiori Search and SAP Fiori Fact Sheets

SAP Fiori fact sheets are based on search models, and the results list of SAP Fiori search is the main entry point to fact sheets.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 5 of 7

Note
The setup of SAP Fiori search is thus a prerequisite for the use of fact sheets.
SAP Fiori fact sheets for business objects provide information on top of what is displayed in the search results. Furthermore, they enable you to navigate to fact
sheets of related business objects and to transactional apps, or to access back-end transactions, and you can drill down into a business object's details.

Activities
Setup of SAP Fiori Search in the Front End
You must have set up SAP Web Dispatcher. For more information, see Communication Between SAP Web Dispatcher and ABAP Servers.

Setup of SAP Fiori Search in the Back End

You must have set up the Embedded Search technology. The setup process consists of the following main steps:
1. Implement SAP Notes
Implement the SAP Notes listed in the Release Information Notes (RINs) for SAP NetWeaver Enterprise Search and for SAP Fiori Fact Sheets:
SAP NetWeaver Enterprise Search:
SAP NetWeaver 7.40 Support Package Stack 05: RIN 1965792
SAP NetWeaver 7.40 Support Package Stack 06: RIN 1976027
SAP Fiori Fact Sheets (SAP Notes to be implemented on back-end and front-end server): RIN 1998490
2. Set secondary database connection for search to SAP HANA database
Make this setting in Customizing for your back-end system under
Cross-Application Components
General Application Functions
HANA-Based
Search for SAP Business Suite Configure Indexing Set TREX/BWA Destination or SAP HANA DB Connection .
Alternatively, you can use report ESH_ADM_SET_TREX_DESTINATION to set the database connection.
Prerequisites:
You have created a second database connection in transaction DBCO.
A data base user not equal to SAP<SID> is available. Database users must have the following authorizations:
Object authorizations TREXVIADBSL and TREXVIADBSLWITHPARAMETERS
Scheme authorization SELECT for the _SYS_REPO scheme.
Scheme authorizations SELECT, ALTER, and INDEX for the SAP<SID> scheme.
For more information, see SAP Help Portal at http://help.sap.com under
SAP NetWeaver SAP NetWeaver Platform
<release> Application Help
Function-Oriented View Search and Operational Analytics
Embedded Search Setting Up Embedded Search Creating a Connection Between
Embedded Search and SAP HANA or TREX/BWA .
3. Activate connector-based authorization checks
To restrict the search results to the business object instances a user is authorized to see, embedded search supports authorizations based on business
object instances. In addition, authorization checks based on search connectors are supported mainly for performance reasons. For more information, see
SAP Help Portal at http://help.sap.com under
SAP NetWeaver SAP NetWeaver Enterprise Search Security Guide Authorizations
Restricting
Authorizations for Searching .
Activate the connector-based authorization checks in Customizing for your back-end system under
Cross-Application Components
General
Application Functions
HANA-Based Search for SAP Business Suite Search Configuration Set Parameters for Federated Search .. Under Model
Authorization , select Check from the dropdown menu.
4. Activate business functions
Activate the following business functions in Customizing for your SAP Business Suite back-end system under Activate Business Functions :
To enable SAP Fiori search and fact sheets: SAP HANA-Based Search for SAP Business Suite (BSESH_HANA_SEARCH)
To enable fact sheets: SAP HANA-Based Navigation for SAP Business Suite (BSCBN_HANA_NAV)
Furthermore, the activities under
Cross-Application Components
General Application Functions
HANA-Based Search for SAP Business Suite
are relevant in Customizing for your SAP Business Suite application.
5. Activate UI services
Activate the following services for the Embedded Search in transaction Activate Service (SICF) in your back-end system.:
default_host sap
bc
webdynpro sap
default_host sap
bc
webdynpro sap
default_host sap
bc
webdynpro sap
default_host sap
bc
webdynpro sap
default_host sap
bc
webdynpro sap
default_host sap
es
cockpit
default_host sap
es
saplink
default_host sap
es
search
default_host sap
es
ina GetResponse
default_host sap
es
ina GetServerInfo
default_host sap
es
ina Loader
6. Create connectors
Prerequisite: You need the following authorizations:
SAP_ESH_SEARCH

ESH_ADMIN_UI_COMPONENT
esh_eng_modeling
esh_eng_wizard
esh_search_results_ui
wdhc_help_center

SAP_ESH_LOCAL_ADMIN
Create connectors in the Connector Administration Cockpit (transaction ESH_COCKPIT).
The connectors required for each fact sheet and the relevant search software components are documented in the implementation documentation for the
single fact sheets.

Note
Note the following system behavior:
Search software components build a stack: On top of the basis component, different layers can be installed.

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 6 of 7

Search models can be available in different components: In their original component, but also in higher layer components (extension components).
Once you create a search connector in an extension component, all search models from the original component are transferred into the extension
component. You will therefore no longer find the search models in the original component.
Example:
You have created a connector for a search model originating in search component SAPAPPLH. You have created the connector via component
EAAPPLH, not via its original component SAPAPPLH.
From that moment on, all search models originating in component SAPAPPLH can only be found under the EAAPPLH node in transaction
ESH_COCKPIT.
For more information about connector creation, see SAP Help Portal at http://help.sap.com under
<release> Application Help
Function-Oriented View Search and Operational Analytics
Creating Connectors .

SAP NetWeaver
Embedded Search

SAP NetWeaver Platform

Setting Up Embedded Search

Note
When search models are transported, for example in the event of a system upgrade, manual steps can be required. For more information, see SAP
Help Portal at http://help.sap.com under
SAP NetWeaver SAP NetWeaver Platform
<release> Application Help
Function-Oriented View
Search and Operational Analytics
Managing Search and Operational Analytics
Search-Specific Administration Tasks and Information
Transporting Search Models .
7. Start indexing of Connectors
For more information, see SAP Help Portal at http://help.sap.com under
SAP NetWeaver SAP NetWeaver Platform
<release> Application Help
Function-Oriented View Search and Operational Analytics
Embedded Search Setting Up Embedded Search Start Indexing of Connectors .

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 7 of 7