Browse the Book. Deployment Options, Installation, and Configuration Table of Contents. Index. The Authors. SAP Gateway and OData

Transcription

1 First-hand knowledge. Browse the Book In this chapter, you ll discover SAP Gateway embedded and hub deployment, as well as your deployment options for SAP Fiori and SAP S/HANA. You ll begin your installation with a quick start guide, before diving into the configuration details using step-by-step instructions. Deployment Options, Installation, and Configuration Table of Contents Index The Authors Bönnen, Drees, Fischer, Heinz, Strothmann SAP Gateway and OData 81 Pages, 2019, $89.95 ISBN

2 Chapter Deployment Options, Installation, and Configuration This chapter discusses the methods of deploying SAP Gateway, including how to best install SAP Gateway, the necessary configuration steps for the chosen deployment method, and when to use which method. In this chapter, you ll learn the specifics about the different deployment options for SAP Gateway, including the advantages each method provides. We then look at preparations needed for a typical SAP Gateway installation and configuration process, followed by walking through a minimal installation and configuration in what we call a Quick Start Guide. Because this Quick Start Guide just addresses the absolute basics needed to have SAP Gateway up and running, we then present an overview of a standard installation and configuration process and look at selected steps in detail. The chapter closes by discussing the SAP Gateway best practices that are relevant during installation and configuration..1 Introduction to SAP Gateway Deployment There are basically two ways to look at the SAP Gateway deployment options: from the perspective of SAP Gateway itself and from the perspective of SAP Fiori and SAP S/HANA, where SAP Gateway is part of the application stack. Both perspectives need to be taken into account to see the full picture. We highly recommend selecting your option wisely, based on your system landscape and your intended use case. Deployment options In SAP Gateway, there are major differences with respect to deployment, depending on the underlying SAP NetWeaver version. Since SAP Net- Weaver 7.0, the add-on structure has been streamlined and further optimized for the OData channel, as compared to prior SAP NetWeaver versions. 155

3 Deployment Options, Installation, and Configuration.1 Introduction to SAP Gateway Deployment Prior to SAP NetWeaver 7.0 Basic SAP Gateway functionalities, if running on releases prior to 7.0, are contained in different add-ons that have to be deployed separately. The SAP Gateway server or hub functionalities require that the GW_CORE and IW_ FND add-ons be deployed on the server. IW_BEP has to be deployed on the SAP Business Suite systems for backend enablement (see Table.1). Core Components Backend Enablement Name Type Version Notes IW_FNDGC ABAP 100 Optional. Only to be installed if generic channel services (outdated and not recommended) are still used. Table.2 Software Components and Optional Add-Ons for SAP Gateway in SAP NetWeaver 7.0 (Cont.) Version 7.31 and Earlier GW_CORE IW_BEP From SAP NetWeaver 7.0 IW_FND As of Version 7.0 SAP_GWFND SAP_GWFND Table.1 SAP NetWeaver Version and Required SAP Gateway Add-Ons As of SAP NetWeaver 7.0 and higher, the SAP_GWFND software component is installed as part of the SAP NetWeaver 7.0 standard and includes the functional scope of IW_BEP, GW_CORE, IW_FND, and IW_HDB. As a Deployment The term deployment in this case for versions as of SAP NetWeaver 7.0 describes where SAP Gateway functionality resides because there is no actual deployment needed anymore. Since SAP Gateway components come as part of SAP NetWeaver, it s more of a configuration. We stick to the term deployment here for simplicity reasons and because it has become a set expression. result, any SAP Business Suite system as of SAP Enhancement Package (EHP) 7 or any SAP S/HANA system comes with SAP_GWFND already From an architectural perspective, the big question is whether to go for a Deployment options installed. hub deployment, for an embedded deployment, or for a deployment in SAP Table.2 shows the software components and optional add-ons of SAP Cloud Platform, as described here: Gateway with respect to SAP NetWeaver 7.0. Embedded deployment Name Type Version Notes In previous versions SAP NetWeaver 7.0, SAP Gateway IW_FND and GW_CORE core components were deployed in the SAP Business Suite SAP_GWFND ABAP 7.0 Installed as standard in systems based on SAP NetWeaver 7.0 and contains the following: system. Alternatively, the SAP backend system is based on release 7.0 or higher, where the SAP_GWFND software component is part of the SAP NetWeaver standard and just needs to be configured properly. Runtime components Metadata component Shared services (e.g., monitoring) OData libraries Business enablement provisioning (BEP) Business content adapter for SAP Gateway with SAP HANA to enable exposure of SAP HANA views Table.2 Software Components and Optional Add-Ons for SAP Gateway in SAP NetWeaver 7.0 Hub deployment In versions before SAP NetWeaver 7.0, SAP Gateway IW_FND and GW_ CORE core components are deployed in an SAP Gateway hub system. Alternatively, a 7.0 or higher system is used as the hub system where the SAP_GWFND software component is part of the standard and just needs to be configured properly. SAP Cloud Platform deployment SAP Cloud Platform OData Provisioning offers a service in SAP Cloud Platform that provides the SAP Gateway Hub capabilities for SAP Business Hub architecture using SAP Cloud Platform

4 Deployment Options, Installation, and Configuration.1 Introduction to SAP Gateway Deployment Suite OData services in a cloud context. (SAP Cloud Platform OData Pro- The SAP Gateway service is thus deployed on the SAP backend systems visioning does not support SAP S/HANA backend systems.) This means (where either IW_BEP is deployed for systems prior to SAP NetWeaver 7.0, that no separate SAP Gateway Hub system has to be deployed. Instead, or the software component SAP_GWFND is configured for SAP NetWeaver SAP ensures secure operation and takes care of runtime aspects such as 7.0) and is then published on the SAP Gateway server. monitoring, upgrading, and system administration. The hub deployment can be further split up into two suboptions. Each of these options has advantages and disadvantages. In this section, we ll discuss all four, compare them, and also discuss the scenario where you might use a mixed deployment that consists of both options. The following are the main use cases for this kind of deployment: Scenarios where development takes place in the SAP Business Suite or SAP S/HANA system Scenarios where a developer needs to leverage native interfaces, Data Dictionary (DDIC) structures, or Core Data Services (CDS) in the SAP Busi- Deployment use cases ness Suite or SAP S/HANA systems.1.1 Hub Deployment with Development in the SAP Backend System SAP Fiori for SAP Business Suite scenarios (Section.1.6 for more details) In the case of hub deployment with development in the SAP Business Suite or SAP S/HANA system (Figure.1), the SAP Gateway server functionalities are only used on a single dedicated server the hub system. Consumers SAP Gateway Hub OData Runtime GW_CORE and IW_FND or SAP_GWFND HTTPS The hub deployment with development in the SAP backend offers the following advantages: Support for routing and composition of multiple systems. Single point of access to multiple SAP backend systems. More flexibility. Hub systems can be based on a newer release (SAP Net- Weaver 7.50 up to SAP NetWeaver 7.52) than any of the connected SAP backend systems that supports additional authentication options (Kerberos, Security Assertion Markup Language [SAML] browser protocol) and can be updated more frequently without too much overhead (service windows, regression tests). Advantages SAP Backend System RFC The only disadvantages to this method are the following: An additional server is needed for SAP Gateway. Disadvantages OData Design Time & Service Provider Runtime A slight overhead with regard to performance due to the RFC call needed IW_BEP or SAP_GWFND from the SAP Gateway hub to the backend system. RFC BOR BW WF Figure.1 Hub Deployment with Development in the SAP Backend System.1.2 Hub Deployment with Development on the Hub For hub deployment with development on the hub (Figure.2), the SAP Gateway server functionalities are only used on a dedicated server the hub system. In contrast to the first option (hub deployment with development in the backend systems), this is where service deployment takes place. This option can be taken into account in the exceptional case either if no development can be performed on the SAP backend systems or if you

5 Deployment Options, Installation, and Configuration.1 Introduction to SAP Gateway Deployment can t deploy the IW_BEP add-on in the SAP Business Suite (for releases prior Scenarios where SAP Gateway add-ons can t be installed in the SAP Busi- to SAP NetWeaver 7.0). In this specific case, the developer is limited to ness Suite system for security, stability, or incompatibility (due to sys- using the interfaces that are accessible via remote function call (RFC) in the tem release) reasons. In this case, this deployment option is mandatory. SAP Business Suite systems. For SAP S/HANA systems, this deployment option is of no interest. Proof of concept (POC) with SAP Gateway (no changes to existing infrastructure required). Consumers The following are the disadvantages of hub deployment with development on the hub compared to development on the backend: Disadvantages SAP Gateway Hub OData Runtime & OData Design Time & Service Provider Runtime GW_CORE and IW_FND or IW_BEP or SAP_GWFND SAP_GWFND HTTPS No direct access to native interfaces, DDIC structures, or CDS in the SAP Business Suite or SAP S/HANA systems. Access is limited to remote-enabled interfaces (RFC function modules, Business Application Programming Interfaces [BAPIs], or SAP BW Easy Queries). SAP Backend System RFC Remote-enabled interfaces might not be optimal (e.g., might not offer appropriate filter options). RFC BOR BW WF Since OData services delivered by SAP as part of SAP Fiori applications require the deployment of IW_BEP for releases prior to SAP NetWeaver 7.0 on the SAP Business Suite system, such a setup cannot be used if you want to use SAP Fiori standard applications. Deployment use cases Figure.2 Hub Deployment with Development on the Hub Example In validated environments (e.g., the pharmaceutical industry), it s a very time-consuming process to change anything in the validated SAP Business Suite systems. Development for these systems is even more restricted. In these scenarios, deployment with development on the hub can be extremely beneficial for using new technologies without disrupting ongoing business-critical processes. The following are the main use cases for a hub deployment with development on the hub:.1.3 Embedded Deployment For embedded deployment, the core components for SAP Gateway are deployed together in the SAP Business Suite or SAP S/HANA system (see Figure.3). As of SAP NetWeaver 7.0 and higher, the SAP_GWFND component is already installed as part of the standard SAP NetWeaver delivery, so embedded deployment is possible without any additional effort on every SAP Business Suite system running on top of SAP NetWeaver 7.0 and higher and on every SAP S/HANA system as well. For this deployment option, no additional SAP Gateway server is needed only an SAP Business Suite or SAP S/HANA system. Development of SAP Gateway services takes place in the SAP Business Suite or SAP S/HANA system. Scenarios where no deployment of add-ons in the SAP Business Suite system is allowed or wanted

