Before I get into the full description of an issue we are facing. I would like to know if anyone out there is using ChaRM and has 2 development systems defined.
Basically Charm works up on TMS.If you can define a transport route with two sourse system in STMS transport route,you can then enable charm for controlling it.
We have 2 landscapes each with a development and quality system. Also there is a single volume test system. Both landscapes point to a single production system. So it would look like this
DW3 DW4
QW1 QW2
VW1
PW1
The DW3 landscape is defined as the production landscape (normal releases) and the DW4 landscape is defined as the emergency landscape. The emergency landscape is synchronized with the production landscape during a normal release.
The migration path for a normal release would be DW3, QW1, VW4, (now synchronizing) DW4, QW2, PW1.
The migration path for an emergency fix would be DW4, QW2, VW4 (if performance testing is required), PW1.
All these systems are defined in the ChaRM landscape
When a task list is generated, you are asked which development system, DW3 or DW4. When the task list is generated, it starts at DW4, QW2, PW1, DW3, QW1, PW1 (We have not defined a volume VW4 system in or test landscape).
As well when a creating a transport, and DW3 is selected, ChaRm generates an error stating the task list is out of sequence,
You will notice that the task list goes to PW1 twice. Is there a way to generate the task list in the correct order. DW3, QW1, DW4, QW2 and PW1.
Looks like a starting point for a retrofit approach.
That would mean, you have your normal dev line (DW3, QW1) pointing not to test system (VW4) but to your emergency line (DW4, QW2). From there, it's going to VW4 and PW1.
The emergency fixes would go as currently, but there's a retrofitting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.