Landscape Management is your main application for the management and reporting of your system landscape. It comprises several pages that allow you to report on the LMDB content or to maintain advanced configurations, like disaster recovery (DR).
With SAP Focused Run 5.0 we introduced a new "Overview" page in our renamed Landscape Management application. The overview provides a high-level overview and a directed jump-in into the Landscape Management View for Technical Systems. Select your customer network to start getting the systems in the "Overview".
The Landscape Management view for technical systems offers information about the header data of technical systems such as EXTSID, system type, Installation Number, short display text, Lifecycle status, and IT Admin role. Additionally, the system database, status of data supplier completeness checks, and consistency checks are provided. You can customize the columns and order of the result set and export it to Microsoft Excel.
Starting with SAP Focused Run 4.0 FP02 it is possible to maintain several additional custom attributes at once via LMDB Tools.
Prerequisites:
With SAP Focused Run 4.0 FP02, we introduced a new technical system editor in the "Technical Systems" view.
This new technical system editor shows the managed system in a hierarchical view.
To open the technical system editor click on the hierarchy icon next to the technical system name in the technical system list.
On the left side of the editor, you see the system hierarchy. On the right side, you see the details for the system component currently selected in the graph to the left.
For bigger systems, you can switch to a convenient tree view.
On the right, you will find the new Detail View and related links. The related links can take you to the classical technical system editor or use cases supported for the selected component.
In LMDB Tools you can see the status of the data supplier completeness check for each system.
The status shown in LMDB Tools is the last status provided by the Self-Monitoring Data Supplier Completeness Check metric. This means to see the status in LMDB Tools, you need to setup the Self-Monitoring for the managed system using a template where the metric is active.
Click on the data supplier status in the column "Data Supplier Completeness" to see the details for each data supplier.
To (re)configure missing and outdated data suppliers, see SAP note 1869701 - Overview of the SLD Data Suppliers of Technical Systems
In LMDB, the status of system consistency can be evaluated via LMDB consistency checks.
Click on the check result bar in the column "Consistency Check" to see the checks and their results in detail.
The consistency checks can be executed one by one or all at once executing the report RLMDB_CHECK_REPAIR as described in SAP note 3457006.
To execute a consistency check for a specific system:
For some checks, you can repair inconsistencies automatically. If this is possible the "Repair inconsistencies" button on top of the check table will be active.
Find more information in the single checks in SAP note 3315520 - LMDB Consistency Checks
The view for Technical Instances offers information about technical instances for ABAP, JAVA, and HANA systems like instance host, type, and name. You can customize the columns and order of the result set and export it to Microsoft Excel.
The view for Products and Software Components offers reporting in the LMDB for software components and product versions. Based on a reporting use case, different filter options are available to perform searches and create reports on the objects in LMDB. You can customize the columns and order of the result set and export it to Microsoft Excel.
The view for Hosts provides an overview of all currently existing hosts. In addition to the default columns, you can also display specific additional attributes of the hosts. Furthermore, you can perform searches, customize columns, sort, and export the table content to Microsoft Excel.
Cross Datacenter Database Replication Association Maintenance enables you to maintain associations across different namespaces in the LMDB.
This concerns the "Disaster Recovery of Databases" use case, where the whole database setup is done in multiple data centers, resulting in a setup using multiple namespaces. An overall description of disaster recovery of SAP HANA is provided here.
For the technical implementation in the LMDB, you should consider the following example:
For disaster recovery (DR), we assume there are two data centers: one in Rot, where the primary and secondary databases are located, and one in Amsterdam, where the tertiary database is located.
The registration information from Rot is sent via reverse proxy. It arrives in the persistence layer via the WBEM client and CIMOM. The databases are stored in Namespace 1. In LMDB, the primary database is associated with the secondary database. The secondary database is also associated with the tertiary database. However, since the tertiary database is not in Namespace 1, it is only an empty placeholder.
The data center in Amsterdam reports the information for the tertiary database via the reverse proxy into LMDB. The database is reported for Namespace 2. The database appears to be complete. There are no associations to the databases in Namespace 1. This is our starting point.
We have enhanced the LMDB with the LMDB tool Cross Data Center Database Replication Association Maintenance to realize associations between databases in different namespaces. In this tool, you can create the namespace-independent associations.
In case of a failover, the primary and disaster recovery databases are exchanged.