| Author |
Message
|
| deepak_paul |
 Posted: Wed Dec 21, 2011 10:39 pm Post subject: WTX plugin node not showing up |
 |
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
All,
We are trying to automate the broker build process for a WTX based broker project. We have installed WMB toolkit on Linux where we have Hudson installed as well. This hudson based build process through ant scripts works well that it is able to create bar file without issues. But if we want to build a bar file fro the WTX project, it is failing to recognize the WTX plugin nodes and so failing to create BAR file. later we found, and installed WTX Integration Server also on Linux server. But still we are not able to see the WTX plugin node recognized in the message flow when we open the broker toolkit on linux. I blelieve, there is no installable of WTX design studio for Linux.
Versions we use:
1. WMB toolkit 7.0.0.3 on Linux
2. WTX Integration Server 8.3.0.4 on Linux
Please help me how we can get these WTX plugin nodes to show up.
_________________
Regards
Paul |
|
| Back to top |
|
 |
| deepak_paul |
| Posted: Thu Dec 22, 2011 7:12 am Post subject: |
|
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
The question in short is that how to make WTX plugin nodes show up on Broker tool kit on Linux?
Does anybody have any message flows which have WTX nodes to build through Hudson?
Any suggestions? Thanks.
_________________
Regards
Paul |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Dec 22, 2011 8:42 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Runtime is supported on Linux, not Design Studio. You can work around this issue by manually building a WTX bar file for inclusion in your standard projects.
As previously discussed here, WTX is a legacy product and you should migrate to a recent version of WMB in its place.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| deepak_paul |
| Posted: Fri Dec 23, 2011 6:51 am Post subject: |
|
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
| lancelotlinc wrote: |
| Runtime is supported on Linux, not Design Studio. You can work around this issue by manually building a WTX bar file for inclusion in your standard projects. |
This is how we are building the bar files as of now. Still wondering how we can make Hudson based Broker build work for projects which have WTX plugin nodes.
| lancelotlinc wrote: |
| As previously discussed here, WTX is a legacy product and you should migrate to a recent version of WMB in its place. |
I am already using the latest pack in V7 WMB 7.0.0.3. (Broker V8 just came so we leave it for now)
_________________
Regards
Paul |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Dec 23, 2011 7:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You seem to have outlined the situation very clearly.
You have set up your build system to run on Linux.
You need to use your build system to compile resources using WTX Design Studio.
WTX Design Studio is not supported on Linux.
This is 2+2 <> 5.
If your build system requirements allow you to run an unsupported configuration, you can attempt to understand the aspects of the WTX Design Studio that connect to the Toolkit (and thus are used by mqsicreatebar) and then copy or move the relevant resources from a Windows install to your Linux build system.
Or if your requirement to use linux for your build system is less binding that your requirement to build WTX resources, you can reconstruct your build system on Windows where WTX is supported.
Either way, you should REWRITE your flows TO NOT USE WTX. |
|
| Back to top |
|
|
| deepak_paul |
| Posted: Mon Dec 26, 2011 5:45 pm Post subject: |
|
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
| mqjeff wrote: |
If your build system requirements allow you to run an unsupported configuration, you can attempt to understand the aspects of the WTX Design Studio that connect to the Toolkit (and thus are used by mqsicreatebar) and then copy or move the relevant resources from a Windows install to your Linux build system.
Or if your requirement to use linux for your build system is less binding that your requirement to build WTX resources, you can reconstruct your build system on Windows where WTX is supported.
Either way, you should REWRITE your flows TO NOT USE WTX. |
Why? Just because i can not make my build system work, should i have to change my system architecture to use only WMB in place of WTX or somehow not use WTX at all. Rather i would still see how i can resolve this without changing the system design? At worse, i can go with manual build system wherever i see there is a piece of WTX.
_________________
Regards
Paul |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Dec 27, 2011 6:20 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Very eloquently put:
| mqjeff wrote: |
| Either way, you should REWRITE your flows TO NOT USE WTX. |
If you already have WMB 7, then migrate your WTX flows to WMB 7.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Dec 27, 2011 7:34 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| deepak_paul wrote: |
| mqjeff wrote: |
If your build system requirements allow you to run an unsupported configuration, you can attempt to understand the aspects of the WTX Design Studio that connect to the Toolkit (and thus are used by mqsicreatebar) and then copy or move the relevant resources from a Windows install to your Linux build system.
Or if your requirement to use linux for your build system is less binding that your requirement to build WTX resources, you can reconstruct your build system on Windows where WTX is supported.
Either way, you should REWRITE your flows TO NOT USE WTX. |
Why? Just because i can not make my build system work, should i have to change my system architecture to use only WMB in place of WTX or somehow not use WTX at all. |
This is two separate points.
one - your build system architecture choices are incompatible with the code you are trying to build it with.
Two - In my strong opinion, you should stop using WTX at all. |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Mon Jan 02, 2012 2:08 am Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
I am very keen to know why WTX is being 'discouraged'. Is it being implied that the WMB (especially v8 ) message flows can do a better job than a WTX map ?
I am not a WTX person but we do have some WTX maps dealing with business logic. The extraction of messages from disparate sources are responsibility of WMB and processing them as per business requirements is the responsibility of WTX maps. The map is invoked as a node in the message flow. Although, I think, in our case, we might be better off by hiving of WTX maps into a WTX Event Server environment.
Slight edit to avoid making 8 appearing as an emoticon.
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Jan 02, 2012 10:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Cogito-Ergo-Sum wrote: |
| Is it being implied that the WMB (especially v8 ) message flows can do a better job than a WTX map ? |
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Mon Jan 02, 2012 6:31 pm Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
After my earlier post, I did search this forum for WTX. On multiple occasions there were tips/guidelines/instructions to migrate WTX maps to WMB message flows. The message flows would be having either the new, shiny Mapping node or ESQL files that do the business logic which was formerly being done in WTX maps.
I also peeked into DFDL; it does sound interesting. With the mapping node, perhaps, we can think of WMB based business logic code than regular COBOL code.
All this sounds like "crowd sourced" knowledge than an instruction from the product manufacturer. And this would put me on defensive if I had to bring this migration up with management. (We are a 'recent' WTX+WMB shop.)
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jan 03, 2012 2:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
What business requirement did you have that justified spending extra money for WTX?
What specific technical requirement was not achievable using plain Broker? |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Jan 03, 2012 2:24 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| mqjeff wrote: |
What business requirement did you have that justified spending extra money for WTX?
What specific technical requirement was not achievable using plain Broker? |
IBM Salesman needing to meet his budget for Q4 perhaps?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| Cogito-Ergo-Sum |
| Posted: Tue Jan 03, 2012 3:26 am Post subject: |
|
|
Master
Joined: 07 Feb 2006
Posts: 293
Location: Bengaluru, India
|
| mqjeff wrote: |
What business requirement did you have that justified spending extra money for WTX?
What specific technical requirement was not achievable using plain Broker? |
Alas...the decision to include WTX was taken much before me ....
_________________
ALL opinions are welcome.
-----------------------------
Debugging tip:When you have eliminated all which is impossible, then whatever remains, however improbable, must be the truth.
---Sherlock Holmes |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 03, 2012 5:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Cogito-Ergo-Sum wrote: |
| Alas...the decision to include WTX was taken much before me .... |
Then why would you be on the defensive bringing this up with management? If you were not part of the WTX decision, it's the responsibility of those who made that decision to jutify it in terms of the business / technical requirement WMB doesn't meet that WTX does.
Whatever that is.
I'm also inclined to a salesman possibly not padding his sales figures (I'm being more charitable in 2012) but having a less than total grasp of WMB's capabilities & recommending WTX to fill any percieved gaps. Possibly if the sales team was more familiar with earlier versions of WMB than the newer ones with the increased functionality.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
