Part 1: Solution Manager 7.2 – Installation and Configuration – I – Installations

Part 2: Solution Manager 7.2 – Installation and Configuration – II – Configurations

Part 3: Solution Manager 7.2 – Installation and Configuration – III – Changes from 7.1 to 7.2

Part 4: Solution Manager 7.2 – Installation and Configuration – IV – Managed System Config – General Info

Part 5: Solution Manager 7.2 – Installation and Configuration – V – Managed System Config – ABAP System

Part 6: Solution Manager 7.2 – Installation and Configuration – VI – Managed System Config – HANA DB

Part 7: Solution Manager 7.2 – Installation and Configuration – VII – Managed System Config – Busines Objects

Part 8: Solution Manager 7.2 – Installation and Configuration – VIII – Managed System Config – Java System

This document is about the Managed System Configuration of a HANA DB system.

I did managed system configuration of HANA DB system according to below link on Solution Manager 7.1 and used the same link for 7.2 version, too.

Managed System Setup of HANA in SAP Solution Manager 7.1

You will find short descriptions and practice of the configuration below. For more details and explanations use the wiki link.

Here are the steps performed for Managed System Configuration of HANA DB System.

Install Diagnostics Agent on HANA host

The first step is to install the Diagnostics Agent on the HANA servers.

You need latest SWPM and the Kernel DVDs for Linux. Also latest SAPEXE, SAPHOSTAGENT, SAPJVM and SAPDIAGNOSTICSAGENT SAR files as seen below.

SM72_Part6_sarfiles.jpg

Download them and transfer them to your HANA DB server.

I used MobaXterm tool for connecting to server and running sapinst.

If prerequisies are met there won’t be any “Condition not met” cases and you will install DAA on your HANA DB server successfully.

The parameters screens can be seen in previous blogs so I will not put them also in this document. If you want to have your agent’s SP levels latest you should enter the current archive locations as seen above in the last step of parameter entry.


After the istallation DAA Instance is registered to your Solution Manager. You can check it using the URL http://<solmanjavahostname>:<portnumber>/smd/AgentAdmin

Sometimes the servername of your DAA isn’t seen on the list. That time you can run below script to correct the name of your server.

Run the script smdsetup.bat changeservername servername:”evehrprd” in script folder as seen below.

SM72_Part6_smdsetup.jpg

Checking and Updating SAP Host Agent Version

When you install DAA instance SAPHOSTAGENT is also installed. Check the version using “saphostexec -version” script. You can see details in previous blogs of the series.

Since I have chosen the latest SAPHOSTAGENT*.SAR when I am installing DAA I donot need to upgrade Host Agent.

Creating Monitoring User in HANA

For Solution Manager connection you should create a HANA DB monitoring user.

Use HANA Studio to connect to DB and create the user and assign the roles MONITORING and PUBLIC to the user.

SM72_Part6_monitoruser.jpg

Use below SQL commands to make password of this user doesn’t have to be changed anymore.

ALTER USER <SID>MONITOR DISABLE PASSWORD LIFETIME;

CONNECT HRPMONITOR PASSWORD <password>;

Configure HDB User Store for SAP Host Agent

Login to system using <sid>adm.

Run below command to enable the SAP Host Agent to connect to HANA and can receive process information.

/usr/sap/hdbclient/hdbuserstore SET <SID>SAPDBCTRL <hana-master-host>:3<Sys-No>15 <SID>MONITOR password

Check the setup running below command:

/usr/sap/hdbclient/hdbuserstore LIST <SID>SAPDBCTRL

To check the setup there are some more commands that you can run. You can see the details in the mentioned wiki link at the top.

Register HANADB in SLD

Use HANA Platform Lifecycle Manager to register HANA in SLD:

SM72_Part6_SLD1.jpg

Enter the SLD connection parameters as seen below.

SM72_Part6_SLD2.jpg

And execute the registration process.

SM72_Part6_SLD3.jpg

You can find HANA in the SLD of Solution Manager under Administration -> Content Maintenance -> HANA Database System:

SM72_Part6_SLD4.jpg

You can also use HDBLCM tool to register HANA DB to SLD. You can see the details in wiki page.

Install HANA client software on SAP Solution Manager

If there is no HANA DB Client software installed on your Solution Manager before, download the client software and install it on your Solution Manager system. You can check the note 1597627 – SAP HANA connection for more.

SM72_Part6_Client.jpg

Set DB parameter on Solution Manager

  • Add X:\usr\sap\hdbclient path to the environment variable of Solution Manager sidadm user.
  • Add “dbs/hdb/connect_property = DISTRIBUTION=OFF” parameter in the SAP Solution Manager DEFAULT.PFL profile.
  • Restart Solution Manager System after these updates.

Check LMDB

Call LMDB transaction on your Solution Manager System, select your HANA DB System.

