on 07-16-2007 4:28 AM
Hello all...
Need opinions and/or best practice info.
We are implementing ESS/MSS and have the need to customize ESS, MSS, and PCUI SCs. Is it better or recommended to create ONE track containing all of these SCs or separate tracks for each one?
Thanks in advance!!
I would recommend creating one track.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Marc,
That was my exact theory... PCUI dev in one track means having to import it/merge it into the other tracks. I would assume the same thing would apply if you had PCUI dev contained in either ESS or MSS tracks. So with that in mind, plus other feedback, I'm going with one track.
My only concern is it is very large (like 1041 DCs), so it will take a while to build/assemble. Hope our NWDI box can handle it!!
Thanks everyone.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
David,
well, if it doesn't work you know where to ask..
The number of DCs are not that relevant. The bigger issue is that ESS contains some DCs that are rather heavy (tra/trp/* and some of the ../bp_* DCs). If possible ensure that your CBS has enough memory and that the CBS rootFolder is placed on a fast disk with enough space (depending on number of parallel builds, >10 GB should be safe).
Regards,
Marc
I've looked at this document before and from what you are saying, one track is the better way to go? No real reason why we can't I just wanted to confirm.
Thanks...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi David,
well, just turn it around. Assuming you have one track for PCUI customizing, one track for MSS customizing and one for ESS customizing. Now since some changes you want to do in ESS or MSS might depend on other changes in PCUI you would have to do your customizing in the PCUI track (dev system), transport changes to cons, assemble, approve, forward to the MSS or ESS customization track and do your changes there. I doubt that you would want to do it like that.
Regards,
Marc
Please check the following link up:
<a href="https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_cts/~form/handler">ESS Cookbook</a>
Keep it simple
And pay attention to SC dependencies (you might see it in SLD; during track configuration CMS helps to includes all required for development SCs) - it may be pretty painful to keep consistency and development process eficciency in case of separation among several tracks.
Let me know if such non-technical recommendation is not sufficient
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.