| Author |
Message
|
| Cubersome |
 Posted: Wed Mar 07, 2012 10:46 am Post subject: Need Help with WMB-WTX issue |
 |
|
Apprentice
Joined: 02 Mar 2012
Posts: 37
|
Hi,
I wrote a simple map which converts XML message to COBOL copybook format and then I used that map in MB. In my message flow I used MQInput node,Compute node and WTX node and MQOutput node. I am putting the XML message in the input node it is getting passed to the WTX map and I am getting an exception which is getting written to the trace node. But the thing is the map is executing perfectly fine in WTX. And also I am putting the trace option ON in map settings and the WTX trace is not getting written that file. Please help me why the map is failing and the trace is not getting written? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Wed Mar 07, 2012 10:51 am Post subject: Re: Need Help with WMB-WTX issue |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Cubersome wrote: |
| In my message flow I used MQInput node,Compute node and WTX node and MQOutput node. |
| Cubersome wrote: |
| I am getting an exception which is getting written to the trace node. |
What Trace node? It's not shown in the flow you posted.
| Cubersome wrote: |
| I am putting the trace option ON in map settings and the WTX trace is not getting written that file. |
What trace file?
| Cubersome wrote: |
| Please help me why the map is failing and the trace is not getting written? |
What does the broker trace show?
Why are you using WTX inside WMB rather than the native WMB features? What does the Compute node in your flow do?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Cubersome |
| Posted: Wed Mar 07, 2012 11:19 am Post subject: |
|
|
Apprentice
Joined: 02 Mar 2012
Posts: 37
|
| I forget to mention I routed the failure terminal of the WTX node to Trace node to capture the exception details. In the map settings option of the WTX node I switched the Trace ON and wants to write that WTX run time exception details into that file. But the file is not getting written. Also Broker is not showing any traces as well. I used compute node because I am dynamically populating the map and server location. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 07, 2012 12:07 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Cubersome wrote: |
| But the file is not getting written. |
No it wouldn't. That's not how this works.
| Cubersome wrote: |
| Also Broker is not showing any traces as well. |
Did you enable the broker trace?
| Cubersome wrote: |
| I used compute node because I am dynamically populating the map and server location. |
Fine. I repeat, why are you using WTX not native WMB?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Ric-Tic |
| Posted: Wed Mar 07, 2012 12:57 pm Post subject: |
|
|
Apprentice
Joined: 18 Nov 2003
Posts: 38
Location: Zurich, Switzerland
|
| Cubersome wrote: |
| I forget to mention I routed the failure terminal of the WTX node to Trace node to capture the exception details. In the map settings option of the WTX node I switched the Trace ON and wants to write that WTX run time exception details into that file. But the file is not getting written. Also Broker is not showing any traces as well. I used compute node because I am dynamically populating the map and server location. |
The WTX trace gets written to the map location by default. Did you set it to Custom?
Are the map and server location being set correctly?
Does the compute node propagate the LocalEnvironment?
Is the map compiled for the correct runtime environment? |
|
| Back to top |
|
|
| Cubersome |
| Posted: Wed Mar 07, 2012 2:16 pm Post subject: |
|
|
Apprentice
Joined: 02 Mar 2012
Posts: 37
|
@Vitor,
We enabled the broker trace but nothing is written to it. We are using WTX in MB to check the performance between esql transform and WTX transformation.
@Ric-Tic,
I tried both ways. I coded the map in windows and trying to execute that in zlinux. I am setting the map and server location through compute node.
Yes I am propagating both the local environment and message. Yes I build the map for all enironments. The thing is..it is giving some wrong type execption which I couldn't figure out for which field it is giving that error. But the map is running fine in WTX. |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Mar 07, 2012 3:28 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| We are using WTX in MB to check the performance between esql transform and WTX transformation. |
The facts are:
- XML to COBOL is right in the sweet spot of WMB-and-MRM. I can almost guarantee that WMB + WTX will get nowhere near the same performance.
- There is almost no work at all to create a message set for COBOL. Just use the ( extremely well tested ) COBOL importer.
- I don't know what you mean by 'ESQL transform'. I really hope that you are not trying to construct the output message ESQL string manipulation functions - that would be really bad practice.
There are cases where WMB+WTX is the correct choice. Yours is not one of them, by the sound of it. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Mar 08, 2012 5:48 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Have you read this article?
http://www.mqseries.net/phpBB2/viewtopic.php?t=60423&sid=2159efc84129b7c5a0faa698461a7257
| Quote: |
1. WTX provides some customers with valuable assistance in transforming industry-compliant data payloads. WTX accomplishes this in a rigid, brittle way.
2. WTX is a legacy product and does not work well with modern architectures. It requires platform-specific deployment considerations and a special build process that is difficult to fully automate.
3. Some of the source used to build customer WTX functions is maintained in binary form and cannot be source-text compared to previous versions so that managers can approve or disapprove the software source code change (ie. ClearCase vdiff tool).
4. WTX architecture is not multi-threaded friendly. Many problems exist when customers have WTX maps execute in the same Execution Group. The only known workaround is to limit each EG to a single WTX map. This means that for every WTX map, the customer must create a new EG. As you can imagine, this can grow to be unmanageable.
5. WTX Design studio runs on 32-bit Windows only. Linux and 64-bit Windows OS results in WTX being unable to function.
6. Type tress have to be re-imported every time some minor change to the XML schema happens rather than re-synchronize the type tree to the existing map. This requires deleting the old definition, which can be cumbersome and time-consuming.
7. WTX does not interface well with Java tooling or adapters.
|
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 08, 2012 6:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Cubersome wrote: |
| We enabled the broker trace but nothing is written to it. |
If there's nothing in a broker user trace you're doing it wrong or your install is broken. If there's nothing about the WTX map but a lot of stuff about your flow then the WTX is a balck box component (never personally used one in WMB so I'll defer to others on that).
| Cubersome wrote: |
| We are using WTX in MB to check the performance between esql transform and WTX transformation. |
Properly written ESQL is faster, and a better choice within WMB irrespective of speed.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
