Technical Articles
Cloud Integration in GO (CIG) Desktop version – transports management
A few months ago, I published a post related to the CLI tool for Cloud Integration.
Here is a link to that post: https://blogs.sap.com/2022/08/26/cloud-integration-cli-in-golang-cig/
Now the time has come for a desktop version for this tool – I have named it cigDesktop.
The application can be run on Windows, macOS and linux systems. I have put the executable files for windows/amd64 on Github.
At the moment, this application solves the problem of transferring/transporting integration flows between different tenants. The application can also be used to move iflow in the same tenant.
The main advantages of using the app:
- When you do the iflow transport the first time – the configuration parameters are taken from source system
- When you do the iflow transport next time – there is no need to create the configuration parameters from scratch.
- The transported iflow is transferred as a new version to the target system. You have access to earlier versions.
- It is possible to change the Id and Name of the iflow during transport.
- intuitive interface
The project repository is available at:
https://github.com/tobiaszgithub/cigDesktop
Executable files for the windows operating system are available at:
https://github.com/tobiaszgithub/cigDesktop/releases
Integration flows View
Transport View
Settings View
This is the first version of the app, I have some ideas on what to improve and what can be added.
@Tobiasz Hołtyn - Thank you for the nice tool. Do you mean using the standard CTMS or file transport we can't achieve the below point? My understanding is that the config parameters are never overwritten using the standard options.
When you do the iflow transport next time – there is no need to create the configuration parameters from scratch.
Also, please confirm if we need to deploy the iFlow after moving the transport.
Hello Abraham,
CTMS for cloud integration is additional service. You don't always have access to it.
For the time being, you must additionally deploy iflow. This is one of the features I intend to add.