Show TOC

Function documentationRegister Technical Systems Automatically by Data Suppliers Locate this document in the navigation structure

 

The preferred way of creating system landscape information in the Landscape Management Database (LMDB) is automatic system registration by SLD data suppliers, which are implemented on most system types. The data suppliers send their data to the System Landscape Directory (SLD), which forwards the information 1:1 to LMDB by synchronization. Some data suppliers, such as the SMD Agents (Outside Discovery), write directly into LMDB.

Prerequisites

  • You have performed the basic configuration of LMDB.

  • You have initially synchronized SLD and LMDB. For more information, see Connect LMDB to System Landscape Directory (SLD).

  • You have maintained the users and authorizations for systems to be connected:

    • AS ABAP administration user

    • AS Java administration user

    • For all other products, see the product IMG.

    • SLD user: SLDDSUSER or another user with SAP_SLD_DATA_SUPPLIER role.

Features

Each architecture entity has its own data supplier, which is described in detail in its documentation. For hosts, Microsoft IIS, and databases, the SMD Agent supplies data by “Outside Discovery” and writes directly into LMDB. Outside Discovery enhances the system information, which would not be sufficient otherwise. All data suppliers that use the executable sldreg are configured in the same way; for more information, see SAP Note 1018839.

Information for some other system types must be created manually. The following tables list the recommended system integration procedure per system type.

Detailed information about individual products is beyond the scope of this setup guide. For more information about the configuration of specified products, see Maintenance of Products in the System Landscape in the SAP Community Network at http://wiki.sdn.sap.com/wiki/x/4I-uDQ.

Technical System Type

Name of Available Data Supplier

Comment on Data Supplier

Application Server ABAP (AS ABAP)

BCSystem

Since release 4.0B, there is an SLD data supplier for AS ABAP. Always register an AS ABAP in SLD with transaction RZ70 and the system information will be synchronized automatically with LMDB and SMSY. For more information, see Setting Up the SLD Data Supplier for AS ABAP-Based Systems in the SAP Help Portal at https://help.sap.com.

Application Server Java (AS Java)

J2EESystem

The data supplier is usually set up during system installation. Until NetWeaver Release 7.0, the configuration can be performed manually in the Visual Administrator. For Release 7.1 and above, the configuration is done in SAP NetWeaver Administrator. Since NetWeaver Version 7.02, the AS Java data supplier delivers the information about installed product instances, so installed products only need to be configured in LMDB for older NetWeaver versions. For more information, see Setting Up the SLD Data Supplier for Java-Based Systems in the SAP Help Portal at http://help.sap.com.

Apache Tomcat Server (ATC)

ATCServer

The data supplier for the Apache Tomcat server delivers product information. But product information is not always provided for the installed applications, so manual post-processing in LMDB can be required.

SAP BusinessObjects Cluster (BOBJ)

BusinessObjectsEnterpriseSystem

The data supplier for SAP BusinessObjects Enterprise (BOE) delivers product information.

For other BOBJ products, information is provided by the Unspecific Application System data supplier.

Database System (DBSYSTEM)

-

Database system information is delivered by various data suppliers, e.g. AS ABAP. The SMD agent Outside Discovery delivers all the information directly to LMDB (the information is not available in SLD). The Outside Discovery delivers software component information, which is sufficient for database systems, so manual post-processing in LMDB is not required.

Diagnostics Agent (DIAGAGENT)

DiagnosticsAgentInstance

There are data suppliers for diagnostics agents, which deliver all necessary information, so manual post-processing in LMDB is not required.

External Service (EXT_SRV)

-

External services describe any kind of Internet service or on-demand service. Only a minor description is required, which you create in LMDB, manually.

SAP HANA Database (HANADB)

HanaDatabase

An sldreg—based SLD data supplier is available as of SAP HANA Platform 1.0 SPS 04.

Wily Introscope Enterprise Manager Server (IS_EM)

-

You manage information about the Introscope Enterprise Manager, in the SAP Solution Manager transaction SOLMAN_SETUP, so manual post-processing in LMDB is not required.

Wily Introscope Manager of Manager (IS_MOM)

-

You manage information about the Introscope Manager of Manager in the SAP Solution Manager transaction SOLMAN_SETUP, so manual post-processing in LMDB is not required.

SAP liveCache

-

