Update Oct 11, 2016: with the introduction of Simple URL and built-in SAML authentication to SAP BusinessObjects Cloud in the recent releases, significant architectural changes have been brought into the BOC landscape that have implications on the reverse proxy configuration. I have written a new blog post that covers the necessary changes. As rewriting URLs in HTML becomes necessary in most typical scenarios, Web Dispatcher is not the recommended reverse proxy anymore, as it lacks of HTML rewriting capability. Check out the new blog for more details: What's Changed - Setup Remote HANA Connection with SAML SSO in SAP BusinessObjects Cloud (link)
Over the past few months, I have gotten to know a lot of customers who are trying out SAP Cloud for Analytics (C4A) and would like to connect it to their on-premise/remote HANA systems. The main benefits are:
High-level of data privacy. Data is not moved from corporate network to the cloud at all.
Online/real-time data access to on-premise HANA
In order to achieve that, a reverse proxy needs to be setup in the corporate network. It does take quite a few steps to properly setup a reverse proxy for C4A, so I have published a how-to guide on setting up SAP Web Dispatcher as a reverse proxy for C4A and HANA: