SAP HANA ADMIN TOOLS

Overview:
  1. SAP HANA Cockpit
  2. SAP HANA Studio
  3. SAP HANA HDBSQL
  4. SAP Solution Manager
  5. SAP DBA Cockpit
  6. SAP Landscape Management
HANA ADMINTOOL
SAP HANA Cockpit:
SAP HANA cockpit provides a single point of access to a range of tools
for the administration and detailed monitoring of multiple, individual, and tenant SAP HANA databases. It also integrates the SQL develop- ment functions required by administrators. SAP HANA cockpit, a Web-based HTML5 user interface that you access through a browser, runs on SAP HANA extended application services, advanced model.
You can use the cockpit to monitor and manage systems running SAP HANA 2.0 or SAP HANA 1.0 SPS 12.
SAP HANA Studio:
The SAP HANA studio supports core administration and monitoring of SAP HANA databases, including system configuration, user management, and performance monitoring capabilities. It also supports SAP HANA development of content, including modeled views and stored procedures general system administration and monitoring       tasks.SAP HANA studio is both the central development environment and the main
administration tool for the SAP HANA database.
SAP HANA HDBSQL:
SAP HANA HDBSQL is a command line tool for executing commands on SAP HANA databases.
SAP Solution Manager:
SAP Solution Manager is a central hub for the holistic lifecycle management
of your SAP solution landscape. It contains central alerting infrastructure and business process analytics, end-to-end root cause analysis, monitoring and unified alert inbox for the entire solution landscape, guided issue resolution, and business process reporting.
SAP DBA cockpit:
The DBA Cockpit is a platform-independent tool provided by SAPNet-
Weaver Application Server ABAP systems, which you can use to monitor
and administer your SAP HANA database.SAP HANA cockpit can also be used on mobile devices.
SAP Landscape Management:
SAP Landscape Management is a powerful automated solution designed
to simplify, centralize, and orchestrate the management and operations of the entire application landscape powered by SAP HANA. With the enterprise edition of SAP Landscape Management, you can perform various operations on SAP HANA instances, such as start, stop, monitor, or system replication operations.

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