The liveCache system information is provided by the following versions of the AS ABAP data supplier: 640 SPS23, 700 SPS17, 701,702 710 SPS07 and all higher releases. In all other cases, create the SAP liveCache manually in the LMDB technical system editor. The data supplier provides no product information, so assign the SAP liveCache product instance to the SAP liveCache system in the technical system editor.

SAP NetWeaver Master Data Management Server (MDM)

MDM_Server

MDM provides an sldreg—based data supplier. For more information see http://service.sap.com/installmdm71

Microsoft Internet Information Service (MSIISINST)

MSIISInstance

The data suppliers deliver product information about the Microsoft Internet Information service via Outside Discovery. You must specify the products of the applications which run in the MSIISINST, manually.

.NET System (MS_.NET)

StandaloneDotNetSystem

The data supplier can deliver product information for .NET systems.

TREX System

TREXSystem

The data supplier does not deliver product information, so you must enter it in the LMDB technical system editor, manually.

SAP Web Dispatcher (WEBDISP)

-

There is a data supplier, but it does not deliver product information, as of version 7.2. You must add the product information in LMDB.

Sybase Unwired Platform (SUP)

SUPSystem

The Sybase Unwired Platform registers itself in SLD with product information.

IBM WebSphere Cell (WEBSPHERE)

IBMWebsphereSystem

There are data suppliers that deliver product information. Manual post-processing in LMDB may be required for the applications which run in WebSphere.

Unspecific Cluster System (UNSPECIFIC),

Unspecific Standalone Application System (UNSPAPP)

UnspecificClusterSystem,

UnspecificStandaloneApplicationSystem

There are data suppliers that provide product information, so manual creation in LMDB is not required.

If there is no data supplier for an unspecific application system, you can manually create the information in the LMDB.

Unspecific Three-Tier System (UNSP3TIER)

-

Create the system description in LMDB, manually.

Host (Computer System)

A host is not really a technical system – technical systems are installed on hosts. The technical systems are based on the host, but because the host is an underlying entity, accurate information about it is important. The required detailed information is provided by the Outside Discovery, via the SMD agent. As of release 7.1 SP2, SAP Solution Manager contains a host editor. For more information, see the Host Editor section.

Unspecific Three-Tier-System

An unspecific three-tier system describes any three-level system architecture:

  • Level 1: a distributed (cluster) system

  • Level 2: technical instance installed on a single host

  • Level 3: a group or individual operating system processes

Unspecific three-tier systems are always created manually, there is no automatic data supplier. Typical examples are JEE servers besides AS Java and IBM WebSphere.

Unspecific Application Systems

There are several variants (technology types) of unspecific application systems. They can be stand-alone (UNSPAPP) or a cluster (UNSPECIFIC). An unspecific stand-alone application system has only one server, an unspecific cluster application system can have several application servers.

Currently, there are the following unspecific application systems:

Unspecific Application System Technology Type

Type

Product

Data Supplier

ALLOY

Stand-alone

SAP Alloy (IBM)

yes

BCMClusterTechnology

Cluster

SAP BCM SOFTWARE

yes

BOFC_Cluster

Cluster

SBOP FINANCIAL CONSOLIDATION

yes

BPCMSCluster

Cluster

SBOP BPC MS

yes

BPCNWCluster

Cluster

SBOP BPC NW

yes

ClickSoftwareCluster

Cluster

SAP WS BY CLICKSOFTWARE

yes

ConvergentChargingCluster

Cluster

SAP Convergent Charging

yes

CSLCluster

Cluster

TPT Commodity SL

yes

DataServicesCluster

Cluster

SBOP Data Services

yes

EPOSCluster

Cluster

SAP ENTERPRISE POS

yes

ESOCluster

Cluster

SAP SOURCING/CLM

yes

InfoInterchangeServer

Stand-alone

SAP INFO INTERCHANGE

yes

LiveEnterprise

Cluster

SBOP EVENT INSIGHT

yes

MigrationCluster

Cluster

SMSY Migration

yes

MSReportingService

Stand-alone

MSAnalysisService

Stand-alone

MSIntegrationService

Stand-alone

Others

(can only be used for technical systems entered manually; dedicated for project-based integration of customer products in SAP Solution Manager)

Cluster/Stand-Alone

Standard customer-specific product

no

PCMCluster

Cluster

SBOP PCM

yes

PMCluster

Cluster

SAP PROMOTION

yes

RTOMCluster

Cluster

SAP RTOM

yes

SAPPOS_Cluster

Cluster

SAP POS

yes

SBOPEnterprise31

Cluster

SBOP Enterprise 3.1

yes

More Information