Automating SAP PI/PO to SAP Cloud Integration Part 3
It is one thing to build a prototype but it’s another to make a solid product that works in more environments with all the legacy workarounds that have existed.
We released the first version in August 2021 and got to run it at a customer in September. It was one thing to build it for an internal test system another was to work with real clients systems that have evolved over 15 years. So we had to invest in making the application more robust.
If you want the un-cut version. Here you can see an end to end migration with the tool. In 15 minutes you can see how to migrate an ICO, create and run test on it and then move the iFlow to QA.
The Original version had the following features:
Creation of iFlow from ICO/Receiver Determination
Migration of Message Mappings even with Function Libraries included
Migration of channels to CPI blocks
Testing of the migrated iFlows
Transport, configuration and documentation of transport to production
Over time,we listened to the feedback provided by partners and customers to figure out how to improve the tool.
Since the original launch of the tool we added the following:
Stability to work in SAP PI 7.1 environment with a lot of old configurations
Migration of RFC lookup functions where it would add an empty function you can fill in with the lookup if you need it.
Support for BE/Synchronous scenarios where you will get both mappings included
Support of multi mappings
Possibility to use the Operations Mapping.This ill allow you to convert multiply mappings and add them to your existing iFlow in a simple way
Message Mappings with parameters are converted and added automatically to the iFlow as external properties.
Support for multiply external properties with the same name but with different values. This will allow you to have channels with HOST and have two different values for them
Route based on Operations in the payload
Improved testing so you can take your SAP PI/PO test cases and run them on the Cloud Integration iFlows. We also added improvements if you had made transport manually.
There are many times that we would like to improve the tool.
One of our next things is to add an overview screen to give you a full insight into the migration process. You can see the report here.
The idea would be to show list of your ICOs and their status of the migration. From this list you can handle and oversee much of the migration process.
Migrate an ICO automatically or select the manual iFlow you wanted to use it for
How many messages on the ICO last month
Create test cases from the ICO
Show the transport status of the migration, so you can follow progress
If there are any problems with the migration like cases that cannot be supported
In the foreseeable future I would not expect to be able to automate the full assessment of what can be migrated and what you would expect to handle manually.
I would also like to find a way to handle cases with XSLT, Java mappings and Adapter modules. XSLT should be pretty easy to convert but the two other options will be quite difficult to convert easily.
We are also considering different options to build more robust iFlows to handle all cases.
Try it yourself
The tool can either run on your laptop for a PoC or you can run it in SAP BTP Cloud Foundry which is the better approach to run the tool in productive setting.
We have created a Discovery Center mission to show you how to get started with the tool.
You can also keep up with the latest updates for the SAP PI to CPI migration tool and sign up for it at our website. There is a free trial that is pretty easy to set up yourself to experiment with the capabilities of the tool.
We are also on the SAP App Center
thank you for the great blog. One question regarding custom extensions in the PO flows, how is the tool handling these? Will this ones require manual adaption?
Or are they adapted by the tool?
Thanks and regards,
The Tool does not support modules and it is something you will have to handle.
Also special adapters or differences between adapters is something you will need to handle outside of the figaf migration tool. You can use the tool to create you own XSLT mapping between one of your custom adapter to a iFlow Adatper block. It probably is you have more than 5-10 of a specific adapter.