You can configure your mediation flow component to route messages to endpoints that are determined dynamically at runtime. Since these service endpoints are not statically defined in the mediation flow, you can change service endpoints without the need to update and redeploy the mediation flow.
An endpoint in a mediation module can be selected either statically by using an import's binding, or dynamically by using an endpoint address identified by a target address element in the message header. This endpoint address can be added to the target address element in the message header by mediation primitives within a mediation flow. The endpoint address could be updated with information from a registry, a database, or with information from the message itself.
In order for the runtime to implement dynamic routing on a request, the Use dynamic endpoint property of the callout node must be set. When this property is set, the callout will route the message using the endpoint address in element /headers/SMOHeader/Target/address in the message. If there is no endpoint address information in the message header, a service will be selected statically, if an import is wired to the associated reference of the callout in the mediation flow component. By default, the Use dynamic endpoint property is set, and therefore dynamic routing is enabled. For a summary of this behavior, see "Message routing when dynamic endpoint property is set" in the topic links below:
Related information