Posts

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.

Governing SAP CPI with Figaf Tools Webinar replay

Managing and running an SAP CPI system can be easy. You can if you don’t have any quality control and can move everything. I have examples on fixing a feature request and move it to production in 30 minutes. No governance was made in this process. Which was not optimal nobody would know what was going on.

If you want to be able to govern the approach then you need it will take some longer. Govern is about managing the process to ensure there is proper audit trail for all changes, testing, and documentation is in place. This is something that can take a lot of manual hours to get working. With the Figaf tool we have automated the full process, so you developers, architects, and business experts no longer need to spend as much time on the tasks.

You can see the replay of a webinar below. This covers a lot of the process around change management and it even shows what is possible with the development process.

Try the Figaf tool

You can try the Figaf tool you can signup here

Figaf 2.11 is out, enabling DevOps for SAP PI and CPI

Now we are able to deliver Figaf IRT 2.11, it will enable automation of SAP Integration never seen before. It contains 150 tasks or bugs and 55k new lines of code. So it is a massive improvement we have worked on. It contains two main areas.

  • Transport and governance system
  • Migration of SAP PI/PO if you are still missing to migrate to 7.5

Transport and governance process

When we have talked with clients of the Figaf tool and our integration with CTS+. It seems like only 50% of the customers were using it. I could configure it on our system without much knowledge in 4 hours. So it should be possible for all SAP users to use it.

My these on why CTS+ it has not been implemented as much is that it is not adding much value, and is just complicating the process. You cannot really see what is in the transports and once you have imported the directory you anyway needed to perform manual steps to configure it.

That is the reason I’m stoked we have created our own transport approach. It is really simple to configure and make it possible to improve the delivery of SAP Integration. This is the way transports are supposed to be handled in the modern world.

The process is as follows, in most cases:

  1. Create a Ticket that links to the business requirement or failure created
  2. Add the objects that you have changed
  3. Figaf will then know what objects need to be tested and can test the flows
  4. You can create transport with all the objects.
  5. You then configure what channels will be like on other systems in the landscape
  6. A user can then approve the transport and allow you to transport in the landscape
  7. You can import the transport in the landscape, and it will then configure the communication channel
  8. You can create an Excel report of the change and upload it to Jira, Service now

You can see how this enables DevOps for SAP PI/PO in this video.

Migration of SAP PI/PO

The new release also enables users to help optimize the migration process. A lot of users still need to perform migration projects. It is quite a labor-intensive process that you need to perform. That is why it would make sense to automate the process. If you are looking for a migration project, recommend to check out the migration option. I have created a video of the process

Roadmap

There are still areas that we would love to improve, depending on what customers see as most important. Like how to perform validations on the QA system. Does it require running the test on that platform, or are there other functions that could make sense. A lot of the configuration on how transport should be imported is now possible it just requires users to figure out what they need to be.

For the migration support of Classical scenarios is also on the which list, but will require we can work with a customer to enable it.

If requested we can incorporate it with CTS+ so it will still run your transports and Figaf would handle configuration and documentation.

Get Started now

You can start using the Figaf tool for free. Just go to Figaf.com/IRT and signup. Then you will get a free license key you can use for the migration.