Automating testing of your SAP PI/PO to Integration Suite migration
For your migration project from SAP PI/PO to Integration Suite you can use the Figaf Tool to test your migration for free to allow you to run your migration project easier. This is our migration edition.
Why should you be testing your migrations
When moving between two platforms, there can be differences in how mappings, UDF or other modules. There can be some small but significant changes you want to check before connecting with partners.
And if developers can test a large part of the integration faster, they will save a lot of effort and be much more productive.
Testing will be a large part of your migration project so it makes sense to understand how you can automate the testing as much as possible as easy as possible.
Figaf is a Java application. The best way to run it is in your BTP account, which uses a Cloud Foundry Runtime and Postgresql database. The normal run cost in BTP credit is about 400 EUR/month. For a PoC you can run it on a laptop quite easy.
Installation is fairly easy and would take under 60 minutes in most cases.
How Figaf can test your integration
Figaf connects to your SAP PI/PO system. Then it can fetch payloads from the original messages and the mapped message.
The payloads can be fetched either from the
- ICO logging
- SAP Adapter modules they are added automatically.
You just select the ICOs you want to log payloads then you can select to fetch historical, future messages or just some specific messages that have been processed. You then add the suite to a test case.
There is a lot of options for classifying different messages to fetch the types that match most with your setup. It can be to extract parameters from the payload like message type or partners.
Once you have created the recording Figaf fetches messages from the PI system and you can then create a test case.
If you use the free edition, you cannot run the test on the PI system, but if you have a real edition, you will be able to run the tests.
Migrating the testcase
Once you have created the test case, you can migrate to the place in the iflow. We recommend that you in the overview, connect the ICO with the iFlow, that way, you have a way to control the migration.
Then you can select line and migrate test cases.
If you have used SAPs migration tool you will need to specify where each of the messages can be found. You do this by connecting each message step from SAP PI to a place in the iFlow model.
Once you are satisfied with the mapping you can convert the test case.
Running the test
You can easily run the test. Figaf will switch the iflow into trace mode and send messages into the flow.
Once the iflow has been processed, Figaf will automatically fetch all the selected messages and compare them with the result of the PI. It is easy to ignore time stamps and other things compared.
Then you can dig into the payload like the following.
If you click the element with an error, you can create an XPath to ignore that element and then rerun the comparison, and you have a test case.
This successful test can then be used as documentation that the flow works and you can start testing with the other involved parties if needed.
You can see the demostration here.
The main one is that the message in- and output should have the same structure and interface. So if you changes the flow, in and output you will need to test the changes manually.For now, we cannot test with the original file if you use File content conversion.
The tool can also help you with different parts of the migration. Like migrating ICOs with our own process or with transporting your integration to production. There are free trials of the two approaches in the release.