Configurating SAP NetWeaver Gateway 2.0

(1)

(2)

Copyright

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable 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 express warranty statements accompanying such products and services, if any. Nothing herein should be construed as

constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

Please seehttp://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

(3)

Icons in Body Text

Icon Meaning Caution Example Note Recommendation Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions

Type Style Description

Example text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation.

Example text Emphasized words or phrases in body text, graphic titles, and table titles. EXAMPLE TEXT Technical names of system objects. These include report names, program

names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

(4)

SAP NetWeaver Gateway Configuration Guide

Once you haveinstalled [External] the SAP NetWeaver Gateway components, you must configure your system to allow the consumer servers’ applications to retrieve the data requested by users.

The SAP NetWeaver Gateway Configuration Guide contains the steps for customizing settings for SAP NetWeaver Gateway and describes system configuration activities. The sequence of mandatory and optional configuration tasks is as follows and depends on your use case.

1. Basic configuration [Page9] (mandatory) 2. OData Channel Configuration [Page20]

3. Configuration Settings for content scenarios [Page62] (optional)

Implementation Guide

The SAP NetWeaver Gateway specific configuration tasks are included in the

SAP NetWeaver Gateway Implementation Guide (IMG) which is available in the system: 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 before executing each step.

Note

If 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, seeDeployment Options [External].

Recommendation

We 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 OData design-time development . For more information, seeSAP NetWeaver Gateway Service Builder [External].

(8)

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 Former Development .

Additional Software Components

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

Business Enablement Provisioning (IW_BEP)

SeeConnection Settings for OData Channel and BEP [Page53] and

Backend Event Publisher (BEP) Configuration [Page61].

The IW_BEP specific configuration tasks are included in the Gateway Service Enablement Implementation Guide (IMG) which is available in the system: 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 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 by the users and activities for developers. For more information, seeSetting Up User and Administrator

Authorizations [Page23].

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 relational database accesses. It follows the Java Database Connectivity (JDBC) diction in its class and model structure.

Workflow

You can find more information about the Workflow-related configuration activities inConfiguring Workflow for SAP NetWeaver Gateway [Page64]. In addition, the relevant IMG activities are available in the Implementation Guide in the backend system: In transaction 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 withinBusiness Process Enablement [External], such as Process Service and Process Context Service, the relevant IMG activities are available in the Implementation Guide in the backend system. In transaction SPRO open the SAP Reference IMG and navigate to: SAP NetWeaver Gateway Service Enablement Content

Business Process Enablement .

Consumer Settings

(9)

Basic Configuration Settings

After havinginstalled [External] 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 Example

Fully 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 SAP NetWeaver AS ABAP to install and maintain the system

SAP administrator

HTTP/HTTPS ports

HTTP and HTTPS port numbers of the central instance of the AS ABAP

80000 for HTTP and 80001 for HTTPS

SAP system

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

System ID, system number Server name

HTTP / HTTPS port Administrator credentials

In addition, several settings are important for smooth operations:

Profile Parameters [Page10] ICF Services [Page11] Initial Logon [Page16] Language Settings [Page19]

(10)

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 Value

login/accept_sso2_ticket 1

login/create_sso2_ticket 2

You maintain these profile parameters via transaction RZ10.

More Information

For information on profile parameters and profile parameter maintenance, seeProfile Parameters for Logon and Password (Login Parameters) [External] andChanging and Switching Profile Parameters [External].

(11)

ICF Services

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

Caution

Activated ICF services represent a security risk because they can be accessed directly by the HTTP protocol from the Internet. You therefore need to use suitable 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 transaction SICF. 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:

o Using menu option Service/Host Activate .

o 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 tree icon):

(Example)

For SAP NetWeaver Gateway you need to activate the following services: /sap/public/opu

Note that /sap/public/opu/resources is needed for loading resources, such as images in the MIME repository. For example, the generic player gets a service

