Originally posted by: bdebruin

I'd like to hear people's experiences using the WTX node in WMB as it seems many companies are either making the move from the launcher to the broker or talking about it.

I'm curious if other WTX mappers find it really easy to develop in WMB using the map node, but overly complicated using ESQL, Compute nodes, and Collector nodes. I feel that WTX's strength is speedy development with very little syntax and other hurdles that I'm running into using ESQL in WMB.

I'm a newbie to WMB (WTX 10 year veteran), so I really want to know the pro's and con's of using ESQL verses a simple map called with the map node. Is there really a big performance gain by using the ESQL when I can do the same thing using WTX in a few minutes or is it just "the right way" to use WMB?

One example is using ESQL to split a file verses using a WTX tree, controlled break logic, and a PUT in the WTX map. Another example is using the Collector node versus using a GET to pull data off a queue in order to concatenate two files tgether. I feel it's much easier to look at, maintain, and probably even performance-wise to use the map, but, then again, I'm totally biased.

Thanks for your opinions,

Barry
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender