Adding HANA system to Solution Manager 7.2 - step by step guide

[former_member688309]

Adding HANA system to Solution Manager 7.2

 

Content of this blog post

 

1. Installing Diagnostics Agent on HANA system host


2. Setup monitoring User in HANA


3. Setup HDB User Store in HANA


4. Register HANA in SLD


5. Check SLD and LMDB content for the system


6. Add Managed System in Solution Manager


7. Report the system to SAP and check the results


8. Useful links

The idea of this blog post is to help you to add a SAP HANA system as managed to the existing SAP Solution Manager infrastructure. You will get the system reported and will be able to manage it. In this guide also the steps of adding the ABAP server will be covered, however there are some specifics, that are not mentioned here, because the HANA part is the main focus.

After the configuration on Solution Manager system is completed and all the settings for HANA support are set properly, we can proceed to adding the HANA system to the Solution Manager.

Check the prerequisites:

The setup of Solution Manager should be absolutely completed. This means that all activities (manual and automatic) should be executed and should be successful. This is mandatory for adding a managed system at all. Additionally, for adding a HANA system, we should configure the libraries and the client on the ABAP solution manager host.

If you are unsure if the Solution Manager system is configured properly to work with HANA as managed system, please take a look at my other blog post on the topic: Configuring SAP Solution Manager 7.2 to support SAP HANA DB instances. If all the above is fulfilled, then we can start the activities for adding the HANA system.

For this example, I have chosen to set the Solution Manager system in Test role:

This helps in the process by saving time, because if it is set as Productive System, roles cannot be created directly on the system and should be transported. Also please login and execute all of the following activities with the user, that has been used for setting up the Solution Manager system or copy of this user with the same roles and permissions. The following steps are the same for adding any type of managed system, but in this blog post are described the specifics for HANA system. The scenario for every managed system is shown in this figure:

 

1. Installing the Diagnostics Agent.

The first step is to download and install the Diagnostics Agent. The process of installation is done by launching SWPM and choosing Generic Options -> Diagnostics in SAP Solution Manager -> Install – Diagnostics Agent:

The needed files can be downloaded from SAP Marketplace and are specific for the OS that you are running. In this example, we have:

First, we must choose the JVM version, that we are going to use. We should stick to SAP JVM 8 (latest version):

After this, the setup will ask us to provide the sources, mentioned before. After success we can continue with the next steps.

Since Diagnostics agent is a separate instance on the host, it needs an instance number. Most of the cases it is 98 (starting from the last available instance numbers). According to documentation:

In our case:

Please keep in mind that only one Diagnostics Agent is needed per host, no matter how many SAP Systems are installed on it.

The next important configuration step in the wizard is set the connection. We must provide JAVA SCS Message Server in this step:

If we have the request to use SSL connectivity, we should first configure the Solution Manager system’s JAVA AS to enable P4S port. This requires certificate. In our case, we will use the unsecure method:

After confirmation for the settings and finishing the installation, we can check on the host, that the DAA instance is started and <SID>adm is created (in our case the default one DAAADM):

If the status is GREEN, then we can proceed to the next step. If it is not, then we can check the status and the logs for issues using Internet Explorer and opening the address of the type:

http://<HOSTNAME>:50013/sapmc/sapmc.html?SID=DAA&NR=98&HOST=<HOSTNAME>;

or

https://<HOSTNAME>:50014/sapmc/sapmc.html?SID=DAA&NR=98&HOST=<HOSTNAME>

*you should have configured your Internet Explorer to work with JAVA and add the URL to trusted in JAVA control panel

We can open now the Agent Administration on AS JAVA. The URL is:

http://<HOSTNAME>:50000/webdynpro/dispatcher/sap.com/tc~smd~server~agent~admin/SMDAgentAdminApplicat...

and the newly installed agent will show up in the section Non-authenticated Agents:

We should mark the agent and click on Update Agents. After few minutes the agent will show up again in the same section, but the version will be latest (the one as the component on the AS JAVA):

If we update this exact component on the AS JAVA, then we can automatically update all the agents. PLEASE DO NOT UPDATE THIS COMPONENT SEPARATELY. The issue is that the AS ABAP is checking for consistency of the versions, so if you are on version SP09 on AS ABAP and AS JAVA and update on AS JAVA only component LM-SERVICE to SP10, then the AS ABAP will detect the difference and will bring up an error message in Solution Manager cockpit. If you need for some reason to update all agents on the managed systems, then you have to update the whole Solution Manager stack version, starting from the AS ABAP and then AS JAVA. If you install a newer SP of Diagnostics Agent on the managed system, after clicking on Update Agents it will actually downgrade the version on the managed system to match the one for the whole Solution Manager stack.

