2.6    Configuration

In this section, we’ll walk you through a typical configuration. We’ll cover how to perform both manual and automated configuration through predefined tasks.

2.6.1    SAP Fiori Launchpad

SAP Fiori launchpad is the entry point for all SAP Fiori apps. You need to configure SAP Fiori launchpad so that your end users can log in and access the apps. In the sections that follow, we’ll walk through the configuration steps needed for SAP Fiori launchpad.

Activate SAP Fiori Launchpad and SAP Fiori Launchpad Designer Services

The first step in the configuration is to activate the OData services for SAP Fiori launchpad and the launchpad designer. Follow these steps:

1. Log on to the ABAP front-end server.
2. Run Transaction /IWFND/MAINT_SERVICE.
3. Click the button.
4. Select the Input Help button in the system alias. Select Local for the System Alias.
5. Enter “page_builder*” for the External Service Name (see Figure 2.36).
   

   Figure 2.36    External Service Name

6. Click Get Services.
7. Select all the following services, as shown in Figure 2.37:
   • /UI2/PAGE_BUILDER_CONF (used by SAP Fiori launchpad designer)
   • /UI2/PAGE_BUILDER_CUST (used by SAP Fiori launchpad designer)
   • /UI2/PAGE_BUILDER_PERS (used by SAP Fiori launchpad)
   

   Figure 2.37    Selecting All Services

8. Click Add Selected Services.
9. Select Local Object.
10. Click Continue, or press (Enter).
11. Repeat steps 6 to 10 to get and add the following services:
    • /UI2/Interop (used by both SAP Fiori launchpad and SAP Fiori launchpad designer)
    • /UI2/TRANSPORT (used by SAP Fiori launchpad designer)
12. Go back to the Activate and Maintain Services screen (Transaction /IWFND/MAINT_SERVICE). You should now see the activated services in your customer namespace.
13. Select ZINTEROP from the Service Catalog (see Figure 2.38).
14. Select the OData row under ICF Nodes, and then click Call Browser (see Figure 2.39).
    

    Figure 2.38    Selecting ZINTEROP

    

    Figure 2.39    Clicking Call Browser

    You should now see an XML document in the browser without any errors (see Figure 2.40).
    

    Figure 2.40    XML Document

15. Repeat all the above steps for the remaining four services.

Check the Hash Key

Every time you call an OData service, a hash key is generated in the background. These hash keys are required for the generation of authorizations to assign administrative roles for SAP Fiori launchpad. To check whether the hash key is generated, follow these steps:

1. Return to the SAP GUI (ABAP front-end server), and run Transaction SE16 to view the table contents.
2. Enter “USOBHASH” in the Table Name field, and click on the Table Content button (see Figure 2.41).
   

   Figure 2.41    Data Browser

3. In the next screen, enter the following details, and click Execute (see Figure 2.42):
   • PGMID: “R3TR” (program ID)
   • OBJECT: “IWSG” (object type)
   • OBJ_NAME: “ZINTEROP*” (one of the services activated in the previous steps)
   

   Figure 2.42    Selection Screen

You should receive a table content screen with the hash key details of the INTEROP service (see Figure 2.43).

Figure 2.43    Hash Key

Activate Internet Communication Framework Nodes

The next step is to activate the Internet Communication Framework (ICF) nodes for SAP Fiori launchpad. The following is a list of services that must be activated:

• /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/bc/ui2/nwbc
• /default_host/sap/bc/ui2/start_up
• /default_host /sap/public/bc/icf/logoff
• /default_host/sap/public/bc/ui2
• /default_host/sap/public/bc/ui5_ui5

Follow these steps:

1. Run Transaction SICF.
2. Enter “/sap/bc/ui5_ui5/sap” in the Service Path field (see Figure 2.44).
   

   Figure 2.44    Service Path

3. Click .
4. Drill down to ar_srvc_launch.
5. Right-click ar_srvc_launch, and choose Activate Service (see Figure 2.45).
   

   Figure 2.45    Activate Service

6. Click Yes with the hierarchy to activate all the child nodes (see Figure 2.46).
   

   Figure 2.46    Activating All with Hierarchy

7. Repeat steps 2 to 6, and activate the remaining services:
   • /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/bc/ui2/nwbc
   • /default_host/sap/bc/ui2/start_up
   • /default_host /sap/public/bc/icf/logoff
   • /default_host/sap/public/bc/ui2
   • /default_host/sap/public/bc/ui5_ui5

