Could anyone can provide give some comparison between WTX and FFD performance in datapower?
Pinned topic Which one is better option for xml to nonxml conversion, WTX or FFD?
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-01-22T03:30:40Z at 2012-01-22T03:30:40Z by Jaango
irazabal 120000B9EN218 Posts
Re: Which one is better option for xml to nonxml conversion, WTX or FFD?2012-01-19T13:42:52ZThis is the accepted answer. This is the accepted answer.well, I don't think you'll get many volunteers for this question: FFD is not really supported. It's legacy and it has its uses, but it is NOT intended as a replacement for WTX - only simple things like wrapping a text string with tags. So a comparison between the two is like comparing apples and oranges...
Jaango 2700038M7T267 Posts
Re: Which one is better option for xml to nonxml conversion, WTX or FFD?2012-01-21T08:18:03ZThis is the accepted answer. This is the accepted answer.
- irazabal 120000B9EN
> FFD is not really supported.
Does it mean that
1)The support is only for FFD's that are used, built in within datapower appliance? Referring to the ffds which are in store/// folder like pkcs7-*.ffd files
2)The support is for the ffds which are built like the above plus ffds, which are crafted from the Contivo analyst tool(not handcrafted)
HermannSW 2700006U545936 Posts
Re: Which one is better option for xml to nonxml conversion, WTX or FFD?2012-01-21T10:23:52ZThis is the accepted answer. This is the accepted answer.
- Jaango 2700038M7T
Alex's statements were not completely correct.
Both, WTX maps and Contivo FFDs, are supported by DataPower.
Until 2007 Contivo Analyst was the Binary mapping tool for DataPower.
Since 2007 WTX (WebSphere Transformation Extender Design Studio) is the strategic Binary Mapping tool for DataPower.
But both were supported and are supported, which means that you can raise PMRs in case of problems.
If you have a problem with a WTX mapping on DataPower you raise a single PMR at IBM.
For Contivo FFD mapping problems you might have to interface between IBM and Liason (the company who owns Contivo Analyst).
I worked on many FFD PMRs and sometimes the XSLTs generated with Contivo Analyst were wrong.
In those cases customer had to go to Liason to get Contivo Analyst fixed.
(see XSL-list posting [xsl] questions on "number('+5')"
Another major difference is that (with one exception) no new features for FFD-type binary mappings have been implemented.
(In 184.108.40.206 18-digit precision has been implemented, see 220.127.116.11 Release Notes)
So new developments are based on WTX binary mappings since 2007.
Back to the implications on how to do Binary Mappings with DataPower:
- WTX maps: you need WebSphere Transformation Extender Design Studio
- Contivo FFDs: you need Contivo Analyst product
- no handcrafted FFDs are supported (you cannot raise PMRs against handmade FFDs)
- there are 4 exceptional, simple FFDs that are supported, see the WebCasts on basics and advanced techniques
Non-XML data processing in DataPower Stylesheets (2/2), advanced
(presentation, audio and sample files of this presentation):
Previous webcast (1/2, presentation, audio and sample files):
I always made heavy use of these simple FFDs for solving all kinds of problems (eg. "how to deal with broken Webservice responses"):
WebSphere DataPower SOA Appliances and XSLT (Part 1 and Part 2)
I personally like to make use of store:///pkcs7-convert-input.ffd which is shipped with the product (XI50, XB60, XM70, XG45+DIM).
Despite its name it can be used for input and output and provides (nearly) anything needed:
Only in case you need to deal with (non-XML) text consisting of XML characters in an encoding different to UTF-8 you need one of the other FFD types.
Or if you want to process EBCDIC-encoded XML:
All of the above statements were wrt usability of tools or support.
For performance you need to do measurements to decide on which solution you want to use, if you have the option.