WebSphere Enterprise Service Bus for z/OS, Version 6.2.0 Operating Systems: z/OS


Dynamic invocation

WebSphere® ESB supports re-routing of messages, by dynamic override of statically-defined endpoints or dynamic invocation using a target import.

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:

If a message flow is changed dynamically within a mediation module, the new route applies only to that message and any response coming back. When the message has been sent and any response returned, the dynamic routing changes are discarded and the original static values defined in the module are used as the default values again.

There are three main ways that dynamic invocation takes place:

Any response message always returns using the same route as the original outgoing message. You cannot dynamically override the routing for a response message.

During a dynamic invocation, the invocation target type is identified by examining the endpoint URI. If the URI begins with sca, this indicates an SCA component.

A URI prefix of http or jms is assumed by default to indicate a Web service endpoint. A URI prefix of http does not by default indicate an HTTP service. A URI prefix of jms does not by default indicate a JMS service.

However, if the reference is wired to an import with a JMS or HTTP binding, then the URI is assumed to be JMS or HTTP, and not Web services.

The bindingType field in the Endpoint Reference (EPR) can be used to change this. For example, using the SCA Endpoint Reference API to set the bindingType field to a value of EndpointReference.BINDING_TYPE_HTTP uses a URI prefix of http in the EPR which is interpreted as indicating an HTTP service for that message.


concept Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 21 June 2010


http://publib.boulder.ibm.com/infocenter/dmndhelp/v6r2mx/topic//com.ibm.websphere.wesb620.zseries.doc/concepts/cwesb_dynamicinvocation.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).