Skip to Content
Author's profile photo Wolf Hengevoss

Agent Data in the SAP Solution Manager LMDB

Agent Data in the SAP Solution Manager LMDB

Many applications of SAP Solution Manager workcenters use data from managed application systems and the hosts where they are installed on. Such information is about details of the application system landscape, configuration settings as well as logs or performance metrics.

Figures 1a, 1b, and 1c show a Technical System in the LMDB, where agent data has been added to the information sent via SLD Data Suppliers:

Technical System in the LMDB with host data

Figure 1a: A Technical System in the LMDB – selection of host data display.


Technical System in the LMDB and host editor access

Figure 1b: A Technical System in the LMDB – host data and opening of the host editor.


Technical System in the LMDB with host data in the host editor

Figure 1c: A Technical System in the LMDB – host data in the host editor.


You see that the Diagnostics Agent itself is also handled as a Technical System and shown next to Technicla Systems of type AS ABAP and AS Java.

Setting Up Agents in the SAP Solution Manager

To be able to use agents’ data, you need to configure them. This is done in SAP Solution Manager.

There are two steps you have to perform:

  • Registration of Agents in the SAP Solution Manager (see section Landscape Data and Outside Discovery). This is done in step System Preparation in transaction SOLMAN_SETUP.
  • Assignment of the Diagnostics Agent(s) to a Technical System. This is done in step Managed System Configuration in transaction SOLMAN_SETUP.

Once these steps have been performed, your Technical System has been set up to be managed by SAP Solution Manager.

Agent Types

There are two agents which need to be installed for better system management:

  • Host Agents
  • gather information about the host’s operating system
  • important to have at least the minimum version of the host agent installed (For more information refer to SAP note 1365123, which contains a detailed presentation as an attachment. The setup of the automatic update process is described in SAP note 1473974.)
  • Diagnostics Agents (formerly called Solution Manager Diagnostics [SMD] Agent)
    • gather information of the managed application on the host systems
    • send it together with the data collected by the SAP Host Agent to SAP Solution Manager

Figure 2 shows the two agent types and how they are installed on the physical or virtual hosts (both can be installed with the same installer):

Agents: SAP Host Agent and SAP Diagnostics Agents on physical and virtual hosts

Figure 2: Agents: SAP Host Agent and SAP Diagnostics Agents on physical and virtual hosts.

One Host Agent must be installed for each physical host and one Diagnostics Agent for each “managed host” represented by physical, virtual or logical host name. One Diagnostic Agent can support multiple managed system components running on the same named host.

In a 3-tier system landscape additional Diagnostics agents need to be installed as one Diagnostics Agent can only report to a single SAP Solution Manager. Thus each managed host would need an own Diagnostics agent reporting to the SAP Solution Manager installation of the development or quality assurance landscape.
Note: In addition to the SLD Data Suppliers being part of the technical system itself, as of SAP Solution Manager 7.2, SPS06 the SLD can be a target for agent data – see SAP Note 2556432 – Switch Outside Discovery from Diagnostics Agent to SAP Host Agent. So you can address this issue using the mechanisms in the SLD – for details, see SLD Topology: How-To Gather and Distribute SLD-Data in Your IT-Landscape?

Data collected by the Agents

Landscape Data and Outside Discovery

Most of the landscape data application is already sent by the managed application systems to the System Landscape Directory (SLD) and from there synchronized to the Landscape Management Database (LMDB) of the SAP Solution manager 7.1. However, in some cases this data needs to be enriched by data which has been collected by agents and written directly to the CIM model based LMDB.

As the agents are neither part of the operating system nor of the installed application system of a host, the term “Outside Discovery” is used for this kind of data collection. In “Outside Discovery” both agent types work together in the gathering and sending process to SAP Solution Manager. Outside discovery works on three different areas:

  • OS discovery provides details about the operating system
  • DB discovery provides details about installed database software(s)
  • MS discovery provides details about Microsoft Internet Information Services on Microsoft operating systems.

Figure 3 shows different agents and their connections to the SAP Solution Manager:

