Skip to Content
Technical Articles

SAP HANA Cloud: What’s New (and Changed) – Manage Services

SAP HANA Cockpit: Manage Services

In the upcoming days and weeks, we will be publishing new tutorial videos about what’s new and changed for SAP HANA Cloud. The focus of this series is on system administration with SAP HANA cockpit.

For the overview blog about What’s New with SAP HANA Cloud Administration, see

Any good? Post a comment, share on social media, and/or give a like. Thanks!

/wp-content/uploads/2016/02/sapnwabline_885687.png

Video Tutorial

In this video tutorial, we navigate from the Overall Database Status card to the Manage Services view and explain the information displayed and what actions can be performed from this view (app). We also briefly compare the view with the predecessor of HANA Cloud, the SAP HANA Service, and with the on-premise environment. Finally, we show how the same information can be obtained using SQL and the Database Explorer Statement Library.

SAP HANA Cloud: Manage Services

/wp-content/uploads/2016/02/sapnwabline_885687.png

Manage Services with SAP HANA Cockpit

Overall Database Status is a card (tile) on the System Overview page of the SAP HANA cockpit. It displays the host name (format <UUID>.hana.prod-<region>.hanacloud.ondemand.com) and HTTPS port 443 in the header and the status, related alerts, usage type, number of hosts (1) and services (6) in the body.

Overall Database Status (card)

When selected, Manage Services opens (view/app), listing a customisable selection

  • Name
  • Status
  • Role
  • Process ID
  • TCP ports (internal communication)
  • SQL Port (database service)
  • Start Time
  • Alerts
  • CPU usage
  • Memory usage

Plus any of the other 30+ fields available for selection.

Manage Services (view)

SAP

Columns

HANA Cloud Services

Manage Services shows a connection to a tenant database (H00) and lists local and shared services.

Local Tenant Database Services

  • indexserver
  • dpserver – data provisioning
  • diserver – deployment infrastructure (HDI)

The indexserver contains the row and column data stores and the engines for processing the data. It is the actual “database”.

The data provisioning server originates from SAP HANA Smart Data Integration (SDI), introduced with SPS 09 (2015), and also used in SAP Data Hub/Intelligence, for example. The dpserver provides connectivity to external (remote) data sources, such as:

  • SAP HANA Cloud
  • SAP HANA on-premise
  • Amazon Athena
  • Google BigQuery
  • Microsoft Azure SQL database
  • Any data source supported by SAP HANA Smart Data Integration (SDI)

For the documentation, see

The deployment infrastructure server is part of the HANA Deployment Infrastructure (HDI) and handles the deployment of design-time artifacts into the SAP HANA database.

For the documentation, see

Shared Services

  • daemon (watchdog)
  • nameserver (system database)
  • compileserver (SQL / SQLScript)

Shared services are managed from the system database but as our HANA Cloud instance only contains a single tenant database private to our account, we “share” these services only with SAP.

The nameserver hosts the system database which contains metadata from the tenant database but apart from that is completely separate and isolated. The superuser SYSTEM account of the system database, for example, cannot access a tenant database (nor can any other account). Database catalog, security, backups, etc. – is all strictly separated. In other words, SAP cannot access our data but vice versa, we cannot access the system database (for example to move fast and break things).

The compile server compiles SQL and SQLScript code for execution.

With the daemon service the SAP HANA instance starts and the service monitors service health. For the details, see blog post (although irrelevant information for a cloud service)

For a complete list and description of SAP HANA services (on-premise), see

Not Included

We already mentioned in a previous blog that SAP HANA XS is no longer included, so related services like xsengine, webdispatcher, xscontroller, etc. are not listed.

When compared to the SAP Cloud Platform, SAP HANA Service, the following services are also no longer included

  • preprocessor (shared)
  • scriptserver
  • docstore

The preprocessor provides support for the indexserver for SAP HANA Text Analysis features.

The scriptserver is used to execute to execute AFLs (application function libraries written in C++), like those of the PAL (Predictive Analysis Library). The PAL plug-in is installed in HANA Cloud (see previous blog) but without scriptserver we will not be able to use it (time of writing).

The docstore process is required for the JSON (NoSQL) Document Store.

Service Operations

From Manage Services, we can stop local services using the Stop Service action. For enabled services, however, the watchdog process (daemon) will automatically attempt to restart any service in stopped state. This is configurable but only from the system database, in other words, only by SAP.

If the service does not respond to a friendly stop request, we can become less polite and select the Kill Service link. Optionally, we could request the instance to generate a crash dump file. Use case? SAP Support.

Service crashdump file in SAP HANA Database Explorer

From Manage Services we can navigate to the Memory Analysis and Performance Monitor views, and to Alerts. We will cover these topic in a future blog.

Manage Services is documented in the SAP HANA Cockpit guide for SAP HANA Cloud.

/wp-content/uploads/2016/02/sapnwabline_885687.png

Manage Services with Database Explorer

Should you prefer SQL, you can also manage services using the SAP HANA database explorer. The Statement Library includes a Services Overview script that queries the M_SERVICES system monitoring view. Alternatively, you can select Open Data for the view which provides similar information.

The scripts in the Statement Library reference different SAP HANA platform releases but are not specific to SAP HANA Cloud (time of writing). Some scripts, like the Mini Checks, return errors due to missing views or tables.

SAP HANA Database Explorer – Statement Library

SAP HANA Database Explorer – Services Overview

The equivalent of the Stop Service and Kill Service actions in SAP HANA cockpit are the SQL command ALTER SYSTEM STOP SERVICE. This command (and the corresponding actions in cockpit) requires the RESOURCE ADMIN system privilege.

ALTER SYSTEM STOP SERVICE '5d33b5e3-cc63-44be-bbfa-015eb452d52d:30043'
ALTER SYSTEM STOP SERVICE  <host_port> [IMMEDIATE [WITH COREFILE]]

Manage Services is documented in the SAP HANA Cockpit guide for SAP HANA Cloud.

/wp-content/uploads/2016/02/sapnwabline_885687.png

Learned Something New?  

Post a comment, share on social media, and/or give a like. That’s how the community works. Thanks.

If you would like to receive updates, connect with me on

Best,

Denys van Kempen

/wp-content/uploads/2016/02/sapnwabline_885687.png

 

2 Comments
You must be Logged on to comment or reply to a post.
  • Hi Denys,

    I am not happy with this paragraph:

    The data provisioning server originates from SAP HANA smart data integration (SDI) for both real time and batch provisioning including transformations, data quality, etc. using the same technology as SAP (BusinessObjects) Data Services

    SDI is not using Data Services in most of the cases. SDI has many adapters and one of the rarely used adapters is the bridge to Data Services. The reason it is not used often is because only the native SDI adapters support realtime. Data Services does not support realtime changed data capture from sources and hence SDI’s Data Services adapter does not either.

     

    • Hi Werner,

      Thank you for pointing this out. I have updated the sentence accordingly (but do not hesitate to reach out to me in case this needs adjustment as well). Expertise is always appreciated.

      The last thing we want is for our reader to be unhappy!

      Thx