Thursday, 15 April 2021 17:58

Modeling in SAP HANA Cloud (part 2): starting with the project files and users

Written by Witalij Rudnicki
Rate this item
(0 votes)
Source https://blogs.sap.com/2021/04/16/modeling-in-sap-hana-cloud-2-understanding-the-project-sap-bas/
“© 2020. SAP SE or an SAP affiliate company. All rights reserved.” “Used with permission of SAP SE”

So, in the previous part, we worked to set up the project in SAP Business Application Studio that would allow us to do the modeling (creation of the calculation views) in SAP HANA Cloud. These models will be used in SAP Analytics Cloud later on.

Reopen the project

First, because it is a new day, I need to open my project and start my SAP HANA database in the SAP HANA Cloud trial:

  1. Go to my SAP Business Application Studio trial (either bookmarked or from https://account.hanatrial.ondemand.com/trial/#/home/trial),
  2. Start my Dev Space TPCDS, and open it when started,
  3. Open my last tpcds project (aka workspace), e.g. via File -> Open Recent Workspace in the studio.

Bu now the Cloud Foundry (CF) login token has expired since I worked with the environment last time, so

  1. I want to login into my CF space in the SAP Business Technology Platform (SAP BTP) trial in eu10 region again;  I like using the SSO option for that with
    cf login --sso -a https://api.cf.eu10.hana.ondemand.com,
  2. I want to start my SAP HANA Cloud, SAP HANA database vital-hc-hana; and instead of going to the UI, I like using the command line for that with
    cf update-service vital-hc-hana -c '{"data":{"serviceStopped": false}}'.

So far, so good and we can continue from where we left before.

Understand the structure of the project

In order to build calculation views, we are working on the SAP HANA Multitarget Application (aka MTA) based on the Cloud Foundry programming model.

It is just that in the case of analytics modeling our MTA contains only one module called db used to build and deploy the SAP HANA database artifacts.

mta.yaml

The elements and dependencies of the multitarget application are defined using mta.yaml file (1).

The wizard generated an MTA with one module db (2) that currently requires a single hdi_db resource. This is the target container service.

This resource hdi-db (3) is an HDI container that has been created by the wizard as well. The name of the container is not hard-coded but is coming from a variable ${service-name}. In turn, it is used as well as a property in the db module’s requirements via a reference~{hdi-container-name}.

The SAP HANA Projects pane in the Explorer of the studio makes it easy to see the structure of the project, including object names i/o variables. We can use as well pre-installed mtacommand-line tool (4).

mta resolve -m db -p mta.yaml 
Continue reading here
Read 106 times

Leave a comment

Make sure you enter all the required information, indicated by an asterisk (*). HTML code is not allowed.