(12)

/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: o /sap/opu/sdata/iwcnt

o /sap/opu/sdata/iwfnd o /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 on your target system:

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

If the default_host node is inactive in transaction SICF, the HTTP requests could result in an ABAP runtime error RAISE_EXCEPTION with the following short 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 the Implementation Guide for SAP NetWeaver is: Application Server Internet Communication Framework Activate HTTP Services or Activate Services in Installation.

Note that the system performs a check against theauthorization object S_ICF_ADM [External] when an ICF node is created.

Standard Mode

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

(13)

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 protection

See alsoCross-Site Request Forgery Protection [External]

Content-Type required for Put/Post request

An 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 Request

Empty property elements (for example, <name/>) are not allowed anymore. Nullable needs to be set properly, and besides that, if an entry with a null string is to be created set m:null="true", for example, <name m:null="true" />. Null values in the response of a Get/Put request

Intial values for date time fields in combination with nullable properties are rendered as <...m:null="true" />.

Values of keys in Post request in case of server generated keys

If 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 predicates

Seehttp://www.odata.org/developers/protocols/overview#AbstractTypeSystem. Key properties

Sending properties that are not key fields in an URI is not longer possible. String parameters

Quotation marks enclosing string parameters (for example, search string) are now required and removed.

(14)

Inverted commas in URI

Inverted commas in URI, for example, $filter=name eq 'Jame''s shop' can now be properly escaped by an inverted comma.

OData error response

The 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 themessage container [External] or build from the text id of theexception [External].

The structured inner error section is available showing Extended Passport (EPP) transaction ID. All messages of the message container and the additionally provided error details are shown in a special format (micro format).

Things

The workspace for Things, element <app:workspace sap:semantics="things">, is no longer available. Service maintenance

The service maintenance transaction distinguishes between services of the Standard Mode and of the Compatibility Mode for SP02.

Compatibility Mode for SP02

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

Caution

This node is in maintenance mode.

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

Alias Handling in ICF

The ICF standard function ofexternal aliases [External] 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 for your service node.

Note

(15)

More Information

Administration of ICF server functions (authorization assignment):Server Function Administration [External]

Administration of ICF client functions (creation of RFC destinations, and so on):Client Function Administration [External]

ICF services:Creating and Configuring an ICF Service [External]

(16)

Changing Password for Initial Logon

Note

This 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, seeDefining the Logon Procedure [External].

SAP systems may require some additional (browser) features if the password needs to be changed because of being initial or outdated. Therefore, the ICF nodes can 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 Passwords

SAP NetWeaver Gateway offers a special ICF node which can be accessed to change the password, for example for the initial logon sequence. This node is used 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 <host>:<port>/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 additional information, 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 take precedence over all basic settings.

(17)

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.

(18)

(Custom implementation example)

9. Choose Input (Enter) to save your settings.

Caution

If 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 URL

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

(19)

Language Settings

The language which is displayed to the user depends on a variety of factors. For more information seeDetermining the Logon Language [External].

As to languages, the SAP NetWeaver Gateway system supports only the intersecting set of the languages of the connected SAP Business Suite backend systems.

(20)

OData Channel Configuration

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

SAP NetWeaver 7.00 and 7.01

The OData Channel configuration settings are available in the Implementation Guide (IMG) in the system where software component IW_FND is deployed. In the SAP 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.31

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

(21)

Recommendation

We 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 OData design-time development . For more information, seeSAP NetWeaver Gateway Service Builder [External].

Depending on whether you want to develop SAP NetWeaver Gateway content in an SAP Business Suite backend system or in an SAP NetWeaver Gateway hub system, you can choose between embedded deployment or central hub deployment. For more information, seeEmbedded Versus Hub Deployment [External] and

Deployment Options [External].

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

(OData Channel IMG in IW_BEP)

SAP NetWeaver 7.40

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 SAP Reference IMG navigate to SAP NetWeaver Gateway and SAP NetWeaver Gateway Service Enablement .

