on 10-03-2007 7:07 AM
Hi All,
Maintaining a Single SLd is Better Or Multiple SLD's are Better While Working with the DEV, QTY, PRD..............
Please Give me the Reason
Regards
Babu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Single is recommended.
But then the choice depends upon the scenarios and landscape involved.
Single is recommended coz then there would not be any inconsistency problem that may arise while transporting objects across the SLDs.
But a good option is to use 2 SLDs, 1st for Dev and 2nd for QA and Prod. The reason is tht if u have single SLD, during the development the developer may create several business system just for testing purpose. And this may lead to many objects that r not relevant for prod perspective. So 2 SLD s r used with only relevant objects in Prod landscape.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Go through this guide. It explains the landscape strategies clearly.
Regards,
Sudheer.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
In general Single SLD is the central repository of information. it depends upon the performance and project requirement we need to maitain..
Chilla
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi babu,
check this
see what Bhabes wrote ....
SAP recommends a Single SLD.
Having a separate SLD for every environment beats the concept of SLD itself. SLD is a place where you can look and understand what components/ system run in your landscape. If you are going to hve one for every Environment, it is against the concept of SLD itself. More maintenance is another issue.
Single SLD as recommended by SLD has the problem that you do not want to provide access to a component that can be used in production to developing teams and so on .What Barry has pointed is something that is a more practical approach.
There are no hard and fast rules. A client present across Geographies, havinng multiple vendors and IT teams handling different geographies would prefer to have multiple SLD's one for each Geography and then maybe a master SLD that is going to conain all info of the other Sld's and so on., There is no direct answer to this question other than it purely depends on individual clients.
Regards
Bill
<b>reward points if it helps u</b>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
maintaining a single SLD is better , we can transport then in DEV,QTY,PRD.
why do u need multiple SLD?
regards,
phani
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.