#5.pngThis is a part of the implementation details of How To… Implement End-to-End Push Notifications with HCPms and SAP Gateway.


Implementation Plan

/wp-content/uploads/2015/10/10_816239.png

Deploy and configure HANA Cloud Connector so that HCPms can talk to SAP Gateway Hub system over the firewall.


Steps to Implement


– Install HANA Cloud Connector


Have a read through the official HANA Cloud Connector documentation: SAP HANA Cloud Platform

and do the installation step.

– Configure the cloud connector for SAP Gateway


Click on the “Access Control” on the left side and press “Add…” for Mapping Virtual To Internal System. Select SAP Gateway pulldown.

/wp-content/uploads/2015/10/5_1_827336.png

In the Add System Mapping popup, enter your SAP Gateway Hub system host name and its HTTP port.

/wp-content/uploads/2015/10/5_2_827337.png

In the Add System Mapping – this one you can enter whatever host name and port# value.  For this example the port # is 443+Gateway Instance#.

/wp-content/uploads/2015/10/5_4_827339.png

Once you created the entry, click on “Add…” button of Resource Accessible On <hostname>:<port>.

/wp-content/uploads/2015/10/5_3_827338.png

Enter the value “/sap/opu/odata” for URL Path field. And choose “Path and all sub-paths”.

/wp-content/uploads/2015/10/5_5_827340.png

Once you save it – you should be able to confirm the status gets green.

/wp-content/uploads/2015/10/5_6_829450.png

Now your OData client should be able to fetch the OData via HANA Cloud Connector from outside the firewall!


– Update the Backend URL in HCPms


Let’s ensure if this roundtrip is really working fine.

/wp-content/uploads/2015/10/5_8_829018.png

Now you can use the new OData Endpoint URL for your app config in HCPms Cockpit.


Note – following steps requires RMTSAMPLEFLIGHT OData services (a part of the SAP Gateway installation) that should be already installed & activated.


Maintain your current application config on HCPms (remember you entered the dummy value for the Backend URL during the steps in #2?) Here you enter the new Backend URL. This example shows the host & port value, which was defined in the HANA Cloud Connector. The FLIGHT OData service document path is “/sap/opu/odata/iwfnd/RMTSAMPLEFLIGHT/” – for my demo system, the FLIGHT OData service on the SAP Gateway Hub system requires Basic Authentication, so the correct values are entered for Authentication Type, User Name, and Password too.

/wp-content/uploads/2015/10/5_7_829457.png

Time to test the new setting. Set those parameters for the REST client:

Method – GET

URL – https://<hcmps server>/<your app id>

Headers – X-SMP-APPCID = <your app connection id on HCPms> (May not required, depends on your HCPms account role setting)


The URL maps to the Service Document of the Gateway service.


Perhaps the browser will request for the basic authentication for HCPms credential. Your request & response should look like this – with the 200 OK in the response header. You should confirm the OData service document payload in the Response Body too.

/wp-content/uploads/2015/10/5_9_829459.png

Congratulations, now the roundtrip via the HANA Cloud Connector is successfully done.


What’s next? Let’s configure the SAP Gateway Hub.



#6 How To… Implement End-to-End Push Notifications with HCPms and SAP Gateway

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply