USE
Testing REST interfaces are based on the synchronous test type. Int4 IFTT uses the request XML or JSON message to trigger the interface. Then validates the XML or JSON response and the final document creation on the SAP backend side (if there is such a receiver and business need). Creating the configuration object allows linking the request message with the response and the business document.
Separate configuration objects will be required for each REST operation handled by the interface.
There are two ways of configuring REST configuration objects:
- A. Direct call of REST PO service by Int4 IFTT. This way can be used when the REST channel doesn't require additional authorizations and is accessible by HTTP.
- B. Dedicated receiver communication channel in SAP PO to call the sender channel. This way can be used when the REST sender channel requires an additional authentication method.
PREREQUISITES:
- receiver communication channel for sender (Option B)
...
2. Define Additional Parameters:
...
Since version 2.7.1 Int4 IFTT supports natively JSON comparison and JSONPath expressions.
In previous versions JSON payloads have to be treated as flat files and configured with following parameters;
| Param name | Description | Value |
|---|---|---|
| FLAT_FILE | General: Flag for flat-file interfaces | X |
| FLAT_LS | General: Flag for flat-file Line Separator | { |
...
- Afterward, depending on the connection to REST adapter (Option A: direct or Option B: via receiver communication channel)
...
| Param name | Description | Value |
|---|---|---|
| SYNC_URL | PI: Synchronous: Direct HTTP URL | URL to call REST channel (without SAP PO hostname & port). Example: RESTAdapter/webshop/material/{MATNR} the URL might be dynamic and use Int4 IFTT Variables. TThe variable's name must be provided in uppercase and surrounded by {} brackets. |
| SYNC_HO | PI: Synchronous: Direct HTTP Operation | The REST operation like GET, PUT, DELETE, etc. |
Option B: This option is the same as any other synchronous interface. The receiver channel needs to be created only for int4 IFTT. This channel would be used to call the original interface.
...
As these three parameters are linked, the counter field should be filled with the same value, for example, A or 1.
3. In the Object Variables, tab define variables names and descriptions. Then in the Variable Processing tab, define actions and variable processors that will process each of the variables data
In REST testing, there might be two purposes for using the variables. The first one is like described above to create a dynamic URL for the REST channel. In such a case, the variable contains Action 10 (Populate variable before execution) with procedure USER_DEF (Read user-defined value from the cockpit). This setting allows providing a dynamic value for each case directly in Testing Cockpit. Example:
...