Skip to Content

How to Setup Connection to a Remote HANA System for SAP Cloud for Analytics via SAP Web Dispatcher

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:

 

  1. High-level of data privacy. Data is not moved from corporate network to the cloud at all.
  2. 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:

 

     How to Setup Connection to a Remote HANA System for SAP Cloud for Analytics via SAP Web Dispatcher

 

I hope you will like it, and let me know if you have any question.

 

Enjoy! 🙂

29 Comments
You must be Logged on to comment or reply to a post.
    • If you’ve got an error (5), this is probably a download error. In my case, after using the download manager to download SAP Web Dispatcher, I was able to extract successfully using SAPCAR.

  • @Dong I am facing an error that I can’t seem to resolve. I would appreciate your advice on it.

    After arriving at Step 8 of your guide (sapwebdisp pf=sapwebdisp.pfl), I have received the message in cmd that says “SAP Web Dispatcher up and operational…etc.”

    The problem is whenever I go to https://localhost:4310/sap/wdisp/admin/ I get 404 error Resource not found.

    I appreciate the help of the community on this error.

    Thank you,

    Moe

      • Thank you for the response. I have now arrived at step number 26 – https://<WebDispatcherFQDN>:4310/sap/fpa/ui/tenant/003 <– I have replaced the <webdispatcherfqdn> by my domain and the tenant number to 6 (which is my tenant number).

        The error I received is 503 Service not available even though the web dispatcher gave me a “fully operational” message after adjusting the sapwebdisp.pfl and the adding the rewrite.txt.

        I would appreciate your guidance Dong 🙂 Please bear in mind that I have done a ton of troubleshooting prior to this message.

  • Hi Dong,

    I have arrived at step# 34, creating the connection in C4A – I am getting very close!

    **Before I present the challenge I am facing, I believe there is a typo in the screenshot/info on step# 28. Since we are doing an http connection, the port should be 8010, not 4310.

    So the challenge I am facing is C4A is giving me an error when I try to connect to HANA. Here is what I have done.

    1) I have written the correct line in the sapwebdisp.pfl and rewrite.text. Here is a screenshot.

    1_Sapwebdisp.pfl.PNG

    2) I verified that I was able to access HANA XS, logged in and received the items in this screenshot.

    2_HANA_Test_success.PNG

    3) Finally, I went to the C4A website using my localhost, 4310 port, and /sap/fpa/ui/tenant/006. This is the error I received.

    3_Firefly_Error_503.PNG

    I hope the material I am posting here helps other members in tackling their problems when they attempt to connect to HANA. Again, I appreciate all the support you are providing Dong.

    • It is NOT a typo in step 28. Although the communcation between Web Dispatcher and HANA is HTTP, the communciation between Web Dispatcher and the web browser is always HTTPS at port 4310 (SRCSRV). HANA’s HTTP port is already defined in EXTSRV.

    • The HANA Cloud Connector is unrelated to connecting C4A to on premise HANA or HCP. HCC is used to connect to UNX, BW, and BPC.

      Hope this helps.

      Moe

        • Hi Jorn,

          That’s an excellent observation! I don’t think you can access on-premise HANA using HCC because otherwise it would’ve been mentioned on the user guide, but I won’t discourage you from playing around with it. 🙂

          Like I said in my previous comment, HCC is only used for unx, bpc, and bw, not hana (at least what the user guide entails).

          Moe

        • Hi Joern,

          HCC is used for Data Acquisition mode only, and reverse proxy is used for online/real-time data access. Data Acquisition mode is not available for HANA at the moment.

          Regards,

          Dong

      •  

        Former Member

        I am trying use a java OData which is deployed in our XSA HANA system(on premise). When i try to use the OData in BOC application it is not working. In some the documentations i read it says for using the OData in on-Premise system we must have a HANA cloud connector in the system. Can you please help me in this scenario ?

  • I have managed to set up Web Dispatcher for both C4A and Hana database and the test URL-s work fine. However I cannot login from the /sap/fpa/ui/tenant/xxx URL because I get wrong credentials error.

    When I log in from https://epmxxxxxxxxxx.hana.ondemand.com/y/Z (where y.Z is the content namespace seen in the Administration area of the account) I can use the same credentials to log in. But with the /sap/fpa/ui/tenant/xxx I get wrong credentials.

    Which credentials should I use there to log in to C4A?

  • Hi.

    First of all, thanks for the guide. It was very helpful.

    My question is:

    I setup everything as mentioned.

    I can connect with the externel URL to the BusinessObjects Cloud via Webdispatcher.

    When I try to connect to my HANA TENANT with external URL the Webdispatcher routes correct to the HANA but the HANA Webdispatcher receives the external URL not the internel HANA URL and so it gives the error:

    IcrFindTargetSystem: No system found for vhost: “external.URL” addr: “HANADBIP:8000” url: /sap/bc/ina/service/v2/GetServerInfo

    The browser logicaly gives me a 503.

    Any ideas?

  • Hello Dong,

    Connection to Remote hana system for SAP cloud for analyticss via web dispatcher is done successfully.

    I am able to login to reverse proxy URL set from HANA B with user having INA roles.

    But after logging in ,Nothing is displayed.

    I am unable to follow step 32 mentioned in link.getting the error as “the remote server could not be found.Kindly check the Live data connection details”

    Please help us 🙂

    Thanks,

    Charan

  • Hello Dong,

    I am trying use a java OData which is deployed in our XSA HANA system(on premise). When i try to use the OData in BOC application it is not working. In some the documentations i read it says for using the OData in on-Premise system we must have a HANA cloud connector in the system. In one of the comments here I saw HCC is not needed for HANA system. If not HCC why is my OData not getting connected in BOC application. Can you please help me in this scenario .

    Thanks & Regards

    S.Balavignesh