Quick Starter Configuration Guide -

SAP Gateway
created by Andre Fischer on May 14, 2013 4:55 PM, last modified by Andre Fischer on Mar 27, 2015 4:36
PM
Version 13
inShare2

Updates:
o July 8th, 2013: Fixed typo in step 2 (the description of step for system alias maintenance) and explained importance of the
field system id in this step.
o July 9th, 2013: According to the hint from Roy I now recommend to activate the flag "for local app"
o June 26th, 2014:
Added the information that the prerequisites are fullfilled automatically when using SAP NetWeaver 7.40.
Changed the name SAP NetWeaver Gateway to the new product name SAP Gateway
o March 27th, 2015: Updated links to the most recent online help version (GW 2.0 SP10)

In the past I have frequently been asked for a quick starter configuration guide for SAP Gateway since the configuration
guide does explain all options which might confuse people.

In this document I therefore want to describe the basic configuration steps that have to be performed to activate SAP
Gateway if
1. embedded deployment has been chosen or if
2. IW_BEP is deployed on the hub or if
3. SAP NetWeaver 7.40 is used

in these cases the core components for SAP NetWeaver Gateway (GW_CORE, IW_FND and IW_BEP) and any optional
backend components are deployed together in the SAP Business Suite backend system or at least IW_BEP is deployed on the
hub system which is also a good idea in case you want to set up a hub-based deployment.In case SAP NetWeaver 7.40 is
used the software component SAP_GWFND is deployed as part of the SAP Basis which comprises the functionalities of the
AddOn's (GW_CORE, IW_FND and IW_BEP).

So this quick starter configuration guide will also help you if you set up a Gateway hub system.

After you have performed these three steps you should be able to develop a service on the hub / embedded system and
publish it. You will nevetheless have to perform additional configuration steps later on as described in theconfiguration
guide.

Prerequisite (if the system runs on 7.0, 7.01, 7.02 or 7.31):

Deploy the Add-Ons IW_BEP, GW_CORE and IW_FND
As a prerequisite you have to deploy at least the following three add-ons IW_BEP, GW_CORE and IW_FND using
transaction SAINT.

When using SAP NetWeaver 7.40 this step is not necessary since the software component SAP_GWFND is already deployed
as part of SAP Basis.

Step 1: Activate SAP Gateway

As described in the Online Help you start transaction SPRO and navigate to the Activate or Deactivate SAP NetWeaver
Gateway node in the implementation guide (IMG).
Step 2: Create a SAP System Alias
You now have to create a system alias entry that points from the hub system to the backend system. Since you have chosen
an embedded deployment you will create a system alias entry LOCAL using the RFC destination NONE. This is described in
the Online Help.
Here you fill in the following values:

Field Value
SAP System Alias LOCAL
Description Local Gateway
Local GW X
X (recommended for performance reasons because no RFC destination is used and thus rfc calls are local and
For Local App more stable)
Software Version DEFAULT
System ID The SID of your backend system (here GWM)
Client The client you are in (here 800)
WS Provider
System

This is shown as an example in the following screen shot:

Caution:
You must maintain the field System ID though it is not mandatory. This is because transaction SEGW when being run in the
backend selects all system alias entries of the backend system from where it calls the hub using the SID of the backend as a
filter. If no value is maintained the system alias will not show up in the list. If only one entry is found it is taken as a default
and no dialogue will show up.

Step 3: Create a Gateway Alias

This step is needed to have at least one entry for the Gateway hub in the Service Builder (transaction SEGW)
toregister services that you are going to develop. This is described in the online help.
Please note that this time you have to navigate to a different part in the implementation guide called Gateway Service
Enablement that contains the Gateway hub specific customizing settings.

Here you enter the following values

Field Value
Destination System GW_HUB
Client The client you are working in (here 800)
System Alias GWM (Enter a unique name for the host of SAP NetWeaver Gateway, for example the SID of your system)
RFC Destination NONE

This is shown as an example in the following screen shot.

Step 4: Activate node 'opu'

1. In a freshly installed system you have to activate the 'opu' node using SICF.

2. In the following dialogue you have to confirm that all sub nodes shall be activated as well

3. Press refresh
4. Expand the node 'opu' again and to check whether the changes have been performed

Step 5: Test Your Settings

You can now test your settings by developing a simple service using the Service Builder (transaction SEGW).

As you can see the name of the destination system of the SAP NetWeaver Gateway alias is shown in the Service
Maintanance node in SEGW.
When choosing Maintain in the context menu the Activate and Maintain Service transaction is started on the hub system.
Please note that the service has been registered for the system alias LOCAL that you have maintained in step 2.

Step 6: (For Development Systems Only !)

Since this quick starter configuration guide will probably mostly used for development or test systems I would like to
recommend to raise the Error Log Level for the error log in IW_BEP and IW_FND.

Use the following transactions to change the settings for the Error Log Level from Secure to Full as shown in the following
screen shots:

Backend Error Log --> transaction /n/iwbep/error_log . There from the menu choose Error Log --> Global Configuration

and

Gateway Server Error Log --> via transaction /n/iwfnd/error_log . There from the menu choose Error Log --> Global
Configuration