| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSeries Data Conversion Exit VS MQSI |
« View previous topic :: View next topic » |
| Author |
Message
|
| pauillac |
 Posted: Sat Jul 14, 2001 1:56 am Post subject: |
 |
|
Novice
Joined: 13 Jul 2001
Posts: 21
|
Can I use MQSeries Data Conversion Exit to do XML to COBOL/Assembly data structure mapping/conversion instead of using MQSI? How do these two approaches compare?
|
|
| Back to top |
|
 |
| kolban |
| Posted: Sat Jul 14, 2001 5:26 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
Interesting question. In principle, any MQSeries exit that allows manipulation of the data prior to delivery to the target queue could be used to transform the data based on its value. To craft your own instead of using MQSI has the following drawbacks:
o LOTS of coding and maintenance. You would have to utilize your own XML parser, break out the fields, perform data conversion etc etc and map those to contiguous storage mapping to a cobol data area.
o If you use exits, these are currently only available to distributed messages. If an app puts a message to a local queue, it doesn't pass through an exit. This means that message transformation would only be available for network transported messages.
The power and strength of MQSI is simplicity of use and raising the work effort out of code to a higher level. Where MQSeries concerns itself with data delivery, MQSI works on the data content. In principle, anything you could acheive with MQSI you could acheive by native coding but the effort involved is substantially higher. In addition, you have very little re-use or maintainability.
[ This Message was edited by: kolban on 2001-07-14 06:27 ] |
|
| Back to top |
|
|
| shilpadesai |
| Posted: Fri May 10, 2002 11:48 am Post subject: |
|
|
Novice
Joined: 09 May 2002
Posts: 12
|
I invistigated this issue for one of project I worked. We have to send the data between AIX machine to OS/390. On AIX side we are running Websphere, a J2EE application talking to Local QueueManger running on AIX, which in turn talk to Queue Manager running on OS/390. The J2EE application uses EAB + JMS to access the MQ Series queues. We have MQSI broker running on the same box as MqSeries. Under this circumstances we have two choices to do data transformation/conversion.
1. Use EAB where you can set Endian/Character set etc and then sent the COBOL record as bytes to MQSI. MQSI Flow knows that conversion is already done so will do other processing and will skip the conversion part.
2. Do not handle conversion at EAB and let MQSI FLOW handle the conversion.
I was convinced that 2 as best alternative for following reason.
1. Your are putting target host knowledge in MQSI Flows which are easy to maintain.
2. Using MRM format it will be easy for manipulate the message.
3. If properly done we can reuse many conversion nodes across the flows.
4. Also only one team (broker developers) will take care of conversion issues's and rest application team do not have to worry about it.
Hope this helps.
Regards,
Shilpa Desai
MQSeries/MQSI Prog/Analyst |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
