SAP

ProcessDirect adapter

Sergei Ignatov

Feb 27, 2024 — 3 min read

The SAP BTP Integration Suite offers various adapters for integration flow developers to utilize. Among these are frequently used options such as HTTPS, SFTP, OData, and Mail.

See Configure Adapter in Communication Channels

In this post, I would like to demonstrate one of the adapters that could potentially be used in BTP development to facilitate communication between different iFlows within the same BTP tenant. The adapter I am referring to is ProcessDirect.

See ProcessDirect Adapter

When do I need to start using this adapter?

According to the documentation provided by SAP, you can commence using the ProcessDirect adapter when you require establishing fast communication between iFlows hosted within one BTP tenant.

💡

Use ProcessDirect adapter (sender and receiver) to establish fast and direct communication between integration flows by reducing latency and network overhead provided both of them are available within a same tenant.

Additional information

Before the development of the iFlows begins, it is necessary to bear in mind that several producer iFlows can trigger one consumer iFlow using the ProcessDirect adapter.

❗

Multiple producers can connect to a single consumer, but the reverse is not possible. The cardinality restriction is also valid across integration projects. If two consumers with the same endpoint are deployed, then the start of the second consumer fails.

While configuring the ProcessDirect adapter, please pay attention to the receiver address that you are using to trigger the consumer iFlow from the producer iFlow.

Representation of address customization for the DirectProcessing adapter in both consumer and producer iFlows

Example

For demonstration purposes, I am going to create two producer iFlows that will have the Content Modifier step in them. The Content Modifier step is used to create the new exchange property and then print it out in the message body.

Here are the settings of the ProcessDirect adapter for two producer iFlows

Moving to the consumer iFlow now. To make the consumer iFlow available to be started from the producer, it is required to set up the ProcessDirect adapter as a starting entry point by providing the correct address. Please refer to the screenshot below.

After deploying the changes, I am triggering the first producer's endpoint

and the second one

If I open the Monitoring tool, I would be able to see two calls of Producers' iFlow and two calls of Consumer's iFlow as well.

I hope this makes sense.

Resolving Issues with PGP Decryption in SAP BTP iFlow

Hey there! I want to address an issue that may arise in projects involving encryption/decryption within the SAP BTP iFlow and its embedded PGP engine. Scenario description Imagine you've installed the latest version of the gpg4win application (version 4.3.1) to generate public and secret keys

Creating an API for iFlow: A Step-by-Step Guide

This guide aims to outline the steps required to create an API for iFlow and subsequently run the iFlow through the API. Step # 1. Develop an iFlow Begin by creating a simple iFlow. Deploy any changes made. Step # 2. Setting Up API Providers Navigate to the API section on the

Logging the iFlow's payload

This note contains an example of a Groovy script that may help the developer trace the payload within the iFlow, especially if it changes during its lifecycle. It is worth noting that the beauty of the script below is that it adds an attachment to the processed message that can

Overwriting standard BTP iFlow header parameters

This brief note aims to highlight the possibility of overwriting standard iFlow header parameters, offering developers flexibility in addressing various requirements. Specifically, this discussion centers around the header parameters SAP_Sender and SAP_Receiver. See Headers and Exchange Properties Provided by the Integration Framework SAP allows developers to overwrite the