WTX Map Transformation Performance

The following performance test was done with a 40MB flat file transforming from one file to 8 different output files. This test is done on a Lenovo T61 with 3GB of RAM and 2.o GHz Core 2 Intel Chipset:

All nine transformation was processed in 2:13 minutes.

Please see the document below for more performance tuning tips on your WTX maps:


WTX limitations deployed onto Datapower

What limitations are their with regards to deploying some WTX maps to Datapower?

When you create a WTX map and select the Map Settings -> Map Runtime as Websphere Datapower the rebuild and run the map to see if there is any errors. See the errors below when trying to compile SWIFT transformation maps:

So before you develop your maps please review the following link to make sure that your transformation maps will work correctly on Datapower:


Using WebSphere Transformation Extender with IBM Enterprise Service Bus products

The transformation to a service-oriented architecture (SOA) includes aspects that cover the entire lifecycle of a solution, from inception, to design and development, to its ultimate deployment and management. IBM® published an SOA Reference Architecture that helps structure and position these aspects into a number of different components, and the IBM SOA Foundation includes a set of products that address specific components within the overall architecture. This article is the first of several that will discuss how products that are part of the IBM SOA Foundation can be used together. First up: how to add advanced transformation capabilities to IBM’s set of Enterprise Service Bus (ESB) products: WebSphere® Message Broker, WebSphere ESB, and WebSphere DataPower®. This content is part of the IBM WebSphere Developer Technical Journal.

For more information see the following link:


Websphere Transformation Extender Map Build Errors

Build errors prevent a map from being compiled. If build errors occur, view the errors, correct the problem(s), and build the map again. A map cannot be run if it has not been built.

In the following build messages; these letters are used as variables:

x = the map where the error occurred

y = the output that contains the rule in error

wz = numbers

Words used as variables are in italics. For example, map-name represents the name of a map.

There are other map build error codes that could occur when you are building WebSphere DataPower maps in addition to the ones listed below. See “Map build errors for WebSphere DataPower maps” for a consecutive list of these additional map build error codes for a WebSphere DataPower map.

See link  below for more info: