Dual landscape for ChaRM

[Former Member]

Hi All,

we have a two landscape one for implementation and another for maintenance,

DEV(Impl)-QA(impl)----

---

>Implementation landscape

DEV(Maint)-QA(Maint)-PROD(Maint)----

---

>Maintenance landscape.

this is what currently defined in STMS also.

currently the basis team, as part of cut over activity forward the TR to maintenance landscape.

i wanted to know how can we achieve this using charm.

the TR moved from implementation landscape to maintenace landscape shud be moved through DEV(Main)-QA(Maint) and reach PROD(Maint).

when i read about the retrofit i got an idea about moving TR from maintenance landscape to implementation landscape. but in my case i wanted the reverse one from implementation to maintenance.

1. i wanted to wht kind of STMS config we need to achieve this.

2. how will charm take of thie TR.

kindly share your ideas.

thanks,

Subhashini.

[Former Member · Accepted solution]

Hi Subhashini,

You can move transports any direction using logical component.

like path Dev(Impl) -QA(impl)- Prod(impl)

-QA(Maint)-Prod(Maint)

you can add system in a logical component from solar_project_admin under a project.

Evaluation System, Development System, Quality Assurance System, Production System, Training System, Demo System, SAP Referenc System, Pre Production these are the standerd system role available you can create new role if you want.

Thanks,

Suman Pramanik

Edited by: Suman Pramanik on Jun 3, 2010 7:19 PM

[raguraman_c · Accepted solution]

Hello Suman,

Please note that she has got two development systems. Do you think it is supported?

Subhashini: Can you explain to next level detail? What is your requirement, after you transport your requests from projects Dev to Maintenance step.

Feel free to revert back.

-=-Ragu

[Former Member]

Hi Ragu and suman,

thanks for your replies.

and sorry for the delayed reply.

our req.is we have got two lanscapes one for implementaion and another for maintenance.

during cutover pahse, the dev system in maintenance landscape will act as the test system,

due to which we have got a confusion on how to go ahead.

we have tried using the retrofit part, by creating 2 tracks one for implementation and another for maintenance.

we have tried it with different client and it is working fine.

we want to know whether is it a best practise to use that or not.

and also we are getting a popup with the systems(dev system of maintenance and dev system of impl.)

can we able to suppress it or not.

kindly guide.

thanks,

Subhashini.