ChaRM for a 5 system landscape

[Former Member]

Hi all,

we got a requirement to implement charm for 5 system landscape. but the problem is

currently the scenario followed for the rollout is

1. AA(DEV-proj)--> BB(QUA - proj)

Then the TR is forwarded from BB system to the maintenance landscape

DEV>QUA> PROD

they don't want to implement retrofit functionality.

is there any way we can mapp this scenario to charm.

kindly advice in this regard.

Thanks,

Subhashini.

[Former Member · Accepted solution]

Hi Ragu,

Thanks for the reply.

currently a two systems are separated from the maintenance landscape.

they are forwarding the TRs to the development system.

is there any way we create 2 tracks.

1. AA-BB-DEV-QUA-PROD

2. DEV-QUA- PROD

again i not having a clear idea on how to differentiate the tracks as both leads to the same production system.

or is there any way develop a custom method for forwarding this TR to the DEV system.

kindly sugggest on how to go about.

Thanks ,

Subhashini.

[raguraman_c · Accepted solution]

Hi,

The only way out I could think of is use Retrofit.

You can think of using SCC1 for copying TR from BBB to DEV. Thereafter your ChaRM - 3 System Landscape.

Again you may not have tight control on the TRs moved from BBB to DEV since, ChaRM doesn't play a role there. This is a workaround you can think of.

Hope this helps.

Feel free to revert back.

-=-Ragu

[Former Member]

Hi Ragu,

Thanks for the reply.

i think we have no other option other than retrofit.

we will use the same.

Thanks,

Subhashini.

[raguraman_c]

Hi,

Do you have a single transport track?

This may be possible only with retrofit. The reason is,

You can assign exactly one development system to a production system, and that these two systems are connected by exactly one unique transport track.

If a development system and a production system are connected by more than one transport track, this may lead to inconsistencies within the transport distribution. This type of transport configuration cannot be supported by Change Request Management, and may cause inconsistencies within the tools involved.

Hope this helps.

Feel free to revert back.

-=-Ragu

Edited by: Raguraman C on May 28, 2010 7:04 AM