(22)

Settings

User, Developer and Administrator Authorizations [Page23]

Connection Settings on the SAP NetWeaver Gateway Hub System [Page29] Activating SAP NetWeaver Gateway [Page41]

Settings for OData Channel Service Development on Backend System [Page42] Settings for OData Channel Service Development on the Hub System [Page46] Connection Settings on the Backend System [Page53]

More Information

Basic Configuration Settings [Page9] OData Channel [External]

(23)

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 Gateway components 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 create your 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 SAP NetWeaver Gateway system. If the users you require exist in your SAP Business Suite backend system, you can replicate these users in the SAP NetWeaver Gateway system by connecting the SAP NetWeaver Gateway system to Central User Administration or to SAP Identity Management and synchronize the users in this way. If this is not possible, you must create the users manually.

SAP NetWeaver Gateway provides predefined roles as templates for: Developers

Administrators

End users of the different content scenarios

These templates follow the naming convention /IWCNT/RT_USER_<application name>.

Support colleagues

These 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 begin with a namespace ID that corresponds to the software components you use.

SAP NetWeaver Gateway Developer Role

Create 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 for

Framework /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

SAP NetWeaver Gateway Screen Scraping Developer

(24)

SAP NetWeaver Gateway Administrator Role

Create 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 User Settings 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 to access transaction SPRO and find the SAP NetWeaver Gateway Implementation Guide there. You can now log onto the SAP NetWeaver Gateway host as the administrator 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, seeSetting Up User and Authorization Administrators [External].

The following templates are available for administrators:

Framework /IWFND/RT_ADMIN SAP NetWeaver Gateway Framework Administrator

Content Scenario /IWCNT/RT_ADMIN_REP

SAP NetWeaver Gateway Reporting Management Administrator.

SeeSettings for Reporting

Management [Page188] for details on authorizations 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

(25)

SAP NetWeaver Gateway User Role

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

Note

You 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 User Settings Define Role for SAP NetWeaver Gateway User and click on the Activity icon. The Role Maintenance page displays. Proceed as described below.

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 to your 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 on successfully. 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:

Framework /IWFND/RT_GW_USER SAP NetWeaver Gateway User

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

(26)

Content Scenario /IWCNT/RT_USER_REP

SAP NetWeaver Gateway Reporting Management User

SeeSettings for Reporting Management [Page188] for details on authorizations 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.

SeeSettings for Time Management Application [Page212] for details on authorizations required.

Content Scenario /IWCNT/RT_USER_WF SAP NetWeaver Gateway Workflow User

Content Scenario /IWCNT/RT_USER_ACT

SAP NetWeaver Gateway Activity Management User

SeeSettings for Customer Relationship Management on SAP NetWeaver Gateway [Page171] for details on authorizations required.

Content Scenario /IWCNT/RT_USER_ACCNT

SAP NetWeaver Gateway User for Account Management

Content Scenario /IWCNT/RT_USER_CONT

SAP NetWeaver Gateway User for Contact Management

OData Channel /IWBEP/RT_MGW_USR OData Channel User

OData Channel /IWHDB/RT_USER OData Channel HANA Integration User OData Channel /IWBEP/RT_SUB_USR On-behalf Subscription User

(27)

Workflow /IWWRK/RT_WF_SUB_USR

On-Behalf Subscription for

SAP NetWeaver Gateway Workflow Services

Screen Scraping /IWSCS/RT_SCR_USR

SAP NetWeaver Gateway Screen Scraping User

For more information, seeAssigning Authorization to Transaction and Search Help [External]

SAP NetWeaver Gateway Support User Role

The following templates are available for support users (display authorization only). The support templates are available in the SAP NetWeaver Gateway hub system and the SAP Business Suite backend systems respectively. These templates contain read-only authorizations to access SLG1, theapplication log viewer [External] and the corresponding log objects and sub-objects.

