Test messages serialization concept

Default serialization

During test case execution for non-SAP Middlewares, the test message is sent over to the Int4 IFTT Dispatcher by default.
The serialization takes place by validating the whole payloads of the message that Int4 IFTT sends to the Dispatcher and the new input message from the interface processing that gets saved to Int4 IFTT. Specifically, the whole message payload before sent to the Dispatcher is being hashed. The hash-string is saved to compare it with the new hashed input message. That way, you can make any changes to the original message just before re-running the test case to fulfill your testing requirements.

Serialization by variable values

There are cases when the serialization cant be performed based on the whole payload. In that case, there is the possibility to correlate the input messages using message variables.
For that purpose, the following configuration for the given Automation Object must be performed.

1. Add a new variable to the Automation Object

2. Configure the following Action:

   • Populate variable before execution

   • Locate new message using variable value

   • Generate value for new message (optional) - This action is recommended to avoid posting duplicates

   Open

   

    

Serialization by CorrelationId

When custom HTTP headers can be passed to the original process, for example, during a direct SOAP call from Int4 IFTT, the serialization can be achieved by a correlation ID generated from Int4 IFTT during test case execution, unique for each test case. 

It allows identifying all the related messages in the most immediate way.

This HTTP header can be further passed with the rest of the additional details into the SavePayload process and save this information in Int4 IFTT.