Create a Git repository for your SAP CPI development in 20 minutes
If you want to be good a developing Groovy scripts you need to move out of the SAP CPI “Editor”. It will not enable you to run code the correct way. That is why you need an IDE for making sure you have all the correct tools available.
Normal developers would be using a Git repository to handle all the requests they have. It enables them to have access to all the required objects needed for any development effort.
We wanted to make it as simple as possible to use our Git repository. One that you got all the templates and tools so you could start developing fast. No need to go understand how to use Gradle or install plugins. It is all delivered in templates that are easy to use. Even if you have not to spend a lot of time developing it.
Best of all you don't need to write any code yourself.
There is a free 30 day trial of the Figaf Tool that will allow you to try out the tool and create a repository you can use for your Groovy development. I do hope you want to use the tool for longer, but it is not a requirement.
You can see how to use the tool here.
The Video takes 20 minutes and covers:
- How to install Figaf DevOps Tool
- How to connect to an SAP CPI Trial system
- How to create a git repository
- How to create a test case in Figaf
- How to use the test case so you can test your Groovy
- How to debug your groovy
You can see the full video here:
You can download the Figaf DevOps Tool for SAP CPI here.
I do prefer to use IntelliJ since it has all the plugins you need. The community version is plenty to start with. You can also use Eclipse or VSCode it all depends on what you like to use and how difficult it is to add plugins for it.
In the view, I also use Service Key to send messages to SAP CPI To create a service key to send messages to SAP CPI Cloud Foundry.
How to synchronize
There are different ways of working with our Git repository. The simplest approach is that you revert all the changes in your local repository and then pull changes from the irt-sync branch.
Once you have done any changes you just use the Gradle Plugins to up or download the iflow and deploy it.
For more advanced cases you can use the option to not synchronize iflows, then the git repository will only be managed by the developers. It does add some complexity to the process. It will give you some options to manage the workflow and approval processes.
We would still recommend the Figaf tool for managing the release process.
Future of the Git repository
One thing we are focusing on is to give developers a good place to start working. We are considering how we can leverage the Git repository together with.
If you run git on windows we have to see problems with too long filenames. If you get this warning open a cmd as administrator. Then run the command
git config --system core.longpaths true
Then you should be all set
Git and API management
If you want access to Git repository for API management it happens the same way. You just create an API management agent and then you will get access to edit and upload API proxies in a git repository.
It also has the same templates that you can leverage your Gradle plugins.