Template

Type Template Name Template for

Support /IWFND/GW_SUPPORT_RORead-only supportability role for SAP NetWeaver Gateway system

Support /IWBEP/GW_SUPPORT_RORead-only supportability role for SAP Business Suite backend system

More Information

Creating and Assigning Roles [Page28]

(28)

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 example SAP_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 (seeUser and Administrator Authorizations [Page23]) 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.

(29)

Connection Settings on the SAP NetWeaver Gateway Hub

System

Connection Settings: SAP NetWeaver Gateway to Consumer [Page30] Connection Settings: SAP NetWeaver Gateway to SAP Systems [Page34]

(30)

Connection Settings: SAP NetWeaver Gateway to

Consumer

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 are listed. You can find the complete set of configuration activities in the SAP NetWeaver Gateway Configuration 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 Consumer .

Creating a bgRFC Destination for Outbound Queues [Page31] Registering the bgRFC Destination for the Outbound Queue [Page32] Creating the bgRFC Supervisor Destination [Page33]

(31)

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 Connection Settings 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.

(32)

Registering the bgRFC Destination for the Outbound

Queue

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

NetWeaver Gateway OData Channel Configuration Connection Settings 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.

(33)

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.

Note

The 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:

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.

(34)

Connection Settings: SAP NetWeaver Gateway to SAP

Systems

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 Gateway Configuration

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 .

Defining Trust between the SAP NetWeaver Gateway Host and Your SAP System [Page36]

Creating a Type 3 RFC Destination on SAP NetWeaver Gateway Host to SAP [Page

35]

Configuring SAP System to Accept Assertion Tickets from SAP NetWeaver Gateway [Page37]

Configuring the SAP NetWeaver Gateway Host to Accept Assertion Tickets [Page38] Creating the System Alias for Applications [Page39]

(35)

Creating a Type 3 RFC Destination on SAP NetWeaver

Gateway 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

NetWeaver Gateway OData Channel Configuration Connection Settings 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: <system id >CLNT<Client>.

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.

7. On tab Technical Settings and Load Balancing select the relevant option according to your system’s 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 system’s client number. 11. Activate Current User.

12. For Trust Relationship activate Yes.

Note

Ensure that you have previously created the trusted relationship, as outlined in

Defining Trust between the SAP NetWeaver Gateway Host and Your SAP System [Page36].

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 object S_RFCACL assigned to it on the SAP system, select Remote Logon. You should not see any error messages in the status. If

(36)

Defining Trust between the SAP NetWeaver Gateway

Host 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 Suite system (backend system) to be the trusting system, and the SAP NetWeaver Gateway host to be the trusted system.

Note

This 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: <system id >CLNT<Client>..

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.

6. On tab Technical Settings and Load Balancing select the relevant option according to your system’s 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.

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.

(37)

Configuring SAP System to Accept Assertion Tickets

from 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-based Web service

communication.

To accept SAP assertion tickets, proceed as follows:

1. Make sure that the profile parameters are set as outlined inProfile Parameters [Page

10].

2. In your backend system go to transaction SSO2 to run the SSO2 administration wizard.

Note

If transaction SSO2 does not work, use STRUSTSSO2 to import the certificates from the SAP NetWeaver Gateway server; you must import them manually. For further information, seeUsing Transaction STRUSTSSO2 in SAP System >= 4.6C [External].

3. Enter the Type 3 RFC destination created above (for your SAP NetWeaver Gateway system) or the Host Name and Instance Number for the SAP 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

(38)

Configuring the SAP NetWeaver Gateway Host to

Accept 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-based Web service communication. Proceed as follows:

1. In your SAP NetWeaver Gateway system make sure that the profile parameters are set as outlined inProfile Parameters [Page10].

2. In your SAP NetWeaver Gateway system go to transaction SSO2 to run the SSO2 administration wizard.

