Activating SAP Gateway OData Services
The launchpad and launchpad designer need a reverse proxy to direct the browser requests to either the front-end system in which the JavaScript sources are stored, or to the SAP Gateway system in which the OData services are located.
Prerequisite
When activating the OData services, the system alias must be the local system.
To configure that a local connection to SAP NetWeaver Gateway is used, proceed as follows:
- In Customizing (transaction SPRO), choose and launch the IMG activity Manage SAP System Aliases.
- Provide the following:
Field
Value
SAP System Alias
Name of the system alias (for example, LOCAL).
Description
Descriptive text for the system alias.
RFC Destination
NONE
Local GW
Make sure the checkbox is marked to specify that the system alias points to a local SAP Gateway instance.
Procedure
-
Using the system alias defined in the Customizing activity Manage SAP System Alias, in Customizing choose and activate the following OData services:
- /UI2/PAGE_BUILDER_CONF -This is used by the launchpad designer.
- /UI2/PAGE_BUILDER_CUST - This is used by the launchpad designer.
- /UI2/PAGE_BUILDER_PERS - This is used by the launchpad.
- /UI2/TRANSPORT- This is used by the launchpad designer.
- /UI2/INTEROP - This is used by the launchpad and launchpad designer.
For information about activating these services, see the SAP Gateway Developer Guide at .
-
Call each service once.

