on 11-21-2005 10:05 AM
Hi
Normally creating Master SLD in Dev and syncing it to the QA , Prod landscapes looks more common approach towards SLD definition and transport mgmt.One suggestion that has come to my notice is to restrict Dev SLD to Systems used in Dev and QA, while in QA we define a separate SLD with Test and Production instances, and we define Transport paths linking Dev to QA and QA to Prod.Will this be a good approach to maintaining transports..Are there cons from this approach!! Let me know on your views from your experience.
Hi Sriram,
and more information
/people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
we infact use, ONE SLD (for Prod QA & Dev)
Regards
Vishnu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sriram,
I would adviced that you use one SLD for all your Dev, QA and test servers and one seperate SLD for production server.
a blog on the same lines
/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
Best regards,
Naresh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
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.