SLD and Solution Manager landscape

[Former Member]

the SAP general recommendation for SLD landscape is that one SLD has to be installed locally on Solution Manager, another central runtime SLD for every production systems, and another central design-time SLD for every non-production systems. But do you know the recommendation in a landscape with 3 Solution Manager (integration, production, and backup)

Thanks in advance for your responses

[stuart_campbell]

The SLD landscape to implement depends on your requirements

The general recommendation is to have a central SLD on Solution Manager J2EE containing all systems in your organization

and there can be any number of local SLDs which are product and maybe runtime dependant

There are several things to consider here

1) A data supplier is not able to point to 2 SLDs at the same time therefore only 1 SLD will be automatically updated

in order to automatically update a second SLD a synchronization option needs to be configured from the SLD Planning Guide

2) When synchronizing ensure SLDs are on the same versions or CIM levels

3) Some SLD contents maybe is source specific - in the case of business systems always test useage after sync or import

4) Avoid mixing import lines - if you created this system manually it should be subsequently managed manually, if created by sync

or export it has to be subsequently updated via sync or export respectively

Best wishes

Stuart

[Former Member]

Hello,

If you have a 3 system landscape for Solution Manager --> D, Q P ideal would be a two SLD strategy.

1) NON-PROD SLD --> for Non-prod system landscape where all the non-prod systems (DEV/ IST/ UAT/ QUA) of your entire SAP landscape will be registered to and the other will be a

2) PROD SLD wherein you register all your productive instanes of your landscape.

Hope this helps.

Regards,

Bhaskar

[Former Member]

Reasons to Have Several SLD instances:

There may be several reasons to have more than one SLD. For example, if you have geographically

distributed locations with local administration groups that want to see only their local systems in the SLD, you

require a dedicated SLD to be able to provide different views on SLD data.

In addition, several system landscape directories might be required if you want to isolate your production

environment. By having an SLD dedicated for your production systems, you can make sure that only

administrators access your runtime SLD, whereas developers can use a design-time SLD.

Having more than one SLD also gives you the possibility to test content imports, CIM data model updates,

and patches first before performing them in the SLD used for your production environment.

A very important reason to have several SLD instances is to provide improved availability of the information

stored there. This information could be essential for applications running in your production landscape.

For more information, see document: Planning Guide u2013 System Landscape Directory at