SAP HANA

Application Version and Upgrade Details

Introduction

SAP HANA serves as an in-memory platform designed for conducting real-time analytics and facilitating the development and deployment of real-time applications. When deployed on-premise, SAP HANA is available either as a pre-installed solution on certified hardware offered by SAP hardware partners (known as the appliance delivery model) or it can be installed on certified hardware by a qualified administrator following the tailored data center integration model.

However, SAP HANA extends beyond being solely a database management system. It serves as a comprehensive platform for building and executing native data-intensive applications that operate efficiently within SAP HANA’s in-memory architecture and parallel execution capabilities.

At its core, SAP HANA features a high-performance, in-memory database.

Functioning as an in-memory platform, SAP HANA integrates an ACID-compliant database with advanced data processing, application services, and adaptable data integration services. The SAP HANA database is capable of functioning as a standard SQL-based relational database. In this capacity, it can serve as both the data provider for traditional transactional applications (OLTP) and the data source for analytical queries (OLAP). Access to database functionality is achieved through an SQL interface.

Key Use cases

Discovery Use cases

• It discovers the SAP HANA System and its components HANA DB instances.
• Publishes relationships between resources to have a topological view and ease of maintenance.

Monitoring Use cases

• Provides metrics related to job scheduling time and status etc..
• Concern alerts will be generated for each metric to notify the administrator regarding the issue with the resource.

Prerequisites

• OpsRamp Classic Gateway 16.0.0 and above.
• OpsRamp NextGen Gateway 16.0.0 and above.
• Provided IpAddress/hostname, Credentials should work for SAP HANA DB
• The SAP HANA DB credentials should be same for all the HANA DB instances.
• sapcontrol command should be executing from SAP HANA Host System, if not able to execute the sapcontrol command, add SAP HANA System Path to /etc/bash.bashrc
  Example: $PATH=/usr/sap/PSL/HDB10/exe:/usr/sap/PSL/HDB10

Hierarchy of SAP HANA resources

    · SAP HANA Host
        Note: For now this can be removed, however, this host can be         discovered under the SAP HANA system in the future.
            · SAP HANA System
                   · SAP HANA Database

Supported Metrics

Default Monitoring Configurations

SAP HANA DB has default Global Device Management Policies, Global Templates, Global Monitors and Global Metrics in OpsRamp. You can customize these default monitoring configurations as per your business requirement by cloning respective Global Templates and Global Device Management Policies. It is recommended to clone them before installing the application to avoid noise alerts and data.

1. Default Global Device Management Policies

   You can find the Device Management Policy for each Native Type at Setup > Resources > Device Management Policies. Search with suggested name in global scope. Each Device Management Policy follows below naming convention:

   {appName nativeType - version}

   Ex: sap-hana-db SAP HANA System - 1(i.e, appName = sap-hana-db, nativeType = SAP HANA System , version = 1)

2. Default Global Templates

   You can find the Global Templates for each Native Type at Setup > Monitoring > Templates. Search with suggested names in global scope. Each template follows below naming convention:

   {appName nativeType 'Template' - version}

   Ex: sap-hana-db SAP HANA System Template- 1(i.e, appName = sap-hana-db, nativeType = SAP HANA System, version = 1)

3. Default Global Monitors

   You can find the Global Monitors for each Native Type at Setup > Monitoring > Monitors. Search with suggested name in global scope. Each Monitors follows below naming convention:

   {monitorKey appName nativeType - version}

   Ex: SAP HANA System Monitor sap-hana-db SAP HANA System 1 (i.e, monitorKey =SAP HANA System Monitor, appName = sap-hana-db, nativeType = SAP HANA System, version = 1)

Configure and Install the SAP HANA Integration

1. From All Clients, select a client.
2. Navigate to Setup > Account.
3. Select the Integrations tab.
4. The Installed Integrations page, where all the installed integrations are displayed. Click + ADD on the Installed Integrations page.
5. If you do not have any installed applications, you will be navigated to the Available Integrations page. The Available Integrations page displays all the available applications along with the newly created application with the version.
   Note: Search for the application using the search option available. Alternatively, use the All Categories option to search.
