Posts

SAP CPI Testing, now with Mock and secured data

Testing is not really fun. But you need to perform it.

Making a good unit test for SAP CPI and testing full iflows is one of the more complicated processes. You could create some test cases but it became pretty difficult to manage

1) Testing with mock services. This is if you have SuccessFactors systems you cannot call once you want to run regression tests. Then the Figaf tool will replace calls to SuccessFactors and replace them with an HTTP call to Figaf. In the request, it will inject the expected response. So you can get to test scripts, routing, and flows.

2) Secured testing. The best test data you have is from production. This is in many cases confidential like HR data. You, therefore, do not want all your developers to see the information. That is why we have added secured testing. This ensured the payloads are masked in the Figaf tool, so normal developers only see masked data. So they will be able to determine something is wrong but to get the name of the person.

We have written a lot more about the secured testing that also is for SAP PI/PO.

You can see how this works in the following video.

3) Groovy unit tests based on the Figaf test cases you have. This is a simple way to test all your groovy scripts in an Iflow. We have bundled this with the Git integration to make it possible to run the development process simpler. This allow you to run and debug your groovy scripts and it is a lot faster to develop in that way.

Try it out

There is free trials of the tools at https://figaf.com/irt. You can get started in less than 60 minutes to try out what the tool is able to.

If you any questions email info@figaf.com and we will answer your concerns.

The new Roadmap for SAP PI/PO and SAP CPI Suite

At DSAG (German-speaking user Group) there was a roadmap session that we could see some points from. This is what happens after SAP updated their support for ECC/Business Suite to 2027 it and implications for other tools. 

I would assume that this is the current working model and we will see more updates on this later. There will come an official roadmap later, once everything has been cleared. 

I created a video with some more information.

Biggest takeaways were:

  • PI 7.5 will be the last release but support extended some years until 2027.   
  • So now a new version that we got the impression the last years. 
  • There will be an on-prem version of SAP CPI and API management you can run on your own hardware. With a monitor and development tool. 

I really love this. It will have a lot of benefits to SAP customers. 

SAP PI

Java 8 has been extended support for longer by oracle. So there is no reason to upgrade to Java 11 and create a new version of NetWeaver Java. It would be costly for SAP to upgrade and also for customers so it makes a lot of sense. It is both PI but also all the other applications on the suite.

It would also be a stretch to get customers to move to the next NetWeaver release within 2 years, now have customers that have not upgraded for 10 years. 

I don’t know what the investments will be into PI/PO with this extended support. I would assume they free some capital for not having to perform the upgrade. 

SAP CPI

SAP CPI is the path forward and where customers should move. 

Removing PI from the Netweaver stack makes a lot of sense. It was probably 6 months behind cloud deployment and was costly to implement. I would assume there is quite a bit of work to port the framework to use the Netweaver stack compared to the cloud. 

That was the main reason we dropped running our Figaf tool on Netweaver stack. 

My assumptions of this: 

  • I would assume that you need to upgrade every 1-3 months to get support or even be able to use the tool. I expect that SAP does not want customers running 5-year-old versions of CPI. So you need to be able to test and upgrade much more often.
  • If SAP did not have the dependency for Netweaver then CPI can be upgraded to Java 11 and Camel 3.0. 
  • If SAP will allow users to have an on-prem version of the CPI then it means that there will not be a change to WebIDE to develop CPI.

Learn more

If you want to learn more about SAP CPI we have created a course that helps you understand how you can develop SAP CPI, so you can get started faster. On the side you can also find our free version of the course.

If you want to develop and manage SAP CPI better try the Figaf IRT. It enables you to manage, govern, test and document SAP CPI and API management much simpler.

Webinar: Automate your SAP PI/PO, CPI, and API management

On January 30 I hosted two webinars on the topic of how you can speed you your SAP PI and SAP CPI development processes.

From my conversations with people there seems to be a lot of new integration projects going on. And most integration developers have a way to much work they need to work on. We also see trends towards Agile or DevOps where users need to be able to release code much easier, this is what the webinar is about.

