Author |
Message
|
lifeng |
Posted: Mon Jan 14, 2008 8:21 am Post subject: |
|
|
Apprentice
Joined: 11 Jan 2008 Posts: 46
|
Thanks jefflowrey!
I noticed that the doc you sent me says that it applies to V6. My first question to you is: can I follow the doc and do the same on V5.3? Our management's decision is to make the conversion working with the version of MQ we are using (v5.3) now as the prove of concept. Then we will make the move to migrate to V6.
Lifeng |
|
Back to top |
|
 |
jefflowrey |
Posted: Mon Jan 14, 2008 8:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
It's a waste of time to prove out on v5.3.
You need to examine very carefully the v5.3 version of the Using .NET guide (available through the v5.3 documentation library) to see if you have any real hope of getting this to work at all under the version of .NET you want to use in combination with v5.3. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
PeterPotkay |
Posted: Mon Jan 14, 2008 9:00 am Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
the earlier version of MQ 5.3 had a few bugs with .NET support. At the very least make sure you have CSD14 applied to MQ 5.3.
But Jeff is right, don't waste time making this work on an MQ version that is no longer supported. Try with MQ 6.0.2.2.
Here is how I connect and MQ Client to a QM in VB.NET:
Code: |
Dim myHashTable As New Hashtable
myHashTable.Add(IBM.WMQ.MQC.PORT_PROPERTY, 1414)
myHashTable.Add(IBM.WMQ.MQC.CHANNEL_PROPERTY, "My.SVRCONN.Channel")
myHashTable.Add(IBM.WMQ.MQC.HOST_NAME_PROPERTY, "MyMQServerName")
myQM = New MQQueueManager("MyQMName", myHashTable)
|
_________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
lifeng |
Posted: Mon Jan 14, 2008 1:22 pm Post subject: |
|
|
Apprentice
Joined: 11 Jan 2008 Posts: 46
|
Thank you guys again for the valuable inputs!
I communicated again with our management about the version thing but was told that until they decide I still need to be continuing on V5.3.
My question for you now: where do I get CSD14 from?
Thanks
Lifeng |
|
Back to top |
|
 |
lifeng |
Posted: Mon Jan 14, 2008 1:23 pm Post subject: |
|
|
Apprentice
Joined: 11 Jan 2008 Posts: 46
|
Never mind. I found the CSD14.
Thanks.
Lifeng |
|
Back to top |
|
 |
lifeng |
Posted: Mon Jan 14, 2008 3:36 pm Post subject: |
|
|
Apprentice
Joined: 11 Jan 2008 Posts: 46
|
Hi,
Another question, how do I verify that my WebSphere MQ Classes for .Net has been installed on my machine when I install my MQ? The doc (v5.3 version of the Using .NET guide) says that I don't need to install it seperately but I don't seem to be able to find it. The C:\Program Files\IBM\WebSphere MQ\Tools folder, for instance, doesn't contain a dotnet folder as it supposed to. I reinstalled MQ just to make sure I didn't miss important options. I selected both server and client when I install. But I still don't have the dotnet folder under Toos.
Is there a seperate package for this that I can get and install?
Thanks
Lifeng |
|
Back to top |
|
 |
PeterPotkay |
Posted: Mon Jan 14, 2008 6:17 pm Post subject: |
|
|
 Poobah
Joined: 15 May 2001 Posts: 7722
|
The base MQ 5.3 product did not include .NET support. It wasn't until something like CSD5 or CSD6 that you got it. If you are at a real old version of MQ 5.3, applying CSD14 will install the .NET support for you on Windows. Among other things, it will put the .NET MQ manual in the C:\Programs\IBM\WebSphere MQ\ folder.
Base MQ 6.0 includes .NET support right from the start.
Save that email where they said they are staying at MQ 5.3!  _________________ Peter Potkay
Keep Calm and MQ On |
|
Back to top |
|
 |
|