Mediation primitives let you change the format, content or target of service requests.
A mediation flow component can contain one mediation primitive, a number of mediation primitives or no mediation primitives. Using more than one mediation primitive lets you create more complex mediations.
A mediation flow component contains flows for handling requests and flows for handling responses or faults.
A request flow begins with a single input node for the source operation. The input node is followed by one or more mediation primitives in sequence and a callout node for each target operation, all wired together. If a message is to be returned to the source directly after processing, it can be wired to an input response node in the request flow. If fault messages are defined in the source operation, an input fault node is also created.
A response flow begins with a callout response node for each target operation. The callout response nodes are followed by one or more mediation primitives in sequence and a single input response node representing the source operation, all wired together. If fault messages are defined in the source operation then an input fault node is created. If fault messages are defined in the target operation then a callout fault node is created.