Skip to end of metadataGo to start of metadata

• Sap Sld Url
• Sap Hana 2.0 Sld Registration
• Sap Hana Sld Registration Renewal

The steps described in this wiki page have to be performed after finishing the SAP HANA setup steps on the SAP HANA database, the SAP HANA host and the SAP Solution Manager host, to finish the SAP HANA managed systems setup and make the SAP HANA system available for System Monitoring setup.

Virtual dj 7.1. SAP HANA, platform edition 2.0 Keywords KBA, sld registration, virtual host name, virtual hostname registration, HAN-DB-HA, SAP HANA High Availability (System Replication, DR, etc.), HAN-DB, SAP HANA Database, Problem. The fixes address flaw in the following SAP products: Business Client, HANA XSA, ABAP Platform (SLD Registration), Disclosure Management, Solution Tools Plug-In (ST-PI), Note Assistant, Business Objects, Manufacturing Integration and Intelligence, Business One Mobile Android App, and WebIntelligence BILaunchPad (Enterprise).

• You have configured the SAP HANA system to connect to the System Landscape Directory (SLD). The registration itself is performed by the SLD data supplier service. This configuration task can also be performed in batch mode and using a configuration file.
• HANA information is missing or incomplete after register to SLD using HDBLCM tool. Incomplete information of HANA in SLD can lead to issues in Solution Manager, like: The definition of Technical System 'SIDHANADB' is not correct. Only 2 associations class SAPHDBSystem in SLD.

Prerequisites

Make sure you have performed the OS and DB level preparations for the Managed System Configuration as described here: Prepare Managed System Setup for SAP HANA

Check SAP HANA System in LMDB

Before running the managed system setup, you should check if the SAP HANA system was successfully reported from the SLD into LMDB of SAP Solution Manager. If you changed the SLDSYSTEMHOME for HANA to the SAPDBHOST in ABAP, the assignment between HANA and the ABAP system should happen automatically.

Even if the ABAP system already registered a HANA earlier via the RZ70 SLD data supplier, as long as HANA and the ABAP system register with the same SystemHome value, the assignment between HANA and ABAP system happen automatically. The formerly registered RZ70 HANA system will be enriched with the additional information from the HANA SLD data supplier.

Please note that SAP HANA systems with MDC and/or System Replication will have to look differently in LMDB than a simple SAP HANA installation. Please refer to the respective wiki pages for more information.

Call transaction LMDB and select your HANA system by switching the Type to SAP HANA Database and entering the relevant Extended System ID.
Click on 'Display' or 'Edit'. On the first page 'System Overview' please verify that the product version is supplied automatically.

On the 'Software' page, check the SAP HANA DATABASE software is marked as 'Installed on Instance'. This should at least be the case for the HANA master node.

Make sure all HANA nodes are reported under 'Technical Instances'. In our case it is just one node, for multi-node HANA databases you should see multiple lines under “SAP HANA Database Server”.

In case your ABAP system is running on HANA, please check that the database is known to your ABAP system matches the HANA DB. To do this, open the ABAP system in LMDB and check the database information under System Database.

Run Managed System Setup for HANA

The next step is to run the managed system configuration for SAP HANA. Unlike other database systems, SAP HANA has its own Technical System Type. Here we have to distinguish between a setup for a standalone HANA and an ABAP system having a HANA as a DB. For ABAP on HANA it is enough to execute the guided procedure for ABAP, which will include the HANA relevant steps as well.

Before you can run the managed system setup, make sure that the Diagnostics Agents for all HANA nodes are available. HANA nodes always register with their internal HANA hostname. So if you installed the agents manually without HLM but with the external HANA hostname you might have to create agents on-the-fly for the internal HANA hostnames. Or you just install the agents with the internal HANA hostname to begin with.

More information on agents on the fly can be found here.

To start the managed system setup for HANA, call transaction SOLMAN_SETUP → Managed System Configuration. Search for your HANA System. You’ll find it on the tab “Technical Systems”.

In the first step Assign Product you have to assign product information to a technical system. To do so, click on Edit button at the top screen and click on Set Automatically to set a diagnostics-relevance flag.

In the second step Check Prerequisites you perform an automatic activity to verify if the prerequisites are met.

In the step Assign Diagnostics Agent an agent should be assigned to each server where a HANA node is installed. Furthermore, you can check the status of the corrensponding SAP Host Agent.

In the next step you have to maintain the system parameters. To set up the DB Connection in this step you can use the same MONITOR user, created during HANA preparation steps for monitoring earlier.

