| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Reference Message vs. Segments Message |
« View previous topic :: View next topic » |
| Author |
Message
|
| cots |
 Posted: Wed Jun 02, 2004 4:10 pm Post subject: Reference Message vs. Segments Message |
 |
|
Centurion
Joined: 16 Jun 2003
Posts: 105
|
Hi all,
I realized there are two options to handle huge messages across queue managers, one is by using reference message and the other is by using QM/application segments message. But I am not quite sure what are the advantage and disadvantage to the two, can someone pls explain if you know.
Thanks in advance
cots |
|
| Back to top |
|
 |
| EddieA |
| Posted: Wed Jun 02, 2004 7:55 pm Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Actually, you have mentioned 3 options. Reference messages, Queue Manager Segmentation, and Application Segmentation.
Reference Messages require an exit to be written/installed at the sending and receiving ends.
Queue Manager Segmentation requires a change to the sending and receiving applications to add an extra option to the PMO and GMO. However, both applications must be able to allocate a buffer large enough for the entire message.
Application Segmentation means changes to the sending/receiving applications to perform the segmentation/rebuilding of the message.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| cots |
| Posted: Thu Jun 03, 2004 7:10 am Post subject: |
|
|
Centurion
Joined: 16 Jun 2003
Posts: 105
|
Eddie,
Thanks for the response, I have futhure questions on reference message and application segmentation message.
As you mentioned. reference message requires an exit. However, MCA also has limitation, that means sending exit has to slice the message in chunks where each message can only send up to the MCA MaxMsglength then resemble all the message on receiving exit, right? if this is right, then what is the advantage of using reference message vs. application segmentation message. they both require the slice message at sending end and reasemble at receiving end. again, thanks for your response.
COTS |
|
| Back to top |
|
|
| mqonnet |
| Posted: Thu Jun 03, 2004 7:38 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
From app prog guide.
"The Reference Message samples allow a large object to be transferred from one node to another (usually on different systems) without the need for the object to be stored on WebSphere MQ queues at either the source or the destination nodes. "
" then what is the advantage of using reference message vs. application segmentation message. they both require the slice message at sending end and reasemble at receiving end. again, thanks for your response.
"
---You should not really compare the two as application segmentation has the overhead on the application developer and eventually the app. As opposed to the Queue manager/MCA in reference messages/qm segmentation respectively.
I am not sure what you are trying to gather here, but bottom line is, you may not achieve any network performance selecting one over the other. The only advantage in selecting one over the other is, if you select either qm segmentation or use referenc messages, the overhead is not with the application. Hence you dont really need to handle this(segmentation) in your code.
Hope this helps.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| 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
|
|
|
|
