Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

SAP Netweaver Gateway Configuration through SPRO

Dear All ,

We need a help for SAP Net Weaver Gateway configuration.

Currently we have Installed  Net Weaver Gateway 2.0 SP9 . We have Installed IW_BEP in Back end SAP system and Other two GW_CORE and IW_FND in a separate server. Now what are the configuration like RFC destination, Alias names et. required in both SAP back end system as well as Gateway Hub system through SPRO. I have searched in the SCN but most of the configuration helps are related to embedded system where all the three components are installed in SAP back end.  Some others configuration helps are also available but these are related to deployment where Three components  IW_BEP, GW_CORE and IW_FND are installed in separate server but not in SAP back end.

Please help.




You need to do following steps:

In Backend:

     1. Create RFC destination in your backend system(where IW_BEP is installed) to Hub system(where GW_CORE & IW_FND are installed). PS: Please check the user you are going to use for registering, has developer access in Hub system also.

     2. Create a System Alias in the backend for the Hub system. ( SPRO > SAP Netweaver > Gateway Service Enablement >  Backend OData Channel > Connection Settings to SAP NetWeaver Gateway).

In Hub System:

     1. Create RFC destination system (in Hub) to your backend system.

     2. Create system alias in Hub for backend. ( SPRO > SAP Netweaver > Gateway > OData Channel > Configuration > Connection Settings > SAP Netweaver Gateway to SAP System > Manage SAP System Aliases).

The sample config is like: (the highlighted one)

Here Local GW and Local App are not checked because this alias will not work as local gateway (its a backend system and does not have FND component). The local app is also not checked because the DPC & MPC classes are not defined in the local system (these classes will be defined in the backend). Leave software version as Default. Specifying System ID and Client is optional. Defining these two will help in F4 help of system alias in the backend system at the time of registering the service.

With these steps you should be able to create the project in the backend system and register it on the Hub system also.

1 View this answer in context
Not what you were looking for? View more on this topic or Ask a question