Press "Enter" to skip to content

Posts published in “Architecture”

Naming Conventions for SAP PI

0

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…

Content Organization in SAP PI for Interface Designers

0

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…

Messaging Principles for Interface Designers

0

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…

Design Principles for Interface Designers

1

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…

WHINT Interface Catalog for SAP Process Orchestration / PI

4

Functionality This solution provides you with an overview about your Integration Landscape: All information from your configuration (Integration Directory) of your SAP Process Orchestration System. The tool downloads (e.g. periodically)…

Usage Dependencies in Software Components

0

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…

SAP Plain J2SE Adapter Engine in Proxy Mode

0

In case you want to track your HTTP requests (e.g. to SOAP / HTTP / REST receivers), the SAP Plain Adapter Engine might offer a nice surprise to you. You…