Skip to Content
0
Former Member
Feb 21, 2011 at 12:19 AM

SCC4 settings and landscape consistency

1574 Views

guys,

we have a three system landscape here - dev, qa and production, no seperate sandbox system. following are the clients in these systems:

DEV 100 - golden client

DEV 200 - Unit Test/Sandbox

QA 100 - QA configuration client--- dont really use it

QA 200 - Testing client

PROD 100 - production client.

So as you can see, we dont have a seperate sandbox system. I am not sure which clients in DEV I should make modifiable for customizing and repository changes so that my golden client stays clean and so that we can also maintain consistency within entire landscape. Following is what I am thinking about, please let me know if this would be the right approach or not:

DEV 100 -- allow customizing and repository changes and allow recording and transport of changes or should I lock it against development ?

DEV 200 ---

For customizing - changes without automatic recording and no transports allowed, so that users can do R&D but do not allow transports and then make the same changes in DEV 100 (golden) and transport changes from there.

For development --- I dont understand what settings I should use, If I do not allow changes, developers would have to start their development in DEV 100, my golden client and if they somehow abondon the development and do not eventually transport the changes into QA and production, my landscape would become inconsistent. Is that acceptable ?

On the other hand, If i do allow changes to repository from this client, it effects the entire system and once again my golden client gets affected too. I would really like to know where to start development if a seperate sandbox system is not available.

CIQ 100, CIQ 200 and PROD 100 --- no changes allowed for customzing or repository

Please provide your feedback,

thanks,

VM