Configure Authorization Roles

In the next step, we’ll copy the standard SAP-delivered SAP Fiori launchpad roles and assign them to administrators and end users.

Follow these steps:

1. Run Transaction PFCG.
2. Enter Role name “SAP_UI2_ADMIN_700”, and click Copy Role (see Figure 2.47).
   

   Figure 2.47    Role Maintenance

3. In the To Role field, preface the name with the letter “Z”.
4. Click Copy All (see Figure 2.48).
   

   Figure 2.48    Copy Role

5. Edit the new role by clicking the Change icon .
6. Select Authorization Default under the Menu tab (see Figure 2.49).
   

   Figure 2.49    Authorization Default

7. Select TADIR Service from the dropdown menu.
8. Select Program ID “R3TR”.
9. Select Obj. Type “IWSG”.
10. Add the services activated in the previous step (see Figure 2.50):
    • ZINTEROP_0001
    • ZPAGE_BUILDER_CONF_0001
    • ZPAGE_BUILDER_CUST_0001
    • ZPAGE_BUILDER_PERS_0001/
    • ZTRANSPORT_0001
    

    Figure 2.50    Adding Services

11. Click the Copy button, then go to the Authorizations tab.
12. Click to propose a Profile Name (see Figure 2.51).
    

    Figure 2.51    Generating Profile Name

13. Click Change Authorization Data (see Figure 2.52).
    

    Figure 2.52    Changing Authorization Data

14. Click Yes to save the role. You should now see the five services under the copied role.
15. Click Save, then click the Generate icon (see Figure 2.53).
    

    Figure 2.53    Generate

16. We’ve now copied the SAP standard role for SAP Fiori launchpad administrators. Next, repeat steps 2 to 15 to copy the SAP standard role for SAP Fiori launchpad end users by following these steps:
    • Copy the role SAP_UI2_USER_700.
    • Add the following services to the copied role:
      • ZINTEROP_0001
      • ZPAGE_BUILDER_PERS_0001
    • Generate the authorizations.

Assign Generic Roles to User

In this step, we’ll assign the generic admin role to a FIORIADMIN ID and the generic user role to a FIORIUSER ID.

Follow these steps:

1. Run Transaction SU01.
2. Enter the User Name, and click Edit (see Figure 2.54).
   

   Figure 2.54    User Maintenance

3. Navigate to the Roles tab, and add a new row by clicking .
4. Enter the role name created in the previous step and press (Enter) (see Figure 2.55).
5. Repeat steps 2 to 4, and assign the role ZSAP_UI2_USER_700 to the FIORIADMIN user.

Figure 2.55    Adding Generic Role

Activate Cache Buster

Browsers store resources like JavaScript files, stylesheets, and images in the browser cache; when there’s a software upgrade and these resources are changed on the server, you want the browser to load these new resources from the server rather than from the browser cache. With Cache Buster, the resources in the cache are reloaded automatically only when there’s a new version available, so the system invalidates the cache only when resources are updated on the server. Follow these steps to activate Cache Buster:

1. In the ABAP front-end server, run Transaction SICF.
2. Enter “/sap/bc/ui2/flp” in the Service Path field.
3. Click Execute , or press (F8).
4. Choose Activate Service in the context menu.

After activating Cache Buster, SAP Fiori launchpad with Cache Buster can be accessed via any of the following URLs:

• https://<server>:<port>/sap/bc/ui2/flp/
• https://<server>:<port>/sap/bc/ui2/flp/index.html
• https://<server>:<port>/sap/bc/ui2/flp/FioriLaunchpad.html

Configure the SAP Fiori Launchpad Login Screen

The last step is to configure the login screen for SAP Fiori launchpad and SAP Fiori launchpad designer. Follow these steps:

1. In the ABAP front-end server, run Transaction SICF.
2. Enter “/sap/bc/ui5_ui5/ui2/ushell” in the Service Path field.
3. Click Execute , or press (F8) (see Figure 2.56).
   

   Figure 2.56    Service Path

4. Double-click the ushell service.
5. Click the Error Pages tab.
6. Select the System Logon radio button, then click Configuration (see Figure 2.57).
   

   Figure 2.57    Configuring SAP Fiori Launchpad Login Screen

