Author |
Message
|
tulip |
Posted: Mon Jul 28, 2008 8:49 am Post subject: MQ configuration |
|
|
Newbie
Joined: 26 May 2008 Posts: 7
|
I am Using MQ6.0.2.4 on Solaris10. We are connected to 70 customers with MQ to MQ(MQ channels), our message size up to 15MB and there is rquest resopnse time limit that is 5sec. How can I achieve this and is there anything from TCP/IP perspective? |
|
Back to top |
|
 |
sami.stormrage |
Posted: Mon Jul 28, 2008 11:15 am Post subject: |
|
|
 Disciple
Joined: 25 Jun 2008 Posts: 186 Location: Bangalore/Singapore
|
Depends on the platforms involved. _________________ *forgetting everything * |
|
Back to top |
|
 |
gbaddeley |
Posted: Mon Jul 28, 2008 7:55 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
Do the math on the message sizes, volume and response time requirement. Is the available end-to-end network bandwidth sufficient?
Have a look at channel compression in the Intercommunication manual. _________________ Glenn |
|
Back to top |
|
 |
AkankshA |
Posted: Mon Jul 28, 2008 8:30 pm Post subject: Re: MQ configuration |
|
|
 Grand Master
Joined: 12 Jan 2006 Posts: 1494 Location: Singapore
|
tulip wrote: |
I am Using MQ6.0.2.4 on Solaris10. We are connected to 70 customers with MQ to MQ(MQ channels), our message size up to 15MB and there is rquest resopnse time limit that is 5sec. How can I achieve this and is there anything from TCP/IP perspective? |
yes
How much time messages take to travle across..
How much time is the application takeing to generate the reply or is it MQ report ?
Demand vs supply of msgs.. ??
many many things to consider..
 _________________ Cheers |
|
Back to top |
|
 |
zpat |
Posted: Mon Jul 28, 2008 11:18 pm Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
Volume of messages is the important factor.
Are they non-persistent or not? Do they need to be?
Usually messages with response time goals are queries and so can be non-persistent (better for performance).
Make sure the message servicing application is set up properly (multi-threaded as appropriate). Use MQGET with WAIT, not a timer poll. |
|
Back to top |
|
 |
|