When moving from SAP PI to SAP Process Orchestration we should be careful about the settings for staging and logging which is maintained on iFlow / Integrated Configuration (ICO) level.…
Posts published by “akiwon”
The monitoring and alerting of messages and artifacts in error is a key element to control an interface landscape. However to analyze errors in detail, you have to navigate into…
When using SAP Cloud Integration, me might have many entry points (URLs) available, how our iFlows and OData Service can be invoked. Finding this information is quite hard as we…
Monitoring your interface landscape is important to identify issues and minimize delays and downtimes. With WHINT Interface Monitoring for SAP Process Orchestration you can already monitor the major components of SAP…
The monitoring and alerting of messages with status FAILED, RETRY and ESCALATED is a key element to control an interface landscape. With the latest update of WHINT Interface Monitoring for…
Functionality This JCA Adapter for SAP Process Orchestration uses the Advanced Message Queuing Protocol (AMQP) to connect to RabbitMQ, a reliable way to establish a properly decoupled application integration using…
With SAP Process Orchestration 7.50 we can deploy Integration Content from SAP Cloud Integration into SAP Process Orchestration locally.With this update of WHINT Interface Catalog for SAP Process Orchestration you…
Connectivity from SAP ABAP Systems to SAP CPI via ABAP Proxy can be done via XI adapter (XI runtime: SXMB_ADM) or SOAP adapter (WS Runtime: SOAMANAGER). In case of XI…
Transferring files is not a good integration pattern (see here why to avoid especially using flat files). However, sometimes we have to. And then it is good to know how…
SAP Cloud Integration does not store message payloads by default (queueing). In case an error occurs (mapping, routing, connectivity), we have to design the desired behavior ourselves. This document describes…