7. Select the Custom Implementation radio button.
8. Enter “/UI2/CL_SRA_LOGIN” in the ABAP Class field (see Figure 2.58).
9. Click .
   

   Figure 2.58    Custom ABAP Class

10. Click Save on the Create/Change a Service screen.
11. Repeat steps 2 to 10 with the /sap/bc/ui5_ui5/sap/arsrvc_upb_admn service to configure the logon for SAP Fiori launchpad designer.
12. Log in to SAP Fiori launchpad with your ID (see Figure 2.59):
    http(s)://<host>:<port>/sap/bc/ui5_ui5/ui2/ushell/shells/abap/FioriLaunchpad.html?sap-client=<Client>.
    

    Figure 2.59    SAP Fiori Logon Screen

13. Log in to SAP Fiori launchpad designer with your ID:
    http://<host>:<port>/sap/bc/ui5_ui5/sap/arsrvc_upb_admn/main.html?
    sap-client=<client>&scope=CUST.

Configure the SAP Fiori Launchpad Logout Screen

After users log out from SAP Fiori launchpad, the browser displays a generic logout screen (see Figure 2.60). However, you can configure a custom HTML page to be displayed as the logout screen.

Figure 2.60    Default Logoff Screen

Follow these steps to add a custom logout screen:

1. In the ABAP front-end server, run Transaction SICF.
2. Click Execute , or press (F8).
3. Click External Aliases.
4. Select the root node of the alias, and choose Create New External Alias by clicking .
5. In the External Alias field, enter “/default_host/sap/public/bc/icf/logoff”.
6. In the Trg Element tab, double-click the logoff node: /sap/public/bc/icf/logoff (see Figure 2.61).
7. Navigate to the Error Pages tab, then select the Logoff Page tab.
8. In Redirect, enter the URL of the logout page in HTML format (see Figure 2.62).
9. Save your entries.

Figure 2.61    Target Element

Figure 2.62    Logoff Page

Users should now see the custom logout screen whenever they logout from SAP Fiori launchpad.

If you’re running SAP NetWeaver 7.4 SP 06 or higher, you can use the SAP_FIORI_LAUNCHPAD_INIT_SETUP task list to automatically setup and configure SAP Fiori launchpad and SAP_GATEWAY_ACTIVATE_ODATA_SERV to activate the OData services for SAP Fiori launchpad. We’ll cover the task lists in detail in Section 2.6.5.

2.6.2    SAP Gateway

Depending on the deployment option that you’ve selected, you need to install and configure the SAP Gateway server. As previously discussed, if your SAP NetWeaver version is 7.3, then you must install the SAP Gateway 2.0 SPS 10 component, which is comprised of GW_CORE 200 SP 10, SAP IW_FND 250 SP 10, and SAP WEBUIF 7.31 SP 10.

To install SAP Gateway 2.0, refer to the online help at http://help.sap.com/nwgateway, and choose Installation and Upgrade Information • Installation Guide.

In SAP NetWeaver 7.4, the GW_CORE, SAP IW_FND, IW_BEP, and IW_HDB components are replaced with the new software component SAP GW_FND (SAP Gateway Foundation SP 10). Therefore, if you’re running SAP NetWeaver 7.4, you don’t have to install any additional software components; they’re already included in SAP NetWeaver 7.4.

Activate SAP Gateway

First, you’ll have to activate SAP Gateway services. Follow these steps:

1. Run Transaction SPRO.
2. Click .
3. Drill down to activate or deactivate SAP Gateway, and click (see Figure 2.63).
   

   Figure 2.63    Implementation Guide

4. Click Activate (see Figure 2.64).
   

   Figure 2.64    Activating SAP Gateway Service

Integrate SAP Gateway and SAP Business Suite

In this step, we’ll set up the trusted RFC connection to define a trusted relationship between SAP Gateway on the ABAP front-end server and SAP Business Suite on the ABAP back-end server.

Follow these steps:

1. Log in to your ABAP front-end server.
2. Run Transaction SM59.
3. Click Create .
4. Set the following configurations on the next screen (see Figure 2.65):
   • RFC Destination: Enter “ERPCLNT120” (this is the RFC destination name).
   • Connection Type: Enter “3”.
   • Description 1: Enter “SAP ERP”.
   • Load Balancing: Select No.
   • Target Host: Enter the SAP Business Suite server name.
   • Instance Number: Enter “00”.
