Register an SAP HANA database instance
The following sections provide instructions for using a wizard to register an SAP HANA database instance (either self-managed or SAP HANA Cloud) for monitoring with DPA.
If you register a database instance within the 14-day trial period, DPA begins monitoring the instance immediately. After the trial period, you must activate a license to monitor the database instance.
License requirements
To monitor SAP HANA database instances, you must have one of the following DPA license types:
- Database Self-Hosted (DBSH)
- Temporary or trial
Options for creating the monitoring user
DPA requires an account with certain privileges to gather information from the database instance. This account is called the monitoring user. If DPA is not integrated with CyberArk, the registration wizard displays options to determine how the monitoring user and utility package are created or configured.
If DPA is integrated with CyberArk, these options are not displayed. You must create the monitoring user.
The monitoring user can be created in either of the following ways:
-
DPA can create the monitoring user. When registering an SAP HANA database, you provide the credentials of a privileged user that DPA can use to create the monitoring user.
DPA does not store the user credentials of the privileged user. They are used only during registration and then forgotten.
-
You can create the monitoring user manually. Before starting the registration, create a user with the required permissions.
Register an SAP HANA database instance and create the monitoring user yourself
Task 1: Create the monitoring user
Create a user in the SAP HANA database instance that you are registering. Grant the following minimum permissions:
MONITORINGCATALOG READ
Task 2: Complete the registration wizard
- In the upper-left corner of the DPA home page, click Register DB Instance for Monitoring.
- Select one of the following:
- Under Self-managed, select SAP HANA.
- Under SAP HANA Cloud, select SAP HANA.
- If the monitoring user prompt is displayed, select I will create the monitoring user manually. Then click Next.
-
Complete the Connection information panel:
-
In the Host field, enter the fully qualified domain name or IP address of the server that hosts the database instance.
The Host field is not required if you are using SAP HANA User Store (hdbuserstore) for authentication.
-
Verify or update the port used for the connection.
-
(Self-managed only) Enter the system database name or the tenant database name used for the connection (for example, HXE).
-
Under SSL mode, specify the type of secure socket layer (SSL) connections established between the instance and the DPA server.
SSL mode Description Disable SSL encryption is not used. (This option is available only for self-managed instances.) No certificate validation SSL is enabled, but no server certificate checks are performed. Validate server certificate SSL is enabled. The client verifies that the server is trustworthy by checking the certificate chain up to a trusted certificate authority (CA). Validate server certificate and match hostname SSL is enabled. The client verifies the certificate chain and also verifies that the server hostname matches its certificate's Subject Alternative Name or Common Name (CN). -
Do one of the following:
-
If you are using the SAP HANA User Store (hdbuserstore) for authentication, select the Use HDBUserstore check box. Then enter the key used to retrieve SAP HANA credentials from hdbuserstore.
To use the hdbuserstore, the SAP HANA client must be on the DPA server with hdbuserstore configured for the DPA service account.
-
If DPA is configured to use CyberArk, enter the CyberArk credentials query for the monitoring user.
-
Otherwise, enter the user name and password of the monitoring user created previously.
-
-
Click Next.
DPA validates the connection information and the privileges of the monitoring user.
-
-
Specify the following Instance options.
The instance name and group membership can be changed after registration.
-
If your repository database is Oracle, choose the tablespace in the repository database to store DPA performance data for this monitored instance.
By default, the performance data is stored in the default tablespace of the repository user. However, data for monitored instances can be stored in separate tablespaces.
-
Enter the name that DPA will display to identify this database instance.
The Display name field defaults to the name retrieved from the database instance.
-
(Optional) If you have manually created instance groups, you can assign this database instance to one of the groups.
If no manual groups exist, this option is not shown.
-
(Optional) If you have existing alert groups, you can assign this database instance to one or more groups.
If no alert groups exist, or the existing groups do not match this instance's database type, this option is not shown.
-
Click Next.
-
-
Review the information on the Summary page. Click Back if you need to make changes. When the information is correct, click Register.
Register an SAP HANA database instance and let DPA create the monitoring user
Task 1: Identify the privileged user
When you register a database instance using this option, you must provide the credentials of a privileged user. During registration, the privileged user either creates the monitoring user or grants the required privileges to an existing user that you designate as the monitoring user. DPA does not store the credentials of the privileged user.
The privileged user must have the following role and privileges:
MONITORINGroleCATALOG READsystem privilegeSESSION ADMINsystem privilegeWORKLOAD ADMINsystem privilege
For example, you can specify the SYSTEM user (for self-managed instances) or the DBADMIN user (for SAP HANA Cloud instances).
Task 2: Complete the registration wizard
- In the upper-left corner of the DPA home page, click Register DB Instance for Monitoring.
- Select one of the following:
- Under Self-managed, select SAP HANA.
- Under SAP HANA Cloud, select SAP HANA.
- At the monitoring user prompt, select DPA will create/configure the monitoring user. Then click Next.
-
Complete the Enter Monitored Database Instance Connection Information panel:
-
In the Host field, enter the fully qualified domain name or IP address of the server that hosts the database instance.
-
Verify or update the port used for the connection.
-
(Self-managed only) Enter the system database name or the tenant database name used for the connection (for example, HXE).
-
In the Sysadmin User and Password fields, enter credentials for the privileged user that DPA can use to register the instance.
DPA does not use or store these credentials after you complete the wizard.
-
Click Next.
DPA validates the connection information and the privileges of the privileged user.
-
-
Create or specify the account that DPA will use to gather information (the monitoring user).
To ensure that the account has the required permissions, SolarWinds recommends creating a new account.
-
To create a new account:
-
Next to Create Monitoring User, select Yes.
-
Enter a user name and password for the new account, or accept the default values.
-
Optionally, assign the new user to an SAP HANA user group.
The User Group drop-down menu is displayed only if groups exist.
-
Click Next.
-
-
To specify an existing account:
-
Next to Create Monitoring User, select No.
-
Enter the user name and password of an existing account.
DPA requires the monitoring user to have the following minimum permissions:
MONITORINGCATALOG READ
DPA ignores data on the monitored database instance from the monitoring user. Make sure the monitoring user will not cause load on the monitored instance.
-
Click Next.
If your repository database is Oracle, the Oracle Repository Tablespace panel opens. If not, continue with step 7.
-
-
-
If your repository database is Oracle, choose the tablespace in the repository database to store DPA performance data for this monitored instance. Then click Next.
By default, the performance data is stored in the default tablespace of the repository user. However, data for monitored instances can be stored in separate tablespaces.
If your repository database is not Oracle, the wizard skips this step.
-
(Optional) Select the alert groups you want the new database instance to join. Then click Next.
-
If no alert groups exist, or the existing groups do not match the database type of this instance, the wizard skips this step.
-
Group membership can be changed after registration
-
-
Review the information, and click Register Database Instance.
-
When the registration is complete, click Finish to return to the DPA home page.
Enable SAP HANA to collect network and admission control metrics
SAP HANA collects network and admission control metrics only if the feature to collect them is enabled. Otherwise, the values for all network and admission control metrics will always be 0.
To enable network metric collection, run the following command:
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM')
SET ('sql_client_network_io', 'enabled') = 'true'
WITH RECONFIGURE;
To enable admission control metric collection, run the following command:
ALTER SYSTEM ALTER CONFIGURATION ('indexserver.ini', 'SYSTEM')
SET ('admission_control', 'enable') = 'true'
WITH RECONFIGURE;
After you run these commands, SAP HANA might take a few minutes before it starts exposing these metrics to DPA.