You can try Figaf in your migration projects for free. Just start a free trial and you can get started with the tool right away. Figaf covers all the needs you have for your migration projects.
You will need to be performing many migrations and you need to find a good way of working with them. One that will allow you to continue to become better at delivering the integration.
I normally recommend taking one ICO at a time and migrate it or the required interfaces from it. Mostly when you are getting started or in the pilot project.
Everybody can migrate to iFlows. It is only when you test the integration that you get credit for the work. Otherwise you are just wasting the time.
The best place is to use the Migration overview to find the interfaces and see what is migrated. You can also see other information like the number of tests created on SAP PI or that has been migrated.
Once you have migrated an interface you will need to work on a few manual steps.
Some of the manual actions you may need to perform are:
- Adapter configurations that after the migration do not match what is needed. Note if there is a need to update the template.
- Check security credentials
- Are there any problems with the message mapping that need to be corrected before release.
- Do all of the UDFs still work or should they be corrected.
- Create test data from the PI system
- Testing the integration. If you have not created test cases in advance you will need to do it first.
- Test coordination with business
- Move to production
- Coordinate go-live
- Make documentation
You should of course figure out what works for you and adapt. There are likely many cases that can be optimized like one person who is creating the SAP PI/PO test cases for all the different scenarios in a release. It can simplify the operation and enable developers to test faster without having to wait for test data.
Batch migration
Many would ask: now that I have these 100 ICOs, can I just press migrate all to Integration Suite?
Figaf lets you select several ICOs and migrate them in one batch. It can save time, but as I see it, there are still a lot of steps you will need to do for each migration. The more you get to use the tool the more you will see what needs to be changed.
If you migrate 10-100 ICOs in one go, you will still have to go through each of the iFlows and check if they are correct according to the list above. And if you find a problem on the 5th iFlow, you may need to re-migrate the other iFlows with different settings. So start with one ICO at a time, and use batch migration once you are confident in your templates and settings.
Future
As tools progress, more of the process can be automated, but you should be fairly confident that the result is what you want. It would be nice if we could automate the process fully but I don’t see that we will have the confidence for fully automated migration in the short term. Maybe we will get much more confidence in our processes and allow much more automation and take the decisions ourselves.
