How to handle dynamic Receiver/Sender change

This video offers a comprehensive guide on handling dynamic sender and receiver determination for testing dynamically in different environments.

The video explains a basic configuration of Int4 Suite necessary for dynamic test case execution in various types of environments. It also demonstrates a step-by-step configuration on how to resolve the following error when sending messages: No sender agreement configured that matches the message's header fields (sender party: "", sender service: "abc", interface: "<INTERFACE> ", receiver party: "<PARTY>", receiver service: "<SERVICE>")

If you watched the video and are still encountering the issue above - make sure that the business system names are configured properly.

Open

Dynamic routing based on the value in the message payload

In addition to the above scenario you may also have the one where you message is routed to the correct system based on the value in a message payload. Watch the video below to see the solution for such scenario. Below scenario also can be helpful when you are encountering the issues like below during test cases execution:

Receiver Determination did not find any receivers at all

Missing message: Party: <party> Receiver <Receiver> Int4: <Interface> Ns: <Namespace>

Open