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…
Posts published in “Integration Cookbook”
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…
Sync-Async Patterns with BPM on SAP NetWeaver Process Orchestration (PRO) are quite easy to implement. However, when you want to design the integration flow as lean as possible, this document might…
Your first steps – find basic information about SAP HCI (PI) SAP Help Developer Guide Public Integration Content Catalog HCI Tools SCN Landing Page Apache Camel Enterprise Integration Patterns