How to enable dynamic invocation of an endpoint with a wired EIS data binding import, using SMO.
You create a mediation module that includes the dynamic endpoint using WebSphere® Integration Developer.
>>-scheme--:--jca-variant--:--jndiName-------------------------><
An example of a valid JCA URI would be:
jca:jndi:SAPConn
This URI tells the EIS Import handler to look for a Connection Factory defined in JNDI as SAPConn.
The EIS binding uses the Connection Factory to obtain the target address of the dynamic endpoint. If a target address is found, the message is sent there. If no target address is found, the message is sent to the original endpoint.
Dynamic invocation takes place when the export is invoked with a message containing routing criteria that resolve to SvcProvider 2. The mediation flow component identifies the routing criteria in the message. The mediation flow component uses the Message Element Setter primitive to set the new target address in the SMO header, using the incoming message content and routing criteria. Alternatively, the mediation flow component might use the Business Object Map or XSL Transformation primitives to set the new target address.
The callout uses information from the SMO to invoke SvcProvider 2. Any response is returned by the response flow to the caller of export.
A one-way invocation message works the same way as a two-way message, except that no response message is returned.
A runtime exception occurs if an invalid target address is set in the SMO header. The exception is thrown by the import, and returned in the response flow.