Check that product version is supplied.

SM72_Part6_LMDB1.jpg

Check the SAP HANA DATABASE software is marked as Installed on Instance

SM72_Part6_LMDB2.jpg

Check that all of the HANA services can be seen under Technical Instances

SM72_Part6_LMDB3.jpg

From LMDB initial screen select your ABAP system and check that the DB of your system is your HANA DB.

SM72_Part6_LMDB4.jpg

Run Managed System Setup for HANA

From SOLMAN_SETUP transaction you choose your HANA DB system and select configure system as seen below.

SM72_Part6_MS_0.jpg

1- Assign Product

In this step you define the product installed for the technical system.

Diagnostics-relevance is also set with product SAP HANA PLATFORM EDIT. 1.0.

SM72_Part6_MS_1.jpg

2- Check Prerequisites

In this step, you check the prerequisites for the configuration of SAP Solution Manager automatically.

SM72_Part6_MS_2.jpg

3- Assign Diagnostics Agent

In this step, you assign Diagnostics Agents to each server (host) on which managed systems are running. You can also check the status and version of the DAA.

SM72_Part6_MS_3.jpg

4- Enter System Parameters

In this step, you specify the system parameters required to configure the managed system, which depend on the type of the managed system.

You specify the Introscope EM, Managed System Load Balancer Host and port. And enable EWA alert inbox and system recommendations.

You use the created HANA DB user in DB Parameters section and by saving you setup DBA Cockpit and DB extractors.

SM72_Part6_MS_4.jpg

5- Enter Landscape Parameters

In this step, you can verify and add landscape parameters. Verify the landscape parameters carefully, to avoid time-consuming error-handling.

SM72_Part6_MS_5.jpg

6- Finalize Configuration

There are automatic and manual activities that needs to be fulfilled in Final Configuration step. You can leave postponed activities as is. Fot manual activities got to each transactioon or URL to perform the activity.

SM72_Part6_MS_6.jpg

7- Check Configuration

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.

SM72_Part6_MS_7.jpg

8- Complete

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.

SM72_Part6_MS_8.jpg

Managed System Configuration of a Busines Objects Cluster is coming next.

Thanks for your interests.

.

To report this post you need to login first.

6 Comments

You must be Logged on to comment or reply to a post.

  1. Steven Schäper

    Hello Yüksel,

    your guides help me very much, thank you for doing them.

    I am facing a problem with my system, maybe you got a quick answer?

    Currently I want to do the Managed System Setup for the Solution Manager itsself. My SolMan 7.2 runs on HANA so at first I wanted to make sure that everything is fine in lmdb. I followed your instructions but sadly in the lmdb entry of the Hana I cannot see any product instances.

    Maybe you know something, would be awesome!

    Best regards,

    Steven Schäper

    (0) 
      1. Steven Schäper

        Hello Yüksel,

        thank you for your fast reply. Seems like you’re really enthusiastic about this topic. I like that 🙂

        Yep, I did the the steps you mentioned. But I did not use the newest files for the DAA. I used the same SWPM, Kernel and other files like I used for installing Solution Manager 7.2 SP1. Could this be the problem?

        Best regards,

        Steven Schäper

        (0) 
        1. Yuksel AKCINAR Post author

          Hello Steven,

          Trying to contribute on NW Admin and Solution Manager. 🙂

          Check “SLD Registration using HDBLCM (SAP HANA >= SP08)” section in the wiki mentioned at the top.

          “Make sure that your HANA Database System has more than just 2 associations. 2 associations indicate that this HANA system was reported by the RZ70 SLD data supplier and is incomplete.”

          Can you check below section from Admin Guide “Configure SLD Registration Using the Graphical User Interface”?

          Next Steps

          After you have configured the connection parameters, you can manually push the registration of the SAP HANA system in the central SLD system instead of waiting for the SAP HANA system to be registered automatically at a later point in time.

          To do so, as a <sid>adm user, execute the following command:

          /usr/sap/hostctrl/exe/saposcol -b | sldreg -connectfile /usr/sap/<SID>/SYS/global/slddest.cfg -stdin –oldtransferdtd

          /usr/sap/hostctrl/exe/saposcol -b | sldreg -connectfile /usr/sap/EHP/SYS/global/slddest.cfg -stdin –oldtransferdtd”

          After you corrected the DB data will be synched to LMDB.

          Regards,

          Yuksel AKCINAR

          (0) 
          1. David Nguyen

            Great blog Yuksel! Very detail oriented. By the way, part 3 and 4 are not accessible. Did you remove them. If so, may I have the link..? Thanks again for your time.

             

            Part 3: Solution Manager 7.2 – Installation and Configuration – III – Changes from 7.1 to 7.2

            Part 4: Solution Manager 7.2 – Installation and Configuration – IV – Managed System Config – General Info

            (0) 

Leave a Reply