For this next one you need to alter the groovy script on the iFlow and re-deploy. Once you have the java library file you can add it to your class path and re-execute your project to find the next missing class. Vadim’s and Eng Swee’s approach involves executing your incomplete groovy project, identifying an error relating to a missing dependency in eclipse, and using that missing class name on an additional groovy script, which you need to deploy on CPI to download the corresponding java library from your tenant. I’d like to show you a much more integrated way of doing this without comprising Eng Swee’s goal of teaching a man to fish instead of simply giving him a fish to eat, so he has the skills to feed himself going forward. Vadim and Eng Swee left you with a very cumbersome approach to retrieve the java libraries. The blogs, mentioned above, walk you through the dependency problem with SAP’s standard class “Message” and explains, in detail, how to solve it. Import. ĭef Message processData(Message message) ĭisplayMaps('Headers:', msg.getHeaders())ĭisplayMaps('Properties:', msg.getProperties()) Message processing script “src/com/convista/groovydemo/oovy”: package Have a look at my slightly adapted demo structure below, which I am going to refer to from hereon. Then, you notice that the project produces errors due to missing dependencies. So let’s say you’ve installed Eclipse Neon, the groovy plugin and added Eng Swee’s initial scripts for message processing and running the test. You will need them to be able to execute your groovy script from eclipse.įind out how my custom iFlow finds java libraries on your CPI tenant on Vadim’s amazing blog post.Īlso, Eng Swee produced a fantastic write up on how to start your first functional tests with a groovy script.

I am going to build upon their amazing work and equip you with a custom iFlow and a Postman request that allows you to “hunt” for the Java-Libraries residing on your own Cloud Platform Integration tenant. You at least want to have syntax checks, code completion and the ability to test messages easily without deploying entire iFlows and executing them.įortunately, there are some clever people at the SAP community, who can show us how to setup a development environment for those CPI scripts. As an integration developer you want a little more than syntax highlighting. So, basically, it is like developing whilst blindfolded and then hoping for the best during deployment and runtime. The only downside is that the SAP Cloud Platform Integration WebUI does development environment. SAP offers two flavors of scripting – JavaScript and Groovy. Whenever there’s a complex transformation requirement, for instance combining rows from an excel sheet into one object by a common identifier, Scripting is a great way to tackle the issue. Today, I’m going to make your life as integration developer a whole lot easier.

Eclipse neon 2 final strings