SAP Host Agent gathers information on the host’s operation system

Figure 3: Agents: SAP Host Agent gathers information on the host’s operation system.

The Diagnostics Agent sends data on database or IIS to the SAP Solution Manager. Available Diagnostics Agents can be registered in the SAP Solution Manager directly (Host A1) or via the System Landscape Directory (B1).

Configuration Data

Besides the more static landscape information some functionality of the SAP Solution Manager may also rely on configuration data, which may change over time. Such configuration information (for example environment settings) is important in the configuration and change analysis or also in root cause analysis applications. Amongst other sources configuration data is frequently collected by the agents and persisted in tables on the managing SAP Solution Manager system.

Logging and Tracing Data

The Diagnostics Agent is able to collect logging and tracing data from the applications installed on a managed host and sends it to SAP Solution Manager for storage. This data is used for monitoring and alerting, root cause analysis, reporting and E2E tracing applications.

Monitoring Data

Another usage of agents is to collect monitoring data on OS level as well as on application system level from the agent host. This data is either sent to the directly to the SAP Solution Manager (such as availability data or file system monitoring) or to an Introscope EM (e.g. OS or application performance metrics) and processed further to SAP Solution Manager applications.

Data Flow in Outside Discovery

The data flow between hosts and the SAP Solution Manager is as follows:

  • Host Agents collect data and exposes it via web services to the Diagnostics Agents.
  • Diagnostics Agents process the data from SAP Host Agents and write into LMDB

Figure 4 shows the architecture of connections from hosts to the SAP Solution Manager and the consumers of such data:

Architecture of agents and data flow from agents to SLD, LMDB and consumers

Figure 4: Architecture of agents and data flow from agents to SLD, LMDB and consumers.

The SAP Host Agent on physical host B connects to the Diagnostics Agent running on the virtual host B1. In parallel, data from data suppliers is sent to the LMDB via the SLD.

Installation of Agents

There are two scenarios, when installing and configuring Diagnostics Agents. This depends on one hand side whether during installation of the Diagnostics Agent you know or do not know which SAP Solution Manager System you’re going to use to manage the system:

  • Usually the first happens when the agent is installed by using a Diagnostics Agent installation package.
  • The second scenario happens normally when the agent is installed silently during the setup of the managed application system.

Both installation scenarios may also be used in an unattended mode. The unattended mode allows the Diagnostics Agent installer package to be used in silent mode to automate the installation of a higher number of agents (please consult SAP Notes 1294713 and 1486330).

Similar to the Diagnostics Agent the SAP Host Agent can be installed in an attended and an unattended mode. It is part of the Diagnostics Agent installation package.

Agent Registration

In order to have a fully functional agent, two registration steps need to be done.

  1. The Diagnostics agent need to be connected to a SAP Solution Manager to download the latest applications from the managing system
  2. The managed systems need to be connected to the Diagnostics Agent(s)

For the first step depending on the installation strategy the agent is either registered directly to the SAP Solution Manager (mainly during the agent installation) or by usage of the agent candidate management during the SAP Solution Manager setup (when the agent has registered to SLD).

  1. During Diagnostics Agent installation, the SAP Solution Manager system is known:
    a. The Diagnostic Agent is already connected to SAP Solution Manager (the direct registration can also be performed after the agent installation using a configuration script on the agent host).
    b. Data is available in SAP Solution Manager directly and information about the existence of a Diagnostic Agent is optionally written to an SLD (in an SLD the agent itself is considered as a SAP technical system. Please note that the SLD must not necessarily be the same as used for the content synchronization to LMDB).
    c. During managed system setup, the system(s) running on the host with the Diagnostics Agent is (are) connected to the SAP Solution Manager and therefore can directly be linked to the managed system.
  2. During Diagnostics Agent installation, SAP Solution Manager is not known:
    a. The Diagnostics Agent is registered in an SLD (setting is done during installation).
    b. SAP Solution Manager in Solution Manager Setup during phase Preparation for SLDs and registered Diagnostics Agents.
    c. Available (not already used) Diagnostics Agents are connected to the SAP Solution Manager.
    d. During managed system setup, the managed system running on the host with the Diagnostics Agent is connected to the SAP Solution Manager

