Configuration of iflows Edge Integration Cell

Configuration is one of the tasks that requires a lot of effort for transports.

It is one of the tasks that Figaf really simplifies.

SAP has in 4.11.x added an option to configure Cloud Integration and Edge Integration Cells (EIC) differently.

Unfortunately, the public API only supports configuring the Cloud Integration at the moment.

It means that all the EICs would have the default configurations.

Since EIC is important for some of our customers, we have created a fix that enables you to configure the EIC flows to the same values as Cloud Integration.

They have go-lives, and the manual effort of configuring the landscape would make it challenging to go live in time.

We do hope that SAP will enable the public API to resolve. Then we will need to implement a solution to resolve the configuration for iflows both in Cloud Integration and EIC.

Workaround solution

In Figaf 2606.1 we have added an option on the landscape configuration to Set Transport Configuration as 'Default Values' for Edge runtime:

The notes state.

When this option is enabled, transport writes the values defined in the Transport Configuration into the target IFlow model as 'Default Value' of the externalized parameters, in addition to applying the IFlow configuration through the Public API.
This is a temporary workaround and should not be used as a regular setting. It exists because SAP Integration Suite now keeps the configuration of externalized parameters separately for each runtime, and the Public API as it stands today exposes only the configuration of the Cloud Integration runtime: the configuration of an Edge Integration Cell runtime can be neither read nor written through it. Writing the values into the IFlow model as default values is therefore the only way to deliver them.
Scope: only IFlows whose runtime profile resolves to an Edge Integration Cell runtime on the target system are affected. IFlows resolved for the Cloud Integration runtime are left untouched and keep their configured values as usual. On a target system without an Edge runtime, the option changes nothing.
Parameters set to 'Inherit from target' are left out - the transport does not change their value on the target, so nothing is written as their 'Default Value'. This does not preserve the 'Default Value' the target IFlow had: default values are part of the IFlow model and are transported with it, so the target ends up aligned with the source, exactly as it does when this option is disabled.
Impact on the affected IFlows: the separation between 'Default Value' and 'Configured Value' is lost on the target - the transported values appear in the 'Default' section.
For the same reason it can't be checked whether a target IFlow already holds configured values for the Edge runtime. If it does, they take precedence over the default values and the transport will not change the values that IFlow actually runs with - they have to be adjusted directly on the target system.