Note

If transaction SSO2 does not work, use STRUSTSSO2 to import the certificates from the SAP NetWeaver Gateway server; you must import them manually. For further information, seeUsing Transaction STRUSTSSO2 in SAP System >= 4.6C [External].

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 the appropriate fields. 4. Choose Execute.

Note

You 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.

(39)

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 you thus 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 local system. 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 an inbound request is the local SAP NetWeaver Gateway instance itself.

NetWeaver Gateway OData Channel Configuration Connection Settings 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 Description

SAP 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 BOR Generator locally.

If you activate Local GW for a SAP System Alias called LOCAL the RFC Destination is usually NONE.

For Local App

The system alias is to be used by BEP. For more information, see the F1 help in the system andHub OData Channel with IW_BEP Installation [External].

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 the value to set for your GSDOs:

In transaction SPRO open the SAP Reference IMG and navigate to: SAP NetWeaver 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 your GSDO type and choose GSI Implementation.

(40)

Field Description

system ID. The SAP target system, together with the target client, determines the 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.

Note

We recommend that you check the system alias configurations usingCheck SAP System Aliases [Page159].

(41)

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 servers can 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.

Note

Before 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.

(42)

Settings for OData Channel Service Development on Backend

System

OData Channel implementations retrieve the data from an SAP Business Suite (backend) system. Both application logic and metadata are hosted on the SAP Business Suite system. After the ABAP development activities, that is developing the runtime service and the model provider class, the services need to be activated.

For this the following registration process is done on the SAP Business Suite system: Maintain models

Maintain 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 SAP NetWeaver Gateway Service Enablement Backend OData Channel Service Development for Backend OData Channel Maintain Models and Maintain Services. For more information seeMaintaining Models and Services [External].

To get an overview of the settings the IMG activity SAP NetWeaver Gateway Service Enablement Backend OData Channel Service Development for Backend OData Channel

Display Models and Services is provided. Note that this activity is read-only. For more information seeDisplay Models and Services [Page44].

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. SeeMaintain Services [External].

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, seeOData Channel Generation Tool [External]. In addition, an activity is provided to define parallelization of batch queries. For more information, seeDefine Parallelization of Batch Queries [Page45].

Repository Objects

The registration process of OData Channel models and services is unique: In order to allow collecting authorizations per data provider class (DPC) a repository object type is available. This is integrated into transaction SU22. Thus two additional repository object types exist in SAP NetWeaver Gateway. For more information seeRoles in the SAP NetWeaver Gateway Landscape [External].

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 unique services. You create service /MYNAMESPACE/MYSERVICE with version 0001 which then results in http://<host>:<port>/sap/opu/odata/mynamespace/MYSERVICE.

(43)

Prerequisites

The following entities must exist:

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

More Information

(44)

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 and navigate to SAP NetWeaver Gateway Service Enablement Backend OData Channel Service Development for Backend OData Channel Display Models 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 registered services and models. The maintenance activities are done viaMaintaining Models and Services [External].

(45)

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 is available: In transaction SPRO open the SAP NetWeaver reference IMG and navigate to Gateway Service

Enablement Backend OData Channel Service Development 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 just the 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 Queries

Mark 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 than the maximum number of dialog work processes available at parallelization time which is based on system settings (transaction RZ11, profile parameters rdisp/rfc*) . Zero (0) means it only depends on current system resources. Default value: 0.

(46)

Settings for OData Channel Service Development on the Hub

System

