SAP Integration weekly: Move from Neo to Integration Suite

SAPinsider EMEA is Next Week!?

SAPinsider EMEA starts next week and I am excited to see how it goes as it is being hosted here in Copenhagen. I am attending and I am also hosting a session there about the Pipeline Concept.

I hope to see you there!

?

Move to Cloud Foundry: Neo to SAP Integration Suite

Neo to Integration Suite move is the perfect time to clean up old integrations.

?

Since then, you have probably been using Cloud Integration to HCI and many different developers on your platform.

You probably have some better ideas about how to name integration better. There are likely new ways of delivering and supporting existing integration.

?

As part of the Neo to Integration Suite migration, you should consider renaming objects and cleaning up many of the unused configurations.

?

With Figaf, you can easily rename the objects as a part of your migration journey. I created a video showcasing this this type of migration with Figaf.

You can then use the entire governance process of the transport tool to support how you deal with the integration.

Do you still have a need for specialized tools for handling SAP Integration Suite?

When does it make sense to use a separate app to handle your transport for a SAP product and when should you use a global tool?

?

These are some of the reflections on whether it makes sense to add a separate tool.

?

Are there some criteria you would recommend adding to the list?

?

Restore/Undelete flows in SAP Integration Suite

Continuing my thoughts on choosing a specialized tool to manage your SAP Integration Suite: What is the reason that Figaf makes sense?

?

When you need something around the Integration Suite platform that is not currently on the roadmap.?

?

This example with Restore/Undelete flows is something you do once, and then you know not to do it again. It has been in the influence program for a long time but will not be developed now.?

?

I like that SAP states they will not develop those features. There are over 1000 requests in the influence program. They should not deliver all of the features. They should focus on the parts that add the most value for customers with the least effort.

?

In Figaf, we added an option to restore in August 2020.

?

Learn more here: Restore CPI iFlows and Packages

Before it you could restore the objects from our git repository.?

You can also build your own tool to keep a backup of your integrations with some of the different DevOps / Git solutions.

?

And yes nobody would get Figaf just for the Restore feature but the fact that we can add such improves much faster can make your life easier.

And if you look a the feature requests on the influence program there are a lot of them that we already support or some that we plan to support in November.?

Transport selected artefact to Cloud Transport Management service using Agent UI

There seems to be some improvements in the Cloud Transport management. You can now select multiply different objects as a part of your transport.

I do think this is quite an improvement. But as I see it there are still a number of gaps where Figaf can make your transport process easier. You cannot see when they where changed.

?

Like you can only see the version, see what is changed but there is no configuration of parameters.

?

Have a great weekend.