Introduction Landscape: Management Database (LMDB):
The Landscape Management Database (LMDB) is a directory of system landscape elements. To describe them, LMDB uses the SAP enhancement of the Common Information Model (CIM; for more information, see www.dmtf.org). Typical model elements are technical systems, product systems, products, and software components.
The main task of LMDB is to centrally provide information about the system landscape. The System Landscape Directory (SLD) and the SAP Solution Manager System Landscape (SMSY) provide comparable functions, with different technologies, for different purposes. LMDB aims for a more flexible extendibility of the landscape model and for using the same landscape data model as the SLD in a unified approach.
LMDB was introduced with SAP Solution Manager 7.1 and since then is mandatory.
If you upgrade from SAP Solution Manager 7.0 to 7.1, you must configure LMDB. As of SAP Solution Manager 7.1, technical system data can only be maintained in the technical system editor of LMDB, not in SMSY any longer.
Integration of LMDB into Landscape Data Management Topology
Landscape Management – “The Big Picture”
The following graphic describes the flow of landscape data management components.
Sources That Provide LMDB Content
The content of LMDB comes from the following sources, independently of the technical data flow:
System Landscape Directory (SLD)
To create landscape descriptions in LMDB, SLD synchronization is the preferred way.
SLD gets landscape data from data suppliers, which are implemented in the managed systems, for example Application Servers ABAP send data to SLD with transaction RZ70.
Technically, LMDB is the ABAP complement of Java-based SLD. SLD and LMDB synchronize contents in the same way two SLD systems do. All data from a connected SLD can be synchronized with LMDB in a 1:1 relationship.
Outside Discovery
Some data suppliers on technical systems write landscape data directly into LMDB. They are called “Outside Discovery”.
SAP Software Catalog (CR Content)
Data about available products and software components is delivered in the SAP Service Marketplace. This CR content is transported to SLD and synchronized 1:1 into LMDB. It comprises SAP products as well as registered third-party products.
For more information, see SAP note 669669.
SAP CIM Model
The current SAP CIM Model is delivered by the SAP Service Marketplace via SLD, like the SAP software catalog.
Technical System Editor in LMDB
If there is no data supplier, or if it cannot be used (for example because of a firewall), you can manually register a system in the Technical System Editor of LMDB. The disadvantage of this
manual method is that you also have to update manually created data manually, otherwise, it can become obsolete. If the system is subsequently registered by an SLD data supplier, information that was entered manually before is not overwritten.
SAP Solution Manager System Landscape (SMSY)
Data migration from SMSY to LMDB is an optional step in SAP Solution Manager Configuration (transaction SOLMAN_SETUP). It copies technical system information from SMSY into LMDB, usually only once and immediately after upgrading to SAP Solution Manager 7.1
The Landscape Management Database (LMDB) is a directory of system landscape elements. To describe them, LMDB uses the SAP enhancement of the Common Information Model (CIM; for more information, see www.dmtf.org). Typical model elements are technical systems, product systems, products, and software components.
The main task of LMDB is to centrally provide information about the system landscape. The System Landscape Directory (SLD) and the SAP Solution Manager System Landscape (SMSY) provide comparable functions, with different technologies, for different purposes. LMDB aims for a more flexible extendibility of the landscape model and for using the same landscape data model as the SLD in a unified approach.
LMDB was introduced with SAP Solution Manager 7.1 and since then is mandatory.
If you upgrade from SAP Solution Manager 7.0 to 7.1, you must configure LMDB. As of SAP Solution Manager 7.1, technical system data can only be maintained in the technical system editor of LMDB, not in SMSY any longer.
Integration of LMDB into Landscape Data Management Topology
Landscape Management – “The Big Picture”
The following graphic describes the flow of landscape data management components.
These are the basic steps to distribute technical system information in the system landscape and in SAP Solution Manager:
1. You set up data suppliers that will automatically register technical systems in the System Landscape Directory (SLD). The setup can be done for ABAP systems with transaction RZ70, for Java systems with the Visual Administrator or NetWeaver Administrator, for third-party systems with the sldreg executable, or other clients to transfer information.
2. In a full, automatic synchronization, the landscape description, CIM model, and SAP Software Catalog (CR Content) are copied to the Landscape Management Database (LMDB).
3. Technical system descriptions are continuously replicated from LMDB to the Solution Manager System Landscape tool (SMSY) to keep SMSY updated. Note that during the following SAP Solution Manager versions, more and more SMSY functionalities will be merged to LMDB.
3* Optionally, you can migrate technical system descriptions that were created in SMSY manually to LMDB. This is a one-time activity. Afterwards, you must create information in LMDB only.
4. Different SAP Solution Manager applications access the landscape descriptions of LMDB and SMSY, for example, the Maintenance Optimizer, Monitoring and Alerting, and Root Cause Analysis.
5. Based on the landscape descriptions, the applications monitor, maintain, and enhance technical systems.
The content of LMDB comes from the following sources, independently of the technical data flow:
System Landscape Directory (SLD)
To create landscape descriptions in LMDB, SLD synchronization is the preferred way.
SLD gets landscape data from data suppliers, which are implemented in the managed systems, for example Application Servers ABAP send data to SLD with transaction RZ70.
Technically, LMDB is the ABAP complement of Java-based SLD. SLD and LMDB synchronize contents in the same way two SLD systems do. All data from a connected SLD can be synchronized with LMDB in a 1:1 relationship.
Outside Discovery
Some data suppliers on technical systems write landscape data directly into LMDB. They are called “Outside Discovery”.
SAP Software Catalog (CR Content)
Data about available products and software components is delivered in the SAP Service Marketplace. This CR content is transported to SLD and synchronized 1:1 into LMDB. It comprises SAP products as well as registered third-party products.
For more information, see SAP note 669669.
SAP CIM Model
The current SAP CIM Model is delivered by the SAP Service Marketplace via SLD, like the SAP software catalog.
Technical System Editor in LMDB
If there is no data supplier, or if it cannot be used (for example because of a firewall), you can manually register a system in the Technical System Editor of LMDB. The disadvantage of this
manual method is that you also have to update manually created data manually, otherwise, it can become obsolete. If the system is subsequently registered by an SLD data supplier, information that was entered manually before is not overwritten.
SAP Solution Manager System Landscape (SMSY)
Data migration from SMSY to LMDB is an optional step in SAP Solution Manager Configuration (transaction SOLMAN_SETUP). It copies technical system information from SMSY into LMDB, usually only once and immediately after upgrading to SAP Solution Manager 7.1
No comments:
Post a Comment