| Author |
Message
|
| PeterPotkay |
 Posted: Sat Jan 30, 2016 10:01 am Post subject: WTX 9.0 released (now called ITX) |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
http://www-01.ibm.com/support/docview.wss?rs=2320&uid=swg27008337
Just like WebSphere Message Broker (WMB) became IBM Integration Bus (IIB), and WebSphere MQ (WMQ) became IBM MQ (IMQ), IBM changed the name of WebSphere Transformation Extender (WTX) to IBM Transformation Extender (ITX) in the latest release. 
This release is important because IIB 10 need ITX (WTX) 9, so we are now able to upgrade from WMB 8 to IIB 10.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Feb 01, 2016 7:14 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Is there really function in WTX/ITX that is not available in IIB?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 01, 2016 7:33 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Is there really function in WTX/ITX that is not available in IIB? |
There are 2 key "functions":
- manipulation of bit level data
- validation of complex (EDI / X12) formats
Now both of those "functions" are available within IIB with a little ingenuity but you can't (for example) parse and validate an X12 message in a single DFDL schema. That's why we have both, and run WTX as a node from IIB.
Many sites also use WTX/ITX when they don't have IIB.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 01, 2016 7:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
DFDL fully supports bit level parsing and serializing.
I had thought there were industry packs that covered X12/EDI formats.
Also, it's not clear from the work I've done that you ever need the entire X12/EDI message models deployed in any environment. Certain ones for certain industries, and certain transactions, but not the entire (enormous) set.
Yes, I agree, there are people who struggle along with WTX/ITX instead of the glory of IIB.
I sympathize with their plight.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 01, 2016 7:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| DFDL fully supports bit level parsing and serializing. |
It does, but WTX does the manipulation without code.
| mqjeff wrote: |
| I had thought there were industry packs that covered X12/EDI formats. |
I'm told the IIB packs don't provide the validation ("level 5"? "level 6"?) that the WTX ones do.
| mqjeff wrote: |
| Also, it's not clear from the work I've done that you ever need the entire X12/EDI message models deployed in any environment. Certain ones for certain industries, and certain transactions, but not the entire (enormous) set. |
This is entirely true. We do not have all the possible WTX models and maps deployed.
| mqjeff wrote: |
Yes, I agree, there are people who struggle along with WTX/ITX instead of the glory of IIB.
I sympathize with their plight. |
Who doesn't?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 01, 2016 8:08 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| mqjeff wrote: |
| DFDL fully supports bit level parsing and serializing. |
It does, but WTX does the manipulation without code. |
What does that mean? The DFDL parser should create separate MbElements for each bit-level field. Any IIB transformation method should then allow you to manipulate the data. The mapping node does so "without code".
| Vitor wrote: |
| mqjeff wrote: |
| I had thought there were industry packs that covered X12/EDI formats. |
I'm told the IIB packs don't provide the validation ("level 5"? "level 6"?) that the WTX ones do. |
Ok, that's a valid reason to use WTX/ITX.
| Vitor wrote: |
| mqjeff wrote: |
| Also, it's not clear from the work I've done that you ever need the entire X12/EDI message models deployed in any environment. Certain ones for certain industries, and certain transactions, but not the entire (enormous) set. |
This is entirely true. We do not have all the possible WTX models and maps deployed. |
Ok. It was also not part of your original point, so I concede that there's nothing more to really say here.
| Vitor wrote: |
| mqjeff wrote: |
Yes, I agree, there are people who struggle along with WTX/ITX instead of the glory of IIB.
I sympathize with their plight. |
Who doesn't? |
Presumable the ITX developers.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 01, 2016 8:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Vitor wrote: |
| mqjeff wrote: |
| DFDL fully supports bit level parsing and serializing. |
It does, but WTX does the manipulation without code. |
What does that mean? The DFDL parser should create separate MbElements for each bit-level field. Any IIB transformation method should then allow you to manipulate the data. The mapping node does so "without code". |
Ok, so in this context "without code" should have been "without further user intervention". Apparently you can work on the bits inside the WTX model.
I'm not a WTX guy so I'm basically repeating the use case justification the team here that uses WTX applied to buy WTX as well as the IIB we already had, because you're asking the same questions I did. These are the answers I got and they seemed to be good answers that others (including various IBM GS team members) verified.
Full disclosure - as they were prepared to pay for the WTX PVUs / Design Studios and I didn't have to, my due diligence and attempts to find alternative IIB-based solutions was a bit limited.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 01, 2016 8:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| Apparently you can work on the bits inside the WTX model. |
Huh. Wonder what that means... Turn a 0 into a "v" or something? If it's just a boolean, then
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| ms_mq |
| Posted: Mon Feb 01, 2016 11:08 am Post subject: |
|
|
Acolyte
Joined: 23 Feb 2007
Posts: 69
|
Hi ,
We were waiting for WTX(ITX) V9 as WTX V8.4 did not support IIB 10 . I have installed the ITX V9 Design Studio and Integration Server , but I do not get the WTX(ITX) node in IIB V10 toolkit . Is anyone facing this issue? I am not sure if I am missing anything . Please let me know.
Thanks |
|
| Back to top |
|
|
| Simbu |
| Posted: Mon Feb 01, 2016 6:37 pm Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
| ms_mq wrote: |
Hi ,
We were waiting for WTX(ITX) V9 as WTX V8.4 did not support IIB 10 . I have installed the ITX V9 Design Studio and Integration Server , but I do not get the WTX(ITX) node in IIB V10 toolkit . Is anyone facing this issue? I am not sure if I am missing anything . Please let me know.
Thanks |
Hi, which fixpack of v10 are you using.
Release note says
| Quote: |
Design Studio integration with IBM Integration Bus Toolkit
In V9.0.0, Transformation Extender Design Studio integrates with IBM Integration Bus Toolkit without the need install IBM Transformation Extender for Integration Servers run time on the design-time computer. IBM Integration Bus V10.0.0.2 is the minimum required version. |
|
|
| Back to top |
|
|
|
|
