| Author |
Message
|
| JLRowe |
 Posted: Wed Mar 23, 2005 3:27 am Post subject: |
 |
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
| As the official product from IBM, JText integrates with MRM. It's main problem is that in it's basic configuration (without a custom data handler) the file format handling is not very flexible and you have to code your applications to the adaptor - rather than the other way round. |
|
| Back to top |
|
 |
| javaforvivek |
| Posted: Wed Mar 23, 2005 3:32 am Post subject: |
|
|
Master
Joined: 14 Jun 2002
Posts: 282
Location: Pune,India
|
So do you mean that if we use Jtext, there is an extraordinary effort to customise the message?
For e.g., what to do if, while converting a file into an MQ Message using JText, we want to add some RFH2 header info or something to MQMD (like Reply-to-Queue name), etc.?
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth. |
|
| Back to top |
|
|
| JLRowe |
| Posted: Wed Mar 23, 2005 2:45 pm Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
There are 2 issues.
Firstly, the flat file that JText sends or receives must have the business object name and verb present in each "record" in the flat file. Otherwise, the adaptor cannot determine what format the message should be. To remove the need for this field or any of the limitations of the built in data handler (formatting is much more extensive in MRM), you need to write a datahandler and a namehandler class.
The message that the adaptor talks to your broker with is fixed and is exported into MRM through the WBI toolkit. Your broker of course then, generates the MQ message you need (with RFH headers etc).
It is quite involved to develop, but the experience will definitely help if you ever need to use any of the other adaptors. |
|
| Back to top |
|
|
| solomita |
| Posted: Fri May 27, 2005 7:25 am Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
I saw the support pack to allow a file to be FTPd to the broker but what about NDM?
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri May 27, 2005 7:30 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| solomita wrote: |
| I saw the support pack to allow a file to be FTPd to the broker but what about NDM? |
What is NDM?
Also, look in the MQSeries News/Updates forum.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JT |
| Posted: Mon May 30, 2005 7:39 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
If I'm not mistaken, I believe it stands for Network Data Manager, also known as Network Data Mover. Back in the day it was, and probably still is, a common mainframe file transmission protocol software. |
|
| Back to top |
|
|
| Ian |
| Posted: Tue May 31, 2005 2:13 am Post subject: |
|
|
Disciple
Joined: 22 Nov 2002
Posts: 152
Location: London, UK
|
|
| Back to top |
|
|
| ydsk |
| Posted: Tue May 31, 2005 6:39 am Post subject: |
|
|
Chevalier
Joined: 23 May 2005
Posts: 410
|
I too used the CommerceQuest product earlier and it's good. It has utilities "File2Q" and "Q2File" that take care of all the conversion between all kinds of files ( flat files, datasets, PDS, xml, etc on many platforms) and MQ queues.
Thanks. |
|
| Back to top |
|
|
|
|
