WebSphere deployed to the WebSphere message broker Execution Group ...

Runtime selection of the WebSphere Transformation Extender map deployed to the WebSphere message broker execution Group

WebSphere Transformation Extender is a common data transformation and validation engine that can help you integrate enterprise systems and information with a development model without code and graphics. The WebSphere transformation Extender of WebSphere message Broker extends the message broke with a processing node and an additional node that contains the transformation Extender engine R the ability to transmit messages. This article will show you how to dynamically select the transformation Extender mappings deployed in the message Broker execution group from a single messaging and how to manage changes in a map without using any other system components.

Brief introduction

The Ibm®websphere®transformation Extender (hereinafter referred to as Transformation Extender) is a data transformation and validation engine that enables you to use transformation Extender mappings as well as IBM Websphere Message Broker (hereinafter referred to as messaging broker) is a flow of messages, and there are several ways to invoke the transformation Extender mapping from the word broker:

Transformation Extender Node You can add this node directly to the message flow, which allows you to configure the mappings that will be invoked at compile time or runtime. Javatransformation Extender mappings can be invoked from the Java Compute node using the Java API.

This article shows you how to configure the transformation Extender node to dynamically select a mapping that is deployed on the execution group.

Prerequisite

In order to use the transformation Extender feature of message Broker, you need to install the following software:

WebSphere message Broker V6.1.0.2 or later

WebSphere Transformation Extender Design Studio V8.2.0.3 or later

WebSphere Transformation Extender for Integration Servers V8.2.0.3 or later

Scene

The message flow must select the transformation Extender mapping to perform the conversion based on the specific field of the receive message. When the number of mappings is small, you can use routing or filters in the message flow, but as the number of mappings used by the message flow increases, the difficulty of using this method is increasing. In addition, any changes to a single map are deployed throughout the solution.

The transformation Extender node in message Broker Specifies the mapping name in the Localenvironment tree based on a condition, using ESQL or Java, allowing you to select a run-time mapping. The requirements are deployed on the execution group rather than on the anthology system, because mapping on the file system can cause versioning problems. This article will show you how to take advantage of both methods-deploying mappings on the execution group, but still referencing them dynamically from the message flow at run time.