Skip to Content
Former Member
Oct 20, 2005 at 02:59 PM

SLD Strategy


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.