Last Update: 16. Feb. 2024
Transports across Tenants (Neo & Cloud Foundry, Integration Suite/CPI) usually works like this:
![](https://www.integration-excellence.com/wp-content/uploads/2024/02/image-2-1024x360.png)
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
![](https://www.integration-excellence.com/wp-content/uploads/2024/02/image-3-1024x682.png)
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)
![](https://www.integration-excellence.com/wp-content/uploads/2024/02/image-5-1024x328.png)
![](https://www.integration-excellence.com/wp-content/uploads/2024/02/image-4-1024x507.png)
![](https://www.integration-excellence.com/wp-content/uploads/2024/02/image-8-1024x630.png)
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
![](https://www.integration-excellence.com/wp-content/uploads/2024/02/image-6-1024x600.png)
![](https://www.integration-excellence.com/wp-content/uploads/2024/02/image-7-1024x518.png)
![](https://www.integration-excellence.com/wp-content/uploads/2024/02/image-10-1024x874.png)
![](https://www.integration-excellence.com/wp-content/uploads/2024/02/image-9-1024x852.png)