Config Guide Gw

SAP NetWeaver Gateway Configuration GuidePDF download from SAP Help Portal:http://help.sap.com/saphelp_gateway20sp08/helpdata/en/4c/a670b0e36c4c01ae2b9a042056f9dc/frameset.htm

Created on April 22, 2014

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

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

2014 SAP AG or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AGand its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided bySAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not beliable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the expresswarranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and otherSAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

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

Page 1 of 90

Table of content1 SAP NetWeaver Gateway Configuration Guide1.1 Basic Configuration Settings1.1.1 Profile Parameters1.1.2 ICF Services1.1.3 Changing Password for Initial Logon1.1.4 Language Settings1.2 OData Channel Configuration1.2.1 User, Developer, and Administrator Authorizations1.2.1.1 Creating and Assigning Roles1.2.2 Connection Settings on the SAP NetWeaver Gateway Hub System1.2.2.1 Connection Settings: SAP NetWeaver Gateway to Consumer1.2.2.1.1 Creating a bgRFC Destination for Outbound Queues1.2.2.1.2 Registering the bgRFC Destination for the Outbound Queue1.2.2.1.3 Creating the bgRFC Supervisor Destination1.2.2.2 Connection Settings: SAP NetWeaver Gateway to SAP Systems1.2.2.2.1 Creating a Type 3 RFC Destination on SAP NetWeaver Gateway Host1.2.2.2.2 Defining Trust between the SAP NetWeaver Gateway Host and Your S1.2.2.2.3 Configuring SAP System to Accept Assertion Tickets from SAP NetW1.2.2.2.4 Configuring the SAP NetWeaver Gateway Host to Accept Assertion T1.2.2.2.5 Creating the SAP System Alias for Applications1.2.3 Activating SAP NetWeaver Gateway1.2.4 Settings for OData Channel Service Development on Backend System1.2.4.1 Displaying Models and Services1.2.4.2 Define Parallelization of Batch Queries1.2.5 Settings for OData Channel Service Development on the Hub System1.2.5.1 Assigning SAP System Alias to OData Service1.2.5.2 Multiple Origin Composition1.2.5.3 Dynamic System Alias Calculation Via /IWFND/ES_MGW_DEST_FINDER1.2.6 Connection Settings on the Backend System1.2.6.1 Settings for Idempotent Services1.2.6.2 Defining a Remote Function Call to SAP NetWeaver Gateway1.2.6.3 Connection Settings to SAP NetWeaver Gateway1.2.6.4 Configure the bgRFC Supervisor Destination1.2.6.5 Monitoring bgRFC Queues1.3 Business Enablement Provisioning (IW_BEP) Configuration1.4 Configuration Settings for SAP NetWeaver Gateway Supported Scena1.4.1 Configuration Settings for OData Channel Scenarios1.4.1.1 Configuring Workflow for SAP NetWeaver Gateway1.4.1.1.1 Creating an Administrator Role for Workflow1.4.1.1.2 Customizing SAP NetWeaver Gateway Workflow1.4.1.1.2.1 Configuring Workflow Notifications1.4.1.1.2.1.1 Creating a Type G RFC Destination1.4.1.1.2.1.2 Configuring User Authorizations for Push Notifications1.4.1.1.2.1.3 Running Scheduled Reports1.4.1.1.2.2 Workflow Settings1.4.1.2 Configuring Business Process Content Services1.4.1.2.1 Configuring Services for Deployment Scenario 11.4.1.2.1.1 Connecting Business Process Content and Business Suite Systems1.4.1.2.1.1.1 Creating a Software Version for Provider System1.4.1.2.1.1.2 Mapping the Software Version and Technical Model1.4.1.2.1.2 Creating a System Alias1.4.1.2.1.3 Activating the Process Service1.4.1.2.1.4 Registering Process Context Service for Deployment Scenario 11.4.1.2.1.5 Activating the Process Context Service1.4.1.2.2 Configuring Services for Deployment Scenario 21.4.1.2.2.1 Connecting Business Process Content and Business Suite Systems1.4.1.2.2.1.1 Creating a Software Version for Provider System1.4.1.2.2.1.2 Mapping the Software Version and Technical Model1.4.1.2.2.2 Creating a System Alias for SAP Business Suite System1.4.1.2.2.3 Connecting SAP NetWeaver Gateway and Business Process Content


Page 2 of 90

