SAP Integration weekly 42: New Migration tool and AI generation

This week was a school vacation week so my son was out of school. Luckily, we could send him for hockey camp for a few days, that he really enjoyed. We also went for a family trip to Tivoli Gardens, but it seems like too many others had the same idea. They had made it really nice with a Halloween theme.

AI Script optimization for SAP Integration Suite

It was one of the SAP TechEd keynote announcements. You don't need to wait until Q1 2025 to be able to optimize your Groovy scripts. You can already do it in Figaf.

Check out the short video and Please give it a like or a comment

SAP has updated its migration tool to Integration Suite.

Making it easier to perform the migration.?

I have seen a presentation about it, but I have just been able to look at it in detail.

They have taken the same approach Figaf took with our migration tool 4 years ago by generating iFlow based on the ICO.

There are now only 3 templates, Sync, Async, and Recipient list, where you have multiple receivers. You can always generate the iFlow even if objects cannot be migrated.

It simplifies the migration journey because you don't need to consider a particular pattern for your migration. It also simplifies the effort from the SAP side to maintain the patterns.

Is there still a need for Figaf's migration tool?

We can still add value to the process and reduce your effort for the migration. There are still gaps that would require much time to resolve some migration. But in general, I would recommend that you explore both and, on an object level, decide which makes sense.

Read more about our thoughts on SAP's updated Migration Tool here.

Understanding your SAP PI/PO Landscape before migrating

Before starting a SAP PI/PO migration, knowing what you have in your landscape is essential.

?

I had a conversation with one of our partners. They wanted to better understand the estimates they provided for their customers. I showed them what Figaf could provide (for free), and they could see it improved the quality of the estimates they could provide.

?

In this article, I show some of the data you can get from using Figaf free Migration Edition to create a complete inventory of your SAP PI/PO system.

?

From our experience, it is the small things that impact whether you can migrate a scenario or not. The report provides some details.

Setting up iFlow transport including governance under 45 minutes

It does not need to take a long time to setup a good transport with SAP Integration Suite/CPI.

?This week I had a session with a customer. In just 43 minutes, we created:

• Transport path including a virtual landscape (where Dev tenant is also used for Testing but with full governance)
• Created some transport an validate them
• Configured external properties including automatic replacement of values.
• Created a custom rule to warn if csrf token was not enabled on an adapter
• Worked with the different transport paths
• Check the difference between the deployed versions
• Reused test cases to document that the iFlow worked as expected.?

They got all they needed to be able to start using the tool to transport their integration. Watch an end-to-end setup demo and see what's possible.

?

In the last 10 minutes, we could relax and examine the Groovy Editor and the Alerting monitoring.

?

Camel update: The gift that keeps giving

So this week I got the link to the note about Camel update from Nuno Pereira about a change in the camel update.

From Camel 3.12 the use of ${in.body} is no longer recommended. For my testing, it does not seem to be a problem on our pre-camel tenants. And I don't think it is going to be a problem with Camel 3.14 that SAP is using.

But it may cause problems in the next release of camel.

I did create the following meme. Do check the conversation out on Linkedin. Check it out and share any thoughts/comments on the new update.

Download CTMS transport logs by using Cloud Foundry CL

You can get the logs from the CTMS using the Cloud Foundry Command line if the transport fails of your Integration Suite objects.

It makes it a bit more complicated to access and view the logs.

Unfortunately, not many integration suite developers use CF regularly.

We spent much time in Figaf to be able to provide you with as many logs as possible from the UI. So you can easily understand why your transport fails.