This topic applies only to the IBM Business Automation Workflow Advanced
configuration.

Mediation primitives

Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Mediation flows consist of a sequence of mediation primitives, which define processing steps.
A mediation primitive receives a message, processes it and propagates the processed message to the next primitive or node in the flow. For example, a Database Lookup primitive retrieves a value from a database and sets it in the message. A ready-made set of mediation primitives is available from the Mediation Flow editor palette. If you need mediation capabilities that are not provided by this set of primitives, you can create custom mediation primitives to call your own Java™ implementation or an imported service. Mediation primitives have terminals which receive and propagate messages. For example, these are the terminals of a Message Logger:
Message logger in the mediation flow editor canvas
  • The input terminal on the left receives the message
  • The output terminal (located in the upper right of the diagram) propagates the message on successful processing to the next primitive or node in the flow
  • The fail terminal on the lower right propagates the message and failure information when a run failure occurs in the primitive.
For more information, see these topics:
  • "Mediation Flow editor"
  • "Building mediation flows"