MDM dual maintenance

[Former Member]

We are moving to next phase of release 2 and below is the dual maintenance land scape we are trying to work out where a separate MDM landscape will be created for project/upgrade.

DEV1->QA1->PROD

DEV2->QA2->PROD

MDM experts, do you have any further suggestions on this landscape flow.

[Former Member]

Hi Subin,

I guess current landscape has multiple repositories connected to various systems.

May we know on what is the need for replicating systems in all 3 environments?

Is it a preventive measure to avoid server break-down. If so, how would you avoid breakdown and repository crashes on different environments for repositories ?

Your query would require lot more information on what you actually wish to achieve!

Regards,

Kasim

[Former Member]

Kasim,

The need is for next phase of a large transformation project. First phase is currently in production. So, thought is to have a separate landscape for MDM (like other systems - ECC, PI etc.) for next phase of the project and also this new landscape could be used for any MDM upgrade. Once project/upgrade changes are tested in dev and q (assuming it to be a 2 yr long timeline), we could move these changes to production. Also, we have to ensure current production changes (break fixes, enhancements) need to be updated in project landscape also.

Subin