If you have any problems creating the DB connection, check if there is a DB connection in table DBCON (transaction DBCO). If yes, test the connection using the report ADBC_TEST_CONNECTION. The output of this report will tell you what is wrong and also lead you to the trace file of the workprocess in which the error occurred. If the DB connection doesn't exist yet, please try to create it in DBCO and test it.

The most common reasons for failures here is a not correctly installed HANA client or missing HANA DB libraries. Please refer to the section about the HANA client installation.

In the Enter Landscape Parameters verify and add/change landscape parameters, if required.

The step Finalize Configuration consists mostly of automatic activities, which are relevant for data collection for scenarios like System Monitoring or Root Cause Analysis. Especially, ensure that the extractor relevant steps (Database Extractor and Extractor Setup) are finished successfully. The manual steps are relevant for a remote SAP support.

Check Configuration step performs a configuration check and updates a system status in the overview of the Managed System Configuration.

If you run a multi-node HANA DB, a manual step is required to make sure, that the HANA is still reachable, if the master node moves to another host.

To ensure that the HANA DB can be monitored and reached by DBACOCKPIT no matter who the master node ist, you have to adjust the DB connection used by DBACOCKPIT. You have to add all possible HANA master noder servers to the DB connection string.

Call transaction DBCO and open the DB connection for the HANA DB in change mode. Add the server names for all possible master nodes and ports separated by semicolon in the form:

Run Managed System Setup for ABAP on HANA System

Run the managed system setup for the ABAP on HANA system as usual. There will be some additional, ABAP relevant steps, like Maintain RFC's or Maintain Users, but in general the step sequence of the guided procedure is very similar to the one for HANA.

Troubleshooting

If you have problem with the managed system setup please refer to the Troubleshooting section of this wiki.

• SAP Solman Tutorial

• SAP Solman Useful Resources

• Selected Reading

We have covered some part of System Landscape information under Solution Manager Infrastructure. SAP Solution Manager applications- Technical monitoring, system maintenance captures all information regarding upgrades with Maintenance planner, alerting policy from system landscape. SAP Solman contains the detailed information about technical system landscape.

LMDB is a central repository for Solution Manager to capture all the information and it uses the same CIM model that is used by System Landscape directory. Landscape information contains two parts- SAP software catalog CR content and information sent from SLD.

Sap Sld Url

LMDB connection to SLD

LMDB gets all the information from the System Landscape Directory where all the systems register itself. Most of the technical systems contain data suppliers that provides direct information to SLD for registration.

The LMDB receives SLD changes automatically when a change occurs, using polling by LMDB, or active change notifications by the SLD.

SLD contains data from managed system and their data suppliers, which automatically pass all the information in SLD. The transaction code used for ABAP system is RZ70.

Sap Hana 2.0 Sld Registration

SLD Synchronization is the most common way to transfer Landscape information to LMDB. When Solution Manager is initially set up, it transfers complete Landscape from SLD to LMDB in Solution Manager. This also includes the information from Software catalog.

Once initial full synchronization is done, an incremental synchronization is triggered every 10 minutes.

System Landscape Directory

This directory contains the information about landscape and software component versions. A SAP system can be configured to register under SLD. System Landscape Directory manages information about all installable and installed elements of your system landscape.

You can find the following links in a web page −

Landscape − Under Landscape, you can find the following options.

• Technical Systems − You can view and define systems and servers.

• Landscapes − You can view and configure group of systems.

• Business Systems − You can view and configure business systems for use in Process Integration.

Software Catalog

• Products − To view products in SAP software catalog.

• Software components − To view software components in SAP Software catalog.

• Development

• Name Reservation − This is used for name reservation for NW development.

• CIM Instances − This is used to view and maintain data on CIM level.

System Landscape Directory is based on SAP NetWeaver. The following versions of SAP NetWeaver are supported for SLD synchronization with LMDB −

When your Central System Landscape Directory, integrated with LMDB, does not meet the requirement, you can use a local SLD and synchronize it with central SLD.

Managing Technical System Information

Technical system is known as a software element installed on host system. It can be a standalone system or software elements installed in distributed environment. Technical systems are central element of the Solution landscape in terms of software component deployment and operational activities, such as monitoring and alerting

When a software is installed, technical components are created in the system and they are registered under System Landscape Directory. This information is forwarded to Solution Manager LMDB either manually or using synchronization between LMDB and SLD.

Technical systems are identified using their name, system id or any installation number that has been assigned. Common Technical system types can include −

• Application Server (AS) ABAP
• Application Server Java
• TREX system

In the following table, you can see different Technical system types that can be maintained in LMDB, their source and Editor.

The following technical system types can be maintained in LMDB −

Sap Hana Sld Registration Renewal