6 Deployment Options, Installation, and Configuration.1 Introduction to SAP Gateway Deployment Consumers Routing and composition can t be used. The upgrade of add-ons in an SAP backend system in larger companies is usually only possible once or twice a year (maintenance windows). HTTPS There is also one release consideration. As of SAP NetWeaver 7.0 and higher, the SAP_GWFND component is already installed as part of the stan- Release consideration SAP Backend System dard SAP NetWeaver delivery, so embedded deployment is possible with- OData Runtime & Design Time & Service Provider Runtime out any additional effort on every SAP backend system running on top of GW_CORE and IW_FND or SAP_GWFND IW_BEP or SAP_GWFND SAP NetWeaver 7.0 and higher. RFC BOR BW WF.1. SAP Cloud Platform OData Provisioning With SAP Cloud Platform OData Provisioning, the SAP Gateway server functionalities can also be provided by a service in SAP Cloud Platform. It can Figure.3 Embedded Deployment replace the SAP Gateway Hub server in the previously mentioned SAP Gateway deployment options and hence still needs the backend provisioning Deployment use cases The main use cases for an embedded deployment are the following: Scenarios where developers need to leverage interfaces, DDIC structures, or CDS in the SAP backend systems Scenarios where neither routing nor composition is needed (IW_BEP) component for service creation in the SAP Business Suite backend. The SAP Gateway service is thus deployed on the SAP Business Suite systems (where either IW_BEP is deployed for systems prior to SAP Net- Weaver 7.0 or the software component SAP_GWFND is configured for SAP NetWeaver 7.0) and is then published as an OData end point on SAP Cloud SAP Fiori system landscapes where several SAP S/HANA backend sys- Platform, eliminating the need for an on-premise SAP Gateway server. tems are used (Section.1.6 for more details) Advantages The embedded deployment method provides the following advantages: Less runtime overhead because you save on one remote call When using SAP NetWeaver 7.50 SP 0 or later, you can leverage several performance improvements that have been implemented for co- Known Constraints Please note that SAP Cloud Platform OData Provisioning does not offer the same functional scope as the SAP Gateway on-premise server. The known constraints are outlined in SAP Note Disadvantages deployed systems No additional, separate SAP Gateway system required, resulting in lower total cost of ownership (TCO) because there is one less system to maintain The method has the following disadvantages: If multiple SAP backend systems are used, SAP Gateway has to be config- The main use cases for using SAP Cloud Platform OData Provisioning are the following: SAP Fiori Cloud edition for SAP Business Suite Scenarios that expose the business data for the SAP Fiori apps to the Internet Deployment use cases ured on every single system

7 Deployment Options, Installation, and Configuration.1 Introduction to SAP Gateway Deployment Combinations of deployment options.1.5 Mixed Deployment Options In real-world scenarios, deployment options often build on combinations of the four basic deployment options. Typically these combinations SAP Backend System with Embedded Deployment used as an SAP Gateway Hub Additional SAP Backend System address shortcomings or special situations in a bigger system landscape environment. SAP ERP SAP CRM Combination to be avoided One example is a situation in which an embedded deployment is desired but not initially possible (e.g., because changes in backend systems are only possible during the maintenance windows). Therefore, a first setup includes an SAP Gateway hub deployment with development on the hub that connects to the SAP Business Suite or SAP S/HANA system. This reduces the immediate system impact on the SAP backend system. In a next step, the landscape complexity is then reduced after a piloting phase, meaning the SAP Gateway server is removed from the landscape and replaced by an embedded deployment on the SAP backend system. Another possible example is a combination of hub deployment and embedded deployment in a single-system landscape across several SAP backend systems, which means that some systems use hub deployment and others use embedded deployment. A system with embedded deployment can therefore also be used as a backend system in a hub deployment. A third possible example is a combination of a hub deployment for internal system access and the use of SAP Cloud Platform OData Provisioning to provide system access for external users. Using on-premise SAP Gateway for internal access keeps the customer s business data completely within their network boundaries, thereby supporting data security policies, as the business data must not leave the customer network or the country where the customer is located. Avoid using an SAP backend system with embedded deployment as a hub system for additional SAP backend systems (Figure.). This might lead to a situation where the SAP Gateway release of the hub system is lower than the version of the SAP Gateway backend components of the remote SAP backend system. (Such a situation can occur because it might not be possible to upgrade the hub system at the same time as the SAP backend system.) In this case, you won t be able to leverage new features of the higher version. SAP NetWeaver 7.50 SAP Gateway 2.0 SP 11 SAP_GWFND SAP ERP Not Upgraded SAP NetWeaver 7.50 SAP Gateway 2.0 SP 11 (SAP_GWFND) Connects To Figure. Potentially Problematic Upgrade Path Using an Embedded Deployment as Hub for Another Backend System SAP NetWeaver 7.50 SAP Gateway 2.0 SP 11 SAP_GWFND SAP_GWFND Upgraded SAP CRM Future Version of SAP NetWeaver (e.g. 7.60) Future Version of SAP Gateway Backend Functionality (e.g. SP 12) (SAP_GWFND) Service Pack Level Equivalence in Mixed Environments For mixed environments of SAP NetWeaver 7.0 or 7.50 and SAP Gateway 2.0 on top of SAP NetWeaver 7.31 and earlier, you may wonder which service pack level of SAP NetWeaver 7.0 is equivalent to which service pack level of SAP Gateway running on a release prior to SAP NetWeaver 7.0. The answer to this question can be found in SAP Note : SAP Gateway 2.0 Support Package Stack Definition. Starting with SAP NetWeaver 7.50 SP 03, new developments in SAP Gateway are only performed for the software component SAP Gateway Foundation (SAP_GWFND) in the highest NetWeaver release. No down ports are performed to releases prior SAP NetWeaver 7.50 SP 03. The compatibility matrix of the software component SAP Gateway Foundation (SAP_ GWFND) in SAP NetWeaver 7.52, 7.51, and 7.50 ( SP 03) can be found in SAP Note

8 Deployment Options, Installation, and Configuration.1 Introduction to SAP Gateway Deployment.1.6 Deployment Options for SAP Fiori and SAP S/HANA The main use case of SAP Gateway is to publish OData end points for SAP Fiori applications for SAP Business Suite or SAP S/HANA systems. In addition to the deployment of the SAP Gateway components, we have to take into account the deployment of the SAPUI5 components and the deployment of the SAP Fiori UI components. Both the SAP Fiori UI and the SAPUI5 components can be deployed either on-premise or in SAP Cloud Platform. With the SAP Fiori Cloud product offering, customers can choose to deploy the SAP Fiori UI components in the SAP Cloud Platform. There is prepackaged business content available for SAP Business Suite and SAP S/HANA. The corresponding OData services can be published using one of the following three deployment options (see Figure.5): 1. SAP Gateway (embedded deployment) 2. SAP Gateway (hub deployment) SAP Fiori Cloud On-premise deployment In an on-premise scenario, the SAP Fiori UI components are deployed on the SAP Gateway system, which is then called the SAP Fiori front-end server (FES). As in the case of SAP Gateway, we have two deployment options (see Figure.5): 1. FES embedded deployment 2. FES hub deployment 3. SAP Cloud Platform OData Provisioning The SAP Fiori apps reference library ( com) contains a catalogue of all apps that are supported for SAP S/HANA, SAP Business Suite, and those apps that are available via SAP Fiori Cloud. In the following sections, we ll unpack the SAP Fiori deployment options with a focus on SAP S/HANA. SAP Fiori apps reference library SAP Fiori on-premise SAP Fiori Cloud FES Embedded Deployment SAP Fiori Cloud SAP Fiori launchpad content SAP Fiori UIs SAP Fiori Cloud SAP Fiori Fiori UIs launchpad content SAP FLP Content Fiori UIs SAP Fiori Cloud SAP Fiori launchpad content SAP Fiori UIs SAP Cloud Platform OData Provisioning In this setup, every system has its own SAP Fiori launchpad. The content configuration must therefore be performed for each system with a local scope. Advantages of an embedded FES deployment are an optimized runtime performance, a simplified software lifecycle, and user/authorization management. While this is the recommended deployment option if multiple SAP S/HANA systems are used, the recommended option for multiple SAP Business Suite systems is the FES hub deployment that is described in the following section. SAP Fiori launchpad content SAP Fiori UIs SAP Gateway SAP Gateway enablement SAP S/HANA or SAP Business Suite backend SAP Fiori FES SAP Fiori launchpad content SAP Fiori UIs SAP Gateway SAP Gateway enablement SAP Business Suite or SAP S/HANA backend Cloud connector SAP Gateway SAP Gateway enablement SAP S/HANA or SAP Business Suite backend Cloud connector SAP Gateway SAP Gateway enablement SAP Business Suite or SAP S/HANA backend Cloud connector SAP Gateway enablement SAP Business Suite According to the roadmap of SAP Fiori Cloud, it is planned to offer a central entry point to multiple SAP S/HANA systems with multiple product versions via the SAP Cloud Platform Portal. A single access point to multiple SAP S/HANA systems is currently only possible if a central SAP Fiori frontend server is used that offers custom tiles to launch the SAP Fiori launchpad of the specific SAP S/HANA systems in a separate browser tab or window. Release-independent UIs such as MyInbox or SAP Fiori apps developed by the customer can be deployed on the central server nevertheless. FES embedded deployment FES hub deployment SAP Gateway embedded SAP Gateway hub SAP Cloud Platform OData Provisioning Figure.5 SAP Fiori Deployment OData Provider Options

