...
Choose the target landscape for operation. It could be Development at this stage.
...
| Info |
|---|
Notice that you can migrate one Integrated Configuration to two separate iFlows - Inbound and Outbound. This functionality is supporting for example IDoc or Proxy dispatcher design approach, where inbound connectivity, outbound connectivity and main mapping logic are split into multiple iFlows connected via JMS or ProcessDirect. |
...
Next, use the dropdown to find the newly created iFlow.
...
Enter Automation Object name to reuse existing object. If Automation Object with provided name doesn’t exist it will be created during the process. If Automation Object field is left blank system generates the object using predefined name and sequence number.
...
Finally, choose a folder (might need to be created from APITester first) where to place the migrated test cases dedicated to the iFlow. Click on the box on the left of the scenario name to select it.
...
The automatically created Automation Object might not have all the details needed for properly testing the CPI iFlow. From the SAP IS Test status section, click on the Automation Object name to open the Automation Object and further edit it from there. Please read on in the SAP CPI IS Testing section of the manual how to further configure the Automation Object.
...
CPI: Block in iFlow to get input payload
CPI: Block in iFlow to get output payload
CPI: Adapter type
Following the correct Automation Object configuration, the migration is ready for testing.