Last Update: 16. Feb. 2024
Transports across Tenants (Neo & Cloud Foundry, Integration Suite/CPI) usually works like this:
But, what if we want to manage (and pay for) only a 2-tier landscape (e.g. PLAY & PROD)?
Managing local copies of Integration Flows is a way, but what if you have change and sync them after having done some updates?
Sometimes we do not even need a 3-tier landscape, because the System (Non-SAP-Application or Partner) only provides one or 2 environments.
This article is for those companies, who want to manage only a 2-tier environment, but also need a way to safely copy artifacts (create and update) in an automated way.
Approach
The work is done through an Integration Flow (the Integration Package is available for download on Github)
The iFlow “WHINT iFlow Local Transport” copies the source iFlow to a new one (target)
- KEEPING the NAME (this is important to be able to compare the version afterwards)
- ADDING a SUFFIX to the ID
- into any Integration Package
- both create and update
- if the iFlow id already exists in a different package (not the target package), you will get an error
Procedure
- You select a source Integration Flow ID (from a source Package)
- You select a target Integration Package ID (can be a generic DEV package or even the package of the source iFlow)
- You decide for a suffix which is added to your iFlow ID (e.g. .DEV)
This can be done by entering the values into the configuration of WHINT iFlow Local Transport or by calling a HTML page.
Modes
- Background (enter values in iFlow configuration) and deploy (RUN ONCE is preselected)
- Browser (call a URL)
To be able to call the configuration UI from the browser, your user needs the role ESBMessaging.send (or what you configure), you can also use a user from the Service Key (Runtime, not API, see blogbost) OR you use a certificate (e.g. S-User SAP Passport) and add it to the Service Key as an external certificate:
- Export your S-User Certificate from your browser as Base64
- Add the Base64 String as a Service Key