9 Deployment Options, Installation, and Configuration.1 Introduction to SAP Gateway Deployment FES Hub Deployment For scenarios that include multiple SAP Business Suite backend systems, the SAP frontend server hub deployment is the recommended setup. In this case, both the SAP Fiori apps and the SAP Fiori launchpad content are running on top of the SAP Gateway server. This setup is then called the central frontend server. Classic UIs such as SAP Web Dynpro or SAP GUI for HTML screens remain on the SAP S/HANA backend. Because of this, such scenarios also require a SAP Web Dispatcher in front of the SAP Fiori FES. This setup allows one central entry point (SAP Fiori launchpad) to business applications from multiple systems, since the Fiori UI components of SAP Business Suite systems are compatible with several backend versions. This contrasts with the Fiori UI components of SAP S/HANA, with several backend versions which are not compatible. As a result, a bundling of the access using one single frontend server only works for multiple SAP S/HANA systems with the same release. published on the SAP Cloud Platform directly from backend systems. Therefore, this scenario is called an external access point landscape. Please note that this scenario is currently only supported for SAP Business Suite backend systems..1.7 Comparison of Deployment Options As you ve seen so far, all possible deployment options for SAP Gateway have advantages and disadvantages. At the same time, we have to take into account that when using SAP Fiori and SAP S/HANA systems in your system landscape, it is recommended to use a different deployment option than the one you would choose when looking at the situation from a purely SAP Gateway perspective. To help you decide which option to use in your specific scenario, Table.3 summarizes and compares the major decision points. SAP Fiori Cloud and SAP Gateway On-Premise While the number of SAP Fiori apps in the SAP Fiori apps library ( fioriappslibrary.hana.ondemand.com) that are available via SAP Fiori Cloud is quite limited, it has significantly grown with SAP S/HANA 1610 and even more with SAP S/HANA 1709, where more than 9,000 SAP Fiori apps are available. Applications that are provided via SAP Fiori Cloud are updated automatically on a regular basis, and new applications are made available to customers without impacting their on-premise release cycles. SAP Fiori Cloud supports an external access point landscape as well as an internal access point landscape. The latter prevents sensitive OData requests to the backend system from being routed through the cloud, and SAP Cloud Platform is solely used to provide UI-related frontend services. Regarding the integration of multiple SAP S/HANA backend systems, the same restrictions apply as described previously for the on-premise scenarios. SAP Fiori Cloud and SAP Cloud Platform OData Provisioning When using SAP Cloud Platform OData provisioning, the business data for the SAP Fiori apps is exposed to the Internet: The OData end points are Scenario SAP Fiori for SAP Business Suite (multiple backend systems) SAP Fiori for SAP Business Suite (one backend system) SAP Fiori for SAP S/HANA (multiple backend systems) SAP Fiori for SAP S/HANA (one backend system) Support for routing FES Embedded Deployment FES Hub Deployment SAP Fiori Cloud and SAP Gateway Embedded SAP Fiori Cloud and SAP Gateway Hub O ++ O + SAP Fiori Cloud and SAP Cloud Platform OData Provisioning Not supported Not supported Not supported Supported Not supported Supported Not supported Table.3 Deployment Comparison

10 Deployment Options, Installation, and Configuration.2 Preparing for Installation and Configuration Scenario Support for multiorigin Costs FES Embedded Deployment Not supported No additional server is needed FES Hub Deployment Supported Additional server is needed SAP Fiori Cloud and SAP Gateway Embedded Not supported No additional server is needed SAP Fiori Cloud and SAP Gateway Hub Supported Additional server is needed SAP Fiori Cloud and SAP Cloud Platform OData Provisioning Not supported SAP Cloud Platform licensing cost Guide because these prerequisites are specific for every single add-on. For the main components and SAP Gateway add-ons, the prerequisites (at the time of print) are shown in Table.5. Requirements SAP Net- Weaver Stack Specification The latest kernel patch for the corresponding SAP NetWeaver version has to be applied. Core Components GW_CORE and IW_FND SAP NetWeaver 7.0 SPS 25 SAP NetWeaver 7.01 SPS 10 SAP NetWeaver 7.02 SPS 07 SAP NetWeaver 7.03 SPS 01 SAP NetWeaver 7.31 SPS 01 Table.3 Deployment Table Comparison.3 Deployment (Cont.) Comparison (Cont.).2 Preparing for Installation and Configuration No matter what deployment option has been chosen, before you can start with the actual installation and configuration process, you have to execute several preparation steps. The first step for releases prior to 7.0 is to check whether you fulfill the installation prerequisites. In a next step, you need to get the software. Be sure to make note of important information that will be needed during the installation and configuration procedure. Business enablement provisioning (BEP) component (IW_BEP) Core component SAP_GWFND (remember, this comprises the functional scope of components IW_FND, GW_CORE, IW_BEP, and IW_HDB) SAP NetWeaver 7.0 SPS 18 SAP NetWeaver 7.01 SPS 03 SAP NetWeaver 7.02 SPS 06 SAP NetWeaver 7.03 SPS 01 SAP NetWeaver 7.31 SPS 01 SAP NetWeaver 7.0 SPS 02 Minimum requirements To run SAP Gateway, a number of prerequisites need to be fulfilled in terms of both hardware and software. With respect to hardware, the minimum requirements for SAP Gateway are shown in Table.. SAP backend Table.5 Software Requirements SAP Business Suite or SAP S/HANA system Requirement Processor RAM Hard disk capacity Specifications Dual core or higher, 2 GHz or higher 8 GB or higher 80 GB primary or higher Further Resources Installation prerequisites for SAP Gateway 2.0 SP12 can be found at bit.ly/2dgdkwe. The SAP Gateway Installation Guide can be found at Table. Hardware Requirements With respect to software, the minimum requirements are a little more complicated; check the newest requirements in the SAP Gateway Installation For additional information, check on the product availability matrix (PAM) for SAP Gateway at and search for SAP Gateway 2.0. Also check SAP Note for SAP Gateway

11 Deployment Options, Installation, and Configuration.3 Quick Start Guide Download package For releases of SAP NetWeaver 7.0 and higher, you can skip the software download and deployment because SAP Gateway already comes with SAP NetWeaver. For releases below SAP NetWeaver 7.0, the SAP Gateway download package can be found on the SAP Service Marketplace in the SAP Software Download Center. Go to and navigate to the tab Installations and Upgrades and enter SAP Gateway as a search term, with Downloads selected in the dropdown box. Scroll down to the list entry SAP Gateway 2.0. There you ll find the software under Installation and Upgrade and also the Application Help that allows you to download the online documentation in plain HTML format. Alternatively, you can always work with the online documentation at Finally, before starting the actual configuration activities, a number of pieces of information need to be collected about the SAP Gateway host and the overall landscape (see Table.6). This will save time later and make things easier..3 Quick Start Guide The online documentation for SAP Gateway ( p/sap_gateway) explains all possible configuration options, many of which most people won t even need. Therefore, the idea behind this Quick Start Guide is to get you started quickly with some basic setup. After you have your basic setup running, you can then configure additional features and components as you like. Note that the Quick Start Guide is only valid for the embedded deployment option or for the option of hub deployment with development on the hub, which we ve chosen for this guide. The Quick Start Guide gives you an easy-to-follow overview of the absolutely required steps to set up and configure SAP Gateway. After you ve followed the steps, it leaves you with a working SAP Gateway system that you can use as a playground environment or continue to configure to turn the very basic, absolutely minimal configuration into a fully usable production environment. Embedded deployment quick start Required Information Description Important Notes Fully qualified domain name (FQDN) Administrator credentials HTTP/HTTP(S) ports SAP system Name of the SAP NetWeaver Application Server (AS) for ABAP system or the load-balancing device (e.g., server.domain.com) Login information of the administrator of the SAP NetWeaver AS for ABAP to install and maintain the system HTTP and HTTP(S) port numbers of the central instance of the SAP NetWeaver AS for ABAP (e.g., 8000 for HTTP and 8001 for HTTP[S]) For each SAP system to which you want to connect the SAP Gateway server, the following information is required: System ID, system number Server name HTTP/HTTP(S) port A sufficiently authorized user is required for this Quick Start Guide to work. This configuration is extremely basic, and only the absolutely required steps have been performed, so don t use this setup in a production environment without additional configuration (e.g., authorizations, security)! Full details can be found at the SAP Gateway Configuration Guide, on the landing page of the SAP online documentation: help.sap.com/viewer/p/sap_gateway. Remember, in the case of embedded deployment and hub deployment with development on the hub, the central components for SAP Gateway and any optional backend components are deployed together in the SAP Business Suite or SAP S/HANA system or the hub system. Five steps are required to get your initial SAP Gateway setup running plus an optional step for older SAP Gateway versions: Setup and configuration steps Administrator credentials (i.e., user ID and password of an administrative user) 1. For versions older than SAP NetWeaver 7.0, deploy SAP Gateway addons. Table.6 Information Gathering 2. Activate SAP Gateway

12 Deployment Options, Installation, and Configuration.3 Quick Start Guide 3. Create the SAP system alias.. Create an SAP Gateway alias. 5. Activate the OPU node. 6. Test your settings. After you ve performed these steps, you should be able to develop a service on the embedded SAP Gateway system and publish it. Let s walk through these steps now..3.3 Step 3: Create an SAP System Alias You now have to create a system alias entry that points from the hub system to the SAP backend system. Because you ve chosen an embedded deployment, you ll create a LOCAL system alias entry using the NONE RFC destination. To do so, go to Manage SAP System Aliases in the IMG (Figure.7) by starting Transaction SPRO and navigating to SAP NetWeaver SAP Gateway OData Channel Configuration Connection Settings SAP Gateway to SAP System. System alias.3.1 Step 1: Deploy the SAP Gateway Add-Ons for Older SAP NetWeaver Versions In an SAP NetWeaver 7.0 or 7.5x system, this step can be skipped because the SAP_GWFND software component, which comprises all the functionalities of GW_CORE, IW_FND, and IW_BEP, is already installed as part of the standard. Transaction SAINT For a system below SAP NetWeaver 7.0, you first need to deploy the three add-ons GW_CORE, IW_FND, and IW_BEP using Transaction SAINT, which is the SAP Add-On Installation Tool. Activation in IMG.3.2 Step 2: Activate SAP Gateway In the next step, you activate SAP Gateway by starting Transaction SPRO and navigating to the Activate or Deactivate SAP Gateway node in the implementation guide (IMG) (Figure.6). Figure.7 Creating the System Alias This opens the SAP Gateway Routing Configuration, in which you can create a new System Alias entry using the values shown in Table.7. Field System Alias RFC Destination Local Gateway For Local App OData on Backend Value LOCAL NONE X (blank) (blank) Figure.6 Activation of SAP Gateway Table.7 Change View Values

13 Deployment Options, Installation, and Configuration.3 Quick Start Guide Field RFC Destination Value NONE Gateway hub-specific customizing settings. Enter the values shown in Table.8. Target System ID Target Client Software Version WS Provider System Description The SID of your embedded system The client you re working in DEFAULT (blank) Local Gateway Table.7 Change View Values (Cont.) After you ve entered the values, your screen should look like Figure.8. Figure.9 SAP Gateway Settings Field Destination System Client System Alias RFC Destination Value GW_HUB The client you re working in A unique name for the SAP Gateway host (e.g., the SID) NONE Figure.8 Example System Alias Creation.3. Step : Create an SAP Gateway Alias Table.8 Customizing Values Your screen should now look like Figure.10. SAP Gateway alias The creation of an SAP Gateway alias is needed to have at least one entry for the SAP Gateway hub in the Service Builder (Transaction SEGW) to allow for registering the services that you re going to develop. To create an SAP Gateway alias, navigate to a different part in the IMG called SAP Gateway Service Enablement (Figure.9). This part contains the SAP Figure.10 SAP Gateway Settings Overview

