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/4HANA. You’ll begin your installation with a quick start gui- de, 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 841 Pages, 2019, $89.95 ISBN 978-1-4932-1755-7 www.sap-press.com/4724 Chapter 4 Deployment Options, Installation, and Configuration 4 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 installa- tion 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 instal- lation and configuration process and look at selected steps in detail. The chapter closes by discussing the SAP Gateway best practices that are rele- vant during installation and configuration. 4.1 Introduction to SAP Gateway Deployment There are basically two ways to look at the SAP Gateway deployment Deployment options options: from the perspective of SAP Gateway itself and from the perspec- tive of SAP Fiori and SAP S/4HANA, where SAP Gateway is part of the appli- cation 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. In SAP Gateway, there are major differences with respect to deployment, depending on the underlying SAP NetWeaver version. Since SAP Net- Weaver 7.40, the add-on structure has been streamlined and further optimized for the OData channel, as compared to prior SAP NetWeaver ver- sions. 155 4 Deployment Options, Installation, and Configuration 4.1 Introduction to SAP Gateway Deployment Prior to SAP Basic SAP Gateway functionalities, if running on releases prior to 7.40, are Name Type Version Notes NetWeaver 7.40 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_ IW_FNDGC ABAP 100 Optional. Only to be installed if generic FND add-ons be deployed on the server. IW_BEP has to be deployed on the channel services (outdated and not recom- mended) are still used. SAP Business Suite systems for backend enablement (see Table 4.1). 4 Table 4.2 Software Components and Optional Add-Ons for SAP Gateway in SAP Core Components Backend Enablement NetWeaver 7.40 (Cont.) Version 7.31 and Earlier GW_CORE IW_BEP IW_FND Deployment As of Version 7.40 SAP_GWFND SAP_GWFND The term deployment—in this case for versions as of SAP NetWeaver Table 4.1 SAP NetWeaver Version and Required SAP Gateway Add-Ons 7.40—describes where SAP Gateway functionality resides because there is no actual deployment needed anymore. Since SAP Gateway components From SAP As of SAP NetWeaver 7.40 and higher, the SAP_GWFND software compo- come as part of SAP NetWeaver, it’s more of a configuration. We stick to NetWeaver 7.40 nent is installed as part of the SAP NetWeaver 7.40 standard and includes the term deployment here for simplicity reasons and because it has the functional scope of IW_BEP, GW_CORE, IW_FND, and IW_HDB. As a become a set expression. result, any SAP Business Suite system as of SAP Enhancement Package (EHP) 7 or any SAP S/4HANA 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 Cloud Platform, as described here: Table 4.2 shows the software components and optional add-ons of SAP Gateway with respect to SAP NetWeaver 7.40. ½ Embedded deployment In previous versions SAP NetWeaver 7.40, SAP Gateway IW_FND and Name Type Version Notes GW_CORE core components were deployed in the SAP Business Suite SAP_GWFND ABAP 7.40 Installed as standard in systems based on system. Alternatively, the SAP backend system is based on release 7.40 or SAP NetWeaver 7.40 and contains the fol- higher, where the SAP_GWFND software component is part of the SAP lowing: NetWeaver standard and just needs to be configured properly. ½ Runtime components ½ Hub deployment ½ Metadata component In versions before SAP NetWeaver 7.40, SAP Gateway IW_FND and GW_ ½ Shared services (e.g., monitoring) CORE core components are deployed in an SAP Gateway hub system. ½ OData libraries Alternatively, a 7.40 or higher system is used as the hub system where ½ Business enablement provisioning (BEP) the SAP_GWFND software component is part of the standard and just ½ Business content adapter for SAP Gate- needs to be configured properly. way with SAP HANA to enable exposure of SAP HANA views ½ SAP Cloud Platform deployment Hub architecture SAP Cloud Platform OData Provisioning offers a service in SAP Cloud Plat- using SAP Cloud Table 4.2 Software Components and Optional Add-Ons for SAP Gateway in SAP Platform form that provides the SAP Gateway Hub capabilities for SAP Business NetWeaver 7.40 156 157 4 Deployment Options, Installation, and Configuration 4.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/4HANA backend systems.) This means (where either IW_BEP is deployed for systems prior to SAP NetWeaver 7.40, 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.40) and is then published on the SAP Gateway server. monitoring, upgrading, and system administration. The following are the main use cases for this kind of deployment: Deployment 4 use cases The hub deployment can be further split up into two suboptions. Each of ½ Scenarios where development takes place in the SAP Business Suite or these options has advantages and disadvantages. In this section, we’ll dis- SAP S/4HANA system cuss all four, compare them, and also discuss the scenario where you might ½ Scenarios where a developer needs to leverage native interfaces, Data use a mixed deployment that consists of both options. Dictionary (DDIC) structures, or Core Data Services (CDS) in the SAP Busi- ness Suite or SAP S/4HANA systems 4.1.1 Hub Deployment with Development in the SAP Backend System ½ SAP Fiori for SAP Business Suite scenarios (Section 4.1.6 for more details) In the case of hub deployment with development in the SAP Business Suite The hub deployment with development in the SAP backend offers the fol- Advantages or SAP S/4HANA system (Figure 4.1), the SAP Gateway server functionalities lowing advantages: are only used on a single dedicated server—the hub system. ½ Support for routing and composition of multiple systems. ½ Single point of access to multiple SAP backend systems. Consumers ½ More flexibility. Hub systems can be based on a newer release (SAP Net- HTTPS Weaver 7.50 up to SAP NetWeaver 7.52) than any of the connected SAP SAP Gateway Hub backend systems that supports additional authentication options (Ker- OData Runtime beros, Security Assertion Markup Language [SAML] browser protocol) GW_CORE and IW_FND or and can be updated more frequently without too much overhead (ser- SAP_GWFND vice windows, regression tests). The only disadvantages to this method are the following: Disadvantages RFC SAP Backend System ½ An additional server is needed for SAP Gateway. 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. 4.1.2 Hub Deployment with Development on the Hub RFC BOR BW WF For hub deployment with development on the hub (Figure 4.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 develop- Figure 4.1 Hub Deployment with Development in the SAP Backend System ment 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 158 159 4 Deployment Options, Installation, and Configuration 4.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.40). 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/4HANA systems, this deployment ½ Proof of concept (POC) with SAP Gateway (no changes to existing infra- option is of no interest. structure required). 4 The following are the disadvantages of hub deployment with development Disadvantages Consumers on the hub compared to development on the backend: HTTPS ½ No direct access to native interfaces, DDIC structures, or CDS in the SAP SAP Gateway Hub Business Suite or SAP S/4HANA systems.