Differences between the transformation technologies in WMB and WTX

What are the overlaps and main differences between the transformation technologies in WMB and WTX?

There are some overlaps between transformation capabilities, but at their core, the two products have complementary strengths — WMB's being routing, WTX's being complex transformation

Message Broker is a platform for "enterprise-class data movement and message processing" building off the well proven capabilities of WebSphere MQ. WebSphere MQ is the industry-leading platform for assured transactional message delivery. On its own, it provides no capability to "manipulate" the content of messages, but in combination with WebSphere Message Broker, it offers very powerful capabilities. WMB is rich in detecting and distributing information based on message content, switching between protocols, refacing applications to perform and appear as Web services, providing high volume, high availability processing and more. It also has many different options for data transformation catering to different skill sets. While these data transformation capabilities are typically a class above those offered by other integration vendor's, WMB's focus has been mostly on the domain of small short messages.

WTX comes from a different background and has different strengths. Its heritage is the processing of large file structures, and in this area, it is particularly rich. It can provide complex data transformation capabilities for all and any structured and semi-structured data formats (including "mixed" types). Furthermore, WTX is better suited to handling "custom" tagged message formats or mixed tagged and binary. Finally, it is well suited for large file strucutures.

Combined, WTX and WMB provide a truly winning combination that is unique in the market in its breadth and depth.

Why not include WTXMB as integral component of WMB?

IBM prefers to give customers choice by providing a range of packaging options allowing the start simple and grow as and when required.

MB COMPONENTS :

• Message Flow : A message flow is a sequence of processing steps that run in the broker when an input message is received.

• Message Set   :  A message set is a container for grouping messages and associated message resources (elements, types, groups);COMPLEX TYPE CREATION .

• Execution Group : A grouping of message flows that have been assigned to a broker.

• Broker : A broker is a set of execution processes or groups that hosts one or more message flows to route, transform, and enrich in flight messages.

• Broker Domain : A broker domain is one or more brokers that share a common configuration, together with the single Configuration Manager that controls them.

• Configuration Manager : The Configuration Manager is the interface between the workbench and an executing set of brokers. It provides brokers with their initial configuration, and updates them with any subsequent changes. It maintains the broker domain configuration. It is the central runtime component that manages the components and resources that constitute the broker domain.

-  The Configuration Manager has four main functions:

• Maintains configuration details in an internal repository. This repository provides a central record of the broker domain components.
• Deploys the broker topology and message processing operations in response to actions initiated through the workbench. Broker archive (BAR) files are deployed through the Configuration Manager to the execution groups within a broker.
• Reports on the results of deployment and the status of the broker.
• Communicates with other components in the broker domain using WebSphere® MQ transport services.

WTX INTEGRATION_ WITH_MB

WTX COMPILED MAP PROVIDED BY WTX TEAM:

BROWSE :

INPUT PROVIDED BY WTX TEAM AND BEFORE WTX TRANSFORMATION:

OUTPUT TREE STRUCTURE AFTER WTX TRANSFORMATION:

WTX MAP NODE INPUT PROPERTIES:

WTX MAP NODE OUTPUT PROPERTIES:

WTX MAP SETTINGS SPECIFIED:

Card Number To Wire

    This property specifies which input card of the map should be wired. The result of this property is that, specified map input card receives its data from the prior node in the message flow.

Outputs

On the Outputs tab of the WTX Map node, configure the properties to parse the output     from the map. Here you can specify Message set, Message type, Message format.

CacheMap:

At design time, set map caching to optimize runtime performance. Map caching optimizes the runtime performance because the process does not load the compiled map for every iteration of the running of the map. The compiled map is loaded only on the first invocation of the map. When map caching is set on, any changes that you make to the compiled map are used by the message after you stop and restart the execution group. When map caching is set off, any changes that you make to the compiled map are used by the next message that passes through the message flow. Set up map caching for each WTX Map node to enable individual control for each map node instance. Set map caching on in the Basic tab under Properties in the WebSphere Message Broker Toolkit.

Note: This caching should be enabled when you are sure that, map location will not be changed frequently.

Dynamically overriding the properties of next node using compute node:

* select the compute mode as local environment and message . This property enables us to propagate local environment to the next node

If InputRoot.XMLNSC.Employee_Details.employee.address = 'MI' THEN

        SET OutputLocalEnvironment.WTX.MapServerLocation = 'C:\WTX_MAPS\xml_to_fixed.mmc';

        ELSE

        SET OutputLocalEnvironment.WTX.MapServerLocation = 'C:\WTX_MAPS\xml_to_csv.mmc';

        END IF;