SLD Strategy

[Former Member]

Hi All,

SAP recommend the use of a "single" SLD throughout your environment. But from my understanding, in reality, customers are using 2 SLDs: 1 for DEV/QA and 1 for PROD. Hence keeping their productive environments away from being impacted by inadvertent development changes on the single SLD.

I have the following questions:

1. If you have a single SLD, is there any way of restricting access to developers from modifying production system data ? Can namespaces be used here ?

2. My understanding is that the SLD needs to be implemented on a High Availability environment ... certainly in production. Is this (HA) really required, since all the SLD content is cached locally on the Integration Server ?

Thanks in advance for sharing your thoughts on this topic.

Best.

[Former Member · Accepted solution]

hi,

Single SLD is the way to go.

<i>1. If you have a single SLD, is there any way of restricting access to developers from modifying production system data ? Can namespaces be used here ?</i>

sld is usually not open to developers, developers request for bussiness/technical/swc and SDL adm creates/maintains according to the request

<i>. My understanding is that the SLD needs to be implemented on a High Availability environment ... certainly in production. Is this (HA) really required, since all the SLD content is cached locally on the Integration Server ?</i>

this you can debate on, but the thought is that since all the components in ur landscape now depend on SDL, it has to be HA

cheers,

naveen

[Former Member · Accepted solution]

> hi,

>

> Single SLD is the way to go.

>

> <i>1. If you have a single SLD, is there any way of

> restricting access to developers from modifying

> production system data ? Can namespaces be used here

> ?</i>

> sld is usually not open to developers, developers

> request for bussiness/technical/swc and SDL adm

> creates/maintains according to the request

Yeah ... this seems to be the message from SAP in theory ... but in practice this is not the case. In fact there is an SAP document: "SLD Planning Guide" which goes through a number of landscape scenarios. One of these includes a scenario with 2 SLDs - 1 for DEV/QA environments and 1 for PROD environments. In order to prevent productive interfaces from being inadvertently affected.

In a global environment, where multiple business units and countries are sharing 1 SLD, how can you prevent the SLD Admin guy from inadvertently making changes to PROD system settings ? Is there a way of imposing restrictions ... e.g. through security authorisations etc.

[Former Member]

> 1. If you have a single SLD, is there any way of

> restricting access to developers from modifying

> production system data ? Can namespaces be used here

> ?

I agree with Naveen on this. Developers should not be accessing the SLD directly.

> 2. My understanding is that the SLD needs to be

> implemented on a High Availability environment ...

> certainly in production. Is this (HA) really

> required, since all the SLD content is cached locally

> on the Integration Server ?

From a long term perspective, SAP's vision is to

provide a centralized infrastructure for System

Administration and monitoring. As a step in that

direction, SAP recently released NetWeaver Administrator

that needs access to CCMS and SLD for gathering system

information. Considering the fact that the NetWeaver

Administrator will be the tool to administer the

landscape and has to be highly available, and solution

manager could also be integrated with the Netweaver

components to provide integrated monitoring, high

availability of SLD assumes significant importance.

Regards,

Suresh