14 Deployment Options, Installation, and Configuration.3 Quick Start Guide Transaction SICF.3.5 Step 5: Activate the OPU Node In a freshly installed system, you now have to activate the OPU node using Transaction SICF (Figure.11). Click the Refresh icon. Now expand the OPU node again (see Figure.13), and check whether the changes have been successfully performed. Figure.13 Expanding the Node.3.6 Step 6: Test Your Settings You can now test your settings by developing a simple service using the Service Builder (Transaction SEGW) (see Figure.13). Configuration verification As you can see in Figure.1, the name of the destination system of the SAP Gateway alias is shown in the Service Maintenance node in Transaction SEGW. Figure.11 Activate Node Using Transaction SICF Next, a dialog pops up in which you need to confirm that all subnodes will be activated. To do this, click the Yes button with the hierarchy symbol (Figure.12). Figure.1 Expanding the Node for SAP Gateway Service Builder Figure.12 Confirmation of Internet Communication Framework Services Creation When selecting Maintain in the context menu, Transaction /IWFND/ MAINT_SERVICE (Activate and Maintain Service) is started on the hub

15 Deployment Options, Installation, and Configuration. Installation and Configuration in Detail system (Figure.15). Note that the service has been registered for the LOCAL system alias that you ve maintained in the process. (Optional) Installation and Configuration of SAP Gateway Add-Ons Basic Configuration Information Collection Profile Parameter Maintenance ICF Services Activation Language Settings Maintenance OData Channel Configuration Authorizations Connection Settings SAP Gateway Activation OData Development Configuration Backend Connection Settings IW_BEP or SAP_GWFND Configuration Smoke Testing Figure.15 Activate and Maintain Services Screen Figure.16 Installation and Configuration Process Each of these phases can be further broken down into several steps. Let s. Installation and Configuration in Detail now look into the details of these phases and steps. Needless to say, the configuration just discussed in the Quick Start Guide section is extremely basic and should by no means be used in a production environment without additional steps that are absolutely required for usage in a production system. And even for playground or POC systems, additional configurations are recommended and even required in some..1 Installing the SAP Gateway Add-Ons As stated earlier, this step is only necessary for systems prior to SAP Net- Weaver ABAP 7.0 because the 7.0 release contains the software component SAP_GWFND as part of the standard. Installation cases. To install the required SAP Gateway add-ons for SAP NetWeaver versions below Because only the absolutely required configuration steps were executed, and a number of important steps were dropped, the idea of this section is to provide you an overview of what you need to do for a full-blown installation and configuration of SAP Gateway, and to then dig deeper into some of 7.0 SP 02, you must first download them. Because the downloaded installation packages have a compressed format, the initial step of the actual installation process is to unpack them into your local file system. Next, import the add-ons using the Transaction SAINT installation tool, following these steps: the most important details. Again, a full SAP Gateway configuration guide 1. Call Transaction SAINT, and choose Start. can be found at 2. Go to Installation Package Load Packages From Front End to upload Process overview The installation and configuration process of SAP Gateway consists of five phases (see Figure.16): the installation files that you ve previously downloaded from the Service Marketplace. 1. For systems prior to SAP NetWeaver 7.0, the installation and configuration of the SAP Gateway add-ons 2. The basic configuration of SAP Gateway 3. Select the add-on <add-on> <add-on release>, and choose Continue. If all of the necessary conditions for importing the add-on have been fulfilled, the system displays the relevant queue. The queue consists of the add-on 3. The OData channel configuration. The (optional) BEP (IW_BEP) or SAP_GWFND configuration 5. Smoke testing the installation

