This is second part of my blog where I describe the final steps of extending the Develop a cloud-based Web application with back-end connectivity (read-only) tutorial to include the SAP HANA Cloud Connector into the scenario.

In Part 1 of this blog I described how to install the SAP HANA Cloud Connector onto a VMware virtual machine running SUSE Linux Enterprise 11. Therefore you should now be ready to connect to it via

https://localhost:8443

/wp-content/uploads/2013/08/https_256510.jpg

Ignore the certificate warning by stating that you understand the risk and add an exception and you get to the login page.

/wp-content/uploads/2013/08/admin_256697.jpg

Login with Administrator / manage and change the password as you like. Next you have to configure your SAP HANA Cloud Connector to connect to your SAP HANA Cloud trial account (make sure you connect to hanatrial.ondemand.com.

/wp-content/uploads/2013/08/initial_256698.jpg

And here you are fully connected.

/wp-content/uploads/2013/08/connected_256699.jpg

Now you create a system mapping for the hosted ESPM system.

/wp-content/uploads/2013/08/mapping_256700.jpg

And add the OData resource.

/wp-content/uploads/2013/08/ressource_256701.jpg

You then create a new destination ESPM similar to the SNGATEWAY one but this time using the virtual host and port you defined in the cloud connector. Please make sure that you use proxy type OnPremise which tells the application to use the SAP HANA Cloud Connector.

/wp-content/uploads/2013/08/destination_256702.jpg

Finally adjust connectivity.js to

var serviceUrl = “/ProductCategories/ProxyServlet/ESPM/”;

to pick-up the new destination and redeploy. The result will be the same as without the SAP HANA Cloud Connector.

/wp-content/uploads/2013/08/proda_256703.jpg

However now you control access to the SAP Gateway service via the SAP HANA Cloud Connector and if you disable the URL path access will be denied and logged in the audit monitor.

/wp-content/uploads/2013/08/disable_256704.jpg

/wp-content/uploads/2013/08/error_256705.jpg

Re-enabling the URL path will make the application work again.

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