| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Develop with MQ client only or running Queue Manager locally |
« View previous topic :: View next topic » |
| Author |
Message
|
| Shep |
 Posted: Mon Sep 23, 2002 1:19 pm Post subject: Develop with MQ client only or running Queue Manager locally |
 |
|
Newbie
Joined: 21 Jun 2002
Posts: 6
Location: Massachusetts
|
Should a Win2K development machine have the MQSeries client installed and connect remotely to a Queue Manager - or - have both the MQSeries Client and Queue Manager installed locally?
We are writing a VB.Net application that will run as a Windows Service. It will most likely run in production on the same machine as it's Queue Manager (MQSeries for Windows).
Thanks in advance! |
|
| Back to top |
|
 |
| bigdavem |
| Posted: Tue Sep 24, 2002 10:25 pm Post subject: |
|
|
Acolyte
Joined: 16 Sep 2001
Posts: 69
Location: Sydney, Australia
|
| I'm all for having your development machine mimic your production machine, although I understand there are costs involved wrt MQServer licensing. |
|
| Back to top |
|
|
| Shep |
| Posted: Wed Oct 02, 2002 6:20 am Post subject: Develop with MQ client only or running Queue Manager locally |
|
|
Newbie
Joined: 21 Jun 2002
Posts: 6
Location: Massachusetts
|
I also favor having the development machines configured exactly like production will be but it is a cost, as well as a maintenance issue. Not only will we have to license a QM for each dev machine, but then we need to make sure each one is configured the same all the time.
I guess what I'm wondering is if there are any issues or "gotchas" we need to watch out for if we develop using the client on several machines connecting remotely to a common Queue Manager?? Thx in advance!
Shep |
|
| Back to top |
|
|
| Wjbyczek |
| Posted: Fri Nov 22, 2002 7:17 am Post subject: |
|
|
Newbie
Joined: 08 May 2002
Posts: 4
Location: Domain Systemix
|
| if I understand the environment you're describing, development for running applications on a machine that hosts the QM will probably be easiest if you utilize a machine that runs a local QM instance. Obviously, licensing plays into this, but it seems reasonable to do the actual coding, compiling and linking on a client (making sure you link to MQM and not the client libraries) and porting the code to a single test machine that's configured like the production environment would be. |
|
| 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
|
|
|
|