After matching the version of the Diagnostics Agent on the managed system, you can click on Trust Agents:

After this action, the credentials will be pushed to the managed system. If you have selected SSL communication over P4S port, at this step it will push also the generated certificate.

*** IMPORTANT: If you receive an error for the credentials at this point, you should check the date and time on the machines. If they have difference, you should stop the APP servers, adjust the date and time to be the same and to match between the hosts and start the app servers. After this you will be able to continue.

The result if the operation is successful is that the system is bein shown under Connected Agents with all details like versions, IP address, hostname, OS, JVM, uptime and others:

If the status is green, then we can move on to the next step.

2. Setup HDB User Store in HANA

We have to create a DB user in HANA, that we are going to use in the setup later. The roles, that this user will need are: DBA_COCKPIT and MONITORING.

We should set the user’s password not to expire and set parameter priority to value 8, so under extensive load, the agent will be able to report the status higher with priority.

3. Setup HDB User Store in HANA

To enable the HANA DB to report the status using the created user, we should register it in user store in HDB with the command

hdbuserstore SET <SID>SAPDBCTRL <hana-master-host>:3<Sys-No>15 USER password

executed with <SID>adm user for HANA. If the hosts are more than one, then we should use the command:

hdbuserstore SET <SID>SAPDBCTRL "<hana-master-host1>:3<Sys-No>15;<hana-master-host2>:3<Sys-No>15" USER password

To check if the command has set the properties successfully, we can use:

hdbuserstore LIST <SID>SAPDBCTRL

 

4. Register HANA in SLD

To send the data from the HANA system to SLD we should make the following configuration. Start the HANA Platform Lifecycle Management with <SID>adm and select “Configure System Landscape Directory Registration”

Provide the SLD user, that has the permissions, hostname and port of the SLD server:

And the configuration should be completed:

5. Check SLD and LMDB content for the system

After completing the Diagnostics Agent installation and SLD registration, the LMDB should be able to have all the details for the systems. It could take some time for the reporting. On the ABAP AS server, of B22 in our case, we should configure in /rz70 the SLD registration too. Diagnostics Agent should not be installed in our case, because B22 and H22 are on the same host, but if the APP server is on different host, there should also be installed one. The configuration in RZ70 is standard for ABAP systems:

To check the data in SLD, we can open http://<HOSTNAME>:50000/sld/

After logging in, we can check the systems that have been reported there in menu Technical Systems:

The HANA system is visible in the drop-down Technical System Type:

If it is not present there, you can check in the SLD menu Administration -> Maintenance -> CIM Instances and select the filter to HANA Database System

After selecting for example, the SYSTEMDB, we can see that there are 25 Associations:

This means that the system has reported successfully all the CIM info to the SLD and it has recognized the versions based on the CIM database on the SLD itself.

In case the system is not there, or it is there, but the Associations number is low (for example 2), this means that the SLD knows for this system (from the Diagnostics Agent or someone added it manually* ^{check the important remark at the end of the blog post}), but the Application server did not reported all the data to the SLD. In this case we should start troubleshooting on the HANA system. First, we have to check the logs:

To push a manual sync to SLD, we can use the following command:

sldreg -connectfile /usr/sap/<SID>/SYS/global/slddsdest.cfg -file /usr/sap/<SID>/HDB00/<HOST>/trace/sldreg.xml

Using this manual method, we will force reporting to the SLD using the cfg, that has been generated during the setup in the Lifecycle Manager UI. It will give us an error/result, so we can fix the issue. There is a helpful note for these type of issues: 2537537 (LINK)

After receiving the data to the SLD from HANA system, it will be transferred to the LMDB. We can check the data in LMDB by opening the following URL:

http://<HOSTNAME>:50000/sap/bc/webdynpro/sap/lmdb_wda_expl_oif?WDCONFIGURATIONID=LMDB_WDA_EXPL_OIF_C...

or by executing transaction /nLMDB on Solution Manager AS ABAP

There you can check if the system is reported fully automatically:

This means, that the data in the LMDB is received and collected properly and all versions and patch numbers are reported automatically:

6. Add Managed System in Solution Manager

After the data is transferred to the LMDB from SLD and Diagnostics Agents, we have all the information for the host and the systems on it. We are ready to start the setup of the process of adding the system as managed. In the SOLMAN_SETUP transaction, we can see the menu Managed Systems Configuration. Our new system should be reported there, but it will have all the marks unchecked – so we have to start the configuration process:

Note: H22 is the tenant DB and H220001 is the SYSTEMDB on the same host. The reason 0001 is added, is because the SYSTEMDB and the tenant DB are using the same SID. We must be careful, because if the SYSTEMDB is reported before the tenant, it could be swapped – H22 can be the SYSTEMDB – so always double check. It is noted in the third field (Display Name). There is an option to change the names if it is mandatory.

For the APP server, we have to select it and choose System Operations -> Maintain System -> Technical instances -> Central Services and if nothing is listed there, to click Add and input the Central Instance Service for the APP server. Should look like this:

Click on Save and we are ready to start the configuration by selecting the APP server (B22 in our case) and selecting Full Configuration:

On the first screen we have to click on Set Automatically for both – the Application Server and the Database:

Click on Next and select Execute on the automatic activity. It should be green, and if not – check the logs below. The next activity is manual, and we have performed it earlier on the step to create the HANA Database User, so select Performed and click on Next >

On the next step we have to create the RFCs between the managed system and Solution Manager. The process is automatic, but if you have set the system to Production mode, errors will appear that the roles and users cannot be created, this is the reason we have set it as Test system:

Step 4 is to assign the Diagnostics Agent. It should be present already, so click next and go the Enter System Parameters. Here you have to set the Introscope CA details for the AS ABAP (where it is installed). Also here is set the connection for the DBACOCKPIT. Here we have to set the user, that we have created in HANA DB and set as monitoring. Here is set also the port – we have checked before, that this user is set as Monitoring for the system on this port.

If here on the right side the Connection status is red, you can check the logs. Most probably if you have not completed the steps in the other document to enable the HANA support in the Solution Manager, the system will not have the libraries needed to communicate and will show an error.

In step 6 just check the parameters – they should be OK with the default ones, but if the system does not have the standard installation paths, then change here accordingly.

I step 7 Maintain Users, you should execute the activities. Nothing special:

In step 8 Finalize Configuration, we select Execute all. The result is the following:

Please note, that even the step is with failed status (1 errors), the error is “3 successful”. After re-executing the step, it will become green. The reason behind this, is because at the execution the script is pushing the extractors and does not have result on this.

The Single Sign-On is something different. It depends on the scenario of the whole Landscape. DO NOT execute it if it is already configured, because it will become a problem. If it is needed to be activated – complete the steps. We can set it to Performed.

For E2E Trace Upload service, we skip it in our scenario, the same is with the manual activities: Maintain SAP Router Data, Enable Remote R/3 Connection and Set Up Remote Connection to SAP HANA DB. They are needed depending on the scenario. We have to adjust the HTTP Log Parameter on the AS ABAP and restart it to become active:

Step 9 is used to check everything in total for last time and with this we have finished adding the AS ABAP to Solution Manager as managed system:

Next steps are similar, but we start the same setup by selecting the H22 system. When we start it, we will notice, that many of the configurations are already completed by the setup of the AS ABAP. Just move throughout every step and just confirm. Also do the same for the SYSTEMDB. There the only difference form the H22 is that we have to select different user for DBA Cockpit in step 5. We can create new one or use the SYSTEM user.

As a final configuration, go to tab Hosts and select the host. After this click on Configure Host:

Small wizard (4 steps) will start, again, everything is selected. Just needs confirmation (mainly because of the Diagnostics Agent).

With this we finish adding this host with HANA DB on it and also (because they share the same host) the AS ABAP. 

7. Report the system to SAP and check the results

After everything is completed with the setup and configuration, we can have the system reported to SAP. This is done by selecting the system in LMDB, going to the tab SAP Support Portal and selecting Upload to SAP Support Portal:

System will connect via SAPROUTER to SAP and will report the HANA installation. It will show up in Maintenance Planner with the name of the SYSTEMDB, in our case H220001, because it is the system Database. In the list of menu Explore System, it will be present with info about the Solution Manager SID that reported this system and the last time it has been reported:

After selecting it, we can start different processes like planning and so on…

All SAP SYSTEMS have SLD Data Supplier connection to the SLD (AS JAVA) and send the data there. Everything is combined in the LMDB, where configurations and combinations are created. After this, the LMDB report the data to the Maintenance Planner via connection to SAP. Only the last step is manual (can be configured as automatic), other steps (SID to SLD, DA to LMBD, SLD to LMDB are automatic).

