| Author |
Message
|
| analystLondon |
 Posted: Tue Apr 01, 2008 2:56 am Post subject: .NET and Websphere MQ V5.3 |
 |
|
Novice
Joined: 01 Apr 2008
Posts: 10
|
Hello Everyone,
I’ve recently started working on developing a .NET application to communicate with MQs. The forum has been very useful giving the starting point as I’m very new to all this.
I wanted to ask that does Version 5.3 contains all the drivers required to build a queue connection on a remote machine and post messages using .NET or do I need to upgrade to version 6 to implement that.
And If I can use version 5.3 can I just embed the required dlls into my application and use a Managed connection?
Any help is very much appreciated. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Apr 01, 2008 2:59 am Post subject: Re: .NET and Websphere MQ V5.3 |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| analystLondon wrote: |
| I wanted to ask that does Version 5.3 contains all the drivers required to build a queue connection on a remote machine and post messages using .NET or do I need to upgrade to version 6 to implement that. |
You'll need a client install, and you need to upgrade. Version 5.3 is out of support.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 01, 2008 4:07 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Right. You can't use v5.3 for this, at all.
Even if you have documentation that says you can.
Use v6.
Embed the dlls and use a managed connection only if you have an absolute requirement to minimize your product install footprint AND the capacity to rebuild and re-update and re-distribute your application every six months after applying MQ maintenance to those dlls.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| analystLondon |
| Posted: Tue Apr 01, 2008 5:06 am Post subject: |
|
|
Novice
Joined: 01 Apr 2008
Posts: 10
|
Thanks for the replies guys.
So, as I gather from your comments I do need V6. Will the whole thing work just by installing the standard edition of Client which can be downloaded free from ibm website? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 01, 2008 5:11 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| analystLondon wrote: |
| Will the whole thing work just by installing the standard edition of Client which can be downloaded free from ibm website? |
Yes. I fully agree with the comments of jefflowrey regarding managed connections.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 01, 2008 5:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Yes, one option for distributing your application is to have the end-user download and install the MQ client from IBM's website.
Of course, there must be a queue manager somewhere for that client to connect to.
Whether or not you use a managed connection, your app has a dependency on WebSphere MQ, and you need to manage that dependency the same way you'd manage a dependency on a database or any other kind of external resource. You need to code your app to be aware of PATH issues, and document how to overcome those for your end-users - if you don't bundle the dlls.
You can look at using XMS inside your application, instead of the plain MQ .NET API. This would allow you to manage your MQ dependency in the same way that a JMS system manages it. This may make your setup more complicated or more simple.
If you do use a managed connection, I said you should update the MQ dlls every six months... in an enterprise, this is a reasonable thing. If your app is being distributed a little more widely, or in a less managed way than we expect in an enterprise... then you should plan on updating the MQ dlls in your app every time you make a major release of your app.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 01, 2008 5:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
Of course, there must be a queue manager somewhere for that client to connect to.
|
Probably should have highlighted that! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| analystLondon |
| Posted: Tue Apr 01, 2008 5:23 am Post subject: |
|
|
Novice
Joined: 01 Apr 2008
Posts: 10
|
The application will be deployed on a single machine and it will send messages to Queue on a different machine.
I'm first trying to get this to work on my machine by installing the client and if all is good then I can deploy that on the other box.
After installing the MQ Client, correct me if I'm wrong here I need to add references to all the appropriate dlls in my project and also update those dlls periodically once its being deployed?
I think doing that every 6 months is no issue.
The standard edition does not provide Queue Manager, I guess this will not be an issue in my case as I'm connecting to Queue on a remote machine??
Thanks for the replies guys its very useful. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 01, 2008 5:25 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
If you're using a standard MQ client install, just apply the FixPack for MQ every six months. That will update the DLLs and etc.
Otherwise, the instructions in the Using .Net manual (that you must have already found, since you ask about managed connections) should cover how to set up your project to build your app to link against the client libraries.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 01, 2008 5:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| analystLondon wrote: |
| The standard edition does not provide Queue Manager, I guess this will not be an issue in my case as I'm connecting to Queue on a remote machine?? |
There are 2 distinct products - client & server. Client is a free download that does not provide queue manager functionality, server is a licensed purchase that does.
And no, if there's a licensed server install on the remote machine running a queue manager you're fine.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 01, 2008 5:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| analystLondon wrote: |
After installing the MQ Client, correct me if I'm wrong here I need to add references to all the appropriate dlls in my project and also update those dlls periodically once its being deployed?
|
If you're using a managed connection then the .Net manual will explain what needs to be done.
There are good, opperational & design reasons why you wouldn't want to do that, and use a standard client set up with your application. One of the benefits, but not the only one, is that it allows the client to be updated without changing your application.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| analystLondon |
| Posted: Tue Apr 01, 2008 5:29 am Post subject: |
|
|
Novice
Joined: 01 Apr 2008
Posts: 10
|
| And as I gonna install the MQ client, I can use ClientConnection instead of ManagedConnection? |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 01, 2008 5:32 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| analystLondon wrote: |
| And as I gonna install the MQ client, I can use ClientConnection instead of ManagedConnection? |
With the client installed on the machine running the app, you have access to all the various forms of client connection, as described in the Using .NET & Client manuals.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| analystLondon |
| Posted: Tue Apr 01, 2008 5:40 am Post subject: |
|
|
Novice
Joined: 01 Apr 2008
Posts: 10
|
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Apr 01, 2008 7:00 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
I am exactly refering to that.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
