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

Dynamic override of a fixed endpoint

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
Dynamic invocation by overriding a fixed endpoint can take place, when a service is called using any supported import binding.

This capability is used when the service is available from a different endpoint than originally specified when the mediation module was created and deployed.

Dynamic override of a fixed endpoint can be considered if a company is carrying out maintenance on the fixed service. In this instance, the company does not need to change their entire mediation flow to accommodate for a back up service. The company must modify the target address in the SMO header, which is done by registering the Back up Service in WebSphere® Service Registry and Repository (WSRR) and using an Endpoint Lookup mediation primitive to retrieve the Back up Service target address details.

Figure 1 shows how a message received by this module would usually be sent to the fixed endpoint for the Internal Service. The SMO can be modified to override the fixed endpoint and route the message to a Back up Service.

A new target address is set for the message by changing SMO values, using the Endpoint Lookup mediation primitive, and registering the Back up Service in WSRR. The message can then be dynamically routed to the Back up Service.
Figure 1. Dynamic override of a fixed endpoint using an Endpoint Lookup mediation primitive

This image shows a mediation flow component with an endpoint lookup mediation primitive. There is an internal service and a backup service