1.4.1.2.2.4 Creating a System Alias for Business Process Content System1.4.1.2.2.5 Activating the Process Service1.4.1.2.2.6 Registering Process Context Service for Deployment Scenario 21.4.1.2.2.7 Activating the Process Context Service1.4.1.2.3 User Authorizations for SAP Business Workflow Systems1.4.1.3 Configuring the Task Gateway Service1.5 Former Development1.5.1 Configurations for ERP on SAP NetWeaver Gateway1.5.1.1 Role Templates for ERP Scenarios1.5.1.2 Configurations on SAP NetWeaver Gateway for SAP ERP1.5.1.3 Settings for Time Management Application - OData Channel1.5.1.3.1 Configurations on the SAP NetWeaver Gateway for Time Management1.5.1.3.2 Configurations on the SAP ERP System (Provider System) for Time1.5.1.3.3 Configurations on the SAP NetWeaver Gateway System (Consumer Sys1.5.1.4 Configurations for ERP Customer- OData Channel1.5.1.4.1 Configurations for ERP Customer on the SAP NetWeaver Gateway Sys1.5.1.4.2 Configurations for ERP Customer on the SAP ERP System (Provider1.5.1.4.3 Configurations for ERP Customer on the SAP NetWeaver Gateway Sys1.5.1.5 Configurations for ERP Sales Documents on the SAP NetWeaver Gate1.5.2 SOA Management Configurations on SAP ERP System1.5.2.1 Importing a Profile using a XML Template1.5.2.2 Profile Management1.5.2.3 Importing Endpoints Template using Business Scenario Configurati1.5.2.4 Creating Endpoints using a Business Scenario1.5.2.5 Verifying the Endpoints Created1.5.2.6 Obtaining the External Key of the Provider System1.5.3 SOA Management Configurations on the SAP NetWeaver Gateway Syste1.5.3.1 Importing a Profile File1.5.3.2 Creating a System Connection to Provider System1.5.3.3 User Account Management1.5.3.4 Importing a Business Scenario Configuration XML1.5.3.5 Configuring Service Groups using a Business Scenario1.5.3.6 Verifying Logical Ports1.5.4 Generic Channel Configuration1.5.4.1 Defining Settings for Idempotent Services1.5.4.2 Creating an RFC Destination for the WSIL Service1.5.4.3 Assigning the System Alias Pointing to the SAP System1.5.4.4 Checking SAP System Aliases1.5.4.5 Subscription Settings1.5.5 Code List1.5.5.1 Code List Usage1.5.5.2 Customizing the SAP NetWeaver Gateway System for Code List1.5.5.3 Code List Cache Cleanup1.5.6 Configuration Settings for Generic Channel Scenarios1.5.6.1 Settings for Customer Relationship Management on SAP NetWeaver G1.5.6.1.1 Configuring GSDO to Connect to the SAP CRM System1.5.6.1.1.1 SOA Management Configurations on SAP CRM System1.5.6.1.1.1.1 Creating a New Profile in the Provider System1.5.6.1.1.1.2 Configuring Provider Systems1.5.6.1.1.2 SOA Management Configurations on SAP NetWeaver Gateway System1.5.6.1.1.2.1 Creating a Provider System in the Consumer System1.5.6.1.1.2.2 User Account Management1.5.6.2 Settings for Reporting Management1.5.6.2.1 Settings for Reporting Management on SAP NetWeaver Gateway1.5.6.2.2 Configuring Subscriptions for Report Results1.5.6.2.3 Settings for Reporting Administration1.5.6.2.3.1 Managing Source Systems, Report Types and Formats1.5.6.2.3.2 Managing Reports and their Properties1.5.6.2.3.2.1 Configuring a New Report1.5.6.2.3.2.2 Configuring Report Parameters1.5.6.2.3.2.3 Configuring Multiple Values for a Parameter1.5.6.2.3.2.4 Configuring Delivery Formats for a Report


Page 3 of 90

1.5.6.2.3.2.5 Specifying Roles for a Report1.5.6.2.3.2.6 Report Scheduling1.5.6.2.3.3 Managing Categories1.5.6.2.3.4 Managing Context Variables1.5.6.2.3.5 Configuring System Time Points1.5.6.2.3.6 Managing System Time points and Data Change Events1.5.6.3 Settings for Human Capital Management for SAP NetWeaver Gateway1.5.6.3.1 Settings for Time Management1.5.6.3.1.1 Settings for Time Management on SAP NetWeaver Gateway1.5.6.3.1.2 Configurations on the SAP ERP System (Provider System) for Time1.5.6.3.1.3 Configurations on the SAP NetWeaver Gateway System (Consumer Sys1.5.6.3.2 Settings for Leave Management1.5.6.3.2.1 Configuring SAP NetWeaver Gateway System for Leave Management1.5.6.3.2.2 Configurations on the SAP ERP System (Provider System) for Leave1.5.6.3.2.3 Configurations on the SAP NetWeaver Gateway System (Consumer Sys1.5.6.3.3 Settings for User Profile1.5.6.4 Settings for Code List in the SAP NetWeaver Gateway System1.5.6.4.1 Creating a GSDO Type1.5.6.4.2 Creating a GSDO Group1.5.6.4.3 Assigning System Alias1.5.6.4.4 Maintaining Code Type1.5.6.4.5 Code List Usage1.5.6.4.6 Code List Cache Cleanup1.5.6.4.7 Configuring SAP NetWeaver Gateway System and SAP ERP System-ESA1.5.6.4.7.1 Configurations on the SAP ERP System (Provider System) for Code1.5.6.4.7.2 Configurations on the SAP NetWeaver Gateway System (Consumer Sys


Page 4 of 90

1 SAP NetWeaver Gateway Configuration Guide Once you have installed the SAP NetWeaver Gateway components, you must configure your system to allow the consumer servers applications to retrieve thedata requested by users.The SAP NetWeaver Gateway Configuration Guide contains the steps for customizing settings for SAP NetWeaver Gateway and describes systemconfiguration activities.The sequence of mandatory and optional configuration tasks is as follows and depends on your use case.

1. Basic configuration (mandatory)2. OData Channel Configuration3. Configuration Settings for content scenarios (optional)

Implementation GuideThe SAP NetWeaver Gateway specific configuration tasks are included in the SAP NetWeaver Gateway Implementation Guide (IMG) which is available in thesystem: In your SAP NetWeaver Gateway hub system (IW_FND) go to transaction SPRO, open the SAP Reference IMG and navigate to: SAP NetWeaver Gateway . In your backend system (IW_BEP) go to transaction SPRO, open the SAP Reference IMG and navigate to: SAP NetWeaver Gateway Service

Enablement .For all steps in the IMG there is always consumer-independent documentation available. If you want to see more information, select the Display icon beforeexecuting each step.

NoteIf you have software components GW_CORE 190 and IW_FND 240 installed in your system, the IMG tree will only offer the activities for OData Channel.The same applies if you use SAP NetWeaver Gateway in SAP NetWeaver 7.40 (software component SAP_GWFND).For more information, see Deployment Options.

RecommendationWe strongly recommend using the OData Channel (ODC) programming paradigm for all SAP NetWeaver Gateway development.As of SAP NetWeaver Gateway 2.0 Support Package 05, you are strongly recommended to use the Service Builder (transaction SEGW) for your ODatadesign-time development . For more information, see SAP NetWeaver Gateway Service Builder.Depending on whether you want to develop SAP NetWeaver Gateway content in an SAP Business Suite backend system or in an SAP NetWeaver Gatewayhub system, you can choose between embedded deployment or central hub deployment. For more information, see Embedded Versus Hub Deployment andDeployment Options.

As such, several sections in the Implementation Guide (IMG) are merely available for reference and maintenance purposes.In the backend system this is the section in the SAP Reference IMG under SAP NetWeaver Gateway Service Enablement Generic Channel .In the SAP NetWeaver Gateway hub system these are the sections in the SAP Reference IMG under SAP NetWeaver Gateway FormerDevelopment .

Additional Software ComponentsDepending on the additional SAP NetWeaver Gateway components you implement, further component-specific configuration steps are required:

Business Enablement Provisioning (IW_BEP) See Connection Settings for OData Channel and BEP and Backend Event Publisher(BEP) Configuration.The IW_BEP specific configuration tasks are included in the Gateway ServiceEnablement Implementation Guide (IMG) which is available in the system: Intransaction SPRO open the SAP Reference IMG and navigate to: SAP NetWeaver Gateway Service Enablement Backend OData Channel Connection Settings to

SAP NetWeaver Gateway and Backend Event Publisher Administration .Screen Scraping (IW_SCS) For Screen Scraping you only need to configure roles based on certain authorization

templates. The templates specify the authorizations for content that can be accessed bythe users and activities for developers. For more information, see Setting Up User andAdministrator Authorizations.

SAP NetWeaver Gateway with HANA (IW_HDB) If you want to install the SAP NetWeaver Gateway with HANA component (IW_HDB),this requires SAP NetWeaver 7.02 SPS09 comprising an ABAP Database Connectivity(ADBC) installation. ADBC is an object-based ABAP API for programming relationaldatabase accesses. It follows the Java Database Connectivity (JDBC) diction in its classand model structure.

Workflow You can find more information about the Workflow-related configuration activities inConfiguring Workflow for SAP NetWeaver Gateway. In addition, the relevant IMGactivities are available in the Implementation Guide in the backend system: Intransaction SPRO open the SAP Reference IMG and navigate to: SAP NetWeaver Gateway Service Enablement Content Workflow Settings .

Business Process Enablement For the special services provided within Business Process Enablement, such as ProcessService and Process Context Service, the relevant IMG activities are available in theImplementation Guide in the backend system. In transaction SPRO open the SAPReference IMG and navigate to: SAP NetWeaver Gateway Service Enablement

Content Business Process Enablement .


Page 5 of 90

Consumer SettingsFor information on configuration settings which need to be carried out for the different consumer scenarios and applications, see Configuration Settings for SAPNetWeaver Gateway Supported Scenarios.

1.1 Basic Configuration Settings After having installed the SAP NetWeaver Gateway software components you need to carry out several configuration steps.Before starting with the configuration for SAP NetWeaver Gateway itself, you need to collect some information about the SAP NetWeaver Gateway host.

Required Information Description ExampleFully Qualified Domain Name (FQDN) Name of the SAP NetWeaver Application Server ABAP

(AS ABAP) system or the load balancing device.server.domain.com

Administrator credentials Login information of the administrator of the SAPNetWeaver AS ABAP to install and maintain the system

SAP administrator

HTTP/HTTPS ports HTTP and HTTPS port numbers of the central instance ofthe AS ABAP

80000 for HTTP and 80001 for HTTPS

SAP system For each SAP system to which you want to connect theSAP NetWeaver Gateway server, you need the followinginformation:

System ID, system numberServer nameHTTP / HTTPS portAdministrator credentials

In addition, several settings are important for smooth operations:Profile ParametersICF ServicesInitial LogonLanguage Settings

1.1.1 Profile Parameters In both your SAP system and in the SAP NetWeaver Gateway system you need to set the following profile parameters to certain values:

Profile Parameter Valuelogin/accept_sso2_ticket 1

login/create_sso2_ticket 2

You maintain these profile parameters via transaction RZ10.

More InformationFor information on profile parameters and profile parameter maintenance, see Profile Parameters for Logon and Password (Login Parameters) and Changing andSwitching Profile Parameters.

1.1.2 ICF Services Once you have installed the Application Server ABAP (AS ABAP) all Internet Communication Framework (ICF) services are available in an inactive state forsecurity reasons. After the installation you have to decide which services must be activated for the applications you want to use.

CautionActivated ICF services represent a security risk because they can be accessed directly by the HTTP protocol from the Internet. You therefore need to usesuitable methods for restricting access, for example, only permitting access to the ICF service for users with the appropriate authorizations.

Since multiple services can be executed when you call a URL, all service nodes must be activated in the SICF tree. The URL path is mapped in ICF subnodes(services). For example, if you want to activate the services for URL /sap/public/icman, you have to activate the service tree default_host in transactionSICF. Then you have to activate services sap, public and icman separately.You activate an ICF service as follows:

1. Select the required ICF service in the ICF tree in transaction SICF.2. Activate the ICF service in one of the following ways:

Using menu option Service/Host Activate .Using the context menu and choosing Activate Service .

You can either activate only a selected service node ( Yes ), or the selected service node including all the subservices maintained for it in SICF ( Yes with treeicon):


Page 6 of 90

( Example ) For SAP NetWeaver Gateway you need to activate the following services:

/sap/public/opuNote that /sap/public/opu/resources is needed for loading resources, such as images in the MIME repository. For example, the generic player getsa service document which contains links to images which the player should display for a Sales Order. Then the generic player downloads the image viaURL from the MIME Repository; for example, http://.../sap/opu/resources/pic1.png./sap/opu/odata with its sub-nodes.This is the standard mode for all new applications. When creating a service a new node is created automatically./sap/opu/sdata with the following sub-nodes:

/sap/opu/sdata/iwcnt/sap/opu/sdata/iwfnd/sap/opu/sdata/sap

This is the node used for existing applications, it is called Compatibility Mode for SP02 . If you use Web service based scenarios, that is, if content is consumed which is provided via Web services, then you also need to activate the following nodes onyour target system:

/sap/bc/srt/xip/sap/sap/bc/webdynpro/sap/saml2/sap/public/bc/sap/public/bc/ur/sap/public/mysssocnt

NoteIf the default_host node is inactive in transaction SICF, the HTTP requests could result in an ABAP runtime error RAISE_EXCEPTION with the followingshort text:Exception condition "HOST_INACTIVE" triggered.If a service is inactive in transaction SICF, an error text appears when you try to access the service.

You can also activate services from the SAP Implementation Guide (IMG). In transaction SPRO, choose Display SAP Reference IMG . The path in theImplementation Guide for SAP NetWeaver is: Application Server Internet Communication Framework Activate HTTP Services or Activate Services inInstallation .Note that the system performs a check against the authorization object S_ICF_ADM when an ICF node is created.

Standard ModeThis standard mode refers to the ICF node /sap/opu/odata. This node is available for OData Channel based applications. When creating a service a newnode is created automatically.

NoteThe standard mode is the default for all new applications. All new development will be done on this mode. New functions and features will beavailable for this mode.

The request handler for this node is /IWFND/CL_SODATA_HTTP_HANDLER.The following list consists of the differences of the standard mode as opposed to the compatibility mode for SP02:

XSRF protectionSee also Cross-Site Request Forgery ProtectionContent-Type required for Put/Post requestAn unsupported media type error is thrown if Content-Type is not set for Put/Post requests. Set parameter: Content-Type=application/xml XSRF Security Token Security Session Id$format parameter$format=xml leads to an error except for service document. Do not use it for all requests except for those to get service document .Null values in Put/Post RequestEmpty property elements (for example, ) are not allowed anymore. Nullable needs to be set properly, and besides that, if an entry with a null stringis to be created set m:null="true", for example, .Null values in the response of a Get/Put requestIntial values for date time fields in combination with nullable properties are rendered as .Values of keys in Post request in case of server generated keysIf the keys are generated on the server the values need to be filled in the post request anyway. m:null is not allowed.Rendering of key predicatesSee http://www.odata.org/developers/protocols/overview#AbstractTypeSystem.Key propertiesSending properties that are not key fields in an URI is not longer possible.String parametersQuotation marks enclosing string parameters (for example, search string) are now required and removed.Parameters for function importsParametrize with literals, for example, datetime.... See also http://www.odata.org/developers/protocols/overview#AbstractTypeSystem.


Page 7 of 90

Inverted commas in URIInverted commas in URI, for example, $filter=name eq 'Jame''s shop' can now be properly escaped by an inverted comma.OData error responseThe OData error response has been enhanced. See http://www.odata.org/media/6655/%5Bmc-apdsu%5D%5B1%5D.htm#_Toc246716641.The code field is now either build from the leading error message of the message container or build from the text id of the exception.The structured inner error section is available showing Extended Passport (EPP) transaction ID. All messages of the message container and the additionallyprovided error details are shown in a special format (micro format).ThingsThe workspace for Things, element , is no longer available.Service maintenanceThe service maintenance transaction distinguishes between services of the Standard Mode and of the Compatibility Mode for SP02 .

Compatibility Mode for SP02This compatibility mode for SAP NetWeaver Gateway 2.0 SP02 refers to the ICF node /sap/opu/sdata. This node is available for existing applications whichmight be based either on OData Channel or Generic Channel.

CautionThis node is in maintenance mode.

The request handler for this node is /IWFND/CL_SDATA_ODATA_APP.

Alias Handling in ICFThe ICF standard function of external aliases is also available for SAP NetWeaver Gateway for the Standard Mode , that is, for ICF node /sap/opu/odata.Thus you can define an external alias for your service if you have registered class /IWFND/CL_SODATA_HTTP_HANDLER as handler in the Handler List foryour service node.

NoteNote that external aliases are not supported for namespaces in SICF.

If the handler /IWFND/CL_SODATA_HTTP_HANDLER is not yet registered for your service node, enter the handler name on tab Handler List and activate yourservice. After the handler has been set, you can define the external alias.

More InformationAdministration of ICF server functions (authorization assignment): Server Function AdministrationAdministration of ICF client functions (creation of RFC destinations, and so on): Client Function AdministrationICF services: Creating and Configuring an ICF ServiceAuthentication: Defining the Logon Procedure

1.1.3 Changing Password for Initial Logon

NoteThis section is only relevant if you want to change the password for the initial logon procedure.

The logon configurations for SAP NetWeaver Gateway are handled via the ICF layer. For more information, see Defining the Logon Procedure.SAP systems may require some additional (browser) features if the password needs to be changed because of being initial or outdated. Therefore, the ICF nodescan be configured to permit the initial password change and the direct logon. An additional ICF node is offered to allow the change of passwords with a browser.

Using an ICF Node for Changing PasswordsSAP NetWeaver Gateway offers a special ICF node which can be accessed to change the password, for example for the initial logon sequence. This node isused to change the password and to redirect to any other custom web page.You can find this special ICF node in the service tree under /default_host/sap/opu/utils under the name initial_logon.You can access this node as soon as it has been activated via the URL :/sap/opu/utils/initial_logon.The call of the service requires authentication and does allow to change an initial password via a browser application. If the URL is extended by ?redirectURL=/X then the browser is redirected to the URL wherever X points to. A typical use case for such a redirect URL would be to display additionalinformation, so that the new password data could be used in the settings of a mobile application. If needed, a redirect URL can be configured and will takeprecedence over all basic settings.

( initial_logon )

Changing the Password for ICF Nodes Accessed by Mobile Devices1. In transaction SICF choose Execute (F8) to display the service tree hierarchy.


Page 8 of 90

2. Expand the default host and navigate to the ICF parent node of the initial logon /default_host/sap/opu/utils/initial_logon. This node shall bethe root node which is accessed by your mobile devices and where you want to deny the direct access via mobile device.

3. Double-click on the node and change to edit mode.4. On tab Error Pages choose sub-tab Logon Errors .5. Choose System Logon .

( System logon )6. Choose Configuration .7. Choose Define Service-Specific Settings .8. Under Logon Layout and Procedure choose Custom Implementation and enter ABAP Class /IWFND/CL_COC_SYSTEM_LOGIN.

( Custom implementation example )9. Choose Input (Enter) to save your settings.

CautionIf you have administrator rights you have the additional option to save your settings as global settings. Do not use Save as Global Settings .

10. Activate your ICF node.

Logoff URLThe Internet Communication Framework also offers a default logoff URL on each system.You can define your own logoff pages via Error Pages Logoff Page .

More InformationFor more information on the generic system logon functionality in ICF, see System Logon.

1.1.4 Language Settings The language which is displayed to the user depends on a variety of factors. For more information see Determining the Logon Language.As to languages, the SAP NetWeaver Gateway system supports only the intersecting set of the languages of the connected SAP Business Suite backendsystems.

1.2 OData Channel Configuration Depending on your underlying SAP NetWeaver release the configuration settings for OData Channel and the structure in the Implementation Guide (IMG) maydiffer.

SAP NetWeaver 7.00 and 7.01The OData Channel configuration settings are available in the Implementation Guide (IMG) in the system where software component IW_FND is deployed. In theSAP Reference IMG navigate to SAP NetWeaver Gateway .

( OData Channel IMG for IW_FND in 7.00 and 7.01 )

SAP NetWeaver 7.02 and 7.31The OData Channel configuration activities are listed in the Implementation Guide (IMG) in the system where software component IW_FND is deployed. In theSAP Reference IMG navigate to SAP NetWeaver Gateway OData Channel .

( OData Channel IMG in IW_FND )

RecommendationWe strongly recommend using the OData Channel (ODC) programming paradigm for all SAP NetWeaver Gateway development.As of SAP NetWeaver Gateway 2.0 Support Package 05, you are strongly recommended to use the Service Builder (transaction SEGW) for your ODatadesign-time development . For more information, see SAP NetWeaver Gateway Service Builder.Depending on whether you want to develop SAP NetWeaver Gateway content in an SAP Business Suite backend system or in an SAP NetWeaver Gatewayhub system, you can choose between embedded deployment or central hub deployment. For more information, see Embedded Versus Hub Deployment andDeployment Options.

Apart from basic configuration settings the OData Channel configuration activities for the SAP Business Suite backend system are listed in the ImplementationGuide (IMG) in the backend system where software component IW_BEP is deployed. In the SAP Reference IMG navigate to SAP NetWeaver GatewayService Enablement Backend OData Channel .

( OData Channel IMG in IW_BEP )

SAP NetWeaver 7.40


Page 9 of 90

If you use software component SAP_GWFND in SAP NetWeaver 7.40, IMG activities for SAP NetWeaver Gateway Foundation 7.40 are available. In the SAPReference IMG navigate to SAP NetWeaver Gateway and SAP NetWeaver Gateway Service Enablement . There you find all the relevant ODataChannel IMG activities.

SettingsUser, Developer and Administrator AuthorizationsConnection Settings on the SAP NetWeaver Gateway Hub SystemActivating SAP NetWeaver GatewaySettings for OData Channel Service Development on Backend SystemSettings for OData Channel Service Development on the Hub SystemConnection Settings on the Backend System

More InformationBasic Configuration SettingsOData Channel

1.2.1 User, Developer, and Administrator Authorizations After you have installed the SAP NetWeaver Gateway components you require, you need to set up an administrator role for SAP NetWeaver Gatewaycomponents and assign users to it. Then you set up one or several user roles and assign users to it as well. As you cannot change existing SAP roles, you createyour own roles or copy existing roles to your new custom roles.The SAP system includes templates as opposed to actual users, so you must use the available role templates to create the users you require in the SAPNetWeaver Gateway system. If the users you require exist in your SAP Business Suite backend system, you can replicate these users in the SAP NetWeaverGateway system by connecting the SAP NetWeaver Gateway system to Central User Administration or to SAP Identity Management and synchronize the usersin this way. If this is not possible, you must create the users manually.SAP NetWeaver Gateway provides predefined roles as templates for:

DevelopersAdministratorsEnd users of the different content scenariosThese templates follow the naming convention /IWCNT/RT_USER_.Support colleaguesThese templates provide display authorizations only and are intended to be used by support colleagues who need to view applications logs.

Use the predefined templates to create administrator, developer, user, and support roles for SAP NetWeaver Gateway components. The template names beginwith a namespace ID that corresponds to the software components you use.

SAP NetWeaver Gateway Developer RoleCreate a developer role based on the available templates for all users that are to carry out development tasks such as creating services. Use the developer role/IWBEP/RT_MGW_DSP for accessing a remote system from the Service Builder (transaction SEGW) at design time.The following templates are available for developers:

Template Type Template Name Template forFramework /IWFND/RT_BOR_DEV SAP NetWeaver Gateway BOR Developer

Framework /IWFND/RT_DEVELOPER SAP NetWeaver Gateway Developer

OData Channel /IWBEP/RT_MGW_DEV OData Channel Developer

Screen Scraping /IWSCS/RT_SCR_DEV SAP NetWeaver Gateway Screen Scraping DeveloperFor more information, see Assigning Authorization toTransaction and Search Help

SAP NetWeaver Gateway Administrator RoleCreate a role for an administrator user with permissions and privileges for several tasks, including the following:

Create services.Analyze logs and identify potential issues with the SAP NetWeaver Gateway landscape.Install, configure, and maintain SAP NetWeaver Gateway components and applications that run on SAP NetWeaver Gateway.Configure and maintain users data including roles and user mapping.

In the SAP Reference Implementation Guide (IMG) (transaction SPRO), navigate to SAP NetWeaver Gateway OData Channel Configuration UserSettings Define Role for SAP NetWeaver Gateway Administrator and click on the Activity icon. The Role Maintenance page displays.To check that the role was properly created and assigned, log onto the SAP NetWeaver Gateway system as the user you just assigned. You should be able toaccess transaction SPRO and find the SAP NetWeaver Gateway Implementation Guide there. You can now log onto the SAP NetWeaver Gateway host as theadministrator user you have just created to configure SAP NetWeaver Gateway components and content, and to install consumer applications.For more information about SAP user administrator types, see Setting Up User and Authorization Administrators.


Page 10 of 90

The following templates are available for administrators:

Template Type Template Name Template forFramework /IWFND/RT_ADMIN SAP NetWeaver Gateway Framework Administrator

Content Scenario /IWCNT/RT_ADMIN_REP SAP NetWeaver Gateway Reporting ManagementAdministrator.See Settings for Reporting Management for details onauthorizations required.

OData Channel /IWBEP/RT_MGW_ADM OData Channel Administrator

Business Enablement Provisioning (IW_BEP component) /IWBEP/RT_BEP_ADM Business Enablement Provisioning Administrator

Workflow /IWWRK/RT_WF_ADM SAP NetWeaver Gateway Workflow Administrator

SAP NetWeaver Gateway User RoleCreate a role for a user with permissions and privileges for user-specific tasks. Depending on your application, you can either specify different authorizations fordifferent user roles or have all authorizations bundled together in one user role.

NoteYou must be a SAP NetWeaver Gateway administrator or have a SAP user administrator to create user roles.

In the SAP Reference Implementation Guide (IMG) (transaction SPRO), navigate to SAP NetWeaver Gateway OData Channel Configuration UserSettings Define Role for SAP NetWeaver Gateway User and click on the Activity icon. The Role Maintenance page displays. Proceed as describedbelow.Once you have assigned users to the relevant roles, you can log on as one of these users and work as them. If you use Web service based scenarios, copy the SAP_BC_WEBSERVICE_CONSUMER role to a customer role for end users. Then assign this customer role toyour end users. To do this, proceed as follows:

1. Click on the Activity icon of the IMG activity Define Role for SAP NetWeaver Gateway User mentioned above.The Role Maintenance page displays.

2. In the Role field, enter your customer role for Web services and choose Change .3. On the User tab enter the names of the users to whom you want assign this role and save your settings.4. Choose User Comparison .5. Choose Complete Comparison .6. Save your settings.

To check that you have successfully assigned roles to users, take some of the users assigned to the different roles and make sure that you can log onsuccessfully. If these steps have not been performed successfully, an HTTP request of an authenticated user returns an HTTP 500 error.The following templates are available for end users:

Template Type Template Name Template forFramework /IWFND/RT_GW_USER SAP NetWeaver Gateway User

Framework /IWFND/RT_TU_NOTIF SAP NetWeaver Gateway Technical User for Notifications

Content Scenario /IWCNT/RT_USER_LEMA SAP NetWeaver Gateway Leave Management User.See Settings for Leave Management Application for detailson authorizations required.

Content Scenario /IWCNT/RT_USER_REP SAP NetWeaver Gateway Reporting Management UserSee Settings for Reporting Management for details onauthorizations required.

Content Scenario /IWCNT/RT_USER_SS SAP NetWeaver Gateway Sample Services User

Content Scenario /IWCNT/RT_USER_TRVL SAP NetWeaver Gateway Travel User

Content Scenario /IWCNT/RT_USER_TIMA SAP NetWeaver Gateway Time Management User.See Settings for Time Management Application for detailson authorizations required.

Content Scenario /IWCNT/RT_USER_WF SAP NetWeaver Gateway Workflow User

Content Scenario /IWCNT/RT_USER_ACT SAP NetWeaver Gateway Activity Management UserSee Settings for Customer Relationship Management onSAP NetWeaver Gateway for details on authorizationsrequired.

Content Scenario /IWCNT/RT_USER_ACCNT SAP NetWeaver Gateway User for Account ManagementSee Settings for Customer Relationship Management onSAP NetWeaver Gateway for details on authorizationsrequired.

Content Scenario /IWCNT/RT_USER_CONT SAP NetWeaver Gateway User for Contact ManagementSee Settings for Customer Relationship Management onSAP NetWeaver Gateway for details on authorizationsrequired.

OData Channel /IWBEP/RT_MGW_USR OData Channel User


Page 11 of 90

OData Channel /IWHDB/RT_USER OData Channel HANA Integration User

OData Channel /IWBEP/RT_SUB_USR On-behalf Subscription User

Business Enablement Provisioning (IW_BEP component) /IWBEP/RT_BEP_USR Business Enablement Provisioning User

Workflow /IWWRK/RT_WF_GW_USR SAP NetWeaver Gateway Workflow User

Workflow /IWWRK/RT_WF_SUB_USR On-Behalf Subscription for SAP NetWeaver GatewayWorkflow Services

Screen Scraping /IWSCS/RT_SCR_USR SAP NetWeaver Gateway Screen Scraping UserFor more information, see Assigning Authorization toTransaction and Search Help

SAP NetWeaver Gateway Support User RoleThe following templates are available for support users (display authorization only). The support templates are available in the SAP NetWeaver Gateway hubsystem and the SAP Business Suite backend systems respectively. These templates contain read-only authorizations to access SLG1, the application log viewerand the corresponding log objects and sub-objects.

Template Type Template Name Template forSupport /IWFND/GW_SUPPORT_RO Read-only supportability role for SAP NetWeaver Gateway

systemSupport /IWBEP/GW_SUPPORT_RO Read-only supportability role for SAP Business Suite

backend system

More InformationCreating and Assigning RolesRoles in the SAP NetWeaver Gateway Landscape

1.2.1.1 Creating and Assigning Roles To create a role and assign it to users (user roles, administrator roles or developer roles), proceed as follows:

1. On the Role Maintenance page enter an existing SAP_BC* role : For an administrator role choose a listed standard administrator role, for exampleSAP_BC_BASIS_ADMIN, and for a user role, enter an existing generic user role, for example SAP_BC_ENDUSER.

2. Select Copy Role to create a copy of the standard role.3. In the Query dialog box, enter a name for the new role and then select Copy all .

The new role is created.4. On the Role Maintenance page, select Change .5. On the Authorizations tab select Change Authorization Data under the Maintain Authorization Data and Generate Profiles section.6. Select Edit Insert authorization(s) From template... .

The Choose Template page displays.7. Select the appropriate template from the list (see User and Administrator Authorizations) and choose Continue (Enter) .8. Choose Generate .9. On the Generate Profile window choose Generate .

10. In the Assign Profile Name for Generated Authorization Profile dialog box, maintain the profile name according to your requirements and choose Execute(Enter) .

11. The Change role: Authorizations page displays, with the Status of the profile showing as generated .12. Go back to the Change Roles page and select the User tab.13. Under User Assignments enter the names of the users to whom you want to assign this role and save your settings.14. Choose User Comparison .15. Choose Complete Comparison .16. Save your settings.

For more information about role maintenance, see Changing Standard Roles.

1.2.2 Connection Settings on the SAP NetWeaver Gateway HubSystem Connection Settings: SAP NetWeaver Gateway to ConsumerConnection Settings: SAP NetWeaver Gateway to SAP Systems

1.2.2.1 Connection Settings: SAP NetWeaver Gateway toConsumer When using Push flow and also Web services, you have to specify settings from your SAP NetWeaver Gateway system to consumers.In the following sections only the basic configuration activities to set up the connection between the SAP NetWeaver Gateway host and the consumer system arelisted. You can find the complete set of configuration activities in the SAP NetWeaver Gateway Configuration implementation guide (IMG) in the system. In


Page 12 of 90

Transaction SPRO open the SAP Reference IMG and navigate to SAP NetWeaver Gateway OData Channel Configuration Connection Settings SAP NetWeaver Gateway to Consumer .

Creating a bgRFC Destination for Outbound QueuesRegistering the bgRFC Destination for the Outbound QueueCreating the bgRFC Supervisor Destination

1.2.2.1.1 Creating a bgRFC Destination for Outbound Queues You must create a Background Remote Function Call (bgRFC) destination for communications in an outbound queue or an inbound queue respectively.To create a bgRFC destination for the outbound queue, proceed as follows:

1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP NetWeaver Gateway OData Channel Configuration ConnectionSettings SAP NetWeaver Gateway to Consumer Create RFC Destination for Outbound Queues and click on the Activity icon.

2. Choose Create .3. In RFC Destination , enter IWFND_BGRFC_DEST.4. In Connection Type , enter 3.5. In Description 1 , enter RFC Destination for Outbound Queues.6. Choose Enter and then select the Special Options tab.7. In the Select Transfer Protocol section, select the option Classic with bgRFC from the list and save your settings.8. Accept the warning message with Yes .9. Choose Connection test .

Information about the connection type displays.

1.2.2.1.2 Registering the bgRFC Destination for the OutboundQueue Register the bgRFC destination for the outbound queue to handle communications efficiently. Proceed as follows:

1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP NetWeaver Gateway OData Channel Configuration ConnectionSettings SAP NetWeaver Gateway to Consumer Register RFC Destination for Outbound Queues and click on the Activity icon.

2. Select the Define Inbound Dest. tab.3. Choose Create .4. In the Inb. Dest. Name field, enter IWFND_BGRFC_DEST.5. Choose Enter and Save .6. In the New Prefix field, enter IWFND_CNP for example and choose Create . Repeat the step using IWCNT_WF, for example.7. Save your settings.8. On the Scheduler: Destination tab choose Create .

A message displays, asking if you want an outbound or inbound destination.9. Choose Inbound .

10. In the Destination field, enter IWFND_BGRFC_DEST and choose Save .11. Save your settings.

1.2.2.1.3 Creating the bgRFC Supervisor Destination The supervisor destination for bgRFC receives the configuration settings for the bgRFC scheduler and also starts or stops the schedulers as required.

NoteThe bgRFC supervisor user you specify must have authorizations from authorization object S_RFC. These are defined in role SAP_BC_BGRFC_SUPERVISOR.

To create the bgRFC supervisor destination, proceed as follows:1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP NetWeaver Gateway OData Channel Configuration Connection

Settings SAP NetWeaver Gateway to Consumer Create bgRFC Supervisor Destination and click on the Activity icon.2. On tab Define Supervisor Dest. choose Create .3. In the Destination Name field, enter BGRFC_SUPERVISOR.4. In the User Name field, enter a user name, for example, BgRFC_user.5. Select Create User and choose Enter .6. Choose Save .7. Select Generate Password and choose Save .8. On the bgRFC Destination page, select Save .

1.2.2.2 Connection Settings: SAP NetWeaver Gateway to SAPSystems You must configure settings for SAP NetWeaver Gateway components and define how these settings interface with your existing SAP Business Suite system(backend system).In the following sections only the basic configuration activities are listed. You can find the complete set of configuration activities in the SAP NetWeaver GatewayConfiguration Implementation Guide (IMG) in the system. In transaction SPRO open the SAP Reference IMG and navigate to SAP NetWeaver Gateway OData Channel Configuration Connection Settings SAP NetWeaver Gateway to SAP System .


Page 13 of 90

Defining Trust between the SAP NetWeaver Gateway Host and Your SAP SystemCreating a Type 3 RFC Destination on SAP NetWeaver Gateway Host to SAPConfiguring SAP System to Accept Assertion Tickets from SAP NetWeaver GatewayConfiguring the SAP NetWeaver Gateway Host to Accept Assertion TicketsCreating the System Alias for Applications

1.2.2.2.1 Creating a Type 3 RFC Destination on SAP NetWeaverGateway Host to SAP System A Type 3 connection from the SAP NetWeaver Gateway host to the SAP Business Suite system is required for all scenarios. Create this as follows

1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP NetWeaver Gateway OData Channel Configuration ConnectionSettings SAP NetWeaver Gateway to SAP System Manage RFC Destinations and click on the Activity icon.

2. Choose Create .3. In the RFC Destination field, enter the RFC destination name in the following format: CLNT.4. In the Connection Type field, enter 3.5. In the Description 1 field, enter an explanatory text, for example, RFC Destination to SAP Server.6. Save your settings.7. On tab Technical Settings and Load Balancing select the relevant option according to your systems settings.8. In the Target Host field, enter the (message) server name of the of the SAP system.9. In the System Number field, enter the SAP NetWeaver Gateway system number, for example, 00.

10. On tab Logon & Security enter the SAP systems client number.11. Activate Current User .12. For Trust Relationship activate Yes .

NoteEnsure that you have previously created the trusted relationship, as outlined in Defining Trust between the SAP NetWeaver Gateway Host and YourSAP System.

13. Save your settings. To check that you have successfully created the type 3 connection, choose Connection Test . The connect test should pass.If the user ID with which you are logged on to SAP NetWeaver Gateway and your user ID for the SAP system is the same, and this user ID has the objectS_RFCACL assigned to it on the SAP system, select Remote Logon . You should not see any error messages in the status. If you have any problems, checkSAP Note 128447 for troubleshooting tips.

1.2.2.2.2 Defining Trust between the SAP NetWeaver GatewayHost and Your SAP Systems for Type 3 Connections You define the trust relationship between your SAP Business Suite system and the SAP NetWeaver Gateway host by configuring the SAP Business Suitesystem (backend system) to be the trusting system, and the SAP NetWeaver Gateway host to be the trusted system.

NoteThis is simply a technical RFC destination used to establish the trust. It is not used during runtime.

To configure trust, proceed as follows:1. On the SAP business system, open transaction SM59 and choose Create .2. In the RFC Destination field, enter the RFC destination name in the following format: CLNT..3. In the Connection Type field, enter 3.4. In the Description 1 field, enter an explanatory text, for example, RFC Destination to SAP NetWeaver Gateway Server.5. Save your settings.6. On tab Technical Settings and Load Balancing select the relevant option according to your systems settings.7. In the Target Host field, enter the (message) server name of the SAP NetWeaver Gateway system.8. In the System Number field, enter the SAP NetWeaver Gateway system number, for example, 00.9. Save your settings.

10. In transaction SMT1 choose Create .The wizard for creating trusting relationships displays.

11. Proceed with the steps outlined in the wizard.In the RFC Destination field, enter the RFC destination you created.An RFC logon to the SAP NetWeaver Gateway host takes place and the necessary information is exchanged between the systems.

12. Log on to the SAP NetWeaver Gateway host using your administrator user and password.The trusted entry for the SAP NetWeaver Gateway host displays.

13. Save your settings.

NoteEnd users must have authorization object S_RFCACL assigned to them before they can use a trusted connection. For more information, see RFCTrusted/Trusting Systems.


Page 14 of 90

1.2.2.2.3 Configuring SAP System to Accept Assertion Ticketsfrom SAP NetWeaver Gateway You must configure your SAP Business Suite (backend) system to accept SAP assertion tickets from the SAP NetWeaver Gateway host for message-basedWeb service communication.To accept SAP assertion tickets, proceed as follows:

1. Make sure that the profile parameters are set as outlined in Profile Parameters.2. In your backend system go to transaction SSO2 to run the SSO2 administration wizard.

NoteIf transaction SSO2 does not work, use STRUSTSSO2 to import the certificates from the SAP NetWeaver Gateway server; you must import themmanually. For further information, see Using Transaction STRUSTSSO2 in SAP System >= 4.6C.

3. Enter the Type 3 RFC destination created above (for your SAP NetWeaver Gateway system) or the Host Name and Instance Number for theSAP NetWeaver Gateway system in the appropriate fields.

4. Choose Execute .On the Logon page enter your password.The SSO2 administration report for the designated SAP system displays.

5. Choose Activate (Enter Certificate in ACL and, if Necessary, Certificate List) to configure the SAP system.

1.2.2.2.4 Configuring the SAP NetWeaver Gateway Host toAccept Assertion Tickets from SAP Business Suite Systems You must configure your SAP NetWeaver Gateway host to accept SAP assertion tickets from the SAP Business Suite (backend) system for message-basedWeb service communication. Proceed as follows:

1. In your SAP NetWeaver Gateway system make sure that the profile parameters are set as outlined in Profile Parameters.2. In your SAP NetWeaver Gateway system go to transaction SSO2 to run the SSO2 administration wizard.

NoteIf transaction SSO2 does not work, use STRUSTSSO2 to import the certificates from the SAP NetWeaver Gateway server; you must import themmanually. For further information, see Using Transaction STRUSTSSO2 in SAP System >= 4.6C.

3. Enter the Type 3 RFC destination created above (from your backend system) or the Host Name and Instance Number for the backend system in theappropriate fields.

4. Choose Execute .

NoteYou may be asked to provide a user name and password.

The SSO administration report for the designated SAP system displays.5. Choose Activate (Enter Certificate in ACL and, if Necessary, Certificate List) to configure the SAP NetWeaver Gateway system.

If everything has been configured correctly the traffic lights are green.

1.2.2.2.5 Creating the SAP System Alias for Applications You need to specify where the SAP system alias should point to. Depending on the SAP NetWeaver Gateway content scenario and your system landscape youthus set up the system alias. The system alias is the result of the routing for an inbound request on SAP NetWeaver Gateway. It can be a remote or a localsystem. If that system alias is flagged as a Local GW instance, it means that the system that is responsible for processing (managing and storing) the data of aninbound request is the local SAP NetWeaver Gateway instance itself.

1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP NetWeaver Gateway OData Channel Configuration ConnectionSettings SAP NetWeaver Gateway to SAP System Manage SAP System Aliases and click on the Activity icon.

2. Choose New Entries .3. Enter the following details for the SAP system alias:

Field DescriptionSAP System Alias Name of the system alias.Description Descriptive text for the system alias.Local GW The system that is responsible for processing (managing and storing) the data of an

inbound request is the local SAP NetWeaver Gateway instance itself.This option is typically used for testing scenarios, for example when using the BORGenerator locally.If you activate Local GW for a SAP System Alias called LOCAL the RFCDestination is usually NONE.

For Local App The system alias is to be used by BEP. For more information, see the F1 help in thesystem and Hub OData Channel with IW_BEP Installation.


Page 15 of 90

RFC Destination Specify the RFC destination defined for your SAP system.Software Version This setting is specified by the content scenario you are using. Typically it is

DEFAULT.In the context of Generic Channel development, check the following to determine thevalue to set for your GSDOs:In transaction SPRO open the SAP Reference IMG and navigate to: SAPNetWeaver Gateway Former Development Former Generic Channel Development Generic Service Data Object (GSDO) GSDO Types & GSDO

Contexts & GSI Implementations and click on the Activity icon. Select yourGSDO type and choose GSI Implementation .

System ID Name of the SAP target system.

NoteWhen specifying SAP system aliases we recommend always to enter thesystem ID. The SAP target system, together with the target client, determinesthe system alias for a remote call to a backend system.

Client Target client.WS Provider System Name of the Web service provider business system. Here you only need to enter a

setting if you use content scenarios which are configured via Web services.4. Save your settings.

NoteWe recommend that you check the system alias configurations using Check SAP System Aliases.

1.2.3 Activating SAP NetWeaver Gateway Before you can use SAP NetWeaver Gateway functionality and theyou have to activate it globally in your system.You can activate and deactivate SAP NetWeaver Gateway. When you deactivate it, all SAP NetWeaver Gateway services stop running, no consumer serverscan communicate with it, and an error message is sent to any system that calls for the services.When you have completed the installation and post-installation configuration described in the sections above, you must activate SAP NetWeaver Gateway.

NoteBefore activating SAP NetWeaver Gateway, ensure that you have first installed and configured the consumer server.

Proceed as follows:1. In transaction SPRO open the SAP Reference IMG and navigate to: SAP NetWeaver Gateway OData Channel Configuration Activate or

Deactivate SAP NetWeaver Gateway and click on the Activity icon.A message displays.

2. Choose Activate .A message displays informing you of the current status.

1.2.4 Settings for OData Channel Service Development onBackend System OData Channel implementations retrieve the data from an SAP Business Suite (backend) system. Both application logic and metadata are hosted on the SAPBusiness Suite system. After the ABAP development activities, that is developing the runtime service and the model provider class, the services need to beactivated.For this the following registration process is done on the SAP Business Suite system:

Maintain modelsMaintain services

You can maintain these settings in IMG activities in the SAP Business Suite system. In transaction SPRO open the SAP Reference IMG and navigate to SAPNetWeaver Gateway Service Enablement Backend OData Channel Service Development for Backend OData Channel Maintain Models andMaintain Services . For more information see Maintaining Models and Services.

To get an overview of the settings the IMG activity SAP NetWeaver Gateway Service Enablement Backend OData Channel Service Development forBackend OData Channel Display Models and Services is provided. Note that this activity is read-only. For more information see Display Models andServices.After this registration SAP NetWeaver Gateway can expose the corresponding OData services.Once a service has been defined in the SAP Business Suite system it can be activated on the SAP NetWeaver Gateway system. See Maintain Services.Under the IMG path SAP NetWeaver Gateway Service Enablement Backend OData Channel Service Development for Backend OData Channel an additional activity OData Channel Generation Tool is provided. For more information, see OData Channel Generation Tool. In addition, an activity is provided todefine parallelization of batch queries. For more information, see Define Parallelization of Batch Queries.

Repository ObjectsThe registration process of OData Channel models and services is unique: In order to allow collecting authorizations per data provider class (DPC) a repository


Page 16 of 90

The registration process of OData Channel models and services is unique: In order to allow collecting authorizations per data provider class (DPC) a repositoryobject type is available. This is integrated into transaction SU22. Thus two additional repository object types exist in SAP NetWeaver Gateway. For moreinformation see Roles in the SAP NetWeaver Gateway Landscape.These repository objects have the following impact:

Models and services shall only be transported via the transport objects.The external name of a service is derived from the technical name and cannot be freely defined to ensure a GTADIR connection to guarantee uniqueservices. You create service /MYNAMESPACE/MYSERVICE with version 0001 which then results inhttp://:/sap/opu/odata/mynamespace/MYSERVICE.

PrerequisitesThe following entities must exist:

The data provider class for the serviceThe model provider class for all models

More InformationOData Channel

1.2.4.1 Displaying Models and Services In the SAP Business Suite backend system you can find this activity in the Implementation Guide (IMG): In transaction SPRO open the SAP Reference IMG andnavigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel Service Development for Backend OData Channel DisplayModels and Services .In this activity you can display the models and the assignment of models to services. Thus you get an overview on the existing models and services.This is a read-only activity which simply provides an overview on existing configuration settings. The view cluster can still be used to display all registeredservices and models. The maintenance activities are done via Maintaining Models and Services.

1.2.4.2 Define Parallelization of Batch Queries The transaction for defining parallelization of batch queries allows you to optimize the performance of batch request processing. For this an IMG activity isavailable: In transaction SPRO open the SAP NetWeaver reference IMG and navigate to Gateway Service Enablement Backend OData Channel ServiceDevelopment for Backend OData Channel Define Parallelization of Batch Queries .In case of serialization the duration of the consecutive queries is the sum of all query processing times. Contrary to this, the total duration in parallel mode is justthe maximum duration of these query processing times and a minimal overhead for parallelization.The following parameters are valid for the current SAP client:

Activate Parallelization for Batch QueriesMark or unmark this option to enable or disable the parallelization.Maximum Number of Parallel Queries

Specify the maximum number to limit the amount of parallel processing queries to save system resources. This number will be ignored if it is greater thanthe maximum number of dialog work processes available at parallelization time which is based on system settings (transaction RZ11, profile parametersrdisp/rfc*) . Zero (0) means it only depends on current system resources. Default value: 0.

1.2.5 Settings for OData Channel Service Development on theHub System After you have made the relevant configuration settings in the SAP Business Suite system in which component IW_BEP is installed (SAP NetWeaver releaseslower than 7.40) or in which core component SAP_GWFND is installed (SAP NetWeaver 7.40 or higher), you need to make some additional configuration settings inthe SAP NetWeaver Gateway hub system in which you intend to develop OData services.

NoteIf your SAP NetWeaver Gateway hub system is based on an SAP NetWeaver release lower than 7.40, you will need to install the core component IW_FND inyour hub system. If your SAP NetWeaver Gateway hub system is based on SAP NetWever 7.40 or higher, the core component SAP_GWFND is installed asstandard. For more information, see Deployment Options.

Assigning SAP System Alias to OData ServiceActivate and Maintain ServicesMultiple Origin CompositionDynamic System Alias Calculation Via /IWFND/ES_MGW_DEST_FINDER

1.2.5.1 Assigning SAP System Alias to OData Service You can assign SAP system aliases to a service. With this assignment, an OData request from an SAP NetWeaver Gateway consumer can be routed to thecorresponding backend system. The system can correctly identify the SAP system that is responsible for processing (managing and storing) the data of an


Page 17 of 90

inbound request. Thus, OData Channel based content which is developed either on the SAP NetWeaver Gateway hub system or on a SAP Business Suitebackend system is based on the service.The SAP system alias can have a specific role or a specific host name associated to itself, so that you can specify different roles or host names for the samesystem alias for a service. If you leave the User Role or the Host Name field empty, the setting is valid for all roles/host names. Different backend systems aresupported, if you specify corresponding roles/host names and system aliases. The roles are only for user grouping and do not need to have any specialauthorization.

ExampleIt is possible to separate the development, the quality and the production landscape via dedicated clients on the SAP NetWeaver Gateway hub system.The user will be directed as follows if he has not special roles: If there is a system alias maintained without any role assignment then it is used for all users.The user will be directed as follows if he has two or several roles relative to different system aliases: If a user is assigned to more than one system alias thesystem alias which is marked as default wins. If more than one system alias is found and either none of the system aliases or more than one of these aliasesare flagged as default an error is raised.

Ideally you have a system alias without any role assignment for all users without a role assignment and disjunct roles for the system aliases for all other users tothe different backend systems (development, quality, productive). The system aliases with role assignment should be marked as default in this case.For this an IMG activity is available in the SAP NetWeaver Gateway Implementation Guide (IMG): in transaction SPRO open the SAP Reference IMG andnavigate to SAP NetWeaver Gateway :

For applications based on backend OData Channel system navigate to OData Channel Administration General Settings Assign SAP SystemAliases to OData Service .For applications based on OData Channel with IW_BEP on the hub navigate to OData Channel Development with IW_BEP Registration AssignSAP System Aliases to OData Service .

NoteIn previous support packages OData Channel based content was routed via GSDO groups which are no longer relevant in SAP NetWeaver Gateway 2.0SP03.

1.2.5.2 Multiple Origin Composition Multiple origin composition (MOC) is the ability to collect data from different backend systems, aggregate them in one single service and updating differentbackend systems while using the same user. Thus a service can be made available for several system aliases. For example, you could have two identicalsystems, one located in America and one in Europe, and combine them. MOC is also used for CREATE calls and the metadata. At present, CREATE calls cannotbe done in all configured backend systems, but only in the default system.

NoteThis feature is only supported in Standard Mode .This feature is relevant only for entity sets with an annotation of addressable=true.Implementing this feature creates a different version of the service (The SAP__Origin field is added).

Proceed as follows to use the MOC:1. Customize your service to support MOC.

1. From the SAP NetWeaver Gateway system, activate the desired service. For information on how to activate your service, see Register your Servicein the SAP NetWeaver Gateway System.

2. Open transaction SPRO and choose SAP Reference IMG .3. Navigate to SAP NetWeaver Gateway OData Channel Administration General Settings Activate and Maintain Services to add the

system aliases for the relevant backend systems and define the desired default system.1. In the Service Catalog list, select the desired service. The service appears in the ICF Nodes section on the lower left corner of the screen.2. In the ICF Nodes section, select the Standard Mode ICF Node.3. In the System Aliases section, choose System Alias to add the system alias.4. Choose New Entries or select an existing entry and choose Copy .5. In the Service Doc. Identifier field, enter the ID of the service document followed by an underscore and the 4digit version number (for

example, _0001).6. In the SAP System Alias field, enter the relevant system alias. Only one system is to be defined as the default.7. Repeat as necessary to add the desired backend systems.

NoteThe default system is used whenever the service is not called as MOC. If you have defined more than one default system alias, the first systemis used as the default.

2. Test the service.1. On the SAP NetWeaver Gateway system, open the SAP Reference IMG in transaction SPRO and navigate to SAP NetWeaver Gateway

OData Channel Administration General Settings Activate and Maintain Services .2. Search for the desired service with the Filter icon.3. Select the desired service and choose Call Browser under ICF Nodes .

An example URL for RMTSAMPLEFLIGHT looks as follows:http://:/sap/opu/odata/iwfnd/RMTSAMPLEFLIGHT;mo/

4. Make sure that the SAP__Origin field appears in the service's metadata.


Page 18 of 90

Parallelization of Multiple Origin CompositionWhen using multiple origin composition you can determine both the minimum number of backend systems and the maximum number of parallel backend calls.For this a new IMG activity has been added: On the SAP NetWeaver Gateway system, open the SAP Reference IMG in transaction SPRO and navigate to SAP NetWeaver Gateway OData Channel Administration General Settings Define Parallelization for Multiple Origin Composition .You can use this parallelization of READ_ENTITYSET to several backend systems to achieve optimized performance. In the In the IMG activity you can set thefollowing configuration parameters:

Minimum Number of Backend Systems can have following values:0: No parallelizationn: Parallelization will only be done from n backend systems onwards

The maximum number of parallel backend calls is always based on current resources of the SAP NetWeaver Gateway hub system. Additionally, you canuse parameter Maximum Number of Parallel Backend Calls to limit the use of current system resources. The default value zero (0) means it only dependson current system resources.

Performance ImprovementIn case of serialization the duration of a READ_ENTITYSET within a hub system is the sum of all backend calls. Contrary to this, the duration in parallel mode isjust the maximum duration of all backend calls and means a minimal overhead for parallelization.

Parallelization and SkiptokenIf server paging is realized in any backend data providers, then the OData consumer will only receive results up to this backend including a skiptoken. The nextcall with this skiptoken or any other call with skiptoken will not be parallelized because the result has to be continued by the backend system which returned thisskiptoken before.

ChangesetsIn the context of multiple origin composition, changesets are also supported. All changeset operations for one backend are collected and sent to this backend viaone RFC. You can find an example in SAP Note 1890049.

More InformationError Log

1.2.5.3 Dynamic System Alias Calculation Via/IWFND/ES_MGW_DEST_FINDER Enhancement spot /IWFND/ES_MGW_DEST_FINDER is provided to help you in dynamically calculating which system alias should be used. You can thereforeuse this enhancement spot to overwrite or enhance the standard routing for a service. Alternatively, you can use this enhancement spot to control the traffic fromthe SAP NetWeaver Gateway system to a backend system, so as to limit the load on that backend system.The enhancement spot needs the following input:

OData service IDUser IDResult of the standard routing in the form of a list of system aliasesList of HTTP request parameters which is only provided for data requests and not for metadata requests.

The enhancement sport returns a list of system aliases with the following fields:system_alias of TYPE /iwfnd/defi_system_alias.This has to be defined with the standard implementation guide activity for system aliases.user_role of TYPE /iwfnd/defi_role_name.This field is filled according to the standard routing in the implementation guide which has the role as an optional filer. Note that this field can be empty.is_default of TYPE /iwfnd/mgw_inma_default_alias.If the table contains only one entry this can be empty. If the table contains more than one entry exactly one entry must be flagged as default.

That system alias is used for all normal (non multi destination composition) requests.That system alias is used for multi destination composition requests in case of CREATE, metadata or function imports of multiplicity 1.

ExampleThe service created in the backend system is as follows:

Technical Service Name: /IWBEP/TEA_TEST_APPLICATION

External Service Name: TEA_TEST_APPLICATION

Version: 0001

The service registered on the SAP NetWeaver Gateway system is as follows:

Namespace: /IWBEP/

External Service Name: TEA_TEST_APPLICATION


Page 19 of 90

Version: 0001

Technical Service Name: ZTEA_TEST_APPLICATION (provided during registration)

Service Document Identifier: ZTEA_TEST_APPLICATION_0001 (technical service name plus version)

The URI would be as follows: URI = /sap/opu/odata/iwbep/TEA_TEST_APPLICATION/TeamCollectionThe BAdI input would be as follows:

IV_USER =MRMEYER

IV_SERVICE_ID = ZTEA_TEST_APPLICATION_0001

Table of system aliases containing the result of the standard routing

The BAdI output would then be a table of system aliases which were changed by the BADI (or not changed) as a result of the standard routing.

SyntaxSample coding throwing an exception in case of too much load on the backend system:

01. RAISE EXCEPTION TYPE /iwfnd/cx_mgw_dest_finder EXPORTING textid = /iwfnd/cx_mgw_dest_finder=>backend_load_too_high http_status_code = /iwfnd/cx_mgw_dest_finder=>gc_status_service_unavailable system_alias = lv_system_alias.

1.2.6 Connection Settings on the Backend System The following activities can be used by OData Channel to set up the connection settings to SAP NetWeaver Gateway.

Settings for Idempotent ServicesDefining a Remote Function Call to SAP NetWeaver GatewayConnection Settings to SAP NetWeaver GatewayConfigure the bgRFC Supervisor DestinationMonitoring bgRFC Queues

1.2.6.1 Settings for Idempotent Services HTTP is an inherently unreliable protocol. If connection or other issues prevent the client from receiving a response the client is left in doubt if the request wasprocessed by the server. Idempotency guarantees delivery of synchronous messages exactly once. For idempotent requests (for example GET) the client cansimply re-try the request. But for operations that change the server state (for example, creating a new item or invoking a side-effecting service operation such asReject Workflow) re-issuing the request may result in an undesired state, as for example two items instead of one item are created.Two optional request header attributes and one response header attribute facilitate the ability to retry requests without incurring unintended side-effects:

Request HeadersRequestIDA 32 character GUID string representing a client-generated, globally unique for all time, identifier for the request.RepeatabilityCreationThe date and time at which the request was first created. If specified, the client directs that the request must be repeatable. The client can make therequest multiple times with the same RequestID and RepeatabilityCreation header values and get back an appropriate response withoutthe server executing the request multiple times.

Response Header: RepeatabilityResultA string describing how the server has handled the requested repeatability. The following values are possible.

acceptedThe request was accepted and the server guarantees that the server state reflects a single execution of the operation. The response returns thesuccess or failure state of the operation as first executed by the server, and reflects either the current state of the system or the state as it existedwhen the request was first received.unsupportedThe request was rejected because the server does not support repeatable execution of the request. The server returns 412 (PreconditionFailed) without attempting to execute the request. The server state is the same as if the request had never been received.rejectedThe request was rejected because the combination of RepeatabilityCreation and RequestID was invalid or because theRepeatabilityCreation time was outside the range of values held by the server. The server returns 412 (Precondition Failed) withoutattempting to execute the request. The server state is the same as if the request had never been received.

The request header attributes are passed on to the SAP Business Suite backend system. In the backend system the idempotent utility (provided by theunderlying SAP NetWeaver) handles the idempotent support generically. When the backend system receives a request it delegates the handling of theRepeatabilityCreation header to the idempotent utility class.

Defining Settings for Idempotent ServicesYou configure idempotent services by scheduling a background job that ensures that request messages in SAP NetWeaver Gateway only occur once.For this the SAP NetWeaver Gateway Implementation Guide (MG) has been enhanced. In transaction SPRO open the SAP Reference IMG and navigate to


Page 20 of 90

SAP NetWeaver Gateway Service Enablement Backend OData Channel Connection Settings to SAP NetWeaver Gateway Define Settings forIdempotent Services .To define settings for idempotent services, proceed as follows:

1. Click on the Activity icon of the above mentioned IMG activity.2. Enter the following default values:

For Period Hours in Document the typical value is 6.For Period Hours in Document ID the typical value is 12.

3. Choose Schedule .A message displays confirming that the job has been scheduled.

4. Choose Continue .

1.2.6.2 Defining a Remote Function Call to SAP NetWeaverGateway You create or define a background remote function call (bgRFC) destination, which is used for communications in an outbound queue, and an inbound queueamong SAP systems. This is an activity that is done in the SAP Business Suite backend system, that is, the system where software component IW_BEP isinstalled.If you are using push from an SAP Business Suite backend system to an SAP NetWeaver Gateway hub system, it is important not to have a trusted RFCconnection. This is because the WF-BATCH user which is the current user in the case of Workflow is not a dialog user and therefore cannot be used for RFC.Instead a dedicated technical user like ALEREMOTE has to be maintained in the RFC destination in the backend system.

NoteYou can also use an existing bgRFC destination in your SAP system to the host of SAP NetWeaver Gateway.

You can define this remote function call by using the implementation guide (IMG). In transaction SPRO open the SAP Reference IMG and navigate to SAPNetWeaver Gateway Service Enablement Backend OData Channel Connection Settings to SAP NetWeaver Gateway Create RFC Destination forOutbound Queues .Proceed as follows to create the bgRFC destination:

1. Click on the Activity icon.2. Choose Create . The RFC Destination Window displays.3. In RFC Destination specify a name for the RFC destination to be created. For example, BEP_BGRFC_DEST.4. In Connection Type enter 3, for ABAP connections.5. In Description 1 , enter an explanatory text.6. Choose Enter , and select tab Technical Settings .7. Enter the SAP NetWeaver Gateway host name in Target Host , and enter its corresponding system number.8. On tab Logon & Security enter the technical user and make sure that Current User is not selected.9. Choose Enter and select the Special Options tab.

10. Depending on the SAP NetWeaver version, do the following:For SAP NetWeaver 7.02, go to section Select Transfer Protocol and select 1 Classic with bgRFC from the list.For SAP NetWeaver 7.0, go to section Select qRFC Version and select bgRFC from the list in qRFC Version .

11. Choose Save and Yes to close the warning message that displays.12. Choose Remote Connection to test the connection. Information about the connection type displays.

1.2.6.3 Connection Settings to SAP NetWeaver Gateway The Business Enablement Provisioning (BEP) functionality can publish events to one or more hosts running SAP NetWeaver Gateway. However, you must firstidentify the SAP NetWeaver Gateway landscape to use with it. For OData Channel you also specify the SAP NetWeaver Gateway landscape.

PrerequisitesMake sure that you have:

Defined an RFC destination to SAP NetWeaver Gateway to broadcast the events.The system name, client ID, and a system alias of the host of the SAP NetWeaver Gateway landscape to which you want to connect.

Specifying Connection SettingsYou can specify settings for connecting to a SAP NetWeaver Gateway landscape by using the implementation guide (IMG). In transaction SPRO open the SAPReference IMG and navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel Connection Settings to SAP NetWeaverGateway SAP NetWeaver Gateway Settings .

1. Click on the Activity icon.2. Choose New Entries and enter the following:

Destination SystemSpecify the system name of the host of SAP NetWeaver Gateway.Client

Specify the system client ID of the host of SAP NetWeaver Gateway. The client ID you specify should be in the specified system.System Alias

Enter a unique name for the host of SAP NetWeaver Gateway.


Page 21 of 90

RFC DestinationSpecify the name of the RFC destination to the host of SAP NetWeaver Gateway. For example BEP_BRFC_DEST.

3. Save your settings.

1.2.6.4 Configure the bgRFC Supervisor Destination You configure a supervisor destination for the bgRFC to receive the configuration settings for the bgRFC scheduler. In addition, the supervisor starts or stops theschedulers as required.

PrerequisitesYou have created a system user of type B called BGRFCSUPER. Use transaction SU01 to create the system user. This user is used for the bgRFCcommunication using the destination you will create. For example, BGRFC_SUPERVISOR.You have assigned role SAP_BC_BGRFC_SUPERVISOR to user BGRFCSUPER. Use transaction SU01 to assign role to the user BGRFCSUPER.For SAP NetWeaver 7.0, you have created a bgRFC destination as an ABAP connection, using the RFC destination name BGRFC_SUPERVISOR, withoutload balancing, target host, SAP NetWeaver Gateway host and service.Specify the user, language and password. This ensures that the scheduler is activated on the same application server as the specified user.Later, you configure the supervisor destination for the bgRFC to receive the configuration settings for the bgRFC scheduler.

NoteThe bgRFC supervisor user you specify must have authorizations from authorization object S_RFC. These are defined in role SAP_BC_BGRFC_SUPERVISOR.The procedure you employ depends on the version of SAP NetWeaver in your system.

Configuring the bgRFC Supervisor DestinationYou can configure this bgRFC supervisor destination by using the implementation guide (IMG). In transaction SPRO open the SAP Reference IMG and navigate to

SAP NetWeaver Gateway Service Enablement Backend OData Channel Connection Settings to SAP NetWeaver Gateway Create bgRFCSupervisor Destination .Proceed as follows:

1. Click on the Activity icon.2. Select tab Define Supervisor Dest .3. Depending on the version of SAP NetWeaver, do the following:

For SAP NetWeaver 7.02, choose Create . The Create bgRFC Destination for Supervisor window is displayed.1. Choose Create User . For example, BGRFCSUPER.2. Save your settings.

For SAP NetWeaver 7.0, make sure you have already created a separate bgRFC destination for the supervisor using the nameBGRFC_SUPERVISOR.

1. Enter the bgRFC supervisor destination name BGRFC_SUPERVISOR, in Destination under New Supervisor Destination .2. Choose Enter . The supervisor destination and the user details display.

4. In the bgRFC Configuration window choose Save .

More InformationbgRFC (Background Remote Function Call)

1.2.6.5 Monitoring bgRFC Queues You can monitor and display items in the Background Remote Function Call (bgRFC) queue to check for messages which the system failed to send.All the messages are written in unit queues, which consist of function modules to be processed as an indivisible unit. Find all the messages that failed to betransported from the host of the Backend Event Publisher (BEP) or OData Channel to the consumer environment, because of system fault exceptions.System faults are all standard REST errors, for example: communication error, or other errors that occurred during the activation and operations of Web services.

NoteApplication fault exceptions are displayed in the application itself.

PrerequisitesMake sure that you have the authorization object S_BGRFC for monitoring or customizing activities assigned to your user role.

Analyzing the Results of the MonitorYou analyze each error message and decide how best to correct the error.If the error can be fixed, make the necessary corrections and then send it to the unit again, otherwise delete the unit.


Page 22 of 90

You can manually restart the unit even if the retry limit has been exceeded. You can go into the code to debug the unit (this requires the appropriate authorizationrole), or delete all the units inside the inbound destination.You can monitor the bgRFC queues by using the implementation guide (IMG). In transaction SPRO open the SAP Reference IMG and navigate to SAPNetWeaver Gateway Service Enablement Backend OData Channel Connection Settings to SAP NetWeaver Gateway Monitor bgRFC Queues .Proceed as follows to monitor bgRFC queues:

1. Click on the Activity icon to open the bgRFC monitor.Alternatively you can use transaction SBGRFCMON.

2. Select the option for the Outbound scenario and the Queued unit type. Select other parameters of the monitor as required.3. Choose Execute to run the monitor. The status of the queues is displayed.4. Monitor the Queue with the Event ID and instance number for the messages which were not sent.

1.3 Business Enablement Provisioning (IW_BEP) Configuration After you have installed the Business Enablement Provisioning (IW_BEP) component, you need to complete the following tasks to help you verify the installationand configuration.The following is an overview of the sequence of the configuration tasks:

1. Configure the role templates for Business Enablement Provisioning.Component IW_BEP provides templates on which you base roles for administrators and end users. You configure the roles based on the provided templatesand assign the roles to users. Using roles, you can designate a user or a group of users as a unit that has access to specific content and resources withinIW_BEP. The templates specify the authorizations for content that can be accessed by the users. The IW_BEP specific templates are available when youinstall IW_BEP in your SAP system. For more information on the role templates for IW_BEP, see User, Developer and Administrator Authorizations.

2. Define an event.3. Event Subscription and Notification4. Specify Connection Settings to the SAP NetWeaver Gateway landscape. These settings are available both for theIW_BEP component and for OData

Channel.

More InformationFor more information, see Business Enablement Provisioning (IW_BEP).

1.4 Configuration Settings for SAP NetWeaver GatewaySupported Scenarios The Gateway system should be configured to start using the SAP NetWeaver Gateway services for different supported channels. This section provides theconfiguration information for all the SAP NetWeaver Gateway supported scenarios.SAP NetWeaver Gateway supports services on these channels:

OData Channel See OData Channel Scenarios for information on configuration settings for OData Channel supported scenarios.Generic Channel See Generic Channel Scenarios for information on configuration settings for Generic Channel supported scenarios.

PrerequisitesFollowing are the different components (along with their releases) required for SAP NetWeaver Gateway. You can download the packages and patches from theSAP Service Marketplace at: service.sap.com/swdc.

Component ReleaseSAP ERP ERP 2004 with NW 7.0 SPS 18 (validated stack)SAP ECC add-on ECC-SE 602 or higherSAP BI (optional) BI 3.5 SP 22 or BI 7.0 - SP 17SAP CRM CRM 6.0 or higher

1.4.1 Configuration Settings for OData Channel Scenarios In the following you can find information on the configuration of the SAP NetWeaver Gateway OData Channel supported scenarios.

OData Channel Scenarios Configuration SettingsSAP Enterprise Resource Planning (SAP ERP) Settings for SAP ERP on SAP NetWeaver GatewayWorkflow Services Configuring Workflow for SAP NetWeaver GatewayBusiness Process Content Powered b