If you want to leverage the SAP CPI capabilities and improve the speed of delivery, you need a better way than using the Web front end of SAP CPI. Many users will create a GIT repository to add files to, so users will get access to all files for the project and can use their favorite IDE for it. It does require a lot of effort to keep everything synchronized.
We have started to improve the functionality for users to be able to use SAP CPI from their own IDE. For this, we have created a few new features.
In Figaf DevOps Suite we have added an option to synchronize all your integration content to a Git repository. You can use Github or SAP’s Git service, so all your team can get access to the same source. We support:
- Packages
- iFlows
- Value Mappings
- Script Collections
- Message Mappings
We have also:
- created a Gradle plugin that allows you to download, upload and deploy integration flows from your IDE. This is a free plugin you can use even if you are not using Figaf DevOps.
- created a Gradle plugin that enables you to run a test case for one or more iflows as a part of a change.
Our design principle has been to make it as easy for developers to get to use Git and deliver as much preconfigured. You can add more plugins if you want to.
Watch on YouTube Preview: Figaf makes SAP CPI and Git integration
Since then, the Git integration has grown. Today Figaf commits and pushes all detected changes automatically every time you synchronize, and it can run a pipeline in GitHub Actions that validates your changed iFlows. See how it compares with SAP’s own GitHub integration.
You can sign up to try out Figaf DevOps Suite now on your own CPI system.
