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 Integration (CPI)…
Posts published in “Integration Cookbook”
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…
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…
This article is part of our Integration Cookbook. Name Pattern Example Software Component Same as ESR SWC or generic SWC “BPM” when used in NWDI due to the underlying components BPM of whitepaper-id.com Development Component bpm/<opt:SWC>…
This article is part of our Integration Cookbook. SLD Name Pattern Example Software Product <Name>, <Version> of <vendor-url> Microsoft Navision 3.5 of whitepaper-id.com SAP ERP 6.0 of whitepaper-id.com Software Component (same for Unit) <Name>, <Version> of <vendor-url> (use…
This article is part of our Integration Cookbook. To design interfaces for SAP PI, you need to consider the following aspects and follow the principles regarding Software Components: Separate Sender Application/System from Receiver Mappings are always created in the Receiver (Target) Software Component…
This article is part of our Integration Cookbook. Quality of Service If you can influence the application design of the sender or receiver (doesn’t apply if an external partner/service provider with an existing service…
This article is part of our Integration Cookbook. When we build integration solutions, the following characteristics (principles) of application integration should be clear and defined as goals: Enable Connectivity by…
The WHINT Interface Catalog for SAP Process Orchestration generates two Excel Documents to bring more transparency to your interface landscape. Here is how you can better understand the results: Channel Catalog…
There is a useful functionality to reuse objects from one software component in another one. You can define this usage dependency in SLD or in ESR (software dependencies & underlying…