Padding Differences in IBM WTX

Padding Differences:

"Consider the structure is having the fixed length of 10 with padded 0."

If type tree is used in input side of IBM WTX, and if the data is less than 10 characters then remaining characters should be present in fixed length with padded 0. For example have a look below:

Example: If the input data is 12345 with 5 characters only then five (5) zero's (0's) should be present for validating data property in this case. Without invalid error, the data to satisfy above condition will be as: "0000012345".

Note: If the input element is dragged on any output element then you can find only 12345 as if input element is padded by char [in this case 0] then resulting element at output side will be without padding.

If type tree is used in output side of wtx and if the data is less than 10 characters then the remaining chars will be added automatically in fixed length with padded 0.

Example: If the Output data is "12345'' and it is hardcoded value then five zero’s will be added automatically in this case. The data to satisfy above condition is with invalid error will be as: "0000012345".

IBM WebSphere DataPower: IBM WebSphere DataPower is a network device which is primarily an XML gateway appliance. It can process XML, transform, bridge transport protocols (HTTP, FTP, MQ), provide message level security and act as a lightweight broker (and proxy).

IBM WebSphere Message Broker (WMB): This Message Broker is an Integration tool which can transform, enrich and route the messages. It can also bridge transport protocols as well. This is built on MQ; it supports HTTP, JMS and some more. This WMB also supports custom adapter. Can support publish subscribe models, ESQL scripting, & Message Trees. A WTX map can complement the ESQL\Java scripting for transformation purposes.

IBM WebSphere Transformation Extender (WTX) is primarily a transformation tool. It can hook in to both IBM WebSphere DataPower and as well as IBM WebSphere Message broker also.