That is why I think automation is the way to go. There is a lot of places where it is possible to automate your SAP Integration processes. I normally see the following 5 areas where it makes sense to automate as much as possible.

  • Development
  • Testing
  • Governance
  • Monitoring/Support
  • Migration  (in another replay see video)

In my webinar, I covered the 3 middle parts where the Figaf tool can help you automate the process.

See how to get started

I want to demystify how difficult it is to get started. So in 15 minutes, I’m able to install and connect to both a PI and a CPI system and setup testing on them. You can see this part after 1:07 hour. 

You can get started at https://figaf.com/IRT 

Figaf runs Figaf (SAP CPI Git Groovy scripting)

This week I wanted to try to use our Git for SAP CPI tooling to make some new development and see how it would work out. I wanted to create an SAP CPI microservice to convert XML to PDF, you can see all about it here.

The idea with our Git integration is to take all content from your SAP CPI and API repositories. So it will synchronize all the content in the CPI repository to the Git. The user will then be able to see each iflow with the individual resources. In the Git repository, we had templates to some Gradle plugins. They allow you to upload the content directly to your SAP CPI agent and deploy it all from your IDE like IntelliJ or Eclipse. This speeds up the development because you don’t need to edit files in the WebIDE or upload them manually.

A real editor gives you the option to get syntax highlighting, autocompletion and debugging options. To achieve the running and debugging option we are able to leverage a real test performed with SAP CPI.

Our ide was to make it as simple for normal integration users to be able to edit and run their Groovy scripts without having to know a lot. In my free course about Create SAP CPI Integration faster, I’m covering how you can use the Figaf IRT tool to create a Git repository and configure all parameters, so you can use this development approach. It probably takes you 15 minutes to the repository working. So it is pretty simple.

You can see what the project was about and how the tool worked in this video.

Lessons learned

This was the first time I really used this function to create a useful Groovy script.

  1. It was possible to run the Groovy script pretty simple with the test data generator. That way I could run the message and get the correct output back. Once I was developing the groovy script I could then run it locally in my IntelliJ and even run debug.
  2. Out standard git template does not allow .jar files in the .gitignore file. It is best practice not to have jar files in your git repository because they take up a lot of space. In most cases, you will find the files in a maven repository and use them at runtime. A workaround we used was to add the path to the jar files with the following line in the .gitignore file !demo/XMLtoPDF/src/main/resources/lib/*.jar . ({package}/{iflowname} /src/main/resources/lib/*.jar .You can then add lines for all the iflows you are working on with the tool.
  3. The more you understand Git and Gradle the better. It will make it easier for you to use this workflow.
  4. Our comparison did not understand that the payload was binary for comparison. So it probably does not make a lot of sense to have test cases for it. In the PDF you have a time that is increasing and most of the content is binary. It was possible to create manual test cases and use it to check if the payload was successful.

Conclusion

It does take some time to get use to develop with the Figaf tool to create your SAP CPI iflows. Once you do understand how to create a test case and run it. It is much easier to work in the confines of IntelliJ when you are experimenting and do not know what you need to fix for the code to work.

Try it out your self.

I hope you want to try it out your self. It takes 15 minutes to get started and then you can have all your SAP CPI content in a git repository.

Just go to download it at Figaf IRT

Figaf saves Christmas SAP PI/CPI support

Christmas is the time when you would like to be with your loved ones. And not work on a support case to manage SAP Integration.

This is why we want to help you. We can give you a free 30-day trial of the Figaf tools to making monitoring of your SAP PI and CPI system much easier.

At Figaf we want to make it easier for you to support your SAP PI/CPI and API Mgt system, so you can get time to be with your loved ones and not spending time on finding and solving bugs that somebody else already have solved before. The Figaf has one generic way to handle alerts, so it is much easier for you to handle the support of the system.

We have created a little video that shows you how fast you can get started with the tool.

Try Figaf

As you have seen in the video it is pretty simple to start Figaf IRT.

You can download the on-prem version here or if you want to monitor CPI and API mgt then use the Figaf Cloud.