This series of blog posts will cover how to connect an instance of SAP Cloud Platform, SAP HANA Service (Cloud Foundry) with SAP Analytics cloud to consume Calculation Views in an HDI container.
If you are looking to connect an on-premise SAP HANA system to SAP Analytics Cloud with XS Advanced, check
this series of blog posts.
Disclaimer/Motivation
I will be replicating these steps in different machines or, even worse, instructing people to do this. So I have streamlined this process as much as I could. In other words, this is the result of my being both lazy and having a short attention span (especially when a task is rewarding yet boring...).
Prerequisites:
Contents
Download the on-premise HANA Analytics Adapter
Adapt the adapter
Change the tenant mode for the UAA service (needed in version 1.5.2)
Edit mtad.yaml
Extract the mtar
Deploy the app
Check the application
Download the on-premise HANA Analytics Adapter
This is one of the reasons why I added the disclaimer. I’m using the on-premise adapter for cloud foundry. I did not see a reason not to, but if you have a valid one, I’m listening.
Download it from here:
https://tools.hana.ondemand.com/#hanatools
Adapt the adapter
(Yeah, I did that on purpose)
This is where WinRAR becomes important. WinRAR allows me to modify the MTAR without unpackaging it. Which means that if you do not have the builder installed, it does not matter. It’s also one less command line.
This is the zip file:
And it has an MTAR in it:
Double-clicking on that one:
This is the actual application you will deploy.
You will change some configurations that affect the way the application interacts with the UAA service in your Cloud Foundry subaccount. You will also change the CORS configuration so that your SAP Analytics Cloud connection is not rejected.
Start by xs-security.json.
Change the tenant mode for the UAA service (or not... as you prefer)
I am doing this because I do not have/need a multi-tenant installation.
Right under the “xsappname”, add:
"tenant-mode": "dedicated",
As follows:
If you are deploying this in multiple spaces in the same subaccount, you will need to change the xsappname.
Save the file and go back to edit the application. Say
yes to keep your changes:
Edit mtad.yaml
You will need the hostname of your SAP Analytics Cloud tenant. You will find it in the URL:
Back to the WinRAR: Go into the META-INF folder. Edit the mtad.yaml.
Add the host (without “https://”), remove the port and add the protocol
Save the file. You’ll be asked to confirm to save the changes to the archive.
Of course, the answer is Yes.
Close that window. The archive containing the mtar will also ask if you want to save the changes… Guess the answer!
Make sure your changes are getting saved... guess I don't need to explain why this is important, do I?
Extract the MTAR
Somewhere you can access from the CLI console.
Deploy the app
You are now ready to deploy the adapter.
Get the endpoint of your subaccount:
Log in to the CLI and deploy the archive:
cf login -a <<endpoint>>
cf deploy <<mtar>>
I promised a lazy installation but I am using the CLI? Yes, because this file is heavy and I prefer a verbose console when Murphy's law applies.
Check the application
You now have a running application. On clicking the endpoint for xsahaa-entry…
…you should get to the authentication splashscreen
And this is the next thing you will configure... in the next blog post.
But, wait! Some community service here... Is this helpful? Show some appreciation by hitting the
like button on the top! (and be sure to do that with any other author going out of their way to publish their findings
😉 )
Here's the second part:
https://blogs.sap.com/2019/04/24/connecting-the-sap-hana-service-on-cloud-foundry-to-sap-analytics-c...