| Author |
Message
|
| cicsprog |
 Posted: Mon Jan 28, 2002 1:01 pm Post subject: |
 |
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
Does anyone know of a facility, software package, EXIT in TCPIP, MQSeries Client CHANNEL, etc. that accomplishes the following:
We have 10,000 MQSeries NT clients spread across our network connecting to five OS/390 MQSeries Queue Managers running the same application. We would like to spread the MQSeries NT Client workload evenly between the five MQSeries Queue Manager and have only ONE MQSeries Client distribution sent to these desktops. MQSeries Client Tables do not seem to satisfy this requirement.
Anyone have a solution? |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Mon Jan 28, 2002 1:19 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
I'm sure there must be a more elegant way, but what if in the client code right before the connect you had a little routine that randomly generated a number between 1 and 5 to decide which QM to connect to?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| cicsprog |
| Posted: Wed Jan 30, 2002 10:45 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
Thru other sources...appears DNS is the way to go for a solution. MQM's setup with different IP's and same PORTID can be round-robin thru by clients. MVS Workload Manager also enables some smarts to be built in for IP connection process. Lastly, appears that Cisco Local Director (LD) and Cisco Distributed Director can also be used.
"May your msgs be short" |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Jan 31, 2002 2:32 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You can use IP load balancing through a DNS server but is very basic and continues to send requests to a failed server, although in the case of OS/390 this may not be very likely.
Load balancing servers like IBM's Network Dispatcher can have custom code running so that you can detect problems with queue managers and not direct requests to them if they are overloaded for example.
For simple workload spreading, I like the random selection from a list of Queue managers read by the client application from a ini file. That way if one QM fails, the program can be designed to re-connect around the failure. |
|
| Back to top |
|
|
| ryddan |
| Posted: Fri Feb 22, 2002 5:49 am Post subject: |
|
|
Newbie
Joined: 10 Sep 2001
Posts: 9
Location: Sweden
|
Shared Q:s on OS/390 and dynamic IP should do what your are asking. You don´t need Dynamic IP if your QMGR:s is in same MVS I think. Shared Q:s can only be non persistence.
|
|
| Back to top |
|
|
|
|