*IMPORTANT REMARK: DO NOT create the systems in LMDB, SLD or in the Managed Systems Configuration MANUALLY. This can cause an issue when the system starts to report itself and prevents the troubleshooting in case of problems.

8. Useful links:

Managed System Setup for SAP HANA | SAP Diagnostics Agent Registration |SM_WORKCENTER - Important roles | Install/Upgrade ST-PI and ST-A/PI SAP

If you have any questions or you want to share something on the topic, you can always write a comment here or send me a message.

* the first two images in this blog post are taken from SAP's documentation and are not owned by me. The screenshots are made by me (Mihail Sevdiev) and are from systems in a test environment.

-edit- 12.09.2020: added link to the blog post explaining preparations needed for SAP Solution Manager 7.2 to support SAP HANA db instances.

[former_member296042]

Great post !! Thanks @sevdiev

[former_member688309]

Thank you for the feedback, matias.prado !

[former_member652386]

Excellent Post, very clear explanation, 10/10. Do you have any idea on HANA Duplicate entries Issue.

[former_member688309]

Hello arunkv,

Thank you for your feedback, it means a lot for me.

About the duplicate entries issue, could you please send me details in a private message of the exact issue you are having? If it is for a duplicate entries during upgrade, there is a note with explanation and solutions.

[former_member652386]

I don't see DBA_COCKPIT role in latest version of HANA Systems- hana2sp05 rev55

[former_member328528]

very good post with steps clearly explained.

Recently we upgraded our HANA to 2.0 . Somehow the HANA version still shows 1.0 in my Solution manager(7.2 SP10)'s LMDB for all managed HANA systems. Even the product instances shows HANA 1.0 products that were synced automatically.  I have tried the above steps mentioned but still not worked. Any idea what could go wrong?

[former_member688309]

Hi Saurav,

 

Sorry for the late reply. You can always check the HANA system's file that contains the extracted data. Can you please confirm, that the data there is correct (file is mentioned in step 5):

"To push a manual sync to SLD, we can use the following command"

There is the file, that should be with the updated version info.

[schroederchristian_jh]

Hi,

did you ever register to SLD via HTTPS?

Our SLD only supports TLS1.2 and didn't get a right communication because needed ciphersuites are not available i mean.

 

Best regards

Christian

 

 

 

[former_member688309]

Hello Christian,

 

Sorry for the late reply. If your SLD is communicating on the standard HTTPS port, then you can check on this article:

https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/en-US/48/b7b38cecf26745e10000000a421937/content.ht...

If you are using a custom (different) port, please take in account this:

https://launchpad.support.sap.com/#/notes/0002332263

About the different TLS versions, please check on the options for the updating the ciphersuites.

 

If you need additional help, please post the results of the troubleshooting, so I can try to reproduce the issue on my environment.

 

Thanks!

[schroederchristian_jh]

Hello Mihail,

we solved the issue with missing cipher suites on a HANA Server.

Solution was to set following environments in .sapenv.sh on Linux:

SAPSSL_CLIENT_SNI_ENABLED=TRUE
SAPSSL_CLIENT_CIPHERSUITES=150:PFS:HIGH::EC_P256:EC_HIGH

After that the sldreg was able to communicate with the right ciphers to our SLD and didn't got any handshake failures.

Best regards
Christian

[former_member688309]

Hi Christian,

 

Wow, great info, thanks for sharing. Will be in help for the future for sure.

 

Thanks again!

[former_member700278]

Hi

can we use Certificate authentication for SolMan DBACOCKPIT & HANA DBs? How

 

BR

Gagandeep Singh

 

[evelyn_curreri]

We configured our Hana systems as described on this blog, but recently failed over to secondary node and Solman was unable to connect to the secondary node (unless manually updating the b node on the dbacockpit configuration). We never had to do this before during a failover event. Are there any special considerations for Hana 2.0?

[former_member848213]

Thanks for the effort on making this blog ... but I found the blog confusing.

Where exactly do you create the H22MONITORING user? Is it the systemdb or tenant? It would be nice if this can be clarified.

[r_jakob]

Hello Ma Chi long,

 

I'm not OP but I can help you. H22MONITORING User needs to be created on DB level. You can do it via HANA Studio (like in explanation) or you could use Hana Cockpit (Database Explorer). User shall be created in Tenant of DB.

 

The other important user needed for registering DB to SLD is called SLD_DS_xxx and you need to ceate that user in SAP NW AS JAVA Administrator in UME. The User needs specific authorizations (pls check OSS note for that).

 

All the best - Jakob