5. Click the Logon and Security tab, and use the following settings (see Figure 2.66):
   • Language: Enter “EN”.
   • Client: Enter “120”.
   • User: Select the Current User checkbox.
   • Trust Relationship: Select Yes.

Figure 2.65    Creating RFC Connection

Figure 2.66    Logon and Security

Now, you need to repeat the same steps on your ABAP back-end server, with the target host as your ABAP front-end server. After setting up the RFC destination in the back-end server, you need to run the Creating Trusting Relationships wizard. Follow these steps:

1. Run Transaction SMT1.
2. Click Create.
3. Follow the steps in the Creating Trusting Relationships wizard.
4. Save your settings.

Creating the SAP System Alias for Applications

In this step, we’ll create the SAP system alias that points to the SAP Business Suite system from the central hub system. We’ve implemented an embedded deployment, and the system alias should represent the SAP Gateway system itself, so we’ll have to create a system alias entry (LOCAL). However, if your landscape has a central hub deployment, then you need to enter the SAP Gateway system details.

Follow these steps:

1. Run Transaction SPRO.
2. Click .
3. Navigate to Manage System Aliases, and click . Follow the menu path SAP NetWeaver • Gateway • OData Channel • Configuration • Connection Settings • SAP NetWeaver Gateway to SAP System • Manage SAP System Aliases (see Figure 2.67).
   

   Figure 2.67    Implementation Guide

4. Click New Entries, and establish the following settings (see Figure 2.68):
   • SAP System Alias: Enter “LOCAL”.
   • Description: Enter “Local System Alias”.
   • Local GW: Check this box.
   • For Local App: Do not check this box.
   • RFC Destination: Enter “NONE”.
   • Software Version: Select DEFAULT from the available software versions by clicking in the field.
   • System ID: Leave blank.
   • Client: Leave blank.
   • WS Provider System: Leave blank.

Figure 2.68    System Aliases

Assign a Role Template to an Admin User

In this step, we need to assign the role template /IWFND/RT_ADMIN to the FIORIADMIN user. Follow these steps:

1. Run Transaction PFCG.
2. Enter “ZRT_ADMIN” in the Role field, and click Single Role (see Figure 2.69).
   

   Figure 2.69    Role Maintenance

3. Select the Authorizations tab, then click Save (if there’s a pop-up message).
4. Click Change Authorization Data (see Figure 2.70).
   

   Figure 2.70    Generating Profiles

5. Choose the /IWFND/RT_ADMIN template, and click Adopt reference (see Figure 2.71).
6. Click the Generate icon (see Figure 2.72).
7. Click Save.
   

   Figure 2.71    Adopting Reference, Template

   

   Figure 2.72    Generate

8. Click the Back button, and select the User tab.
9. Enter “FIORIADMIN” in the User ID field and press (Enter) (see Figure 2.73).
   

   Figure 2.73    Adding Administrator to Role

10. Click Save.

Specify the Default Language and Logon Language

You need to make sure that the default language in both SAP Gateway and the back-end system are the same, because the SAP Gateway system supports only those languages that are the same in the connected SAP Business Suite back-end systems. If they aren’t the same, then you need to verify whether the back-end language is a subset of the languages in the SAP Gateway system.

The logon language is based on the user settings in Transaction SU01. If nothing is defined there, then the default language is automatically used (see Figure 2.74).

Figure 2.74    Default Language

If a service in Transaction SICF is activated with the Required with Logon Data indicator, then the system uses the language defined in the Language field (see Figure 2.75).

Figure 2.75    Request with Logon Data

2.6.3    Embedded Search

Search functionality lets users search apps and central business objects, as well as view lists of recently used apps. The search toolbar is in the top-right corner of SAP Fiori launchpad (see Figure 2.76).

Figure 2.76    Search Toolbar

SAP Fiori fact sheet apps are called using this search functionality. As a prerequisite for the fact sheet apps, you need to set up SAP Search.

If your SAP NetWeaver version is 7.4 SPS 06 or higher, you can use the predefined tasks to automatically set up and configure the communication channels among the client, front-end servers, and back-end servers. Using the predefined tasks list, you can configure the initial system setup, SAP Gateway, SAP Fiori Launchpad, and so on. In this section, we’ll focus on the predefined tasks for setting up embedded search.

On the front-end server, you need to set up communication between SAP Web Dispatcher and the ABAP front-end servers, which we did in the previous sections. On the back-end server, you must set up embedded search.

