| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Portable Design |
« View previous topic :: View next topic » |
| Author |
Message
|
| pauillac |
 Posted: Thu Aug 16, 2001 6:13 am Post subject: |
 |
|
Novice
Joined: 13 Jul 2001
Posts: 21
|
In MQMD, there are fields for storing application specific data and message id. For portability reasons, should we put these fields in the message body so that someday we may migrate to another product with less pain if there is a need?
Are there any disadvantages of doing so? |
|
| Back to top |
|
 |
| bduncan |
| Posted: Thu Aug 16, 2001 10:57 am Post subject: |
|
|
Padawan
Joined: 11 Apr 2001
Posts: 1554
Location: Silicon Valley
|
If you really want to go for portability you should code your applications to use JMS (Java Messaging Service) This will sit on top of MQSeries and if you someday decide to junk MQ in exchange for MSMQ, Tuxedo, etc., you don't have to change any of your application code. But trust me, if you simply put your application related information in the data of the message with the hope that such a move will make the system portable, I might be in for a suprise. Unless you have coded your own API on top of the MQI or AMI interfaces to provide a layer of abstraction for your applications, it is unlikely that you'll even be able to port them to the new messaging system without pratically rewriting the communications part of the code from scratch. If that's the case, then it helps little if your messages contain all the necessary application information.
_________________
Brandon Duncan
IBM Certified MQSeries Specialist
MQSeries.net forum moderator |
|
| 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
|
|
|
|
