| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Search found 5 matches |
| Author |
Message |
 Topic: Websphere MQ Client Message Overhead |
sameerg
Replies: 9
Views: 6092
|
 Forum: General IBM MQ Support Posted: Fri Feb 03, 2006 1:19 pm Subject: Websphere MQ Client Message Overhead |
Do you do MQGETs with Wait?
Yes that is correct, we use MQGMO_WAIT with WaitInterval, which is 5 seconds if the app runs in wireless mode Vs 1 sec if it's LAN.
I think you guys are leading me in ... |
| Topic: Websphere MQ Client Message Overhead |
sameerg
Replies: 9
Views: 6092
|
Forum: General IBM MQ Support Posted: Fri Feb 03, 2006 1:11 pm Subject: Websphere MQ Client Message Overhead |
| You could look into using compression exits at the send/receive exit points on the channel (and V6 of MQ has built-in compression available). Of course, it doesn't diminsh the number of sends across ... |
| Topic: Websphere MQ Client Message Overhead |
sameerg
Replies: 9
Views: 6092
|
Forum: General IBM MQ Support Posted: Fri Feb 03, 2006 10:58 am Subject: Websphere MQ Client Message Overhead |
| Whenever you issue an MQ call for a client, you send MQ specific data to and from the Queue Manager. So design your code logic to minimize connects, opens, closes, and disconnects. When you have to pu ... |
| Topic: Websphere MQ Client Message Overhead |
sameerg
Replies: 9
Views: 6092
|
Forum: General IBM MQ Support Posted: Fri Feb 03, 2006 8:15 am Subject: Websphere MQ Client Message Overhead |
| Have you looked at WebSphere MQ Everyplace? WMQ is fairly network intensive, and assumes the network is reliable. WMQe was designed to work over unreliable networks, with a much smaller message size. ... |
| Topic: Websphere MQ Client Message Overhead |
sameerg
Replies: 9
Views: 6092
|
Forum: General IBM MQ Support Posted: Thu Feb 02, 2006 2:03 pm Subject: Websphere MQ Client Message Overhead |
We have an application developed using VB 6.0 front end and Websphere MQ Client communicating with Websphere MQ Server. Over the LAN this architecture works just fine.
We have majority of the users ... |
|
|
|
