SAP HANA ARCHITECTURE

SAP HANA System Architecture
A SAP HANA system is a database management system (DBMS); that is, it is a server
component that manages a database model. A database management system captures and analyzes data by interacting with the user, other applications, and the database itself. A general-purpose DBMS allows the definition, creation, querying, update, and administration of databases.
DB
A DBMS performs the following functions:
● Manages large amounts of data in a multi user environment so that many users can
concurrently access the same data
● Maintains relationships between data
● Provides secure access to data using the user authorization concept
● Recovers data automatically to the most recent consistent status after a system failure
● Delivers high performance for processing data requests.
A database is an organized collection of data and metadata. It is the collection of schemata,tables, queries, reports, views, and other objects. Because the database is only a passive part of a database server, some processes and memory structures are needed to access the data and manage the database. The combination of processes and memory buffers is called a database instance.
An SAP HANA system can be installed as a single-container system or as a multiple-container system.
MULTI CONTAINER DATABASE
SAP HANA Server Components:
An SAP HANA system contains all the server components for an installation of SAP HANA. An SAP HANA system consists of several servers, the most important of which is the index server. The index server contains the actual data stores and the engines for processing the data. The SAP HANA Database functions are implemented in different services. These are briefly described in the figure, Core Processes on an SAP HANA Single-Node Instance. Following the concept of a shared architecture, each of the processes maintains data in the corresponding data and log volumes independently.

Component of Hanna
Daemon : Starts all the other processes and Keeps them running
Server Component Name Service Name in HANA system OS Process Name   Component Details
 
Index Server		  
Indexserver		  
hdbindexserver		 The main database process which preform Data loads,Queries, Calculations, and so no.And Provides the embedded statics service. Responsible for processing SQL statements using SQL/MDX Processors.
 
Name Server		  
nameserver		  
hdbnameserver		 To maintain topology of SAP HANA system. This is used to manage all the running components and data stored on each component and Data distribution.
  XS Classic Server  
xsengine		  
hdbxsengine		 Web service component sometimes termed “application server’ . It can be used to develop and host applications on the top of SAP HANA system.
Data Provisioning Server   dpserver   hdbdpserver To provide SAP HANA smart data access function.
  Preprocessor   preprocessor   hdbpreprocessor Feeds unstructured data (for example, text documents) into SAP HANA .To analyze the text data and perform search capabilities.
 
Compile Server		  
compileserver		  
hdbcompileserver		 Perform the compilation of procedures and programs.  Doesn’t contain any data.
 
Web Dispatcher		  
Webdispatcher		  
Hdbwebdispacher		 It is used to process HTTP/HTTPS request to HANA XS Engine.
SAP HANA Index server consists of several components that implement various features, as follows:
Indexserver
● External Interfaces
Structured Query Language (SQL), Multidimensional Expressions (MDX), and Web
interfaces allow clients to connect and communicate with the SAP HANA database.
● Request Processing and Execution Control
Depending on the interface and the statement, different components for processing can
be used. For example, SQL script implementations are executed within the Calculation
Engine.
● Relational Engines
The table data in SAP HANA is kept in two different relational stores: Row Store and
Column Store. Each of these stores shows significant differences with regard to the main
memory management.
● Storage Engine and Disk Storage
To gain consistency and maintain durable changes, a Storage Engine with Page
Management and Logger is used. This ensures that the database can be restored to the
most recent committed state after a restart. It also ensures that transactions are either
completely executed or completely undone. Disk Storage is divided in Data Volumes and
Log Volumes. While changes need to be written to the log area before a successful commit of a transaction (synchronous writing), the data area contains the complete main memory content at a specific point in time and is written asynchronously.

Comments

Post a Comment

Popular posts from this blog

SPOOL WORK PROCESS

Spool Process: It is the Only Process that is used to output the documents to a Printer, fax, email etc.. Spool Work Processes are created by using parameter risp/wp_no_spo=1 it is possible to configure more than one spool work process based on available resources. Spool Process Work Flow: User Submits the request to print a Document. The Dialog Process handles the request and print directly or schedules to print in the background.The Print requests are stored in the TemSe(Temporary Sequential Files) Temporary Sequential Files are stored either at File System or at database Level which is defined by parameter rspo/store_location. rspo/store_location=”G” or ‘DB’ G means global directory stores the TEMSE in /usr/sap/SID/SYS/global db mean the Tables TST01 and TST03.(TST01 Contains Print Attributes and TST03 Contains the Spool Data to be Printed) Due to Spool in DB the DB Size Increases, as a Result, the backup time increases and Tapes may not fit with the data for S...
Read more

ENQUEUE WORK PROCESS

It is used to lock and unlock the Objects during an update.These locks are displayed in SM12 and Held for longer hours until the transaction is committed or rollback.These locks are issued from a lock table which resides in the main memory of the instance where enqueue process is created/located. Enque Processes are configured by parameter rdisp/wp_no_enq=1. Generally One Enque Process for instance is sufficient,more then one is required in a massive update system. The Lock table size on the memory ranges between 4mb to 100 MB(200 MB in the Net weaver 7.3 Systems ) It is defined by parameter enque/table_size=4 to 200 MB. For 4mb of enqueue table size, the Number of lock/owners/objects/arguments can be restricted up to 3715. Enqueue Flow: User submits the Request for an Update. The Dialog or Background Process Handles the Request Dia or BTC Processes communicates with Enqueue Process and obtains a lock on the record so that no other user has to write access to that r...
Read more

DIALOG PROCESS

Dialog Process: It is the only process that is used to communicate with end users Interactively using Classic GUI or Through RFC or through Http Protocol. The Average Response Time for each dialog step is 600 ms.it is displayed through ST03n Each Process can execute up to a maximum runtime of 600 seconds.if any process goes beyond this time an additional time of 60 seconds is given and the process is timed out.(ST22)(it is not mandatory to allocate additional 60 seconds Each Process Serves 5-10 users.(Calculated based on ST07) Each Process Requires 75mb to 300 mb Memory Each Process can Handle the requests that are initiated for background, spool & update and update them in temporary tables. Dialog Process is not restricted to a User and Users are not restricted to a process which is referred as process multiplexing Parameters to configure dialog processes is rdisp/wp_no_dia There should be at least minimum two dialog processes and maximum up to 100 processes. The ...
Read more