If you are working with any type of SAP Integration you have probably run into the question about how do you ensure the message is being delivered correctly.
This was something we took for granted in the SAP PI world but in SAP Integration Suite it is not possible. Customers and partners have therefore been building different flows to handle guaranteed delivery of messages in a simple way.
In March 2024, SAP released their Pipeline Concept to support this goal. We also released a way that enables you to explore the concept fast with our template.
Moreover, we have been making the first presentations on the topic which had great success.
Note: The following is a vision that we hope to be able to deliver but there is some uncertainty if possible.
My take
I do think it offers a good way of processing messages in a standard way.
I’m not sure SAP has the best solution but I do like the “open source” flow of it so users can customize it.
For users it does have a many benefits that you dont need to think too much about starting to use it. You can get started with low effort. If it becomes the main standard for running, then it becomes easier to train people because everybody will know the framework.
One of the big challenges is how you would maintain such a scenarios without having a good tool for it. This is where Figaf comes in to the picture.
Operation
One of the areas where I think it is quite challenging is on the operation side. Is only an API for the Partner Directory, no UI. It is all something you will need to edit using your own API testing tool. It it will make it complicated to operate at a large scale to the 100s of flows.
That is luckily one of the things we are good at in Figaf. We will therefore enable you to operate such scenarios easier. We will improve the Figaf tool to be able to support the pipeline operations.
We have our DevOps concept for iFlows and all the other objected need to move integration to production in fully govern way.
- Maintenance of parameters for a partner/message combination
- Developing and testing XSLTs for routing with Cloud Integration specific usage
- Transporting configuration for a partner (including reusing Dev also for QA)
- Linking and understanding dependency between iFlows and Partner Directory objects
- Testing (already works but we could simplify the setup)
- Monitoring (not sure what could make it better yet)
Migration
One of the big drives behind this is the ability to simplify the migration of ICOs into iFlows and keeping the logic of asynchronous message processing.
We have currently enabled migration of inbound and outbound processing. This will enable you to create the process direct flows suggested in the template to be able to process a migration. This will be in our upcoming 2404 Release.
But we want to enable you to create the full migration from one ICO. Then it will create everything you need for the model to work that includes
- Inbound flow (if needed)
- Content conversion flow (if needed)
- Outbound flows
- Partner Directory content incl
- Definition of sending system and messages
- XSLTs for Receiver and Interface split
- Parameter template
- Link to all artifacts in the overview
Experiences
I think the main part about this is to understand how this will work in a real scenario for customers. As we learn the framework more we will be able to see how we can improve the processes.
We will be rolling out this changes over the next few months and also learn from the feedback from customers how it works to operate this.
Get started
I think the most important part now for you is to start exploring if the concept will work for you. We do have a short guide here. Then I would urge you to go through a trial of the Figaf DevOps Suite or the Figaf Migration Edition to see if the process would allow you to run smoother. Then you will be able to grow your pipeline practices with us as we improve the tool.