16 Deployment Options, Installation, and Configuration. Installation and Configuration in Detail Configuration Preparations package, support packages, and other add-on packages. To start the installation process, choose Continue.. For more information, call Transaction SAINT, and choose Info on the application toolbar. 5. The system prompts you to enter a password for each add-on component. These passwords can be found in the SAP Gateway Configuration Guide ( Basic Configuration Settings After you ve installed the SAP Gateway components, you must configure your system. The steps for configuration include executing the basic customizing for SAP Gateway and describing system configuration activities. Some tasks are mandatory, and others are optional and depend on specific use cases that you want to enable. With respect to the sequence, the mandatory basic configuration is the starting point after collecting the data needed for the configuration process. Then the OData channel configuration takes place. Before starting the actual configuration activities, several pieces of information need to be collected about the SAP Gateway host and the overall landscape. (Refer to Section.2 for details.) Now that you ve collected the required information, the configuration activities can begin. In a number of areas, settings need to be adjusted to SAP Gateway requirements with respect to values. First, you need to use Transaction RZ10 to maintain the profile parameters with the values shown in Table.9. In the second step, Internet Communication Framework (ICF) services need to be configured. After the initial installation of an SAP NetWeaver AS for ABAP, all ICF services are in an inactive state for security reasons. These services can be directly accessed via HTTP from the Internet. Therefore, unknowingly activated services represent a security risk, which can be mitigated by using suitable methods for restricting access. Because multiple services can be executed when you call a URL, all relevant service nodes must be activated in a Transaction SICF tree. The URL path gets mapped to ICF subnodes (services) included in the URL. For example, if you want to activate the services for URL /sap/public/icman, you have to activate the service tree default_host in Transaction SICF. Then, you have to activate services sap, public, and icman separately. To activate a service, go to Transaction SICF, and select the required ICF service in the tree. You then use one of the two options to activate the service: either the menu option (Service/Host Activate) or the context menu (choose Activate Service). You can activate only a selected service node or the entire subtree (using the tree icon). The SAP Gateway services that need to be activated are shown in Table.10. Service /sap/public/opu /sap/opu/odata with all of its subnodes Comments This service is needed for loading resources such as images. OData is the standard mode for all new applications. When creating a service, a new node is created automatically. ICF services activation Service activation options Profile Parameter Value login/accept_sso2_ticket 1 login/create_sso2_ticket 2 Table.9 Profile Parameters These two profile parameters are only activated after a system restart and are used to enable single sign-on (SSO) from and to the SAP Gateway system. /sap/opu/sdata with the following subnodes: /sap/opu/sdata/iwcnt /sap/opu/sdata/iwfnd /sap/opu/sdata/sap Table.10 Services to Be Activated SData is the node used for existing applications. It s called the compatibility mode for SP 02. This is optional unless you re using scenarios based on the outdated generic channel

17 Deployment Options, Installation, and Configuration. Installation and Configuration in Detail Service If you want to use a web-based scenario, the following nodes on the target system need to be enabled: /sap/bc/srt/xip/sap /sap/bc/webdynpro/sap/saml2 Comments Web-based scenarios here mean that content is consumed via web services. system where the IW_FND software component is deployed. In the SAP Reference IMG, navigate to SAP NetWeaver Gateway OData Channel. SAP NetWeaver release 7.0 and higher If you use the SAP_GWFND software component, IMG activities are available under SAP NetWeaver SAP Gateway and SAP NetWeaver SAP Gateway Service Enablement. /sap/public/bc /sap/public/bc/ur /sap/public/mysssocnt In general, a number of steps need to be performed during the OData channel configuration. This includes setting the appropriate authorizations for users, configuring the connection settings for SAP Gateway to the SAP Table.10 Services to Be Activated (Cont.) backend systems (including RFCs and system aliases), activating SAP Gateway, and configuring the connection settings for the SAP backend system Language settings In a third step, the language settings need to be checked and potentially to the SAP Gateway server. We walk you through these steps next. adjusted. As for languages, the SAP Gateway system supports only the intersecting set of the languages of the connected SAP backend systems. You can still make sure that your users receive the appropriate language. Follow the specific logon language process for this. Authorization Configuration The first task here is to set up an administrator role for SAP Gateway components and assign users to it. After that is done, you can set up one or several user roles and assign users to these as well. To do so, create your own Logon Language For more information about logon languages, we recommend bit.ly/2ok0wml. roles or copy existing roles to new custom roles. To facilitate things, SAP Gateway provides predefined roles as templates for developers, for administrators, and for support use cases. Support templates only have display authorizations and are designed for use by support colleagues. OData channel configuration..3 OData Channel Configuration In the next step, the OData channel configuration has to be maintained. This is a little more challenging due to dependencies on the specific SAP The three most important kinds of templates are the framework templates (Table.11), the OData channel templates (Table.12), and the BEP templates (Table.13). Predefined role templates NetWeaver release. For example, the location of the configuration settings for the OData channel and the structure in the IMG can differ depending on the underlying SAP NetWeaver release, as described in the following list: Template Name /IWFND/RT_ADMIN Template for Role Framework administrator SAP NetWeaver releases 7.00 and 7.01 /IWFND/RT_BOR_DEV Business Objects Repository (BOR) developer The OData channel configuration settings are available in the IMG in the system where the IW_FND software component is deployed. In the SAP Reference IMG, navigate to SAP NetWeaver Gateway. /IWFND/RT_DEVELOPER /IWFND/RT_GW_USER Developer User SAP NetWeaver releases 7.02 and 7.31 The OData channel configuration activities are listed in the IMG in the /IWFND/RT_TU_NOTIF Table.11 Framework Templates Technical user for notifications

18 Deployment Options, Installation, and Configuration. Installation and Configuration in Detail Template Name /IWBEP/RT_MGW_ADM Template for Role OData channel administrator Installing, configuring, and maintaining SAP Gateway components and applications that run on top of SAP Gateway Configuring and maintaining users data, including roles and user map- /IWBEP/RT_MGW_DEV /IWBEP/RT_MGW_USR OData channel developer OData channel user ping Finally, for SAP Gateway users, you must create roles specific to the user s /IWHDB/RT_USER /IWBEP/RT_SUB_USR OData channel SAP HANA integration user On behalf of the subscription user required tasks. Either you can specify different authorizations for different user roles or have all authorizations bundled in a single user role. For more information, see Chapter 16, Section Table.12 OData Channel Templates Template Name /IWBEP/RT_BEP_ADM /IWBEP/RT_BEP_USR Table.13 BEP Templates Further Resources Template for Role BEP administrator BEP user For more information about templates and creating and assigning roles, we recommend Connecting SAP Gateway to the SAP Backend In this step, the connection settings have to be maintained. This holds true in both possible directions SAP Gateway to SAP Business Suite or SAP S/HANA systems and SAP Gateway to consumers. With respect to the connection settings for the consumers, you have to specify settings when using push flow. (For more details about push flow or notifications, see Appendix A.) After that has been done, you have to configure the SAP Gateway components and define how to interface with the backend system. These activities are again performed in the SAP Reference IMG using Transaction SPRO. Navigate to SAP NetWeaver SAP Gateway OData Channel Configuration Connection Settings SAP Gateway to SAP System. Connection settings Role creation steps For creating the three most important roles namely, SAP Gateway developer, SAP Gateway administrator, and SAP Gateway user only a few steps need to be performed. For the SAP Gateway developer, create a developer role based on the /IWFND/RT_DEVELOPER and /IWBEP/RT_MGW_DEV templates, which also contain the usual authorizations needed for ABAP development. For the SAP Gateway administrator, create a role for an administrator user with permissions and privileges for several tasks, including the following: Creating services Analyzing logs and identifying potential issues with the SAP Gateway landscape Further Resources Detailed information on both how to configure the connection settings for SAP Gateway to consumers and how to configure the settings for SAP Gateway to SAP systems can be found at In the first step, you define the trust relationship between your SAP backend system and the SAP Gateway host by using Transaction SM59 to configure the SAP backend system to be the trusting system and the SAP Gateway host to be the trusted system. Creating a RFC Destination on the SAP Gateway Host to the SAP System Next, you will need to set up a type 3 RFC connection from the SAP Gateway host to the SAP backend system. To create one, go to Transaction SPRO, and

19 Deployment Options, Installation, and Configuration. Installation and Configuration in Detail System alias creation Global activation open the SAP Reference IMG. Navigate to SAP NetWeaver SAP Gateway OData Channel Configuration Connection Settings SAP Gateway to SAP System Manage RFC Destinations. There you create the RFC of type 3. It s important to note that you ve previously created a trust relationship between the SAP Gateway host and your SAP backend system. Creating the SAP System Alias for Applications In the next step, you need to specify where the SAP system alias should point. Depending on the specific scenario and your system landscape, you accordingly set up the system alias. This system alias is the result of the routing for an inbound request on SAP Gateway and can point to a remote or a local system. If that system alias is flagged as a local SAP Gateway instance, it means the system that is responsible for processing (managing and storing) the data of an inbound request is the local SAP Gateway instance itself. To configure the system alias, go to Transaction SPRO, and in the SAP Reference IMG, navigate to SAP NetWeaver SAP Gateway OData Channel Configuration Connection Settings SAP Gateway to SAP System Manage SAP System Aliases. After selecting Create System Alias in the SAP Gateway Routing Configuration, enter the required information for the system alias. This information includes the system alias name, the RFC destination, and the software version, among other things. Check your system alias configuration using Check SAP System Aliases to ensure that everything functions properly. Although not mandatory, the system alias should also contain the SAP system ID because it s needed to register an SAP Gateway service from within Transaction SEGW in that backend system. Activating SAP Gateway Now it s time to activate SAP Gateway in your system. (It s always possible to deactivate it again. In that case, all SAP Gateway services stop running, and an error message is sent to any consumer that calls the services.) To activate SAP Gateway, go to Transaction SPRO, and open the SAP Reference IMG. Navigate to SAP NetWeaver SAP Gateway OData Channel Configuration Activate or Deactivate SAP Gateway, and then execute the activation. Activating Services Transaction /IWFND/MAINT_SERVICES (Activate and Maintain Services) is used to maintain all registered services on the SAP Gateway server (hub system), to register and activate services, and to delete services. The main screen is divided into an upper and a lower part, in which the upper part shows all registered services (Service Catalog) and the lower part shows the details of the selected service from the service catalog. The details are split into ICF nodes and system aliases. Settings for OData Channel Service Development on the SAP Backend System OData channel implementations retrieve data from a connected SAP backend system. Both application logic and metadata are hosted there. All SAP Gateway services need to be registered in the backend before being ready for activation on the hub. On the SAP backend system, both models and services need to be maintained (registered). This registration process takes place automatically when generating the runtime artifacts using the Service Builder. Manual Registration of Services in the Backend The registration process can also be started manually, if it hasn t been done during service development, using the Service Builder. If it s necessary to perform the registration process separately, you have to start Transaction SPRO, navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel Service Development for Backend OData Channel, and then choose either Maintain Models or Maintain Services. After a service has been defined in the SAP backend system, it can be activated on the SAP Gateway system. Connecting the SAP Backend System to the SAP Gateway Server In this step, the system alias entries in the SAP backend system have to be maintained. The creation of an SAP Gateway alias is needed to have at least one entry for the SAP Gateway hub in the Service Builder (Transaction SEGW) to allow for registering the services that you re going to develop. OData channel settings in the SAP backend

20 Deployment Options, Installation, and Configuration. Installation and Configuration in Detail Creating a RFC Destination from the SAP Backend System to the SAP Gateway Server A type 3 RFC connection from the SAP backend system to the SAP Gateway host is the next thing to set up. To create one, go to Transaction SM59. There you create the RFC of type 3. It s important to note that you ve previously created a trust relationship between the SAP backend system and your SAP Gateway host. BOR events without writing code, to obtain and send events for SAP Business Workflow, and to send events from your code. To enable BEP, start by configuring its role templates. Next, you define an event and then the event subscription and notifications. Then specify the connection settings to the SAP Gateway landscape. These settings are available both for BEP and the OData channel. Maintaining SAP Gateway Settings in the SAP Backend System To configure the settings for the SAP Gateway system in the SAP backend system, go to Transaction SPRO, and in the IMG, navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel Connection Settings to SAP NetWeaver Gateway SAP NetWeaver Gateway Settings. Here you have to enter the values shown in Table.1. Field Destination System Client System Alias RFC Destination Value GW_HUB Client in the SAP Gateway server where SAP Gateway has been activated A unique name for the SAP Gateway server, for example, the SID The name of the RFC destination you ve created beforehand Table.1 SAP Gateway Settings: Customizing Values.. Business Enablement Provisioning Configuration BEP is a component that you enable in your existing SAP backend system to handle the events and actions activated in the SAP system and to publish these events and actions through SAP Gateway. BEP provides functionality to expose data and events as OData-based REST services and is contained, as of SAP NetWeaver 7.0, in the SAP_GWFND component that comes standard with SAP NetWeaver 7.0 and higher. In older releases, BEP is contained in the IW_BEP add-on. You can use BEP to obtain and publish..5 Smoke Testing Now that we ve finished the installation and configuration, it s important to verify that things work properly. This holds true for all relevant areas namely, service development, service consumption, and operations. In most cases, there s no need to check on every detail; a smoke test is sufficient for POC and development systems. When a production system is concerned, however, we recommend more detailed tests. Depending on the business case, security topics should be specifically tested. Also, before the go-live, an additional review of the system setup and configuration should be performed. For smoke testing a POC or development system, we recommend the following steps: 1. Use the SAP Gateway client via Transaction /IWFND/GW_CLIENT to call the Catalog service that shows the service catalog (/sap/opu/odata/ IWFND/CATALOGSERVICE/ServiceCollection). 2. Call one of the registered services for example, RMT Sample Flight (/sap/opu/odata/iwfnd/rmtsampleflight/travelagencycollection). If both of these services return usable data, this confirms that your SAP Gateway installation works on a basic level. (It might be necessary, however, to generate sample flight data by running report SAPBC_DATA_GEN- ERATOR.) For smoke testing a production system, the same basic steps just described should be executed to confirm that service calls work and return data. Also, a number of smoke tests should be executed to make sure additional important SAP NetWeaver and SAP Gateway features work. This includes, for example, basic security checks. Which tests make sense depends on your specific setup. Potential tests include the following: Installation verification Smoke test procedure Production systems

21 Deployment Options, Installation, and Configuration.5 Summary Additional tests recommended Call SAP Gateway services with different user roles to determine whether the user can see the OData data he is supposed to see. Call SAP Gateway services with a user who isn t supposed to see data and check the result. As we ve already stated, these are only smoke tests. We recommend appropriate tests to ensure your setup works as expected, especially in the performance and security areas. To run test cases, it s possible to store them for the services you re interested in testing. This can be done using the SAP Gateway client, which offers the feature to store test cases in its test database. The handling of test cases using the SAP Gateway client is described in more detail in Chapter 15. A number of factors influence system performance, and this isn t limited to the obvious ones such as main memory or the number and kind of CPUs. There are other factors specific to OData and SAP Gateway that you should take into account as well and that can have a major impact. One example is the format of SAP Gateway service calls. SAP Gateway 2.0 OData-compliant services implementing the JavaScript Object Notation (JSON) format have a lower overhead than those implementing the Atom Publishing Protocol (AtomPub) format when more than one hundred objects are retrieved. So for performance-relevant calls that retrieve more than 100 objects, the recommendation is to use JSON. When fewer than 100 objects are retrieved, the overhead for both AtomPub and JSON is the same. System performance JSON versus AtomPub Deployment bottom line During quite a number of projects, best practices for SAP Gateway installation and configuration have evolved. In most cases, the official SAP documentation already reflects these lessons learned and points you in the right direction. Let s still have a look at the important best practices and where you can find information to give you additional background. With respect to deployment options, the bottom line is that you should only use an embedded SAP Gateway installation for a production environ- Concerning authorizations, the recommendation is to use SAP s role templates as much as possible to make your life easier. When talking about security, the main recommendation is to not directly expose your SAP Gateway system to the Internet because this opens it up for attacks. Instead, use a reverse proxy between the SAP Gateway and the outside world. Role templates Reverse proxy ment in exceptional cases, such as when there is not a lot of load on the Quick Sizer embedded environment, or you re forced to use this setup for other reasons. The strong recommendation is to go for a separate SAP Gateway box to scale better and allow you to always keep the SAP Gateway version up to date. On the other hand, if you re new to SAP Gateway and want to play around and learn or perform a simple POC, the embedded deployment makes things a lot easier and is the first pick for a straightforward and easy start. When you look at sizing your landscape appropriately, SAP helps you with the Quick Sizer tool ( The Quick Sizer is a free web-based tool. It s highly recommended that you use this tool early in an SAP Gateway project, not only to make sure you have enough performance to handle all requests but also to do this in an economically smart way. You can find a document that specifically discusses SAP Gateway in.5 Summary This chapter provided you with background on SAP Gateway s deployment options and an overview of how to perform the setup and configuration. To get you going quickly, a minimal configuration guide was introduced. Additional configuration details and best practices for SAP Gateway system configurations were provided to allow for a well-suited setup in more advanced system environments. With this and SAP s extensive standard documentation, you should be able to start setting up your own SAP Gateway system and tailor it to your specific needs while avoiding potential traps and taking advantage of SAP Gateway s extensive feature set. With this, we conclude Part I of this book. In the next chapter, we dive into the heart of SAP Gateway: the OData service creation process. the SAP NetWeaver document repository of the Quick Sizer tool

22 Contents Foreword by Björn Goerke Introduction Acknowledgments PART I Getting Started 1 Introduction to SAP Gateway Modern Business Applications User Interfaces Infrastructures SAP Gateway for Modern Business Applications SAP Gateway in SAP S/HANA Installation and Deployment Installation Deployment SAP Gateway and Related Products SAP Fiori SAP Cloud Platform, ABAP Environment SAP Cloud Platform API Management SAP Cloud Platform Integration SAP Cloud Platform Portal and SAP Enterprise Portal SAP Cloud Platform Mobile Services SAP HANA SAP Process Integration and SAP Process Orchestration SAP Business Warehouse Summary

23 Contents Contents 2 Introduction to OData OData and REST What Is REST? What Is OData? Structure of an OData Service Service Document Service Metadata Document OData Operations Create Read Update Delete OData Query Options Filtering and Projecting ($filter and $select) Sorting ($orderby) Client-Side Paging ($top, $skip, and $inlinecount) Counting ($count) Inlining ($expand) Formatting ($format) OData in SAP Solutions Mobile Applications SAP Fiori SAP Jam SAP Enterprise Portal SAP Solution Manager SAP HANA SAP S/HANA SAP Cloud Platform SAP Gateway OData Features What s Different with OData.0? JavaScript Object Notation Format Powerful Query Language Cross-Service Navigation Actions and Functions Vocabularies and Annotations Summary Architecture and Integration Gateway Principles SAP Gateway Architecture Consumer Tier SAP Gateway Tier SAP Backend Tier Add-On Structure Evolution Integration with Other Technologies Remote Function Call Business Object Repository Service Provider Infrastructure SAP BW InfoCubes Multidimensional Expressions SAP BW Easy Query Generic Interaction Layer SAP Business Process Management SAP Business Workflow ABAP Programming Model for SAP Fiori Architecture and Technology SAPUI5 and SAP Fiori Elements SAP Gateway and the ABAP Programming Model for SAP Fiori SAP HANA Outlook Summary

24 Contents Contents Deployment Options, Installation, and Configuration Introduction to SAP Gateway Deployment Hub Deployment with Development in the SAP Backend System Hub Deployment with Development on the Hub Embedded Deployment SAP Cloud Platform OData Provisioning Mixed Deployment Options Deployment Options for SAP Fiori and SAP S/HANA Comparison of Deployment Options Preparing for Installation and Configuration Quick Start Guide Step 1: Deploy the SAP Gateway Add-Ons for Older SAP NetWeaver Versions Step 2: Activate SAP Gateway Step 3: Create an SAP System Alias Step : Create an SAP Gateway Alias Step 5: Activate the OPU Node Step 6: Test Your Settings Installation and Configuration in Detail Installing the SAP Gateway Add-Ons Basic Configuration Settings OData Channel Configuration Business Enablement Provisioning Configuration Smoke Testing Summary PART II Service Creation 5 Introduction to OData Service Creation Methods for Creating an OData Service Service Creation Process Overview SAP Gateway Toolset Service Builder Supporting Tools during the Service Creation Process ABAP Development Tools for SAP NetWeaver and CDS Views Steps in the Service Creation Process Data Model Definition in the Service Builder Service Registration in the SAP Backend System Service Implementation Service Maintenance Service Generation via Redefinition Service Generation via Referenced Data Sources Service Generation via OData.publish:true OData Channel Development Paradigm Model Provider Class Data Provider Class and Data Provider Extension Class Technical Considerations Summary Service Development Data Model Definition Creating a Project Creating a Data Model Service Registration Service Stub Generation Service Maintenance Incremental Service Implementation and Model Enhancement Feed (GET_ENTITYSET) Single Read (GET_ENTITY) Query Options

25 Contents Contents 6.5. Navigation Properties Create, Update, and Delete Methods Function Imports Media Resources Expand/Self-Expand Deep Insert Batch Add UI Annotations ABAP Programming Model for SAP Fiori with BOPF Defining the Business Object Defining the Consumption View Determinations, Validations, and Actions Draft Support ABAP RESTful Programming Model Summary Summary PART III Application Development 7 Service Generation Generation via RFC/BOR Interface Data Model Definition Service Registration: Stub Creation Service Maintenance Service Implementation: SalesOrderHeaderSet Service Implementation: SalesOrderLineItemSet Generation via Search Help Generation via Redefinition SAP BW Easy Query Service Provider Interface Summary SAPUI5 Application Development Building Blocks of Web Application Development Introduction to SAP Fiori and SAPUI SAP Fiori SAPUI Installing SAPUI Creating an SAPUI5 Application Manual Creation Using the Eclipse Development Environment Summary ABAP Programming Model for SAP Fiori Development of CDS Views Modeled Data Sources Reference Data Sources Adding Annotations to an OData Service ABAP Programming Model for SAP Fiori with Classic APIs SAP Web IDE Installation and Access Installing On-Premise via the SAP Web IDE, Personal Edition Accessing On-Demand via SAP Web IDE Full-Stack Connecting to SAP Gateway Connecting the Local Installation to SAP Gateway

26 Contents Contents Connecting SAP Web IDE Full-Stack on SAP Cloud Platform to SAP Gateway OData Sample Services Developing SAPUI5 Applications Hybrid Application Development Activate SAP Web IDE Full-Stack Feature Create a Hybrid Android Application Summary SAP Fiori Reference Apps OData Model Editor Activating the OData Model Editor Browse Services via the OData Model Editor Summary Social Media Application Development PHP Facebook Twitter Extensibility Redefining and Extending OData Services Redefinition Field Extensibility Node Extensibility Extending SAPUI5 Applications Extending SAP Fiori Applications Extending the OData Service Extending the SAPUI5 Application Extending SAP S/HANA Cloud Extensibility Concepts for SAP S/HANA Cloud SAP S/HANA Cloud Key User Extensibility Summary Sina Weibo ( 新浪微博 ) Summary Enterprise Application Development Microsoft Excel PowerPivot $format=xlsx Microsoft SharePoint/Office Microsoft Visual C# Windows Desktop Microsoft Active Server Pages (ASP).NET Summary Mobile Application Development 611 PART IV Administration 12.1 Overview Native Application Development SAP Cloud Platform SDK for ios SAP Cloud Platform SDK for Android Lifecycle Management: Testing, Service Deployment, and Operations Testing

27 Contents Contents Testing SAP Gateway Services Testing a Client Application Best Practices for Testing in SAP Gateway Service Deployment Transport of Repository Objects between SAP Backend Systems Transport of Repository Objects and Customizing Entries between SAP Gateway Server Systems Versioning Activate and Maintain Services OData.0 Service Deployment Operations Periodic Cleanup Tasks Monitoring Overview Summary Cloud SAP Cloud Platform Mobile Services Web Server Business-to-Consumer Scenario Read Access Logging Summary PART V Roadmap 17 Recent and Future Developments SAP Gateway and Cloud Computing Gamification Internet of Things Security Summary Network and Communication Security Transport Protection Input Validation User Management and Authorizations Single Sign-On and Authentication Options Basic Authentication SAP Logon Tickets with SAP Enterprise Portal X.509 Client Certificates SAML 2.0 Browser Protocol OAuth Kerberos: Integrated Windows Authentication Recommended Authentication Options HTML5 Web Application Desktop Application Mobile Application (Direct Access) Appendices 787 A Advanced Topics A.1 Connecting Multiple SAP Backend Systems A.2 Configuring Notifications in SAP Gateway A.3 Using the Error Log A. Analyzing Performance and SAP Gateway Statistics A.5 Delta Query Support in Offline Scenarios A.6 Server-Side Caching A.7 Summary B The Authors Index

28 Index.edmx file NET NET Framework $count $expand... 99, 35, 36, 35 statement $filter $format $format=xlsx $inlinecount $orderby... 9 $select $skip $top A ABAP CDS... 2 table functions ABAP Class Builder... 26, 282 ABAP Development Tools , 213, 21, 236, 38 add annotations for SAP NetWeaver install ABAP Development Workbench ABAP for SAP HANA ABAP in Eclipse , 38 ABAP Managed Database Procedures (AMDP) ABAP programming model for SAP Fiori annotations architecture... 12, 13 best practices BOPF... 36, 70 classic APIs... 36, 59 evolution layers... 1 outlook SAP Gateway service generation ABAP RESTful programming model... 37, 8 annotations behavior definition behavior implementation data modeling with CDS service binding service definition test abapgit Actions Addressable Agentry SAP Framework , 819 Agility Analytic queries Analytical annotation app Android emulator Android Studio Android Virtual Device (AVD) Annotation Model for Referenced Service Annotation Modeler... 56, 59 Annotations , 36, 56 add object page SAP API economy management Append structure , 567 Application design log Application development, SAPUI Application Log Viewer Application requirements infrastructure... 0 user interface Approve Purchase Orders app... 56,

29 Index Index Architecture ABAP programming model for SAP Fiori consumer tier , 128, 130 SAP backend tier , 132 SAP Business Suite tier SAP Gateway Server tier SAP Gateway tier , 131 Assign Structure checkbox Association... 75, 8, 55, 73, 585 define set , 585 Atom AtomPub... 69, 71 Authentication... 77, 79 anonymous access basic for B2C for cloud for desktop applications for mobile applications for web applications for web server Kerberos OAuth recommendations SAML SAML 2.0 browser protocol SAP Cloud Platform Mobile Services SAP logon tickets and SAP Enterprise Portal user self-service X.509 client certificate Authorizations Availability... 0 B Backwards compatibility BAPI... 56, 133, 371 Base class Batch Batch handling Beautification , 17, 23 Behavior definition Behavior Definition Language (BDL) Behavior implementation data buffer class... 9 handler class saver class BEx Query Designer... 63, 11, 17 BOL BOPF object define define consumption view draft-enabled... 8 BOR , 138, 139, 250, 269, 371 Breakpoint , 809 Bring your own device (BYOD) Browser protocol Browser-based access Business Application Programming Interfaces BAPI Business Enablement Provisioning (BEP) , 190, 191, 207 Business object view Business process expert C C# CamelCase... 2, 53 Cascading Style Sheets Level 3 (CSS3) , 512 Catalog service CCMS , 726 CDS entity CDS view , 213, 36, 5, 6, 9, 579 ABAP analytical annotations architecture development modeled data source naming... 2 referenced data source SAP HANA SAP NetWeaver Central User Administration (CUA) Cleanup tasks Client server architecture Client-side paging... 9 Cloud... 2, 3, 779 hybrid... 3 private... 3 public... 3 Cloud Build Cloud connector Cloud Foundry Composite interface views Conceptual Schema Definition Language (CSDL) Consumer , 187 connection settings Consumption view contacts Controller, extend Conversion exit Core components Core Data Service (CDS) mapping naming convention... 1 Counting Creatable... 25, 255, 258 Create operation... 85, 39, 05 Cross-service navigation Cross-site request forgery (XSRF)... 70, 71 Cross-site scripting (XSS) CRUD... 68, 85, 116 CRUD-Q... 85, 278, 292, 51 CUD method create delete media resources update Current settings Custom exception class Custom field service implementation Custom Field and Logic app D Data buffer class... 9 Data Definition Language (DDL)... 0, 2, 92 Data Explorer Data model... 76, 250 after import create DDIC declarative EDMX import RFC/BOR , 275 Data model definition , 215, 25, 50 create model create project declarative model , 216 import DDIC import EDMX , 216 import RFC/BOR import via search help RFC/BOR interface service registration Data Model from File option Data provider class (DPC) , 218, 219, 20, 21, 26, 277, 382 base class , 28 interface Data provisioning Data store variety Database management systems DDIC , 162, 250, 266 beautification structure table Deep insert , 35 statement Degradation Deletable... 25, 258 DELETE Delete operation... 88, 399, 08 Delta query protocol Delta request log component

30 Index Index Delta support Deployment... 53, 155, 157 choosing cloud comparison costs embedded... 5, 157 hardware requirements hub... 55, 157 installation and configuration introduction maintenance mixed deployment options performance SAP Cloud Platform SAP Cloud Platform OData Provisioning SAP Fiori SAP S/HANA software requirements Desktop Destination finder BAdI Determinations Digital transformation... 33, 36 Dispatcher method Draft... 58, 83 E Eavesdropping Eclipse , 516, 521 Eclipse Neon edm\ Action Function EDMX Embedded deployment advantages disadvantages FES , 169 release consideration SAP Fiori Cloud use cases Enterprise application development Microsoft ASP.NET Microsoft Office Microsoft SharePoint Microsoft Visual C# Windows Desktop Enterprise Procurement Model (EPM) , 51, 58 Entity... 7 data model with media resource information Entity set... 75, 78, 86, 107 create custom , 586 Entity type... 75, 8 attributes create media supplier Error Error log , 727, 80, 806 backend level , 809 Event EXECUTE_ACTION method Expand extended Computer Aided Test Tool (ecatt) Extensibility in-app extensions mode pane side-by-side extensions Extension class , 277 code include project , 593, 596 Extension includes Extension point contact details second UI element total weight UI element F Facebook Facebook development create application create developer account namespace and app domains website URL Fact sheet app Feeds , 291 Field extensibility File system... 5 Filterable Filters... 90, 117 Flight example (read-only) Floorplan Manager (FPM) flpsandbox.html flpsandboxmockserver.html Formatting Framework template Free-text searches Function import create Function module G Gamification as innovation Gateway as a service (GWaaS) Gateway principle division of work ease of consumption openness timelessness user focus Gateway Productivity Accelerator (GWPA) Generic channel GenIL , 11, 229, 231, 371, 373 mapping with OData GET GET_ENTITY GET_ENTITYSET GETDETAIL method Git repository GW_CORE , 156, 17 H Handler class HAT local add-on Hello World HTML browsers HTML5/SAPUI , 55, 109, 199, 235, 506, 511, 512 button Eclipse minimum requirements function Hello World! manual creation project HTTP body method... 87, 328 status code HTTP(S) communication Hub deployment , 71 advantages , 161 development in SAP Business Suite development on the hub... 56, 159 disadvantages FES , 169 on the backend system SAP Fiori Cloud use case , 160 Hybrid app Hybrid App Toolkit (HAT) Hybrid application, create Hybrid container app Hypermedia link Hypertext Preprocessor (PHP) I idempotency In-app extensibility Incremental exclusion

31 Index Index Industry trends gamification Internet of Things InfoCube , 10 Infrastructure as a service (IaaS)... 3 Infrastructures, point-to-point solutions... Inlining Input mapping Installation and configuration... 51, 155 activation add-ons... 17, 181 Business Enablement Provisioning node OPU OData channel Quick Start Guide , 173 SAP Gateway alias SAP system alias settings smoke testing steps test settings trust relationship Integrated development environment (IDE) Integration Intelligent enterprise Internet Communication Framework (ICF) , 79, 821 Internet Communications Manager (ICM) Internet of Things iviews IW_BEP , 156, 163, 17, 386 IW_CBS IW_CNT IW_FND , 156, 17 IW_FNDGC IW_GIL , 231 SAP S/HANA IW_HDB , , 156 IW_PGW IW_SCS IW_SP, SAP S/HANA IW_SPI SAP S/HANA , 26 J Java Java SE JavaScript , 506 Jetty jquery JSON... 71, 116, 119, 130 K Kerberos , 756 L List Report app List Reporting template... 57, 66 M Managed scenario... 70, 85 Map to data source , 39 Mapping Media resource Merge/patch Metadata component Metadata extension (MDE)... 61, 78 Microsoft ASP.NET Microsoft Excel Microsoft Excel development PowerPivot Microsoft Office minimum requirements SharePoint Microsoft SharePoint development specify source Microsoft Visual C# development Microsoft Visual C# Windows Desktop development minimum requirements MIME type Mixed deployment, use cases Mobile application development , 611, 709 Model provider class (MPC) , , 26, 277, 379, 5 base class Modeled data sources (MDS)... 36, 5 Model-View-Controller (MVC) , 563 Modifying request Monitoring , 725 Multichannel, support Multidimensional expressions (MDX)... 63, 138, 10, 232 Multiorigin/multidestination Multiple origin composition (MOC) , 791 My Inbox app MySQL N Native application development development, pros and cons Navigation property , 37, 58 definition Neo Node extensibility Nondisruptiveness... 0 Nonmodifying request Northwind service (read only) Notification configuring pull , 798 push , 797 Notification center Notification Channel hub Notification provider development workflow items Nullable O OASIS OAuth , OData... 32,, 7, 57, 62, 69 access building blocks client library consumer custom entity set custom field service implementation data model design principles do and don't history introduction library mobile applications producer protocol... 73, 18 query options REST-based protocol SAP Business Suite on SAP HANA SAP Cloud Platform SAP Cloud Platform Backend service SAP Cloud Platform OData Provisioning SAP Enterprise Portal SAP Fiori SAP HANA SAP HANA XSA SAP Jam SAP S/HANA... 9, 113 SAP Solution Manager SAP solutions server vs. OData OData actions and functions annotation authorization checks cross-service navigation JSON format nonmodifying and modifying request query language roadmap vocabularies and annotations

32 Index Index OData.0 (Cont.) vs. OData OData channel activate SAP Gateway activate services authorization configuration configuration... 18, 185 SAP system alias settings for service development template OData channel development paradigm , 22 data provider class model provider class technical considerations OData client library OData exposure OData Model Editor... 76, 260, 550 activation graphical viewer schema-based code assist OData operation client-side paging... 9 counting create delete filtering and projecting formatting inlining query read single read sorting... 9 update OData programming model OData protocol GW_CORE OData sample service functionalities read/write read-only OData service... 7, 11 ABAP programming model for SAP Fiori annotations CDS via RDS OData service (Cont.) CDS views code-based implementation... 17, 19 create , 198, 201 custom entity set custom fields extensibility , 566, 567 external implementation evolution options redefine , 570 register and publish service replace runtime object SAP S/HANA structure... 7 test redefined service third-party ZGWSAMPLE_SRV OData Services Consumption and Integration (OSCI) OData software development kit (SDK) for PHP OData.publish:true , 373, 77 Offline scenario OLAP , 10 Olingo OData Client for JavaScript OLTP Online Database Connectivity Open standards... 2, OpenSearch , 212 description OpenUI Operations application log daily jobs periodic tasks troubleshooting tips Optimistic locking Order by Orion server P Pageable Paging Pair testing Parallelization Parameter BAPI return changing export import select options tables PATCH... 67, 87 Payload Trace tool , 815 Performance analysis Performance trace Performance Trace tool , 732, 792, 812, 81 Perl PHP development download links generate proxy class... 6 Platform as a service (PaaS)... 3 POST PowerPivot minimum requirements plug-in steps Principal entity Product availability matrix (PAM) ProductCollection , 289, 295 Project Astoria Projecting... 90, 37 Properties attribute flags navigation... 75, 80, 81, 8 PUT... 66, 87 Q QR code Query operation... 86, 386, 399 Query language analytical query options Query language (Cont.) filter expanded entities Query option $filter $inlinecount $orderby $select $skip $top Quick Start Guide installation steps R Read media resources operation Read Access Logging (RAL) $batch configuration Redefinition , 373, 13, 555, 556, 560 beautification GenIL... 1 Operational Data Provisioning (ODP)... 1 SAP BW... 1 SAP BW Easy Query... 16, 18 Service Provider Interface... 1, 25, 27 three steps URLs Reference data sources (RDS) , 235, 36, 50, 77 Referential constraint... 37, 381 Remote functional call (RFC)... 1, 56, 133, 138, 139, 160, 187, 250 function module wrapper function module Repeatable requests Repository object , 716, 717 transport... 71, 716 REST... 32,, 57, 65, 130 architecture command link

33 Index Index REST (Cont.) multiple representations of a resource principles stateless communication uniform interface URI Return on investment... 0 RFC/BOR generation create... 39, 05 data model definition delete , 08 process flow query service implementation service maintenance single read , 02 stub creation update , 07 RFC/BOR Generator RFC/BOR interface... 37, 399 Role administrator developer user , 187 Routing custom Runtime artifacts , 280 component S SAML (Security Assertion Markup Language) , 752 SAML 2.0 browser protocol SAP Add-On Installation Tool SAP API Business Hub... 5 SAP API Management , 793 SAP Business Process Management (SAP BPM) , 11 SAP Business Suite... 5, 156, 157, 511 connecting to SAP Gateway notifications SAP Business Suite on SAP HANA... 62, 111 SAP Business Suite tier, components SAP Business Warehouse (SAP BW)... 63, 111, 138, 10 SAP Business Workflow , 137, 138, 10, 12 MDX SAP BW Easy Query , 11, 16 activate service redefine regenerate service... 2 SAP BW on SAP HANA SAP Cloud Platform , 52, 763, 765, 780, 781 connecting to SAP Gateway documentation SDK for Android SDK for ios Web IDE Web IDE full-stack SAP Cloud Platform API Management SAP Cloud Platform Backend service SAP Cloud Platform cockpit , 53 SAP Cloud Platform Integration SAP Cloud Platform Mobile Services... 60, 128, 616 authentication SAP Cloud Platform OData Provisioning... 56, 11, 129, 157, 163, 782 use cases SAP Cloud Platform Portal... 59, 167 SAP Cloud Platform SDK for service development SAP Cloud Platform, ABAP environment... 58, 35, 8 SAP Community SAP Customer Relationship Management (SAP CRM)... 88, 11 SAP DemoContent SAP Developer Center SAP Enterprise Portal... 59, 110, 750 SAP ERP Human Capital Management (SAP ERP HCM) SAP ERP, SAP S/HANA SAP Fiori... 9, 58, 108, 128, 137, 12, 227, 505, 507 apps reference library , 59 architecture create reference app deployment designers developers extensibility manage products mockdata reference apps , 58, 565 SAP Web IDE service Smart Business cockpit SAP Fiori Cloud , 167 road map SAP Cloud Platform OData Provisioning , 169 SAP Gateway SAP Fiori elements... 1, 15, 235, 363, 56 architecture... 1 generate object page preview app SAP Fiori Frontend Server (FES) SAP Fiori launchpad , 508 notifications , 799, 803 SAP Fiori Master-detail application template SAP Fiori Worklist application SAP Gateway... 31, 155, 511 ABAP programming model for SAP Fiori add-on structure advanced topics Analytics Service Generator application creation workflow... 6 application requirements... 7 architecture , 127 Atom client , 706 configuration connecting to SAP Business Suite SAP Gateway (Cont.) consumer deployment extending OData service future developments installation and configuration , 170, 180 installation and deployment... 50, 51 integration integration and deployment integration with other technologies introduction... 21, 31 lifecycle management , 71 modern business applications... monitoring OData OData features open standard... operations , 72 prerequisites related products REST SAP BW integration SAP NetWeaver SAP S/HANA... 9, 113 security service deployment service enablement solution lifecycle statistics , 811, 813 testing tier toolset versioning SAP Gateway client test cases SAP Gateway components GW_CORE IW_BEP IW_FND... 52, 53 IW_FNDGC IW_GIL IW_HDB IW_PGW IW_SCS

34 Index Index SAP Gateway components (Cont.) IW_SPI SAP_GWFND SAP Gateway Developer Center SAP GUI... 37, 38 SAP HANA... 61, 62, 110, 1, 151 architecture SAP HANA Live SAP HANA XSA SAP Hybrid App Toolkit companion connector SAP Interactive Forms by Adobe SAP Jam SAP logon ticket SAP Mobile Platform 60, 61, 110, 796, 797 SAP NetWeaver SAP NetWeaver SAP NetWeaver SAP NetWeaver SAP NetWeaver , 155, 156, 159, 185 SAP NetWeaver SAP Partner Finder SAP Process Integration SAP Process Orchestration SAP Quick Sizer SAP S/HANA... 9, 62, 111, 113, 199, 235, 373 cloud key user extensibility cloud-based deployment extensibility notifications OData on-premise SAP Gateway SAP Service Marketplace... 50, 172 SAP Single Sign-On SAP Solution Manager , 726, 729, 739 SAP StreamWork SAP SuccessFactors SAP test drive SAP Web Dispatcher SAP Web IDE... 16, 511, 516, 525 activate full-stack connect to SAP Gateway , 538 creating a project developing SAPUI5 applications environment for SAP HANA full-stack , 530, 629 installation local installation for SAP Gateway template customization welcome screen SAP Web IDE personal edition (on-premise) SAP_GWFND , 136, 156, 157, 163, 17, 386 SAPUI5... 1, 505, 507, 512, 525, 533, 612 architecture... 1 creation via the Eclipse development environment development, creating an application extending applications extensibility framework platforms hiding UI elements HTML5/SAPUI installation JavaScript file operations SAP Web IDE Saver class Search help service generation service implementation Searchable secure sockets layer/transport layer security (SSL/TLS) Security cross-site request forgery cross-site scripting input validation , 739 network and communication transport protection Security (Cont.) virus scan interface... 7 Semantic annotations Server-side caching Service Adaptation Definition Language (SADL)... 7 Service binding... 37, 85, 90 Service Builder... 76, 133, 10, 16, 150, 176, 189, 197, 205, 269, 371, 77, 551, 58 add annotations annotations catalog service create project... 28, 29 error log functionality mapping dialog objective project , 27 project tree service maintenance service registration Service Catalog... 53, 633 Service creation , 200, 201, 20 data model definition , 215 incremental process overview service implementation , 220 service maintenance , 226 steps supporting tools waterfall approach Service definition , 85, 89 Service deployment activate and maintain service transaction OData Service development , 198, 202, 221, 25 data model definition example navigation property service implementation service maintenance service registration , 285 stub generation Service document... 7, 77, 78, 22 Service Document Identifier Service generation , 202, 371, 372 ABAP programming model for SAP Fiori add-ons CDS views , 37 OData.publish:true redefinition , 372, 373, 13 referenced data sources RFC/BOR Generator , 37 Search Help , 10 Service implementation , 220, 25 CDS view... 6 RFC generation , 22, 225 RFC/BOR interface , 399 service development Service maintenance , 203, 218, 226, 25, 28 RFC/BOR interface Service Maintenance node Service metadata document... 7, 77, 82 Service provider Service Provider Infrastructure Service Provider Interface , 371, 25 activate service create new project system alias Service redefinition , 227 analytic queries data sources GenIL main process steps Service Provider Interface Service registration , 218, 220, 276, 280 RFC/BOR interface Service URL... 5 Service validation tool Service with SAP Annotations Service with vocabulary-based annotations SharePoint, steps Side-by-side extensibility

35 Index Index Sina Weibo... 61, 661 Sina Weibo development create user account PHP SDK Single read... 86, 296, 299, 35 operation , 02 Single sign-on Skip token Social media development Facebook PHP Sina Weibo strategy Twitter Soft state soft state-based query result cache Software as a service (SaaS)... 3 Software development kit (SDK) Sortable... 25, 255 Sorting... 9 Source URI SQL view... 2, 3 SQRC Statelessness Stub creation Subject matter experts... 3 Subscribable Subscription SupplierCollection Supportability System alias transport T Technical model name , 237 Technical service name , 237 Testing best practices client application services Throttling Tombstones Total cost of ownership... 0 Tracing Transaction /IWBEP/ERROR_LOG , 807 /IWFND/APPS_LOG /IWFND/ERROR_LOG /IWFND/GW_CLIENT , 288 /IWFND/MAINT_SERVICE , 226, 236, 28, 77, 71, 718, 720, 822 /IWFND/MAINT_SERVICES /IWFND/STATS /IWFND/TRACES , 81 /WFND/STATS RSRT... 22, 25 SAINT SE , 567 SE SE SE SEGW , 176, 179, 189, 197, 205, 235, 27, 27, 556, 560 SICF , 183 SM SPRO , 793 ST Transactional app Twitter Twitter development create developer account OData tweet SDKs TwitterOAuth-library U UI element add second to extension point extension point hiding Unmanaged scenario Updatable... 25, 255, 258 Update operation... 87, 32, 397, 07 Upgrade URI User interface (UI) agility appeal... 3 availability User interface (UI) (Cont.) business orientation component innovation integration intuitive maintainability nondisruptiveness... 0 reduced TCO requirements security User management User mapping V Validations Versioning , 719 View create Virtual data model (VDM) Visual Studio Visual Studio, Microsoft Visual C# Windows Desktop W Web application development Web services... 1 Web view Workspace... 5 X X.509 client certificate... 76, 751 XAMPP Xcode... 35, 615, 619 XML... 68, 130, 728 XSRF token-based protection

36 First-hand knowledge. Carsten Bönnen works for SAP SE within the strategic Product Management for SAP Cloud Platform. In 2001, he received his MA in computer linguistics and artificial intelligence in Germany and started working at SAP. Initially a Java developer and trainer, he soon became a consultant and led strategic projects in the field of enterprise portals. Volker Drees studied electrical engineering at Fachhochschule in Wiesbaden, Germany, and holds a degree in communications engineering (Nachrichtentechnik). He began his SAP career in 1998 in the consulting department and currently works at SAP SE as a product expert for SAP Gateway and the ABAP programming model for SAP Fiori in the Products & Innovation, Core Platform Division. André Fischer is an SAP Technology Ambassador and has worked in product management for SAP Gateway since the launch of the product in Over the past 10 years at SAP, André has focused on the interoperability of SAP NetWeaver and Microsoft technologies, SAP Enterprise Search, single sign-on (SSO), and SAP Gateway. Bönnen, Drees, Fischer, Heinz, Strothmann SAP Gateway and OData 81 Pages, 2019, $89.95 ISBN Ludwig Heinz is the CIO of the Europe-wide acting recycling company, Theo Steil GmbH. He studied business informatics at the University of Applied Sciences FHDW in Bergisch Gladbach, Germany, and has worked as an ABAP and mobile developer at itelligence AG in Cologne from 2006 till 201. Karsten Strothmann is a Product Manager and evangelist for SAP Cloud Platform at SAP SE in Walldorf, Germany. He has more than 20 years of experience in the software industry, 18 of which at SAP. We hope you have enjoyed this reading sample. You may recommend or pass it on to others, but only in its entirety, including all pages. This reading sample and all its parts are protected by copyright law. All usage and exploitation rights are reserved by the author and the publisher.