Activating Embedded Search User Interface Services

In this step, we’ll activate the central UI services related to the embedded search. In Section 2.6.1, we described how to activate services; follow the same process to activate the following services in the ABAP back-end server:

• default_host/sap/es/cockpit
• default_host/sap/es/saplink
• default_host/sap/es/search
• default_host/sap/es/ina
• default_host/sap/bc/webdynpro/sap/ESH_ADMIN_UI_COMPONENT
• default_host/sap/bc/webdynpro/sap/esh_eng_modelling
• default_host/sap/bc/webdynpro/sap/esh_eng_wizard
• default_host/sap/bc/webdynpro/sap/esh_search_results_ui
• default_host/sap/bc/webdynpro/sap/wdhc_help_center

Assign Authorizations for Embedded Search

In this step, we’ll assign authorizations to the FIORIADMIN user to manage embedded search. Follow these steps:

1. Run Transaction SU01.
2. Enter “FIORIADMIN” in the User field.
3. Click .
4. Enter “SAP_ESH_CR_ADMIN” and “SAP_ESH_BOS_ADMIN” in the Role field and press (Enter) (see Figure 2.77).
   

   Figure 2.77    Embedded Search–Related Roles

5. Click Save.

The FIORIADMIN user will now have access to control the embedded search.

Check Business Functions

In this step, we need to check whether some of the business functions related to embedded search are activated in the back-end server. Follow these steps in your ABAP back-end server:

1. Run Transaction SFW5.
2. Click Continue.
3. On the next screen, open the Enterprise Business Functions folder.
4. Search for the following functions, and check if they’re activated (you’ll see a lightbulb next to their names if they are; see Figure 2.78):
   • BSCBN_HANA_NAV
   • BSESH_HANA_SEARCH
   

   Figure 2.78    Business Functions

5. If these functions aren’t activated, then select the Planned Status checkbox and click Activate Changes.

Set Up Embedded Search Using Task List (Client 000)

Fact sheets are shown in the results lists of embedded search. In this step, we’ll show you how to perform the initial setup of embedded search using the task list. Proceed as follows:

1. Login to the ABAP back-end server using client 000.
2. Run Transaction STC01.
3. Enter “SAP_ESH_INITIAL_SETUP_000_CLIENT” in the Task List field (Figure 2.79), and click to generate the task list. This task prepares the ESH-specific tables in client 000 and then copies the tables to the target client.
   

   Figure 2.79    Task List

4. Click Confirm (Figure 2.80).
   

   Figure 2.80    Task List Documentation

5. The icon indicates that there are manual activities you must Precheck before running the task (Figure 2.81).
   

   Figure 2.81    Precheck

6. Click to confirm that all the preconditions are fulfilled (Figure 2.82).
   

   Figure 2.82    Confirm Task

7. Click Confirm to confirm that all preconditions are met.
8. Make sure the checkboxes next to all the tasks are checked (Figure 2.83), then click to run the task list in the background.
   

   Figure 2.83    Tasks

9. After the task list is executed, you can check the log by running Transaction STC02.

Set Up Embedded Search Using Task List (Working Client)

In the previous section, we set up embedded search for client 000; now, we’ll follow the same steps to set up embedded search in the working client:

1. Login to the ABAP back-end server using the working client.
2. Run the SAP_ESH_INITIAL_SETUP_WRK_CLIENT task list from Transaction STC01. This task list activates ICF services. Set TREX/HANA destination/connection.
3. Confirm that all the preconditions are fulfilled (Figure 2.84).
   

   Figure 2.84    Task List Items

4. Because this task takes a long time to run, we recommend running it in the background. Click to do so.

Configuration Check: Search User Interface (Fact Sheet Apps Only)

To check that SAP Fiori search has been installed correctly, run Transaction ESH_SEARCH in the back-end system; the Web Dynpro UI for the search should appear (see Figure 2.85).

Figure 2.85    Web Dynpro UI

2.6.4    SAP HANA

In this section, we’ll look at some of the generic configuration steps required for analytical apps to work on the SAP HANA database.

Assign SAP Smart Business Modeler Roles

In this step, you need to assign roles to the user to use the SAP Smart Business modeler. Follow these steps:

1. Log in to the SAP HANA server from SAP HANA Studio.
2. Open the Security folder, then open the Users folder.
3. Double-click the FIORIADMIN user name to open the user’s profile (see Figure 2.86).
   

   Figure 2.86    User Maintenance

