The typical setup consists following steps:
1. Identification of the interfaces to and from the external system
First, you need to analyze the current setup and flow of the messages exchanged between SAP and the external system(s). Then, you need to identify which messages are being sent from the system, which IFTT will virtualize. You need to know what response is expected based on a particular request.
...
On the backend system, a PO document is being created. Confirmation quantity based on % should be provided in header text. The creation of this document triggers the integration to the third-party system.
That operation will trigger the Delivery Document creation in the Backend System.
The third-party system receives the message with information about the Purchase Order and the Delivery and sends a shipping confirmation response message. The item quantity in this document should reflect the information provided in the header text of the Purchase order.
2. Implementation of virtualization logic in XSLT or middleware mapping.
You need to specify the transformation logic based on what response is expected based on a particular request. It should be as dynamic as possible.
...
Configuration for Transform Test Messages by XSLT for more information.
3. Creation of the test case responsible for the creation of the Business Document and the listener test case
Create a parent test case (first in the sequence). Like in the classic E2E testing, the full flow will be triggered by a parent test case responsible for creating the first Business Document.
...
For more information on how to create a sequence of test cases for the E2E testing, please refer to the section: Reflecting business process - sequence test cases
4. Creation of Int4 IFTT automation objects
As a next step, create an Automation Object that will be responsible for the implementation of the virtualization logic.
The Automation Object should point to the integration, which is aimed to be virtualized by IFTT. For instance, the expected response message from the external system. For more information about the creation of the Automation Object, please read the section of the Configuration Guides, which fits this particular scenario.
5. Activate the scenario by scheduling a virtualization job using the sequence of the test cases.
In our example scenario, we have created the sequence of the test cases
...
5. As the last step of the configuration, you need to modify the Automation Object used by the “PI Responder” test case. Go to the Additional Parameters, provide Parameter name “TRANSP_INP2” and the “PI listener” test case number as the parameter value
...
Test Cases Execution
To test the entire solution (and virtualization of the external system), you need to run the sequence of the test cases.
...