| Author |
Message
|
| scarified |
 Posted: Wed Jun 06, 2012 10:40 am Post subject: |
 |
|
Newbie
Joined: 01 Jun 2006
Posts: 8
|
Here's one way to do it - the 'Dos prompt' way (which some people like).
1. Export your maps from mms to xml using mexport.exe
2. Export your type trees from mtt to mts using texport.exe
3. You now have plain text maps and trees and you're free to use any source/text tools on them. You can check these text files into source control.
4. When you need to work on the maps/trees in Design Studio, you can check them out and covert them to mms and mtts with timport.exe and mimport.exe.
You can do all of the above using Design Studio with point and click. The steps are generally the same though - export, compare, check in, check out, import.
I encourage you to take a look at WTX 8.4's new thread safety features. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Jun 06, 2012 10:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| scarified wrote: |
| 4. When you need to work on the maps/trees in Design Studio, you can check them out and covert them to mms and mtts with timport.exe and mimport.exe. |
So what's being approved is not the exact resource that is being deployed, it is merely a representation. |
|
| Back to top |
|
|
| scarified |
| Posted: Wed Jun 06, 2012 10:47 am Post subject: |
|
|
Newbie
Joined: 01 Jun 2006
Posts: 8
|
The WTX mms and mtts are never deployed either. They are source representations of what is actually deployed - compiled maps.
This is no different to C or Java or many other technologies. In the development environment you work with text and then at runtime you deploy a binary representation. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jun 06, 2012 10:52 am Post subject: Re: WTX is thriving |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| scarified wrote: |
| lancelotlinc wrote: |
| 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. |
The maps are platform specific, but there is only one tool used to build all of them - "mcompile" - and it is shipped with Design Studio as a command line application - ideally suited for automation. |
Precisely what I said.
http://www.ibm.com/developerworks/websphere/library/techarticles/0907_gupta/0907_gupta.html
| Quote: |
| Using a precompiled map with a WTX Map node: When Message Broker adds the message flow containing the WTX Map node to a BAR file, the map is not automatically compiled, and is not added to the BAR file. You must manually deploy the map to the location that you specified. |
This is a big pain in the arse. It requires manual intervention. I can't tell you how many hours and days were wasted because the wrong MAR was put in the AIX deployment. Some of our developers and sys admins are not that detail oriented. There should be one MAR for every platform and the WTX runtime should make whatever runtime adjustments needed to read and execute that one MAR on the runtime platform. This procedure is too error prone, too manual to be effective in a fully automated continuous integration and deployment environment.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jun 06, 2012 10:53 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| scarified wrote: |
Here's one way to do it - the 'Dos prompt' way (which some people like).
1. Export your maps from mms to xml using mexport.exe
2. Export your type trees from mtt to mts using texport.exe
3. You now have plain text maps and trees and you're free to use any source/text tools on them. You can check these text files into source control.
4. When you need to work on the maps/trees in Design Studio, you can check them out and covert them to mms and mtts with timport.exe and mimport.exe.
You can do all of the above using Design Studio with point and click. The steps are generally the same though - export, compare, check in, check out, import.
I encourage you to take a look at WTX 8.4's new thread safety features. |
I can see where developers may like the DOS prompt way. But supervisors don't. Supervisors like the ESQL files that can be reviewed in seconds.
8.4 makes good thread-safety improvements, but the damage is already done since most people already forced single WTX maps to an EG.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jun 06, 2012 10:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| scarified wrote: |
| This is no different to C or Java or many other technologies. In the development environment you work with text and then at runtime you deploy a binary representation. |
It is entirely different, for this reason. In C/Java/etc, the source representation is directly worked with and manipulated and saved in source control.
What you are saying is that for WTX, the source representation that is directly manipulated is a binary form.
You can then choose to save a text representation of this, with the advantage of allowing for text-based comparison tools and the disadvantage of additional work every time a developer needs to make a change both at check out and at check in. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jun 06, 2012 10:57 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| mqjeff wrote: |
| scarified wrote: |
| This is no different to C or Java or many other technologies. In the development environment you work with text and then at runtime you deploy a binary representation. |
It is entirely different, for this reason. In C/Java/etc, the source representation is directly worked with and manipulated and saved in source control.
What you are saying is that for WTX, the source representation that is directly manipulated is a binary form.
You can then choose to save a text representation of this, with the advantage of allowing for text-based comparison tools and the disadvantage of additional work every time a developer needs to make a change both at check out and at check in. |
Exactly. And if the developer forgets to update these, the supervisor approval is not based on the reality.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jun 06, 2012 11:14 am Post subject: Re: WTX is thriving |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| scarified wrote: |
| lancelotlinc wrote: |
| 7. WTX does not interface well with Java tooling or adapters. |
The tooling for WTX, Design Studio, is actually written in Java and it runs on Eclipse. It installs on top of Message Broker Toolkit, IBM Integration Developer and Rational Application Developer. Some of WTX's own adapters are written in Java (look for m4***.jar in your WTX installation directory - that's them) and have been since version 6. Some WebSphere adapters are shipped out of the box with WTX (FTP, Email, IMS), and WTX provides a public Java API which allows you to create your own adapters - in Java. |
"WTX does not interface well with Java tooling..." Ant. We use Ant to do continuous integration through ClearCase, ClearQuest, BuildForge. We build all bars every hour and deploy these bars to DEV every hour. I should say, we build all non-WTX bars every hour. Because, you see, WTX builds cannot be fully automated and must be manually attended to.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| scarified |
| Posted: Wed Jun 06, 2012 11:23 am Post subject: |
|
|
Newbie
Joined: 01 Jun 2006
Posts: 8
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jun 06, 2012 11:34 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
WTX flows have not been able to be Ant-built consistently and the source code has to be manually approved. As I said above, if you can solve the lack of ClearQuest integration with the WTX product, we could make great strides in reversing the poor view of WTX flows.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| scarified |
| Posted: Wed Jun 06, 2012 11:41 am Post subject: |
|
|
Newbie
Joined: 01 Jun 2006
Posts: 8
|
If you don't like exporting maps and trees to text, you can use Design Studio (which interfaces with any Eclipse compatible source control system) to visually compare maps and trees.
Select two maps (or two trees) in the "Extender Navigator" view, right click and select "Compare With". You'll get highlighted difference view of the two maps/trees which will let you find and inspect the differences (which will show up in red text). |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jun 06, 2012 11:44 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jun 06, 2012 11:55 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
To give some clarity as to what the supervisors are looking at when they approve/disapprove source code, we have a Point-Of-Sale system for insurance. That means we collect and process PCI data as well as ePHI data. What is sensitive is, what information we store in Environment/LocalEnvironment, what information we write to logs, what bar overrides are pointing our SOAPRequest nodes to, etc. etc. They also look to see if we follow coding standards, and whether or not we are writing efficient code, what items are placed in what transaction boundaries, and if the transaction status is accurately reflected in JMX at certain points through the transaction lifecycle.
When code gets rejected in ClearQuest, the ClearQuest server sends an email with an explanation of what needs to change. Developer changes code, checks it in to ClearCase, and resets the BaseCM activity to Ready For Review.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
