SAP HANA STUDIO

The SAP HANA studio is developed in Java and is based on the Eclipse platform.
SAP HANA studio runs on the Eclipse platform, and is both the central
development environment and the main administration tool for SAP HANA.
OverviewStudio1
Administrators use:
The SAP HANA studio
to start and stop services,
to perform monitor the system,
to perform backup and recovery,
to perform Audit policy and Security configuration
to perform license management
to perform other configurations in HANA system
to configure system settings, and
to manage users and authorizations.
The SAP HANA studio accesses the servers of the SAP HANA database by SQL.
Developers use:
the SAP HANA studio to create content such as modeled views and
stored procedures. These development artifacts are stored in the repository, which is part of the SAP HANA database.
SAP HANA Studio: Available Perspectives
The SAP HANA studio presents its various tools in the form of perspectives. Database administration and monitoring features are contained within the SAP HANA Administration Console perspective. Additional perspectives include the SAP HANA Modeler perspective and the SAP HANA Development perspective.
OverviewStudio10
OverviewStudio2
Adding a System in Studio
After the installation, SAP HANA Studio does not contain any system. To add SAP HANA
systems, right click the system window. The following two options are available:
Add System…
Add System Archive Link.
1.Add System
The first option adds an individual SAP HANA system following a guided procedure, in which
you can provide the following information:
● Host name
● Instance number
● Description (for identification in SAP HANA Studio only)
● Locale
● Database User
● Database Password
1
OverviewStudio4
Add System Archive Link
The Add System Archive Link is a new feature that allows users to connect to multiple SAP HANA systems.
A centrally-stored archive of SAP HANA systems is an efficient way of deploying system
information to all users of the SAP HANA studio. Users no longer have to obtain the
connection details of all systems individually or add them individually.
One user can manage the list of all systems in a centrally-accessible archive (through File→ Export→ SAP HANA→ Landscape. Other users can then link to this archive in read-only mode.
System Navigator
OverviewStudio6
Once the system is added, it appears in the system navigator screen on the left of the SAP
HANA Studio window. It contains the following elements: Backup: You can configure the backup (Destination, File size), and view the backup catalog. Catalog:The catalog contains all schemas that have the respective column and row tables. While some schemas exist by default for internal SAP HANA use, others can be created by users, respectively administrators. Content:The content folder holds packages that store development and modeling artifacts. Provisioning:Provisioning relates to the functionality of “Smart Data Access”. It contains remote sources and proxy tables. Security:In the security folder, you can maintain users, roles, and other security settings.
Administration Console Perspective
OverviewStudio7
Screen Areas, provides an overview of the
administration and monitoring activities of SAP HANA using the administration console of the SAP HANA studio (the studio). The administration console of the studio allows system administrators to manage the database, including creating and managing user authorizations. The studio also contains perspectives for other tasks, such as the information modeler that allows modeling users to create new or modify existing models of data, and the lifecycle management that allows you to update the SAP HANA system.
OverviewStudio8Administration Console: Overview Tab
The administration console contains the following tabs:
  • Overview
  • Landscape
  • Alerts
  • Performance
  • Volumes
  • Configuration
  • System Information
  • Diagnosis Files
  • Trace Configuration

Comments

  1. Sonam Singh May 8, 2023 at 3:49 AM

    SAP HANA is an in-memory data platform that is designed to handle large amounts of data and perform real-time analytics. If you're interested in learning how to use this powerful platform, then the SAP HANA Course in Gurgaon offered by ERP Training Gurgaon might be the right choice for you.

    ReplyDelete

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