2.5 Installation
Now that we’ve given you some background about the different landscapes for SAP Fiori and its various deployment options, we’ll cover what you need to install to set up an SAP Fiori system and what you should keep in mind when you’re installing SAP Fiori-related components. First, we’ll give you an installation overview of the components on the ABAP front-end server. We’ll then focus on the installation of components on the ABAP back-end server. Next, we’ll discuss the installation of SAP Web Dispatcher and the SAP HANA server. This book doesn’t include steps to install software such as ABAP AS or to set up the SAP HANA database; we assume that the main software has already been installed.
2.5.1 ABAP Environment
In this section, we’ll look at the different ABAP front-end and back-end server components and the steps necessary to install them.
ABAP Front-End Server
The ABAP front-end server component installations depend on the patch level of the SAP NetWeaver version installed on your ABAP front-end server and the SAP Fiori apps that you want to install and configure. SAP highly recommends using the SAP Maintenance Planner to install components. There are three components that you need to check:
Use the following list to determine what you need to install, based on your SAP NetWeaver version:
-
If the SAP NetWeaver version is 7.31, then you need to install the following:
- SAP NetWeaver version: 7.31 SPS 5 or higher (SAP recommends SPS 8).
- SAP Gateway component: SAP Gateway 2.0 SPS 10; this component contains the GW_CORE 200 SP 10, IW_FND 250 SP 10, and WEBCUIF 731 SP 10 components.
- Central UI components: UI add-on 1.0 for SAP enhancement package (EHP) 3 for SAP NetWeaver 7.0, minimum SPS 12. This component contains UI_INFRA 100 SP 12, UI2_SRVC 100 SP 12, UISAPUI5 100 SP 12, UI2_FND 100 SP 12, UI2_700 100 SP 12, UI2_701 100 SP 12, UI2_702 100 SP 12, and UI2_731 100 SP 12.
-
If the SAP NetWeaver version is 7.4, then the SAP Gateway components and the central UI components that are required are included in the SAP NetWeaver installation. All you need to do is verify the product versions and patch levels of each component:
- SAP NetWeaver version: SPS 4 or higher
- SAP Gateway component: SAP Gateway Foundation SP 10 (SAP_GWFND) is included in the SAP NetWeaver 7.4 installation. This component replaces the GW_CORE, IW_FND, and IW_BEP components.
- Central UI components: User Interface Technology 7.40 SP 12 (SAP_UI 740) is included in SAP NetWeaver 7.4 installation.
- To get the new SAP Fiori 2.0 into your system landscape, you need to upgrade the front-end server to SAP front-end server 3.0 with SAP UI 7.51.
If you’ve already installed the SAP Gateway and central UI components, you can check the versions and the patch levels by following these steps:
- Log in to ABAP front-end server.
-
Choose System • Status (see Figure 2.10).
-
Click the Component information button
.
- Go to the Installed Product Versions tab.
-
Check the SAP NetWeaver version (see Figure 2.11).
Figure 2.11 Checking SAP NetWeaver Version
-
The SAP NetWeaver version is 7.4, so now you need to verify the component versions. As discussed previously, you need to check the following components:
- SAP NetWeaver version: SPS 4 or higher
- SAP_GWFND 740 SP 10
- SAP_UI 740 SP 12
-
Click on the Installed Software Component Versions tab. Figure 2.12 shows the Component, Release, and SP-Level.
- Finally, check in SAP Marketplace for new updates or support packages, and then install any new support packages.
Now you know how to update or install components. Note that if you’re planning to implement SAP Fiori analytical apps, then you’ll have to install the KPI modeler in the ABAP front-end server (see Figure 2.13).
Figure 2.13 KPI Modeler Component
ABAP Back-End Server
Installation of the ABAP back-end server components depends on the back-end database and the SAP Business Suite product. To run the SAP Fiori apps, you need to install the instances you need for your SAP Business Suite products on your ABAP back-end servers. As mentioned previously, SAP recommends using SAP Maintenance Planner to install the components. The following are the two main components that you need on the ABAP back-end server:
-
SAP Business Suite products
SAP Fiori products are installed on the back-end server as add-ons for specific SAP Business Suite products. -
SAP NetWeaver component
If the back-end database is SAP HANA, then this component should be SAP NetWeaver 7.4 SPS 7. If the back-end database is not SAP HANA (for transactional apps only), then the SAP NetWeaver version depends on the SAP Business Suite product, and you need to refer to the product-specific online help to get the version details.
In this section, we’ll explain the components you need to install with a simple example.
If the central application instance of one of the enhancement packages of SAP ERP 6.0 that you’re running is EHP 2 to EHP 7, then you need to install Central App INT. If the central application instance of one of the enhancement packages of SAP ERP 6.0 that you’re running is EHP 7 (SPS 2 or higher), then you need to install Central App INT NW740.
Similarly, if you’re running an SAP ERP Human Capital Management (SAP ERP HCM) application instance for one of the enhancement packages of SAP ERP 6.0 (up to EHP 7), then you need to install HCM INT, and if you’re running EHP 7 (SPS 2 or higher), then you need to install HCM INT NW 740.
Figure 2.14 shows the installed product version on the ABAP back-end server and the SAP Fiori principal apps for SAP ERP 1.0 (FIORI ERP APPLICATIONS X1 1.0).
Similarly, Figure 2.15 shows the product-specific components on the ABAP back-end server.
Figure 2.14 SAP Fiori ERP Applications X1
Figure 2.15 ABAP Back-End Components
In the next section, we’ll show you how to install the components for the ABAP back-end or ABAP front-end servers.
Installing ABAP Front-End and Back-End Components
In Section 2.2, we explained the different components that are required for setting up the SAP Fiori system. In this section, we’ll explore options for how to install the ABAP front-end or back-end components.
SAP Maintenance Planner
SAP recommends using SAP Maintenance Planner to install and update product versions, to make sure all the dependencies are addressed and to ensure that the system remains consistent. SAP Maintenance Planner is the successor of Maintenance Optimizer, Landscape Planner, and SAP Product System Editor, and it’s the central point of access for all maintenance activities. Using this tool, you can easily perform system upgrades, support package installations, and enhancement package updates. In addition, you can consolidate critical tasks, such as defining product maintenance dependencies, and so on.
You can launch SAP Maintenance Planner (see Figure 2.16) from https://apps.support.sap.com/sap/support/mp (log in with your user ID).
Figure 2.16 SAP Maintenance Planner
As shown in Figure 2.16, SAP Maintenance Planner contains the following four areas:
-
Explore Systems
Determines the systems in your landscape. -
Explore System Tracks
Lists groups of technical systems. -
Transactions
Gives you an overview of all the transactions you created. -
Plan a New System
Enables you to add a new system to your landscape.
SAP Fiori apps require front-end and back-end components. These components are delivered in separate products that you need to install in the system landscape. SAP Maintenance Planner addresses the need to install front-end and back-end components delivered in separate products by calculating all the system requirements for an SAP Fiori app installation.
You can choose the apps that you want to install from the SAP Fiori apps reference library and then launch SAP Maintenance Planner from the library to calculate the system requirements to install the apps you selected. Next, we’ll highlight some of the steps that will help you get started on this tool, and we’ll provide an example based on the My Inbox app. Follow these steps:
- Launch the SAP Fiori apps reference library via http://www.sap.com/fiori-apps-library.
-
Search for and select the My Inbox app. Then, go to the Implementation Information tab (see Figure 2.17).
Figure 2.17 SAP Fiori Apps Reference Library
-
Click the Maintenance Planner link at the end of the Installation section (see Figure 2.18).
Figure 2.18 Launch Maintenance Planner
This launches SAP Maintenance Planner with the components required to implement the My Inbox app. -
Log in with your S-User ID, and follow the steps in the wizard (see Figure 2.19). SAP Maintenance Planner automatically starts calculating the system requirements based on your current system.
Figure 2.19 SAP Maintenance Planner Wizard
- At the end of the wizard, you can either select Push to Download Basket or Download Stack XML.
- After you’ve downloaded the archives from SAP Marketplace, you need to use the correct tools to implement the planned landscape changes.
Alternately, you can also download the files from SAP Marketplace and deploy them manually. There are two ways to upload the files to the server: from the front-end server or from the application server.
If the component/file size is too big, we recommend loading the components from the application server. In addition, you can use Transaction SPAM (Support Package Manager) and Transaction SAINT (SAP Add-On Installation Tool) to install or update components. Next, we’ll show you how to install a component using Transaction SPAM. You can follow the same procedure to update any ABAP front-end or back-end components.
Update Support Packages
It’s important to apply the latest support packages for all components or apps that you’re planning to implement.
As an example, if you implement the My Inbox app, the first step is to get the component details from the SAP Fiori apps reference library help page specific to that app. Proceed as follows:
-
Go to the Implementation section of the My Inbox app in the apps reference library. Figure 2.20 shows the front-end components and the versions that your system needs to be on for the My Inbox app to work.
- Check the current version of the components.
- The minimum patch level for IW PGW 100 should be SP 07 for the My Inbox app to work without any issues, and the IW_PGW component in our example system is on SP 06 (see Figure 2.21).
Figure 2.21 IW_PGW (SP 06) Component
In the next section, we’ll walk you through how to derive the components that are required on the ABAP back-end or front-end server, as well as how to install components.
SAP NetWeaver
If your SAP NetWeaver version is 7.31, you first must install the software component, then the support packages.
Download the Component Files
Next, you need to download the component files from SAP Marketplace. Follow these steps:
- Log in to the SAP Software Download Center at http://support.sap.com/swdc.
-
Click Search for Software (see Figure 2.22).
Figure 2.22 Search for Software
-
Enter “IW_PGW” in the Search Term field, and click Search or press the (Enter) key (see Figure 2.23).
Figure 2.23 Searching for IG_PGW Component
- Download the latest support package—that is, SP 0007, as shown in Figure 2.24.
Support Packages
Support packages aren’t cumulative. For example, if your IW_PGW component is on SP 05, and you want to upgrade it to SP 07, then you have to download and install both SP 06 and SP 07.
Figure 2.24 Download Support Packages
Upload Support Packages
The next step is to upload the support packages to the ABAP front-end server. Follow these steps:
- Log in to your ABAP front-end server.
- Run Transaction SPAM.
-
From the menu bar, go to Support Package • Load packages • From Front End (see Figure 2.25).
Figure 2.25 Loading Package from Front-End
- Select the downloaded file.
-
Click Open (see Figure 2.26).
Figure 2.26 Selecting Package
- Click Allow.
-
Click Decompress (see Figure 2.27).
Figure 2.27 Decompressing Package
-
Select the New Support Packages radio button, then click Display (see Figure 2.28).
Figure 2.28 Displaying Support Packages
-
Select the OCS package, then click Queue (see Figure 2.29).
Figure 2.29 Selecting OCS Package
-
Click
in the popup window to confirm the queue.
-
Click Yes to add modification adjustments transports to the queue (see Figure 2.30).
Figure 2.30 Add Transports to Queue
-
You should now see the transport added to the queue; now click the truck icon
(see Figure 2.31).
Figure 2.31 Import Queue
-
Click Confirm to start importing the support packages (see Figure 2.32).
Figure 2.32 Start Importing
- Click Confirm to close the information pop-up window.
-
Confirm the queue by selecting Support Package • Confirm (see Figure 2.33).
Figure 2.33 Support Package Import Confirmation
- You should now see the latest support package applied for the IW_PGW component (see Figure 2.34).
We’ve successfully applied the latest support package for one of the components. You can follow the same process for any back-end or front-end components. However, keep in mind that SAP recommends using SAP Maintenance Planner if you do so.
You should now understand how to install the right components depending on the apps you want to use. In the next section, we’ll look at SAP Web Dispatcher.
Figure 2.34 IW_PGW Component
2.5.2 SAP Web Dispatcher
In Chapter 1, we provided a brief introduction to SAP Web Dispatcher; in this section, we’ll discuss it in greater detail. To recap, SAP Web Dispatcher enables users to access SAP Gateway servers behind a corporate firewall. SAP Web Dispatcher is the entry point for HTTP or HTTPS requests. The main role of SAP Web Dispatcher is to accept or reject connections from the client/browser. After the connection is accepted, SAP Web Dispatcher diverts queries from the browser to your SAP system.
Depending on the type of app you’re running, the queries are directed by SAP Web Dispatcher (reverse proxy) from the browser to the ABAP front-end or the SAP HANA server. For example, when you run an analytical app, SAP Web Dispatcher routes the queries first to the ABAP front-end server and then to the SAP HANA XS engine.
Deploying Transactional Apps
If you’re deploying only transactional apps and running them only via an intranet zone, then you don’t need to set up a reverse proxy. However, if you want to access the transactional apps via the Internet, then you can use a reverse proxy (SAP Web Dispatcher).
SAP recommends installing SAP Web Dispatcher as the reverse proxy. Follow the installation and configuration process available online at https://help.sap.com/saphelp_nw74/helpdata/en/48/8fe37933114e6fe10000000a421937/frameset.html.
After SAP Web Dispatcher is installed, you need to configure the following communication scenarios (we’ll cover these configuration topics in further detail when we discuss security setup in Chapter 3):
- HTTP communication
- SSL termination
- SSL reencryption
2.5.3 SAP HANA Server
As previously discussed, analytical apps run only on an SAP HANA database, using VDMs. A VDM is a structured representation of SAP HANA database views, and these VDMs are deployed with SAP HANA Live.
SAP delivers SAP HANA Live packages for several SAP Business Suite application areas. For more information on SAP HANA Live, go to http://help.sap.com/hba and select the package you want to install.
Depending on the SAP Fiori apps that you want to implement, you must install the correct SAP Smart Business products on your SAP HANA server. These SAP Smart Business products include the VDMs as well. Table 2.1 provides a list of available SAP Smart Business products.
Table 2.1 SAP Smart Business Products
After the SAP HANA Live views are deployed, you’ll be able to view the complete list of views using a standard SAP-delivered tool called the SAP HANA Live Browser (see Figure 2.35). Using this tool, you can search through, sort, and filter the complete list of available views. You can access this tool at http://<host>:<port>/sap/hba/explorer/, where <host> and <port> are the server name and the port.
The SAP Smart Business 1.0 foundation component SPS 4 (SAP Analytics Foundation 1.0) contains an extensive collection of analytic views created within the SAP HANA analytics foundation. The following is a list of components that are automatically installed with the SAP Analytics Foundation 1.0 package:
- HCO_HBA_R_SB_CORE
- HCO_HBA_R_SB_EXT
- HCO_HBA_R_SB_CXO
- HCO_HBA_R_APF_CORE
- HCO_HBA_R_SB_TP
In the next section, we’ll look at the postinstallation configuration steps required to set up the SAP Fiori system.
