CE 7.1 ESR Landscape?

[Former Member]

Per my understanding the service interface models and definitions for proxy-based enterprise services are not used at run-time. Is there any reason why we want to have these service models and definitions in the ESR in production environment?

If we do not move them into production, what is the recommended landscape for ESR (if the CE 7.1 version is used)? Do we need the CE 7.1 ESR in both Dev and QA environments?

Appreciate for any thoughts or pointers.

[Former Member · Accepted solution]

Again, a very good question Jiannan

... the service interface models and definitions for proxy-based enterprise services are not used at run-time. Is there any reason why we want to have these service models and definitions in the ESR in production environment?

You are absolutely right. ESR is not used during runtime. The reason some customers have it in the productive version is to maintain the production state of the metadata. In the future, we can use this information for better governance at runtime.

If we do not move them into production, what is the recommended landscape for ESR (if the CE 7.1 version is used)? Do we need the CE 7.1 ESR in both Dev and QA environments?

As with PI based content, ESR for CE also supports transport using CMS. For all productively used content, the recommended approach is to have to DEV-CONS-PROD content. In this case, you can use an ESR (CE / PI) on each of the systems.

Best regards

Rathish

[Former Member · Accepted solution]

Exactly the answer I am looking for. Thanks a lot!