Currently Being Moderated

In this article I will discuss regarding experimenting the mobile UI for HANA. In particular about Android based chart showing the data coming from HANA.

I took a simple retail scenario using which I wanted to know about a product’s performance across various stores vis-a-vis quantity and price. I created a simple bar chart with X axis being the product name or store name and Y Axis being the quantity or total price of products. In my case I wanted to look into the product quality so as to check all the refunded product aggregations. In the practical scenario this would give the user an idea regarding how a product is performing in any geographical region or worst case if overall it isn’t doing well at all. Many actions could be triggered based on these evaluations.

 

I am listing below the step-by-step information of various tool usages and process to create this above business scenario’s prototype.

     Step1: Install HANA studio by taking the latest release. You can this link from the HANA community.

     Step2: Build your schema and load the data.

      In my case I created the transaction table which is from the POS(Point of Sale) counters. In this data I had the store name,      material/product name and transaction type such as ‘Refund’ or ‘Sale’ type and product actual price.

Step3: Download the Android Development Environment. Install the ADT plug-in for the eclipse.

Step4: I needed the chart library to display the bar chart on the android mobile app. I used the “achartengine” open source library to display a bar graph.

Apart from the above required software you would need Netweaver server and studio to develop & deploy the servlet.

 

 

The three layered architecture to consume the data is shown in the diagram below:

Apart from the above required software you would need Netweaver server and studio to develop & deploy the servlet.

 

 

The three layered architecture to consume the data is shown in the diagram below:

Apart from the above required software you would need Netweaver server and studio to develop & deploy the servlet.

 

 

The three layered architecture to consume the data is shown in the diagram below:

 

 

In the Android layer (UI) layer I implemented the following:

  1. Main android activity which fetches the data from the servlet using the HTTP GET.
  2. Data model of “Product & Quality” data which is stored in the list.
  3. Setting dialog is implemented to change the X-Axis and Y-Axis. X-Axis can be Product Name or Store Name and. Y-Axis can be quantity and total actual price.

Using the achartengine API chart gets displayed in the main view.

In the Android layer (UI) layer I implemented the following:

  1. Main android activity which fetches the data from the servlet using the HTTP GET.
  2. Data model of “Product & Quality” data which is stored in the list.
  3. Setting dialog is implemented to change the X-Axis and Y-Axis. X-Axis can be Product Name or Store Name and. Y-Axis can be quantity and total actual price.

 

Using the achartengine API chart gets displayed in the main view.

image_jpeg.jpg

 

In the Android layer (UI) layer I implemented the following:

  1. Main android activity which fetches the data from the servlet using the HTTP GET.
  2. Data model of “Product & Quality” data which is stored in the list.
  3. Setting dialog is implemented to change the X-Axis and Y-Axis. X-Axis can be Product Name or Store Name and. Y-Axis can be quantity and total actual price.

Using the achartengine API chart gets displayed in the main view.

In the Android layer (UI) layer I implemented the following:

  1. Main android activity which fetches the data from the servlet using the HTTP GET.
  2. Data model of “Product & Quality” data which is stored in the list.
  3. Setting dialog is implemented to change the X-Axis and Y-Axis. X-Axis can be Product Name or Store Name and. Y-Axis can be quantity and total actual price.

 

Using the achartengine API chart gets displayed in the main view.

21638_307_517_cache.jpg

Product and Quantity - "Article-3" is being refunded the most.

 

 

 

The servlet was implemented within the net weaver layer which fetches the data using the calculation View of the HANA newDB. This servlet currently returns a simple string response using comma as column separator and line break for the next record.

The HANA studio was used to create the POS transaction table and the sample data was loaded. Calculation view is created to fetch the data from the columnar POS transaction table and aggregate it across Product and Store id with quantity and actual price as measure.

 

 

Here is the screen shot of the simulator display for Android:

 

21645_316_532_cache.jpg

Conclusion :

The above retail example shows the feasibility of HANA to be consumed via mobile. I see unlimited potential of mobile apps consuming RESTful API’s (via HTTP GET /POST) or web services as HANA new DB provides the power of analytics in milliseconds.

 

I think we have huge potential of using HANA within mobile application and perform real real-time analytics on hand held devices for various industries.

Comments

Actions

Filter Blog

By author:
By date:
By tag: