Press "Enter" to skip to content

Posts published in “Architecture”

Why standard SAP PI alerting is not enough

0

In case of interface errors we have to be notified by the system. This is called alerting and an e-mail is sent to us. Errors can occur in the SAP…

SAP Middleware Interface Reporting

0

Monitoring your SAP PI/PO interface landscape and integration flows on SAP Cloud Platform Integration (CPI) is important. Some technical aspects are being controlled by the SAP Basis team or Operations.…

Cloudy with a Chance of …Interfaces

0

…with a chance of good Interfaces! Good interfaces are robust, reliable, maintenance-friendly and also support independence! We see more and more cloud applications appearing and also several cloud platforms which…

Scaling SAP Process Orchestration

0

In case you need some options how to define and scale your PO landscape… High-Available (HA) Setup:  It is recommended to run the SCS (Central Message Server, Enqueue Server, Gateway)…

SAP Middleware comparison: CPI vs. PO

0

There are some blog posts existing about comparing SAP´s Middleware Solutions from an architectural perspective: On-Premise: SAP Process Orchestration (PO), with SAP PI, SAP BPM, SAP BRM Cloud: SAP Cloud…

Integration Cookbook for SAP Middleware

2

Our Integration Cookbook is a collection of Good & Best Practices for SAP middleware products: SAP Process Integration (PI) SAP Process Orchestration (PO) SAP Business Process Management (BPM) SAP Cloud Platform Integration…

Process Modeling Principles for Interface Designers

1

This article is part of our Integration Cookbook. Modularization Limit the process model to 25 – 50 steps to keep them manageable. This can be achieved by hiding complexity in sub-processes. Interface…

Naming Conventions for SAP Cloud Platform Integration

0

This article is part of our Integration Cookbook. SAP Cloud Integration Content only comes in two levels of content: Package & Artifact. A package only groups artifacts like iFlows but does not…