SAP-System-Landscape with PI

[Former Member]

Hi all,

we are planning to introduce a completely new 5-system-landscape of SAP-Systems (Template DEV, QAS / Maintenance DEV, QAS, PRD), which also contains PI. We will have a central SLD within this landscape as recommended by SAP.

Now what about PI itself?

Is it neccessary to introduce five instances (one within each environment) or do you think it is possible and feasible to share one PI-instance over several environments (let's say Maintenance DEV and QAS)? This would be a way to reduce the number of PI-systems, especially when those systems are not heavily used. After all you would "only" have to provide corresponding configurations within the IB to achieve this.

Is there a best practice or recommodation on this topic?

Thanks in advance,

lars

[prateek]

The most widely used approach includes the three instances for Dev, QAS and Prod. Even for landscapes involving huge PI usage, these three instances suffices. However, an organization could have some specific requirements for which an extra instance may be added.

e.g. In some organization, there is an instance between QAS and Prod sometimes called Pre-Prod server which is exact replica of PI Prod server. This could be used as a backup server for the Prod server.

Therefore to answer your question, technically it is very much feasible to manage the landscape with only three instances. Adding more than three instances should be a strategic decision.

Regards,

Prateek

[Former Member]

Hello Prateek,

thanks for you answer.

However, the number of lendscape is already defined for our company. The question is wether or not to provide an instance of PI for each of this landscapes?

For example:

- Landscape DEV: ERP1, CRM1, PI1

- Landscape QAS: ERP2, CRM2, PI1 [Uses PI of DEV-Landscape]

- Landscape PRD: ERP3, CRM3, PI3

Do you have suggestions on this topic?

Thanks,

lars