After you have made the relevant configuration settings in the SAP Business Suite system in which component IW_BEP is installed (SAP NetWeaver releases lower 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 in the SAP NetWeaver Gateway hub system in which you intend to develop OData services.

Note

If 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 in your 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 as standard. For more information, seeDeployment Options [External].

Assigning SAP System Alias to OData Service [Page47] Activate and Maintain Services [External]

Multiple Origin Composition [Page48]

(47)

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 the corresponding backend system. The system can correctly identify the SAP system that is responsible for processing (managing and storing) the data of an inbound request. Thus, OData Channel based content which is developed either on the SAP NetWeaver Gateway hub system or on a SAP Business Suite backend 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 same system 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 are supported, if you specify corresponding roles/host names and system aliases. The roles are only for user grouping and do not need to have any special authorization.

Example

It 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 the system 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 aliases are 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 to the 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 and navigate to SAP NetWeaver

Gateway :

For applications based on backend OData Channel system navigate to OData Channel Administration General Settings Assign SAP System Aliases to OData Service .

For applications based on OData Channel with IW_BEP on the hub navigate to OData Channel Development with IW_BEP Registration Assign SAP System Aliases to OData Service .

Note

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

(48)

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 different backend systems while using the same user. Thus a service can be made available for several system aliases. For example, you could have two identical systems, 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 cannot be done in all configured backend systems, but only in the default system.

Note

This 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, seeRegister your Service in the SAP NetWeaver Gateway System [External].

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 4–digit 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.

(49)

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://<host name>:<port>/sap/opu/odata/iwfnd/RMTSAMPLEFL IGHT;mo/

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

Parallelization of Multiple Origin Composition

When 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 the following configuration parameters:

Minimum Number of Backend Systems can have following values: o 0: No parallelization

o n: 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 can use parameter Maximum Number of Parallel Backend Calls to limit the use of current system resources. The default value zero (0) means it only depends on current system resources.

Performance Improvement

In 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 is just the maximum duration of all backend calls and means a minimal overhead for parallelization.

Parallelization and Skiptoken

(50)

Changesets

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

Configurating SAP NetWeaver Gateway 2.0

Copyright

Icons in Body Text

Typographic Conventions

Table of Contents

SAP NetWeaver Gateway Configuration Guide

Implementation Guide

Additional Software Components

Consumer Settings

Basic Configuration Settings

Profile Parameters

More Information

ICF Services

Standard Mode

Compatibility Mode for SP02

Alias Handling in ICF

More Information

Changing Password for Initial Logon

Using an ICF Node for Changing Passwords

Logoff URL

Language Settings

OData Channel Configuration

SAP NetWeaver 7.00 and 7.01

SAP NetWeaver 7.02 and 7.31

SAP NetWeaver 7.40

Settings

More Information

User, Developer, and Administrator Authorizations

SAP NetWeaver Gateway Developer Role

SAP NetWeaver Gateway Administrator Role

SAP NetWeaver Gateway User Role

SAP NetWeaver Gateway Support User Role

More Information

Creating and Assigning Roles

Connection Settings on the SAP NetWeaver Gateway Hub

System

Connection Settings: SAP NetWeaver Gateway to

Consumer

Creating a bgRFC Destination for Outbound Queues

Registering the bgRFC Destination for the Outbound

Queue

Creating the bgRFC Supervisor Destination

Connection Settings: SAP NetWeaver Gateway to SAP

Systems

Creating a Type 3 RFC Destination on SAP NetWeaver

Gateway Host to SAP System

Defining Trust between the SAP NetWeaver Gateway

Host and Your SAP Systems for Type 3 Connections

Configuring SAP System to Accept Assertion Tickets

from SAP NetWeaver Gateway

Configuring the SAP NetWeaver Gateway Host to

Accept Assertion Tickets from SAP Business Suite

Systems

Creating the SAP System Alias for Applications

Activating SAP NetWeaver Gateway

Settings for OData Channel Service Development on Backend

System

Repository Objects

Prerequisites

More Information

Displaying Models and Services

Define Parallelization of Batch Queries

Settings for OData Channel Service Development on the Hub

System

Assigning SAP System Alias to OData Service

Multiple Origin Composition

Parallelization of Multiple Origin Composition

Performance Improvement

Parallelization and Skiptoken

Changesets

More Information