When a mediation module is developed and deployed, the flow of messages through the module uses static information. You can enter fixed values describing the imports, bindings and targets using WebSphere Integration Developer. Messages passing through the mediation module use these values.
For some applications, you can override or change some of these static values at runtime. You might do this dynamically by overriding a value specified for an endpoint address. Alternatively, you can select a new target import. In each case, the message flow changes according to the information in the message. For example, you can use WebSphere Integration Developer to create bindings that contain endpoint information specifying the location of a remote service. This static endpoint information can be overridden dynamically by information carried in the message. The dynamic information might specify a different endpoint for the message. You can access the endpoint using one of several supported bindings, including Web service, HTTP, Java™ Message Service (JMS), and WebSphere MQ.
Rerouting a message dynamically allows you to:
- Route the message to a local endpoint within a mediation module.
- Route the message to a remote endpoint, through a wired reference.
- Route the message to a remote endpoint, through an unwired reference.
- Route the message to a remote endpoint, through a named
import within the mediation module.
- First create the simple BO with following fields as shown in below figure
- The scheme for JCA URI is always jca.
- The jca-variant provides more information about the JCA connection, and is always jndi.
- This identifies the JCA Connection Factory providing the dynamic target address for a message.
This URI tells the EIS Import handler to look for a Connection Factory defined in JNDI as dynamicTestJNDI.