016 – Building a reliable SAP PI landscape

Podcast: Play in new window | Download

Subscribe: Apple Podcasts | RSS

In this episode, I’ll share some of the different ideas and techniques that I have seen at customers locations.

Integration services are so important to the business that you must find a way to run SAP PI/PO all the time. It is one of the key things to consider how you can make a good distribution of your system and the workloads. And also be able to support the upgrades/patches as well as configuration as easy as possible.

In the podcast, I mention some different setups they can be combined with a different setup to suit what you want to achieve and how it is best for your organization.

• One installation on multiple instances or server nodes. This is SAPs way of scaling the system. They are all linked but allow you to restart single servers or instances and distribute among the servers. You cannot specify where an integration should run.
• Multi productive PI systems to handle the different flow. Then you can patch one while the others are running. It requires some extra maintenance
• Decentral Adapter Engine. Where all systems are connected to one central system that allows you to distribute workload and just have one place for configuration.
• Preprod failover. Where you are using your reproductive system as a way to have a hot-hot failover. It does require some extra configuration of the scenarios on the PreProd system but gives you some benefits if you want to switch to it.

If you have another idea please post a comment below then others can learn from it.