SLD (System Landscape Directory) basic understanding

Introduction

 Landscape data is for some time being uploaded to SAP Support Portal – for example, to enable the Early Watch Alert. Now, landscape planning tools like Maintenance Planner emerge in the SAP Support Portal using that data. So 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), 

SAP Support Portal Customer Profile. 

  • 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(Data): 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

Pic :1


Pic:2


-->  SAP System's information or details are sent to global SLD from there it is synched with local SLD of the solman.

--> From local SLD it is then synched with LMDB and then to the sap support portal.

Phases :

1.SAP System -->SLD

2.SLD --> local SLD (Solman)

3.local SLD --> LMDB (Solman)

4.LMDB --> SAP Support Portal


1.SAP System -->SLD :

Configurations between SAP ABAP systems and SLD : 

--> Go to RZ70 t-code in the managed system and add the values of 'GatewayHost' and 'GatewayService' from the SLD system.


Gateway host details can get from the SLD :- SLD UI -> Administration -> Parameters ->Section: datasupplier

-->Below RFC's get created automatically from the above configuration setup 

      SLD_UC & SLD_NUC



More details on configuration:

https://blogs.sap.com/2011/02/23/how-to-push-abap-system-data-to-a-java-only-sld/

Batch jobs responsible for updating the system details to SLD from managed systems :

SAP_SLD_DATA_COLLECT" executed periodically and 

"SAP_SLD_DATA_COLLECT_STARTUP" is executed with every system restart



2. SLD --> local SLD (Solam)

--> Data from global SLD is sent to local SLD in solman by using the below configuration in global/central SLD.

  • Exchanging data between SLD systems using full automatic synchronization.
  • All types of SLD data can be sent from one SLD to another or changes can be exchanged mutually between them.
      Note that using specific users is important for data management in SLD.

 Navigate to Content Synchronization maintenance of SLD: On the SLD Home, choose Administration.

Open your SLD on http://localhost:50000/sld


Create a new Sync connection - Choose Content /Content Synchronization


In the SLD content synchronization maintenance, choose Add…


 In the Content Synchronization Wizard Set following options:
- keep Source = Remote
- select the Bidirectional option
- Choose Next


Add a sync user available on the remote SLD:- 
Enter Remote SLD URL e.g. =http://iwdfvm3034:50000
Enter user: SLD_LD1_SYNC and the password


Make rank settings:
- Select a namespace, e.g. sld/test_00 (mostly it will be sld/active).
- Set source rank = 100 (in case of a conflict of  data – occurs, when the same data is changed at the
same time – a higher rank number defines that this SLD’s data will “win”)


         Open SLD Home  Landscape / Technical Systems. - Choose your system tewdf….

      - On tab General read the IP address and make a note to have it available in the next step.

      - Note: After the sync, many systems will be shown.



  Set up local SLD connection: - Local URL = SLD’s IP Address (10.64….) or hostname