4. Click the Granted Roles tab.
5. Enter the following role, then click OK (see Figure 2.87): “sap.hba.r.sb. core.roles:: SAP_SMART_BUSINESS_MODELER”.
6. Repeat the steps to add the remaining roles:
   • sap.hba.r.sb.core.roles::SAP_SMART_BUSINESS_RUNTIME
   • sap.hba.apps.kpi.s.roles::SAP_SMART_BUSINESS_ MODELER
   • sap.hba.apps.kpi.s.roles::SAP_SMART_BUSINESS_RUNTIME
   • sap.hba.apps.ps.s.roles::SAP_SMART_BUSINESS_PROJECT_MANAGER

Figure 2.87    Adding Roles

Assign the KPI Modeler and KPI Framework Roles

In this step, we’ll assign the KPI modeler roles to the administrative user and end user using Transaction PFCG in the ABAP front-end server. Follow these steps:

1. Follow the same steps from the previous section, and assign the roles /UI2/SAP_KPIFRW5_TCR_S and /UI2/SAP_KPIMOD_TCR_S to the SAP Fiori administrator user—for example, FIORIADMIN user (see Figure 2.88).
   

   Figure 2.88    KPI Modeler and KPI Framework Roles

2. Similarly, assign /UI2/SAP_KPIFRW5_TCR_S to an end user—for example, FIORI-USER (see Figure 2.89).
   

   Figure 2.89    KPI Framework Role

Activate SAP Smart Business Modeler Service

In this step, you need to activate a service in the ABAP front-end server. In Section 2.6.1, we showed you how to activate services. Here, you need to follow the same process and activate the following service in the ABAP front-end server: default_host/sap/bc/ui5_ui5/sap/CA_KPI.

Configuration Check

After you’ve configured the KPI modeler framework, you should see the following KPI modeler apps in the KPI Modeler catalog in SAP Fiori launchpad (see Figure 2.90):

• KPI Workspace
• Configure KPI Drill-Down
• Manage KPI Authorizations
• Manage KPI Associations
• Create KPI
• Create Evaluation
• Configure KPI Tiles
• Migration Tool

Figure 2.90    KPI Modeler Apps

2.6.5    Configuration Using the Task List

In section Section 2.6.1, we walked you step-by-step through how to configure the SAP Fiori launchpad manually; in this section, we’ll introduce the predefined task list, with which you can configure your ABAP system automatically. We’ll walk you through an example based on the SAP Fiori launchpad configuration. This predefined task list is available in SAP NetWeaver 7.4 SP 06 or higher. SAP_FIORI_LAUNCHPAD_INIT_SETUP is the task list you need to run to set up SAP Fiori launchpad.

Requirements

Your server must be on SAP NetWeaver 7.4 SPS 08 or higher to use all the available task lists for configuring SAP Fiori.

Follow these steps:

1. Run Transaction STC01.
2. Enter the task name in the Task List field, then click the Display Task List icon to view the tasks (Figure 2.91).
   

   Figure 2.91    Task Manager

3. Be sure to review documentation for every task list before you execute it. To view the documentation, click Goto • Documentation • Display (see Figure 2.92).
   

   Figure 2.92    Task List Documentation

4. After you review the documentation, press (F8) or click to generate the task list.
5. Make sure the checkboxes next to all the tasks are checked, then click to run the task list (see Figure 2.93).
   

   Figure 2.93    Task List Final Check

   Important!

   Some tasks will take a long time to run, so we recommend running those task lists in the background.

6. After the task list is executed, you can check the log by running Transaction STC02 (see Figure 2.94).

Figure 2.94    Task List Run Monitor

After the task list is successfully completed, the initial set up of SAP Fiori launchpad is done. We performed the same process manually in Section 2.6.1.

Table 2.2 presents a selection of tasks and their task lists.

Task	Task List
SAP Gateway—Basic Configuration	SAP_GATEWAY_BASIC_CONFIG
SAP Fiori Launchpad Initial Setup	SAP_FIORI_LAUNCHPAD_INIT_SETUP
Create Trusted Connection from SAP System to SAP Gateway	SAP_SAP2GATEWAY_TRUSTED_CONFIG
Enable Embedded Search	SAP_ESH_INITIAL_SETUP_000_CLIENT
SAP Gateway—Add Back-end System	SAP_GATEWAY_ADD_SYSTEM
SAP Gateway—Maintain System Alias	SAP_GATEWAY_ADD_SYSTEM_ALIAS
SAP Gateway—Activate OData Services	SAP_GATEWAY_ACTIVATE_ODATA_SERV
SAP Basis—Activate HTTP Services (SICF)	SAP_BASIS_ACTIVATE_ICF_NODES

