Create HTTP destination from SAP PO to the backend system where the OData service resides.

Create HTTP Destination to the Backend System: To create the http destination from SAP PO to the backend system where the OData service resides; perform the following actions;

1.Navigate to the NetWeaver Administrator URL

http://:/nwa

2. Navigate through the following to Configuration è Destinations
3. Click on the Create button; choose the Hosting System, assign a Destination Name and select the Destination Type “HTTP“:

4.Click on the next option from the wizard and provide the connection information to the SAP Gateway IW_BEP service;

5. Select the following option to access IW_BEP service in the SAP backend and provide the necessary logon credentials;

Click on the finish tab to complete the process of creating the http destination.

6. Additionally, the new created destination can be tested by clicking the Ping Destination button; if the configuration is done properly, the ping operation should return a successful message: “     Successfully connected to HTTP destination CRD with response code 200. Content type text/html”

Register OData Service in the OData Provisioning Administration: Once the http destination to the backend system where the OData service resides has been set up, then we are ready to register our OData service as a Gateway service. To do this, perform the following actions;

1. Navigate to the SAP PO Gateway OData Provisioning Administration via the url below:

http://:/igwj/Admin 

NB: It is important to note that these two roles (GW_USER and GW_ADMIN) should be added to your user in order to be able access the OData Provisioning Administration and perform necessary actions

2. Once in the OData service cockpit, select the “Register a New Service”

3. Choose the http backend destination created earlier in the NetWeaver Administrator and do a wild card search, select the OData service created earlier in the Backend system from the list;

4. Click on the service to be registered and select the “Register” option, once this is done successfully, the following message is popped up;

5. The Service Document can be opened to view the details of this service in the browser, the metadata can also be accessed by providing the following information in the URL extension of the service: /$metadata eg;

http://:/igwj/odata/SAP/ZODATA_SERVICE_SRV;v=1/$metadata

The metadata URL contains the EDMX (Entity Data Model for XML) which contains the service definition for the OData service.

6. Click on the service name to view all the properties of this gateway service;

After all of the steps above have been performed, the Gateway service is ready and available for consumption by different devices and applications.