- Use newly created user TE2_XX_SYNC / pwd. (administrator user will work, specific users are preferable.

- Choose a namespace
- Choose rank = XX; XX is between 1 and 100, 100 being the highest rank.
- Choose Next.


Confirm with Finish.


 You will see the content synchronization maintenance.

 To get the status of the new sync connection, choose Status / Full Sync (Active)



Now Sync between local SLD and LMDB in solman happens by the below jobs

3.local SLD --> LMDB (Solman) :                                                                                           


Job: SAP_LMDB_LDB_0000000001 is used to synch the data from local SLD to LMDB within the solution Manager.




4. LMDB --> SAP Support Portal :

The "SM: LMDB GENERIC UPLOAD" job replaced the existing jobs that uploaded system data in the past as described in SAP Note 2177157:

  • "LANDSCAPE_FETCH" (obsolete since ST 720)
  • "SM: UPLOAD SYSTEM DATA" (obsolete since ST 720 SP12)

The "SM: LMDB GENERIC UPLOAD"  job runs hourly. In every run, the LMDB generic upload receives data from and pushes data into the so-called postbox of Support Hub Connectivity. Support Hub Connectivity collects data packages once every hour from the postbox. Thus, it may take a maximum of two hours until a requested system data change in the LMDB is sent to SAP’s support backbone.

Execute transaction code LMDB to launch the System Landscape Technical System page. Go to the Technical Systems tab and choose the Type. In this example, we are looking at Application Server ABAP. Enter the Extended System ID which is the SID. Click on Display.

Select the SAP Support Portal tab and click on Upload to SAP Support Portal.

The upload will take some time and see the log messages to confirm the upload is successful.


Comments

Post a Comment

Popular Posts

SAP Logon Configuration(Load Balancing)

Image
Logon groups (or work groups) are configured to dynamically distribute the load being processed by the dialog work processes. Setting up logon groups helps in uniform distribution of the work load across the available instances. While logging on using a logon group, the ABAP message server is contacted to identify the instance with best performance statistics within the selected logon group . A report runs in SAP every 5 minutes which determines the load across each server and updates in the memory area of the message server. This information will be used by SAP GUI to determine the best instance to distribute the next user.   SAP Logon Process Let’s start with discussing an overview of SAP Logon process. High-level understanding of the process will help to explain details of SAP Logon configuration. SAP Logon Process Overview When user(s) accessing SAP system via  SAP GUI , the request is forwarded into ABAP dispatcher for the direct logon. If SAP GUI is using logon group, th...
Read more

EHP Upgrade (SUM)

Image
  Introduction: SAP Technical Upgrade is a periodic project that is implemented across companies to upgrade their SAP system to the latest released version. Most of the upgrade activities are done by the technical team, and functional consultants' role is limited and mostly confined to regression testing. Reasons for SAP Technical Upgrade : Since technology and businesses evolve, companies need to maintain a technological infrastructure that can support that change. This is the major reason why companies should undertake a technical upgrade of their SAP system. Of course, there are many secondary reasons, the significant one being the fact that like all software vendors SAP supports a released version of its software only for a limited period. Now we can go through the detailed phases included in the SUM upgrade process. latest SPAM version and Kernal also considered prerequisites  Prerequisites : 1. Check SYSTEM user is De-active, if yes, it should be activated. Passwords f...
Read more

Interview Questions

Image
1. Startup profile from 7.3? Answer: Now the Start profile contents are merged with the Instance profile. With help of the new Instance, profile SAP processes are started and at the same time, instance-specific parameters are read. 2. SAP Application server connects with Database using database client. 3. Difference b/w profiles? Default.PFL - default profile Instance Profile - SID_DVEBMGS"nr"_Hostname location = usr/sap/SID/SYS/Profile 4. Below are the common errors in SAP transport management Return code 4:  Imported with warnings Generation of program, colomns or row missing . Return code 8 :  Imported with errors Syntax error Program generation error Dictionary activation error or method execution error Return code 12 :  Indicates Import Cancelled Program cancelled due to job Import cancelled due to object missing Import cancelled due to object not active Return code 18 :  Indicates Import Cancelled Due to system down while import Due to user expired during impo...
Read more

SNOTE Implementation and FAQ

Image
 SAP Note : SAP Maintains a knowledge base of problems and resolutions which are accessed from market place. www.service.sap.com/notes.SAP provides resolutions in the form of a note which is a number. Note can be searched on number (if we know)or we can search with the problem code, error number etc. Note provides info. Reg the problem, as follows 1.Problem 2.Pre-Requisites 3.Cause of the problem 4.Solution, Corrections, attachments, and note may redirect one or more notes. Notes of 3 types : 1.Informative note Which consists of details to solve the problem 2.Corrective note This provides changes to the data dictionary elements or repository objects. 3.Manual note: Some of the steps will be present in notes to solve the issue.   Procedure : Read the note carefully and check for validity, Pre-Implementation steps , Post-Implementation steps and Pre-requisite Notes. Do the manual pre-implementation steps in case the Note sugges...
Read more

SAP Startup Troubleshooting

Image
  1. IS DATABASE UP AND RUNNING? This is an  absolute  prerequisite for SAP SYSTEM to start. In order to test this, operating system command  R3trans -d   can be executed (as SIDadm user). Any return code different than 0 means that DB cannot be reached by DIALOG work processes, and so SAP system will not initiate. The following return indicates that the database is up, running, and reachable by SAP work processes: <hostname>:SIDadm > R3trans -d This is R3trans version X.xx (release 742 - 18.11.14 - 20:14:09). unicode enabled version R3trans finished (0000). -->There is  NO POINT  in moving the analysis further while the return code is different than zero. --> In case the return code is different than zero, please involve your DBA/Network/OS teams. 2 . IS SAP STARTUP AGENT (SAPSTARTSRV) RUNNING? There must be  ONLY ONE  sapstartsrv process running for each instance. Examples for each platform below: Examples...
Read more

HANA Installation & upgrade

Image
  Software Download: SAP HANA System Types : Ø   Single-host system - One  SAP HANA  instance on one host Ø   Multiple-host (distributed) system - Multiple  SAP HANA  instances distributed over multiple hosts, with one instance per host. SAP HANA Deployment Types : Tenant Databases : The tenant database deployment type makes it possible to run several SAP HANA instances on the same hardware in a production environment. Multiple Components on One Database (MCOD) : MCOD deployments are characterized by multiple applications on one SAP HANA system. SAP supports deploying and running multiple applications on a single SAP HANA production database  only  for packaged applications and scenarios listed on the "White List" included in SAP Note 1661202. Virtualized : SAP HANA systems can be run on virtual machines with restrictions to the hypervisor (including logical partitions). Multiple Components on One System (MCOS): MCOS...
Read more

SAP HANA Backup

Image
  SAP HANA Persistence To ensure optimal performance, the SAP HANA database holds most of its data in-memory. However, it still uses persistent storage to provide a fallback in case of failure.   During normal database operation, data is automatically saved from memory to disk at regular savepoints . Additionally, all data changes are recorded in the redo log . The redo log is saved from memory to disk with each committed database transaction. After a power failure , you can restart the database as you would with any disk-based database. It then returns to its last consistent state by replaying the redo log since the last savepoints . Although savepoints and log writing protect your data against power failures, savepoints do not help if the persistent storage itself is damaged . To protect against data loss because of disk failures, backups are required . Backups save the payload (the actual data) of the data area and log area to different locations.   Types o...
Read more

SAP Transport Management System (STMS)

Image
TMS is used to move, manage and control copy development objects and customizing settings in an orderly fashion across SAP Landscape. STMS [SAP Transport Management System] Domain Controller–:  It is used to control the landscape. There will be only one domain controller in the landscape. Initially, it is set to development and later can be moved to on higher available system such as PRD/QAS/Pre7/ production but to keep things simple most of the cases we keep DEV as Domain Controller Member Systems–: The other systems are included in the domain referred to as member systems.  How to Configure   STMS Log on to the SAP system, which is decided to be the Domain Controller, in client  000  and enter the transaction code  STMS. If there is no Domain Controller already, a system will prompt you to create one. When the Transport Domain is created for the first time, the following activities happen in the background: Initiation of the Transport Domain / Landsc...
Read more

Set Up SAP HANA System Replication with hdbnsutil

Image
  Procedure:                                               SITE -A Enable system replication on the primary system(SITE A) as follows: In the Administration editor of SAP HANA studio, choose the  Configuration  tab and ensure that  log_mode  is set to "normal" in the  persistence  section of the  global.ini  file. Log mode  normal  means that log segments must be backed up. Log mode  overwrite  means log segments are freed by the savepoint (therefore only useful for test installations without backup and recovery). Do an initial data backup or create a storage snapshot. In multiple-container systems, the system database and all tenant databases must be backed up. As  <sid>adm  on the command line enable the primary for system replication and give it a logical name with the following command. Th...
Read more

SAP Kernel Upgrade in Distributed System

Image
What is the kernel of an SAP system? The kernel is a central program that acts as an interface between the SAP application and operating system. These files help startup the R/3 system, initialize the memory, create buffers and start managing the requests from users and effectively utilizing of hardware resources. The kernel is also responsible for starting and stopping all the application services like dispatcher, message server, collector, etc. Why Kernel Upgrade? SAP Kernel is the core of the application. Like all other applications, the Kernel contains the executable files (.EXE files for stating various processes in SAP). The Kernel is the heart of the operating system. It contains those files which are used to run every event in SAP. E.g.|: starting database, shutdowns of the database, starting sap, shutdown of sap, saposcol, to uncar the sap files etc. That's the reason why when a Kernel upgrade is done it means new versions of the various EXE files replace the older version...
Read more