Integrate Hana DB with SAP Lumira

How To Integrate Hana DB with SAP Lumira

This blog describes simple steps on How to Integrate SAP Hana Database with Lumira .

I have also give overview on how the data can be seen in different ways like pie chart, cross tab, heat map, in graphical representation etc.

SAP Lumira don’t require any connection.

SAP HANA connection is embedded inside the SAP Lumira.

* Lumira is integrated with Hana by using JDBC connection.
* Lumira is all self-service BI.
* Lumira is one tool with rich visualization. Lumira can work as software as a service and also on premise.

 

In order to, connect to sap hana.

Click on file

Click on new

You can connect to SAP HANA Modeling Views in SAP Lumira. This can be done in the following way−

* Connect to SAP HANA

Select connect to sap hana

click on next

It will show you all the HANA Modeling Views that have been recently used. Select the option “Connect to SAP HANA” and then Click the Next button ,this will allow you to access the data in read mode and you can visualize the data in the form of charts.

In the next screen provide the details of HANA system i.e. Host Name, Port Number, User Name and Password.

Click on connect and you are all set.

Search our package and select the view and click on Next

Select Measures and Dimensions you want to add to the data set and click the Create option.

Select required columns, drag and drop the fields.

Here we drag and drop the company code, revenue, Dimension-MAKTX and net revenue.

First, I drag and drop the company code and then revenue.

 

Here we see the graphical representation of company code and revenue.

Again, drag and drop net revenue as shown below.

Here we see the graphical representation of revenue and net revenue by company code.

 

If you want to see acquired sales deduction, in that case drag and drop the Accrued sales deduction.

Here we see graphical representation of revenue, net revenue and sales deduction as shown below.

If you would like to see Dimension MAKTX, then Drag and drop MAKTX under Dimensions Y Axis.

In the below screen we can see the graphical representation of revenue, net revenue and accrued sales deduction by company code and MAKTX.

If you  would like to see this data in different ways, in that case we have to use different charts, table etc.

We have different types of charts.

For example, if you want to see data in pie chart, then click on icon Pie Chart as shown below in diagram.

Similarly , if you want to see data in Donut chart, then click on icon Donut Chart as shown below

 

We  also have option of Map Charts , below diagram shows output in Heat Map model.

 

Another example, here we take cross tab under Tables , it displays data in cross tab model.

As of Lumira Designer 2.0, only HTTP connections to SAP HANA are supported. Such connections need to be configured according to the following documentation in order to be visible to Designer:

https://help.sap.com/viewer/b2ab3c5d05314085985c4b78aa17db2d/2.0.0.0/en-US/c8df56884c2844b8ab1f0e1bb17cf9f3.html

SAP Lumira Connectivity Matrix (for Lumira 2)

What’s New with SAP Business Objects Lumira 2.0 Launch blog series: https://blogs.sap.com/2017/04/18/whats-new-with-sap-businessobjects-lumira-2.0-launch-blog-series/

Register for the Lumira Newsletter: http://info.sapdigital.com/LUM-NSLTR-REG.html

Regards,

Sumit

 

  http://bit.ly/2DwXwks #SAP #SAPCloud #AI

SAP Analytics Cloud Live Universe Consumption – architecture and process flow diagrams

Connecting the on-premise world to the cloud presents many questions and sometimes a picture is the best way to provide an answer. This is why I’ve published architecture diagrams and process flow diagrams for SAP Analytics Cloud consuming SAP BI Platform Universes in a ‘live’ mode.

Live Universe Connectivity Architecture

I’ve presented two diagrams in the wiki:

* a PATH connection, which will use a Reverse Proxy
* a DIRECT connection, which uses CORS bypassing the need for a Reverse Proxy

I encourage you to study the diagrams and here are some noteworthy points:

* The database performance is critical since, the data stays on-premise. It’s never uploaded to the Cloud. Only the model metadata is uploaded to the cloud.

* The BI Platform uses the WACS (Web Application Container Service) as the gateway into the platform via the REST API that it hosts. This in turn talks to

* CMS and the FRS (for the obvious reasons)
* the DSL Bridge Service (to get the universe metadata and map the SAC model to Universe queries)
* Web Intelligence Processing Server (where a .WID is created and a data provider in that document is created and run against the database for each query asked by the SAP Analytics Cloud client)

* Most of the load is on the DSL Bridge and the Web Intelligence Processing Server, so you’ll need to make sure you have these services sized appropriately.
* Each user of SAP Analytics Cloud will connect and login to the BI Platform and thus consume and inherit the security model. Today SAP Analytics Cloud support SAML for SSO, or you can just prompt the user for a user/pass.
* SSL is mandatory and if your organisations browser policy enforces only trusted certificates, you’ll need to make sure the SSL certificate you use will be valid.

Process Flow diagrams

To really help your understanding of the architecture its best to look at the 5 process flow diagrams I’ve created in the wiki. I walk you throw, step by step, from creating a new connection, to creating a model and then using that model to build visualisations and sorting and filtering upon it.

Please do study them. Here’s some additional context to help answer your questions!

* Actions such as sorting and filtering are performed by the client, the backend isn’t hit.
* Actions such as filtering of data are all pushed down to the database.

* The Web Intelligence document is

* created in the BI Platforms users a favourites folder called “BOELiveProviderTempFolder” (name can be configured).
* stores the query and results for each query to the database. If you use my Auditing Universe you’ll see a new data provider is created for each query sent. Currently there’s no smart re-use of existing data providers.
* deleted when the user logs out of SAP Analytics Cloud.

Please do post comments, feedback, questions to this blog rather than one the wiki pages. I will try my best to reply as soon as I can. Please do review other people’s comments and my replies before you post!

As new features and function come into the product I will update the diagrams. I will be publishing a lot more content for consuming Universes, so stay tuned and follow me!

Matthew (Twitter @MattShaw_on_BI) http://bit.ly/2FGWRD5 #SAP #SAPCloud #AI