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


Dynamic invocation with wired EIS import, using SMO

How to enable dynamic invocation of an endpoint with a wired EIS data binding import, using SMO.

Introduction

You can invoke services by using endpoints that are different to those specified in the import. For EIS bindings, you can specify a dynamic endpoint by using a URL that represents the JNDI name of a Connection Factory.
Figure 1. Illustration of endpoint override by dynamic invocation using SMO, with wired import
A message flows through a module and through the import binding to a Web service. Information in the message can override the endpoint dynamically.

You create a mediation module that includes the dynamic endpoint using WebSphere® Integration Developer.

Representing the JCA endpoint

JCA URIs have the form:
Read syntax diagramSkip visual syntax diagram
>>-scheme--:--jca-variant--:--jndiName-------------------------><

scheme
The scheme for JCA URI is always jca.
jca-variant
The jca-variant provides more information about the JCA connection, and is always jndi.
jca-connectionFactory
This identifies the JCA Connection Factory providing the dynamic target address for a message. Parameters can be added to help specify the target address returned by the Connection Factory.

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.

Creating a dynamic invocation with an EIS endpoint

To create a mediation module that includes the dynamic endpoint, perform the following tasks:
  1. Create Mediation Module 1, containing an Export, a mediation flow component, and an EIS JDBC Import. The export is of any type.
  2. Make the Mediation Module import point to static SvcProvider 1.
  3. Create SvcProvider 2.
  4. Check that SvcProvider 1 and SvcProvider 2 have the same port type.
  5. Check that the callout node has dynamic endpoint invocation override enabled.
  6. Deploy the modules to the server.

Using dynamic invocation

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.


reference Reference 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/ref/rwesb_dynamicroutingwithwiredEISimportUsingSMO.html
Copyright IBM Corporation 2005, 2010. All Rights Reserved.
This information center is powered by Eclipse technology (http://www.eclipse.org).