| Author |
Message
|
| tone |
 Posted: Tue Nov 19, 2002 7:07 am Post subject: Using Clients v Servers |
 |
|
Newbie
Joined: 17 Mar 2002
Posts: 5
|
Hi,
We currently have MQ for OS/390 version 1.2 and we wish to allow messaging to and from 2 websphere boxes running MQ for NT version 5.3 using JMS. These websphere boxes run the same applications and are designed to allow load balancing and continuation of service.
We are trying to workout if and how to use MQ clients on the Websphere boxes. Currently the configurations we are thinking of are:
1. A new MQ Server which has a channel to the OS/390 queue manager. The websphere boxes connect to the MQ Server using clients.
2. The Websphere boxes connect directly to the OS/390 queue manager using clients.
3. Run a Queue manager on each websphere Box and connect each to the OS/390 queue manager.
Currently our planned option is 1.
Can anyone advise us if this is a valid approach and/or potential pitfalls?
We spoke to candle briefly about this 9 months ago an they advised against using MQ clients. Unfortunately our minds can't remember the exact reason.
thanks
tony |
|
| Back to top |
|
 |
| glennire |
| Posted: Wed Nov 20, 2002 1:03 am Post subject: |
|
|
Newbie
Joined: 18 Nov 2002
Posts: 7
Location: USA
|
If option one with a separate MQ Server means this machine would run Websphere MQ Integrator then I might understand adding the machine, but would still use server connections from the webshpere boxes. The routing issues to/from the two websphere boxes and 390 are not necessarily evident with the information provided. If this scenario is only using WebsphereMQ, option three seems to be the most direct, but may not meet load balancing and continuation of service requirements.
The advice against using client connections is generally that under some scenarios messaging is not fully assured as it is when binding to the server.
_________________
Glenn Addison
423-956-5561
glennire@gmail.com |
|
| Back to top |
|
|
| Remco |
| Posted: Wed Nov 20, 2002 4:54 am Post subject: |
|
|
Acolyte
Joined: 19 Mar 2002
Posts: 68
Location: Capelle aan den IJssel (Rotterdam)
|
| Why not connecting Clients directly to the MQ Server running on OS/390. I can't think of a better and cheaper sollution. Could anyone please explain to me why not to go for that sollution, because I'm using it without any problems. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Nov 20, 2002 8:40 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Client apps cannot participate in 2 phase commits, so if you need that, you must MQServers local to the apps.
With MQClients, you are relying on a network connection being there before your app can do any MQ work. If MQServers are installed locally, the apps can put their request messages even if the connection to the mainframe is temporaily not there. Of course if you are in a synchronous model, where you are waiting for an immediate reply, this is a moot point.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Remco |
| Posted: Thu Nov 21, 2002 1:26 am Post subject: |
|
|
Acolyte
Joined: 19 Mar 2002
Posts: 68
Location: Capelle aan den IJssel (Rotterdam)
|
Thanks for your reaction Peter,
but my comment was ment for a situation where clients are used. I don't see the need to have a client connect to a server on W2K and then from W2K to the mainframe. In my opinion this is just a wast of money. Ain't I correct. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Thu Nov 21, 2002 5:33 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
If the situation is one client needing to get messages to the mainframe then it is a waste. If you spent the money to buy the NT server and your app can run on that server, it should. If you are going to run the app as an MQ client regardless, than you might as well connect directly to the OS/390.
Now if you 100s of these apps in a remote office, then you wouldn't spend money to give them all MQServers. And you might not want your OS/390 queue manager to have to deal with hundreds of client connections. In that case you can buy a MQServer that acts as a "Client Concentrator". All the clients connect to the concentrator, which then forwards the messages to the mainframe. You have now sheilded the mainframe.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
