Skip to Content

How many ESR's in your landscape

Hi Services Repository Experts,

we have CE and ECC and PI.

PI is our Services Repository.

Question, in our landscape, if we have

Development Line (for CE, ECC, PI etc)

Quality Line (for CE, ECC, PI etc)

Regression Line (for CE, ECC, PI etc)

Production Line (for CE, ECC, PI etc)

How many Services Repositorys is it good practice to have ?

eg, All non-Prod systems use the DEV PI as SR


Prod systems use the Prod PI as SR


every line, Dev, Quality, Regression, Production, every line has its own unique SR serving

only that layer of the landscape ?

Does anybody have any insight into good practices in this design.

Thank you and kind regards,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    avatar image
    Former Member
    Jul 26, 2011 at 09:21 AM

    Hi Petr,

    Firstly, I must admit, I'm struggling to understand your question...

    Let's rather use the acronym ESR for the Enterprise Service Repository. The acronym SR is normally used for Service Registry.

    If you have a PI installation for each of your lines (Dev, QA, Regression & Prod) then surely there would be a PI ESR available for each unique line. So you would do your Dev work on PI Dev & then tranport your development through the different lines as required.

    In your first scenario (i.e. one ESR for non-prod systems), you would then need to transport your PI development from PI Dev straight to PI Prod, that won't be best practice at all. So one ESR per line would be my answer.

    Now: If you meant Service Registry (SR) instead of Enterprise Service Repository (ESR), then you'll have a totally different answer. This would vary on you use cases for the SR. If it's only being used during development (which is how it is in most cases) then only one SR for all non-prod systems would suffice. If you are (or plan to) use the SR in a much more comprehensive manner (e.g. Dynamic routing at runtime, policy enforcement at runtime or Service Registry Synchronisation with another UDDI compliant non-SAP SR for additional runtime governance requirements), then it would make sense to have an SR in the PI Productive landscape as well.

    So there isn't a best practice guide on the subject (or I haven't seen one) because it will vary according to use cases per customer.

    Regards, Trevor

    Add comment
    10|10000 characters needed characters exceeded