Table 2.2    Configuration Task Lists

SAP Cloud Platform

SAP Cloud Platform is a platform-as-a-service (PaaS) for the cloud application. With SAP Cloud Platform, customers can build new cloud apps quickly, extend existing SAP Fiori apps, and easily integrate apps with SAP and non-SAP systems. There are many tools available in SAP Cloud Platform, such as SAP Fiori, cloud edition and SAP Web IDE (see Figure 2.95). Customers can easily integrate SAP Fiori, cloud edition account into their on-premise SAP landscapes to customize and run apps in SAP Fiori launchpad on the cloud.

Figure 2.95    Connecting On-Premise Systems and SAP Cloud Platform

In this section, we’ll show you how to connect an on-premise system to SAP Cloud Platform. The first step is to install and configure SAP Cloud Platform cloud connector, which serves as the link between SAP Fiori, cloud edition and on-premise SAP landscapes.

Install the Cloud Connector

There two versions of the cloud connector. The portable version of the cloud connector can be installed on Windows and Linux, and the installer version of the cloud connector can be installed on Windows, Linux, and macOS.

Prerequisites:

• Memory: Minimum 1 GB RAM; 4 GB recommended
• Hard disk space: Minimum 1 GB; 20 GB recommended
• CPU: Minimum single-core 3 GHz; dual core 2 GHz recommended; x86–64 architecture compatible
• Java developer kit: Version 7 or 8 needs to be installed; most recent version is available via https://tools.hana.ondemand.com/#cloud

Now let's explore the steps to install the cloud connector. Follow these steps:

1. Download SAP Cloud Platform cloud connector 2.x via https://tools.hana.ondemand.com/#cloud.
2. Run the setup file to install the cloud connector, click Next in the setup wizard (Figure 2.96).
   

   Figure 2.96    SAP Cloud Platform Cloud Connector Installation

3. Follow the simple steps in the wizard to complete the installation. Close the installer window once the installation is complete.

You should now see two icons added to your desktop, one to start and one to stop the SAP Cloud Platform cloud connector.

Set Up SAP Cloud Platform Cloud Connector

Once the cloud connector is installed, you need to log in and perform its initial setup, as follows:

1. Launch the cloud connector via https://localhost:8443/.
2. Login with the initial admin credentials; enter “administrator” for User Name and “manage” for Password (Figure 2.97).
3. Change the initial password and click Save (Figure 2.98).

Figure 2.97    Cloud Connector Login

Figure 2.98    Initial Password

Before we move on to the next step, you need to register at https://account.hanatrial.ondemand.com/register to create a trial account for SAP Cloud Platform. Once you create an account, we’ll create a trust between SAP Cloud Platform cloud connector and SAP Cloud Platform, as follows:

In the SAP HANA Cloud Connector admin cockpit, add the trial account details and click Save (Figure 2.99).

We’ve now successfully installed the cloud connector, created an account with SAP Cloud Platform, and connected the two.

Figure 2.99    SAP Cloud Platform Account

Next, we need to create a mapping between SAP Cloud Platform and the on-premise systems using the cloud connector, as follows:

1. Click Cloud To On-Premise in the cloud connector (Figure 2.100).
   

   Figure 2.100    Cloud to On-Premise

2. Click + to add the on-premise system (Figure 2.101).
   

   Figure 2.101    Add Internal System

3. Select the back-end type of on-premise system (Figure 2.102), and click Next.
   

   Figure 2.102    Back-End System Type

4. Select the Protocol (i.e., HTTP/HTTPS, etc.), and click Next (Figure 2.103).
   

   Figure 2.103    System Protocol

5. Enter the Host and the Port name of the on-premise system (Figure 2.104).
   

   Figure 2.104    Host and Port

6. Select a Principal Type (Figure 2.105).
   

   Figure 2.105    Principal Type

7. Enter a Description and click Finish to add the system (Figure 2.106).
   

   Figure 2.106    System Summary

By now, you should have all the pieces in place to start using the SAP Fiori system.