|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Licensing |
« View previous topic :: View next topic » |
Author |
Message
|
wilso132 |
Posted: Mon Jul 26, 2010 5:28 am Post subject: Licensing |
|
|
Newbie
Joined: 12 May 2010 Posts: 8
|
I have a project where I would like to use a couple of the DLL's included in a Websphere full client install (amqmdnet.dll and amqmdnm.dll) *without* having to do the full client install. Does anyone know if just using these DLL's for my implementation breaks any license on IBM and if I'm required to install the client for every place this application will be deployed? |
|
Back to top |
|
 |
zpat |
Posted: Mon Jul 26, 2010 5:43 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
I wouldn't recommend this. Use a silent scripted install if you want to automate it.
Apart from anything else, this sort of thing is a support nightmare as it is impossible to list the installed software and its fixpack level.
Client installs should be kept up to date, these sort of orphaned files get forgotten about.
I have seen similar problems in Java where MQ version 2 (!) jar files have been uncovered. |
|
Back to top |
|
 |
mqjeff |
Posted: Mon Jul 26, 2010 5:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
But.
The Dot Net API provides a Managed Connection to allow you to package your application this way. This does avoid the need for a full client install, as it is not bound to the C client libraries.
But it does nothing to prevent you from building and shipping your application against one version of MQ and then trying to use that against a newer or older version, and getting stung.
Also The client is subject to different license criteria. Generally client installs are free, except for Extended Transactional Clients. But you're also not licensed to distribute them outside your enterprise, either - to customers or etc.
However, your only authoritative source for license information is your IBM Sales rep. |
|
Back to top |
|
 |
bruce2359 |
Posted: Mon Jul 26, 2010 8:08 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9470 Location: US: west coast, almost. Otherwise, enroute.
|
"...just using these DLL's for my implementation..."
While technically possible, this is not a best-practice. First and foremost, it's unsupported. Second, you will inevitably encounter compatibility/coexistence issues with newer versions/releases/upgrades of wmq server software.
"...breaks any license on IBM..."
Re-(read) your license agreement. I'm guessing that this would fall outside the license.
"...and if I'm required to install the client for every place this application will be deployed?"
Installing the client on platforms where the client will execute is a best-practice. _________________ I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
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
|
|
|
|