SAP HANA Overview
SAP HANA Architecture:
HANA Database Modules:
HANA Information Composer
Available interfaces for HANA DB:
HANA ABAP Interface
HANA JAVA Interface
HANA BW Interface
HANA SHINE is used as Development platform, it provides end – to – end solution.
HANA RDS is a Quick migration solution for HANA DB
Data replication Technologies available for HANA:
- SAP DS(Data services)
- SAP LT(replication server SLT)
- SAP DXC(Direct extractor connection)
Business Intelligence for HANA:
SAP BOBI 4.1
Data Mining Technology For HANA DB:
R – Language
L – Language
Cloud Technology for HANA DB:
For bulk data replication in HANA “SMART DATA ACCU” is used, Data services Agent is used for HANA HADOOP.
Data Access Connections for HANA DB:
There are five different replication technologies in HANA DB:
- ETL based Replication: example SAP DS.
- It is used as ETL tool from any Datasouce to HANA DB.
- TRIGGER based Replication: It is for SAP landscape transformation.
- Mainly used for SAP ERP to HANA, and DB to HANA.
- Log-Based Replication: e.g: SYBASE replication server and agent.
- SAP ERP to HANA & DB to HANA.
- WEB-BASED Replication: SAP HANA IC(Information Composer)
- It is used for XLS to HANA transformation via web.
- CLIENT BASED Replication with HANA STUDIO.
With this utility we can transform data from various tools.
HANA Studio is used for Txt/XLS to HANA transformation. HANA STUDIO SMART DATA ACCESS is used for transformation from
SQL DB, ORACLE DB, HADOOP, HANA, TERA DB etc to HANA. This utility is capable of bulk reading of data.
PACKAGES in HANA:
When we install HANA database we will be getting Standard packages. Available SAP Package (RDS à Rapid Deployment Solutions). We can also create custom packages by providing name, description, delivery unit, original language, personal responsible.
ICME( In-Memory Computing Engine)
This component resides under the Index server of HANA DB
Load Controller, Replication server
Metadata manager, Authorization manager, Transaction Manager
Sql Script, Sql Parser, Calculation engine, MDX parser
Relational engine(row store, column store)
Persistence Layer(page management, Logger)
Disk Storage(data volumes, log volumes)
Session management: When the client request for the data at runtime or when the user execute the report through reporting layer, session management will establish the connection to HANA DB and maintain it for each different client.
Request processing & Execution control: Once the session has been established, the SQL parser will take a control and call the respective engine accordingly. All the MDX queries will be processed by MDX engine. There are OLAP engine, JOIN engine and Calculation engine to process different views.
Relational Engine: This has row and column store which stores the data in memory in Row and columnar fashion.
Persistence Layer: The persistence layer ensures that changes are durable and that the database can be restored to the most recent committed start after a restart.
It is the physical storage of data and log volumes.
HANA SERVER and Data Sizing Procedure:
Since HANA supports In-memory computing, the Data sizing is different from other databases. SAP HANA runs on SUSE Linux enterprise server(SLES). The HANA server is a big system which takes up to 8 CPU’s and 80 cores.
RAM = Source data footprint * 2/7
- Disk(data storage):
Disk Persistence = 4 * RAM
Disk Log = 1 * RAM
- Log Storage: For a quick recovery of an SAP HANA system that goes down due to power loss, log storage is used. The system will quickly restore via the logs in case of power shut down etc.
CPU should be 300 SAPS / Active user
Before you can do the HANA sizing, you need to start the quick sizing tool. Quick sizer is for the companies which don’t yet have SAP ERP or SAP NetWeaver BW system, or for those that want to use RAPID Deployment solutions.
Sql to identify memory statistics is given below:
Select Volume_id Sum(all located_page_size) from M_CONVERTER_STATISTICS GROUP BY VOLUME_ID
Different methods available for sizing:
- Database method
- BW HANA sizing method
- ABAP sizing method
- HANA Rapid deploy solutions
- SAPA Netweaver BW powered by SAP HANA
- Standalone HANA
- SAP ERP Powered by HANA
After completion of sizing using Quicksizer tool, we will get the sizing details.
Hardware Vendors: DELL, IBM, NEC, LENOVO, FUJITSU, HP, CISCO, HITACHI, HUAWEI
The Sizing Script output given below according to the OSS note 1514966:
Table footprint of source database: 186348MB = 182GB
RAM = Source data foot print * 2/7 = 182GB * 2/7 = 52GB
Disk persistence = 52GB * 4 = 208GB
Disk Log = 52GB
RDS(Rapid Deployment Solution)
It is used for quick implementation/migration from any source to HANA DB. RDS contains pre-defined ETL logic, BI logic, and modeling logic. The real-time usage of RDS is RDS Sentiment intelligence.
RDS are available in 3 different flavours.
- Standalone RDS – Used for Non-SAP customers.
- BW HANA RDS – Used for SAP BW customers.
- ERP HANA RDS – This is for SAP ERP customers.
ETL logic – .ATL (data service file)
BI logic – .LCMBIAR
Modelling logic – .TGZ
Steps at SAP HANA(Admin):
1. Create a user Sent_rep and add “Public” role.
2. Go to role(tab) à Click on “t” à provide: public and select public à click on add à provide password: Tech123, repeat password à click on activate.
- Add system with Sentiment_rep
- Right-click on navigator P and select “Add systems” à
Host name: HANA5
Instance No: 52
User id : Sent_rep
Then click finish
System will ask you to change the password now, give new password and repeat password.
3. Create a new user Sent_modeling
Go to roles(tab) à Click on “t” à add public modeling Content_admin à OK à Provide Password and repeat password à activate.
4. Add system with Sent_modeling.
Host Name: Hana5
Instance no: 52
Description: sentiment modeling
User id : Sent_modeling
Go to Sql editor à Click on Select system & Select system with (sent_rep) and provide statements.
GRANT SELECT ON SCHEMA SENT_REP TO _SYS_REPO WITH GRANT OPTION;
GRANT SELECT ON SCHEMA SENT_REP TO SENT_MODELING;
Note: _SYS_REPO is admin user, and we have granted same permissions for ETL user SENT_REP.
Steps at SAP BODS(replication):
Place our project ‘Sentiment intelligence in C:1
Log on SAP BODS Designer à Import “.ATL” file à provide parameters like
Jobs: JOB_CRM_1; JOB_SOCIAL_MEDIA_DATA; SENTIMENT_DATA_MODEL.
Datastores: CRM_DS(SAP APP)
HANA_SENTIMENT_DS; HANA_SENTIMENT_DS_INIT(SAP HANA)
Flat files: SA_TABLE_INDEX
Open Flat files: SA_TABLE_INDEX
Then provide Rootdir = “C:\Sentiment intelligence\SAPRDSCONTENT\Data Model.”
Save and close.
Repeat above steps for 3 flat files.