6. Click ADD in the SAP HANA DB application.
7. In the Configurations page, click + ADD. The Add Configuration page appears.
8. Enter the following BASIC INFORMATION:

Notes:

• By default the Is Secure checkbox is selected.
• Ip Address/Host Name and Port should be accessible from Gateway.
• Select the following:
  • App Failure Notifications: if turned on, you will be notified in case of an application failure that is, Connectivity Exception, Authentication Exception.
  • Alert Configuration: map alert configuration for third party alerts into OpsRamp.
  • Alert On Root Resource: Checking this will generate event polling alerts on root resource.
    • Below are the default values set for:
      • Alert Severity: Possible values of Alert Severity filter configuration property are [“HIGH”,“ERROR”,“LOW”,“MEDIUM”]
      • Alert Severity Mapping: Provides alert severity mapping configuration. Default values for Alert Severity Mapping configuration are {“HIGH”:“Critical”,“ERROR”:“Critical”,“LOW”:“Warning”,“MEDIUM”:“Warning”}.

9. Select the following Custom Attribute:

Note: The custom attribute that you add here will be assigned to all the resources that are created by the integration. You can add a maximum of five custom attributes (key and value pair).

10. In the RESOURCE TYPE section, select:
    • ALL: All the existing and future resources will be discovered.
    • SELECT: You can select one or multiple resources to be discovered.
11. In the DISCOVERY SCHEDULE section, select recurrence pattern to add one of the following patterns:
    • Minutes
    • Hourly
    • Daily
    • Weekly
    • Monthly
12. Click ADD.

Now the configuration is saved and displayed on the configurations page after you save it.
Note: From the same page, you may Edit and Remove the created configuration.

13. Under the ADVANCED SETTINGS, Select the Bypass Resource Reconciliation option, if you wish to bypass resource reconciliation when encountering the same resources discovered by multiple applications.

    Note: If two different applications provide identical discovery attributes, two separate resources will be generated with those respective attributes from the individual discoveries.

14. Click NEXT.

15. (Optional) Click +ADD to create a new collector. You can either use the pre-populated name or give the name to your collector.

16. Select an existing registered profile.

17. Click FINISH.

The integration is installed and displayed on the INSTALLED INTEGRATION page. Use the search field to find the installed integration.

Modify the Configuration

• See Modify an Installed Integration or Application article.

  Note: Select SAP HANA DB.

View the SAP HANA Details

To discover resources for SAP HANA:

1. Navigate to Infrastructure > Search > DATABASES > SAP HANA DB. The SAP HANA DB page is displayed
2. Select the application on the SAP HANA DB page
3. The RESOURCE page appears from the right.
4. Click the ellipsis (…) on the top right and select View Details.

5. Navigate to the Attributes tab to view the discovery details.

6. Click the Metrics tab to view the metric details for HPE SimpliVity.

View resource metrics

To confirm HPE SimpliVity monitoring, review the following:

• Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
• Alerts: Alerts are generated for metrics that are configured as defined for integration.

Resource Filter Input Keys

SAP HANA DB application resources are filtered and discovered based on below keys.

Supported Alert Custom Macros

Customize the alert subject and description with the following macros so that it can generate alerts accordingly.
Supported macros keys:

Risks, Limitations & Assumptions

• The integration can manage critical/recovery failure alerts for the following two scenarios when the user activates App Failure Notifications in the settings:
  • Connectivity Exception
  • Authentication Exception
• SAP HANA integration cannot control monitoring pause/resume actions based on above alerts. Metrics can be used to monitor resources and can generate alerts based on the threshold values.
• The default value of the SSH Port is 22. You can modify this from the configuration page, if required.
• Component level thresholds can be configured on each resource level.
• No support of showing activity log and applied time.
• The minimum supported version for the option to get the latest snapshot metric is Nextgen-14.0.0.
• This integration supports both Classic Gateway and NextGen Gateway.