Testing of synchronous interfaces is based on validation of
1. Response message
2. Validation of the document posted in SAP Backend by the synchronous interface (optional)
There are three ways to create a configuration for testing the synchronous interface:
a) Option 1: Regular way like any other asynchronous interfaces (without connectivity testing)
b) Option 2: By the creation of Receiver Channel that will call tested interface Sender channel (within connectivity testing)
c) Option 3: Direct call of HTTP endpoint (used for REST adapter testing) in SAP PO system
The configuration object described below will allow creating test cases based on existing messages in PI persistence. It would also allow using PI Message Selector.
Exemplary ICO of synchronous interface:
And the sample message in PI/PO monitoring:
The request message is presented with the "SI_I_CR_SALESORDER_SYNC" interface. The Interface name is the name of Receiver Interface (see above ICO screenshot).
In the object definition, we will add the proper sender interface (as per ICO):
We need to let Int4 IFTT know that those messages appear in SAP PO monitoring differently, as in the above screenshot. This setting is done by additional parameters:
You will find more details on the parameters in the additional parameter section
3. Additionally, we must indicate that as a request message, we would like to fetch the BI version that logging we activated in ICO in step 1:
This setting is mandatory; otherwise, IFTT will fetch the incorrect content from PI.
4. Create a first test case and test your object definition. The test case is created based on GUID of existing message
More details about SAP PO behavior: https://launchpad.support.sap.com/#/notes/2515359
This approach will also fully validate the communication channel processing.
Please note that currently, Int4 IFTT handles only UFT-8 encoding the synchronous calls using dedicated receiving channels.
The Proxy Sender channel testing is unsupported via option 2 (Option 1 must be used instead).
In opposite to Option 1, the test cases are created based on uploading the request payloads manually.
Create a new object definition with description, name, and the namespace of the tested interface
please follow Creating the configuration object for REST/JSON interface