Landscape data is for some time being uploaded to SAP Support Portal – for example to enable for the Early Watch Alert. Now, landscape planning tools like Maintenance Planner emerge in the SAP Support Portal using that data, so its importance is increasing massively. With new use cases and high importance you have to take into account a valid topology of three layers of landscape data tools now: The System Landscape Directory (SLD), SAP Solution Manager Landscape Management Database (LMDB), and the SAP Support Portal Customer Profile. This blog describes how to avoid erroneous data in this highest layer. While the topology recommendations for SLD and LMDB systems have been described in detail, the connection to the top layer may need some investigation…
Tools, Entities, and Their Connections
These are minimum pieces of information you need to understand why there are three levels of repositories containing data related to landscape management.
- System Landscape Directory: This is where landscape data mgmt. starts. The SLD gets and gathers data from the technical systems and provides this information for several client applications such as SAP Process Integration (for this client, in the SLD business systems are created manually) and SAP Solution Manager.
- Landscape Management Database: The LMDB is seen in this blog mainly as a tool uploading data retrieved from the SLD to the Customer Profile. But there are two more things: The LMDB enriches SLD data in several ways – automatically by agents and manually by adding information that is not exposed to the Customer Profile, such as business partner information, so the LMDB is your source for detailed information on your landscape.
- Customer Profile: For the Maintenance Planner it provides (only) those data required to calculate update, upgrade, and conversion of systems.
What is the “Customer Profile”? As System Landscape Directory and Landscape Management Database, the Customer Profile is a repository for landscape data. In contrast to SLD and LMDB the Customer Profile is hosted with several applications in the SAP Support Portal storing
- …system data of all customers, handling the access by customer numbers assigned to S-users
- …but selected parts, for example sensitive data such as business partner information are excluded
By this, authorized access for users and tools is centrally possible, forming a source of truth making a joint approach to problem solving easier, for example in an incident.
The following figure shows the way, system data gets into the customer profile and are accessed by customers:
Figure 1a: Upload of data from customer landscapes into the SAP Support Portal Customer Profile: Data is sent to the SLD, synchronized with the LMDB and from there uploaded to the SAP Support Portal; (also see figure 5); access to system data in the Customer Profile is only possible through application using the customer number assigned to the technical system. The SID of the uploading SAP Solution Manager is also stored with the data.
Getting Data of the IT Landscape
Getting Data of the IT landscape hasn’t changed: SLD and LMDB gather the data from SLD Data Suppliers and host agents running on technical systems and the LMDB uploads it to the SAP Support Portal:
Figure 1b: Data flow from the technical system to the Customer Profile read by the Maintenance Planner in Detail.
So you need not change these steps if switching to the Maintenance Planner – all data is provided via SLD and LMDB; if still in doubt about these processes, see the detailed information on data and access:
- Software Catalog Data aka CR CONTENT in SLD and LMDB
- Technical System Data Delivered by SLD Data Supplier and Agents
- Uploading, Accessing, and Trouble-Shooting System Data in the Customer Profile Used for Planning Changes in Your IT Landscape
- House-Keeping in the Customer Profile Data Used by the Maintenance Planner
Questions on connections between technical systems, SLD, and LMDB are discussed in the topology part.
The process of sending data to the customer profile, however, will only deliver good data quality, if the involved systems (SLD, LMDB, and their connections to the customer profile) are set up sensibly. This network of systems managing landscape data is what we call their topology.
Topology of SLD and LMDB
Best practices for these tools are available since years. Obviously, still – or even increasing – this knowledge is absolutely necessary for having up-to-date
landscape data in SAP Support Portal (see figure 1). Therefore, if you’re not familiar with this topic, read the following blogs:
- SLD Topology: How-To Gather and Distribute SLD-Data in Your IT-Landscape?
- SLD-LMDB Topology – Connections, Valid, and Invalid Data Exchange Between SLD and LMDB of SAP Solution Manager
Enhancing SLD and LMDB Topology by the Connection to the Customer Profile
Being principles of handling data in repositories, all principles named in the topology blogs for SLD and LMDB apply to the customer profile. You only need to apply them to the last layer. The recommended landscape looks like the following figures. They will describe a scenario each. The following symbols are used to describe connections between SLD, LMDB, and SAP Support Portal:
Default Recommendation – 1 SAP Solution Manager System Uploading Data (no Test System)
One SAP Solution Manager system with role = productive uploads via scheduled automated or via manual direct upload to the SAP Support Portal. The following figure shows this scenario:
Figure 2 shows Scenario 1a – default setup: 1 SAP Solution Manager system uploading data. SAP Solution Manager in role = prod. uploads via
scheduled landscape fetch job or via manual direct upload to the SAP Support Portal.
Note: For SAP Solution Manager 7.2 –this versions is currently in ramp-up and not generally available until officially declared so – there is amn important requirement regarding the SAP NetWeaver version of the SLD. For details see:
Required SAP NW Version of the Source SLD for LMDB in SAP Solution Manager 7.2 & Options to Get there
Default Recommendation – 1 SAP Solution Manager System Uploading Data (with Test System)
1 SAP Solution Manager in role = prod., one = test: Only prod uploads via landscape fetch or via manual direct upload to SAP Support Portal.
Since Solution Manager system with role = test do not upload data to the SAP Support Portal, the handling is almost the same.
The following figure shows this scenario:
Figure 3 shows default setup with a test system of SAP Solution Manager: 1 SAP Solution Manager uploading data. SAP Solution Manager in role = productive uploads via scheduled landscape fetch or via manual direct upload to SAP Support Portal. Note, that one SLD provides data for both Solution Manager systems so that their input is identical.
Alternative: 2 (or more) productive SAP Solution Manager Systems Uploading Data
Here, test systems of SAP Solution Manager are not shown. This scenario is only valid, if both SAP Solution Mangers get completely separated data: Separate SLD for each Solution Manager with no data exchange required plus unique SID/host name combinations (to be ensured by a naming convention) are required.
The reason is that otherwise, you would violate the unique-path-principle, sending data of the same system through different paths, so that contradicting versions of the same system would be shown: System data of the same system would turn up twice, separated by the Sap Solution Manager uploading the data: Such a setup can happen at value added re-sellers and big customers having separated IT landscapes.
The following figures shows this scenario in a valid and an invalid form:
Figure 4a: What may seem as being same scenario as in figure 3, is invalid: both are productive SAP Solution Manager systems get the same data being connected to the same SLD and both are productive, uploading data.
This scenario is shown in its valid form…
Figure 4b: Both SAP Solution Managers get completely separated data (from separated landscape areas) being connected to separate SLD for each SAP Solution Manager system with no data exchange required plus unique SID/host name combinations (to be ensured by a naming convention).
…and in an invalid form:
Figure 4c: Another invalid scenario would be using different SLD systems, which have connections by transport, forwarding, or sync.
Upload via the LMDB Technical System Editor & Settings Avoiding Duplicate Uploads
If you cannot avoid all overlap of system data more than one productive SAP Solution Manager systems, you can still avoid compromising the data in the customer profile: Disable the automatic landscape fetch job for overlapping systems individually in all but one of the productive SAP Solution Manager systems. In LMDB, navigate to the technical systems in question, go to edit mode and on register card SAP Support Portal set System Synchronization to “Do Not Synchronize Selected Technical System”:
Figure 5a: Settings for the upload of technical systems data: The “cross system setting” can be deactivated for individual systems. (Example: LMDB in SAP Solution Manager 7.1.)
The setting can be done for the whole SAP Solution Manager. You’ll find the description when you click the “i”-button on tab SAP Support Portal in the LMDB:
Figure 5b: Cross-System-Settings for the upload of technical systems data. (Example: LMDB in SAP Solution Manager 7.2.)
Figure 5c: SAP Note 2177157 related to the Cross-System-Settings.
Trouble Shooting and Relevant SAP Notes
In case of problems, also see Uploading, Accessing, and Trouble-Shooting System Data in the Customer Profile Used for Planning Changes in Your IT Landscape and a comprehensive list of relevant SAP Notes.