The document outlines the steps to configure a SAP HANA system for monitoring in SAP Solution Manager 7.2 SP5, including: 1. Registering the HANA system in the System Landscape Directory. 2. Installing the Diagnostics Agent and connecting it to Solution Manager. 3. Installing the HANA client on the Solution Manager server. 4. Uploading extractors for HANA 2.0 monitoring. 5. Assigning products, checking prerequisites, and finalizing the configuration.

1. SAP Solution Manager 7.2 SP5
Part 3 of 4
Managed System Configuration
By OZSoft Consulting for ITConductor.com

2. Managed System Configuration : Register HANA system to
SLD
• Open URL https://<HANAServerHostname>:1129/lmsl/HDBLCM/<SID>/index.html
• Login with <sid>adm user and open “Configure System Landscape Directory Registration”
• Restart HANA system to push your system
data in to SLD.
ozsoft-consulting.com ITConductor.com 2

3. Managed System Configuration: Install the Diagnostics Agent
• Start SWPM and navigate to General Option >> Diagnostics in SAP Solution Manager >> Install – Diagnostics Agent
• Specify the paths to complete DVDs or Blu-ray media such as to a mounted kernel DVD,
the path to a download folder containing all software packages, or the paths to several individual
download locations of software packages.
Ref: SAP Note 1833501 - Diagnostics Agent -
Installer Versions and 2385361 - How to connect
Diagnostics Agent to Solution Manager 7.2
system
• Enter the parameters of the connection to a central System
Landscape Directory (SLD).
ozsoft-consulting.com ITConductor.com 3

4. Install HANA client on SAP Solution Manager server
• Download and extract the software to an empty directory. Open a shell and go to the directory where you
unpacked the software. Call the program hdbsetup (GUI installation) or hdbinst (command-line installation).
• Follow the instructions displayed by the installation tool.
• For the environment of users that will use the client, including the user <sid>adm, add the installation path to the
library path environment variable. (Linux: LD_LIBRARY_PATH)
ozsoft-consulting.com ITConductor.com 4

5. Upload the Extractors for HANA 2.0
ozsoft-consulting.com ITConductor.com 5
• Update Stores as per SAP note : 2403493 - Solution Manager: Enabling the Monitoring of HANA 2.0
• Upload the attached CV Template 'SAP HANA DATABASE 2.00.xml'. This template should be uploaded using the following
path: Workcenter Solution Manager Administration -> Infrastructure -> Content -> Root Cause Analysis Content -> Stores.
• Upload the Extractors for HANA 2.0. Please upload the attached File 'Templextr_HANA_20.csv'. This file should be
uploaded using the following path: Workcenter Solution Manager Administration -> Infrastructure -> Content -> Root
Cause Analysis -> Extractors. Than go to Change Mode and press the 'Expert Mode'. Only with the Expert Mode you will
have the possibility to upload the attached file.
• Ensure that the MAI Content is up-to-date. It is available with:
• Solution Manager 7.1: ST_CONT 100 SP 28
• Solution Manager 7.2: ST_CONT 200 SP 9

6. Managed System Configuration: Assign Product
• Run transaction SOLMAN_SETUP and select system:
• Both systems are configured together.
• Set Diagnostics-relevance with Automatic settings
ozsoft-consulting.com ITConductor.com 6

7. • The Software Prerequisites activity now relies on the RTCCTOOL running on the SAP Solution Manager system, for
checking the ST-A/PI and ST-PI versions
• Execute automatic activities first.
• Create HANA Database user.
• Note: We do not want to change this user password so make sure you run script below:
• ALTER USER MONI DISABLE PASSWORD LIFETIME;
ozsoft-consulting.com ITConductor.com 7
Managed System Configuration: Check Prerequisites

8. • In this step you create or delete RFC connections to the clients in managed systems, for example, client 000. For
each managed system, you should create at least a READ RFC connection to the production client.
ozsoft-consulting.com ITConductor.com 8
Managed System Configuration: Maintain RFCs

9. • In this step, you assign Diagnostics Agents to each server (host) on which managed systems are running.
• The “SLD Agent Candidate Management” is no longer accessible from the Managed System Configuration UIs.
• The “Auto Assign” option should be used to assign a Diagnostics Agent to a system. If auto assignments does not
work, the “Agent Admin” UI can be used for troubleshooting, before retrying “Auto Assign”
ozsoft-consulting.com ITConductor.com 9
Managed System Configuration: Assign Diagnostics Agent

10. • In this step, you specify the system parameters required to configure the managed system, which depend on the
type of the managed system, for example, ABAP, Java, or database systems.
ozsoft-consulting.com ITConductor.com 10
Managed System Configuration: Enter System Parameters

11. • In this step, you can verify and add landscape parameters. Verify the landscape parameters carefully, to avoid time-
consuming error-handling.
ozsoft-consulting.com ITConductor.com 11
Managed System Configuration: Enter Landscape Parameters

12. • In this step, you can verify and add landscape parameters. Verify the landscape parameters carefully, to avoid time-
consuming error-handling.
ozsoft-consulting.com ITConductor.com 12
Managed System Configuration: Maintain Users

13. • In this step, you use the automatic activities to configure the technical system and the client that you have selected
in step 3 Select Monitored Systems and step 4 Select Client.
ozsoft-consulting.com ITConductor.com 13
Managed System Configuration: Finalize Configuration

14. • In this step, you automatically check whether the system is configured correctly, and you update the statuses in the
overview of the Managed Systems Configuration.
ozsoft-consulting.com ITConductor.com 14
Managed System Configuration: Check Configuration

15. • This step provides an overview of the steps that have been performed in this scenario, including information about
the users who made the changes, and the status of each step.
• After this scenario is finished, you can proceed by navigating to the next scenario or by choosing a link from the
What do you want to do now? area.
ozsoft-consulting.com ITConductor.com 15
Managed System Configuration: Complete

16. Next – Solution Manager 7.2 SP 5: System Monitoring
• This is the end of the Managed System Configuration phases of
Solution Manager 7.2 SP 5
• “Solution Manager 7.2 SP 5: System Monitoring” - is the next
section that we’ll examine that will actually monitor the HANA
environment we added.
ozsoft-consulting.com ITConductor.com 16

17. • Any Questions?
• Contact Info: info@itconductor.com
• Follow us: https://www.linkedin.com/company/it-conductor
Let
itconductor.com
@itconductor
ozsoft-consulting.com ITConductor.com 17