The host agent does neither register itself to an SLD nor directly to SAP Solution Manager. The communication to the SAP Host Agent is managed via Diagnostics Agent.

Agent Upgrade

Diagnostics Agents are taking their business logic (software) from the SAP Solution Manager system, which they are connected to. Therefore, all Diagnostics Agents in the landscape (that are running and connected) could be patched centrally, by applying an LM-SERVICE Java Software Component Archive on the Solution Manager System

In case a Diagnostics Agent has to be nevertheless upgraded, perform an uninstallation of the old release and do a fresh installation.

Additional Information


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Nicholas Chang
      Nicholas Chang
      Nice blog!
      Author's profile photo Alex MacMillan
      Alex MacMillan

      Why is  the agent information sent to the configured Solution Manager instance rather than the Central SLD?

      By bypassing the Central SLD you have eliminated the possiblity of replicating this agent data to other SLD's or LMDB instances.

      The Central SLD is no longer the most up to date data source in the landscape.

      Author's profile photo Wolf Hengevoss
      Wolf Hengevoss
      Blog Post Author

      Dear Mr. MacMillan,

      thank you very much for your feedback. The agent information you are talking about is very specific for monitoring purposes so it is sent to LMDB directly; the technical systems' data in the SLD is consumed by many other applications such as SAP NetWeaver Process Integration and Web Dynpro Java based applications.

      Best Regards,

      Wolf Hengevoss, SAP AG

      Author's profile photo Former Member
      Former Member


      Thanks for the blog. I have one question -

      We have SAP (single instance) running on Windows , but database is installed in another windows server. We have installed Diagnostic Agent in the SAP Server. To get database details do we need to install Diagnostic Agent in the database server as well ?

      If yes, Do we need to install Diagnostic Agent or only hostagent in the database server ?



      Author's profile photo Wolf Hengevoss
      Wolf Hengevoss
      Blog Post Author

      Dear Samik,

      For a detailed answer see SAP Note 1365123 - Installation of Diagnostics Agents I mentionad in my blog: The attachment in section "What is needed and where" should contain the description you need.

      Best Regards,


      Author's profile photo Juan de la Cruz Arellano Royo
      Juan de la Cruz Arellano Royo


      Awesome details about Agent Registration.

      I'm not totally convinced that the working way of "Outside Discovery" is correct, I mean. The network data (hostname, FQDN, IP) should not be provided by SAPHostAgent in order to avoid inconsistences and wrong data.

      For example, in my current client we work with "Physical Hosts", "Virtual Hosts" and "Logical Hosts". A "Physical Host" can contain (and it have) several "Logical Hosts" to separate logically the SAP systems (and other products).

      For example, if a Physical Host is called PHMAD0012 and contain the following "Logical Hosts" list:

      • LHBWD001 (Business Warehouse Development)
      • LHPID001 (Process Integration Development)
      • LHERD001 (ERP Development).

      When the diagnostic agent requests data to SAPHostAgent, sometimes not working properly. In our case the network data (hostname, FQDN, IP) are wrong. This is the result of outside discovery that we can check at SMDAgentAdminApplication:

      • LHBWD001 (DA1) = LHBWD001.correct.domain (should be LHBWD001.correct.domain)
      • LHPID001 (DA2) = LHPID001 (should be LHPID001.correct.domain)
      • LHERD001 (DA3) = PHMAD0012.correct.domain (should be LHERD001.correct.domain)

      We have tryed to set the SAPLOCALHOSTFULL for each Diagnostic Agent in their profile, stop/restart the agent, but that's not working propertly.

      So, We also have tryed to modify the CIM data of those Diagnostic Agent into Diagnostic Agent Editor but the SMD_RFC  user becomes to change it (I think that's Outside Discovery).

      Then, when we working in an environment that changes hardware too often, it's necessary that Diagnostic Agent collect the right network data.

      How to do it?

      Yours Faithfully

      Juan de la Cruz de Arellano Royo

      Author's profile photo Wolf Hengevoss
      Wolf Hengevoss
      Blog Post Author

      Dear Juan de la Cruz Arellano Royo,

      Thanks for letting me know about this. Having talked to experts, they expected the root cause of your problem to be in the area decribed in Note 962955 - Use of virtual TCP/IP host names.

      If the note does not help you in finding the issue, please open a message.

      Best Regards,


      Author's profile photo Ja Young Ha
      Ja Young Ha

      It is very helpful!

      Thanks a lot!

      And could you explain more detail about physical host and logical host?

      If the customer use IBM LPAR, HP NPAR or VMware ESX/ESXi as logical host, can I install the hostagent in the hypervisor?

      My understanding is the hostagent can be installed in OS, so I can install host agent in the maged system (which is LPAR, NPAR or VMware Guest OS).

      Do you think is it correct?

      Thanks a lot! 🙂

      Author's profile photo Wolf Hengevoss
      Wolf Hengevoss
      Blog Post Author


      details on logical and virtual host are to be found in the attachment to Note
      1365123 - Installation of Diagnostics Agents

      Best Regards,

      Wolf Hengevoss,

      SAP AG

      Author's profile photo Former Member
      Former Member

      Durning installation of Diagnostic Agent my SCS Message Server is affected by note:

      1878116 - P4 port not reachable

      How can I update my Messaging Server to list P4 (this note gives no solution).



      Author's profile photo Juan de la Cruz Arellano Royo
      Juan de la Cruz Arellano Royo

      Dear Grzegorz Niecka,

      These are my suggestions:

      • You must to check the System Profiles (Instance and ASCS or SCS)
      • Check the agent's profile.
      • After you modify and set the correct ports, verify the /etc/services configuration regarding the relevant services.
      • Have a view on /usr/sap/sapservices and modify it if you are sure about it
      • Stop the agent and execute the following command line with daaadm OS user in the correct directory (/usr/sap/DAA/SMDA<nn>/scripts)
      • Check in SolMan there are no app using 50004 port with lsof or netstat
      • Check there are not comunication problems with any firewall between the Managed System and SolMan with telnet.
      • Check the Diagnostic Agent startup log /usr/sap/DAA/SMDA<nn>/SMDAgent/log
      • Execute the following command line in each agent:

      ./ managingconf hostname:”sapms://SolManFQDN” port:”8101” (or the correct port) user:”SMD_ADMIN” pwd:”YourSMD_ADMIN-Password”

      • You can modify the protocol of each agent with SLDAgentCandidates

      Maybe you should delete entries of old configuration in SMDAgentAdmin and/or SLDAgentCandidates.

      Check the Outside Discovery logs for futher information.

      Following some links that may can help you:

      I wish you good luck with your Agent Configuration!

      Don't hesitate to ask me if you need anything else I can do for you.

      Yours faithfully

      Juan de la Cruz Arellano Royo

      Author's profile photo feng dongdan
      feng dongdan

      Thank u very much~ it is pretty conducive 😎

      Author's profile photo Jos Nouwen
      Jos Nouwen

      We have three Windows domains with each a separate dns domain.

      Problem is that the dev server for the bo platform has the same hostname as the qa server and the prod server.

      Outside discovery creates only one host in the lmdb and data is overwritten each time one of three diagnostics agent starts.

      Which steps to take to get all three hosts in lmdb ?

      Author's profile photo Wolf Hengevoss
      Wolf Hengevoss
      Blog Post Author

      Dear Jos,

      See SAP Note 1052122  - Host names in SLD and LMDB:
      "[...] Given the variety of name types used on the Internet (see above), SLD always applies a specific format for identifying hostnames. Identifying host names are written in lower-case characters and do not contain a network domain. [...]"

      To my understanding the 1st "." ending the host name the parts ".dev.." / ".qas..." / ".prd" are already belonging to the part that is not used to identify the host, while etc. would. ..

      I hope that helps.

      Best Reagrds,

      W. Hengevoss

      SAP SE