|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Requested: Network Install option for MQ Client for Windows |
« View previous topic :: View next topic » |
Author |
Message
|
salem.muribi |
Posted: Wed Oct 13, 2010 12:29 pm Post subject: Requested: Network Install option for MQ Client for Windows |
|
|
Novice
Joined: 05 Sep 2008 Posts: 14 Location: Chicago
|
Guys i've submitted request for enhancement R5255.
"Network Install option for Websphere MQ Client for Windows"
The current client installation requires several registry keys which i can't imagine add any value to the product. While making this work, isn't impossible, it is not supported by IBM at this time. I'm personally stunned that in 2010 IBM hasn't yet produced a Windows client that can't be installed on a network file system.
The email for this is mqreq@uk.ibm.com and i would imagine if enough people expressed interest, we could get something done. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Oct 14, 2010 4:29 am Post subject: Re: Requested: Network Install option for MQ Client for Wind |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
salem.muribi wrote: |
I'm personally stunned that in 2010 IBM hasn't yet produced a Windows client that can't be installed on a network file system. |
Here's a question which lacks my usual sarcasm:
How many other equivalent pieces of software can be installed on a network file system? I'm thinking of database clients and so forth. I've not encountered any and look to broaden my horizons.
The obvious follow up questions to this are how many people install such clients on network file systems and what was the requirement that drove it? Indeed, why is the OP trying this?
This is no way diminishes the enhancement request; anything which keeps me out of the Windows registry can only be a good thing. I'm just trying to get a feel for the usage here. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Thu Oct 14, 2010 4:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
Presumably the intent is to be able to install the client software once, and then any machine that needs an mq client can merely create a mount point and be good to go - in fact, an application could initiate the mount point itself as part of it's startup.
But in general, I personally view it as a bit of a six of one, half pint of the other problem. Any systems management tool that can create a network mount can presumably also then run a script afterwards - such that an MQ client installer can be run if needed. So if you have the facility to reach out to a large number of user desktops and create a network mount, you probably also have the facility to reach out to a large number of user desktops and run an MQ client install from a package on a network mount.
And ,as always, if you want to see the product do something that it doesn't, file a requirement. |
|
Back to top |
|
 |
salem.muribi |
Posted: Thu Oct 14, 2010 6:26 am Post subject: |
|
|
Novice
Joined: 05 Sep 2008 Posts: 14 Location: Chicago
|
We have 160 other packages for windows that are accessed from our network drive including Tibco RV, JDK's, ODBC drivers, etc. A similar number on a shared Linux filesystem as well. I agree that some of the database clients are effectively "node locked" on Windows but their linux equivalents are not. Sybase is a good example here.
As far as the silent installs go, yes this is doable but in my opinion the network install makes upgrades easier and more flexible. We have dozens of teams working on different timelines and if they can just choose what version to link against i don't have to worry about what windows hosts get which version. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Oct 14, 2010 7:16 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
salem.muribi wrote: |
We have dozens of teams working on different timelines and if they can just choose what version to link against i don't have to worry about what windows hosts get which version. |
You might have to worry if some <insert adjective here> decides to link against the WMQv7 client so they can use to new features, then runs against a WMQv6 queue manager.
But I take your general point. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
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
|
|
|
|