| Author |
Message
|
| Stalin |
 Posted: Thu Nov 12, 2009 5:13 am Post subject: Do we realy need IBM WebSphere MQ Client to send msg |
 |
|
Novice
Joined: 21 Oct 2009
Posts: 19
|
Dear Friends,
We would like to only send/receive message from our windows server 2003 to/from MQ Server in Sun solaris system (our supplier's)
using the ASP.NET 1.1 application.
I already installed the trial version of MQ server 6.0 and we would able to connect to the MQ server
using the below code which works well.
Dim properties As Hashtable = New Hashtable
properties.Add(MQC.HOST_NAME_PROPERTY, IP address of the MQ server)
properties.Add(MQC.CHANNEL_PROPERTY, "SYSTEM.DEF.SVRCONN")
properties.Add(MQC.USER_ID_PROPERTY, Username)
properties.Add(MQC.PASSWORD_PROPERTY, Password)
properties.Add(MQC.PORT_PROPERTY, Port number)
Dim queueManager As MQQueueManager
'Attempt the connection
queueManager = New MQQueueManager(queueManagerName, properties)
But the question arises here is why we need these installation for just to send messages/receive
to and from the MQ server.
Is there any possibility to achieve our goal without installing client/server?
Is there any possiblity to place the required dll's in our ASP.NET application's bin folder
to send the message without installing the Client?.
Advance thanks for all your time.
Regards,
Stalin |
|
| Back to top |
|
 |
| zpat |
| Posted: Thu Nov 12, 2009 5:30 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
What's wrong with installing the windows MQ client only?
It's free and then it's obvious what version you have installed - you can maintain it etc.
Not good practice to embed part of the MQ client distribution with the application even if technically possible (which I doubt it is). |
|
| Back to top |
|
|
| Stalin |
| Posted: Thu Nov 12, 2009 5:44 am Post subject: |
|
|
Novice
Joined: 21 Oct 2009
Posts: 19
|
Dear zpat,
Thanks for your time.
These external installation is not acceptable by our Administrators.
If it is possible without extra client/server installation by using the referencing of the required dlls in our .NET application , it would
be much more better for us.
Regards,
Stalin |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Nov 12, 2009 5:51 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Your administrators are simply wrong in this case.
If you don't have the access rights necessary to install system software on the server - then request the appropriate team to perform the work.
WMQ is system software not application software. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 12, 2009 6:24 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The .NET interface does support a Managed Connection type that lets you package an MQ DLL in the application.
But you still need MQ Client installed on the machine that's doing the build. |
|
| Back to top |
|
|
| Stalin |
| Posted: Thu Nov 12, 2009 6:55 am Post subject: |
|
|
Novice
Joined: 21 Oct 2009
Posts: 19
|
As i already mentioned, below is the code which i am using,
Dim properties As Hashtable = New Hashtable
properties.Add(MQC.HOST_NAME_PROPERTY, IP address of the MQ server)
properties.Add(MQC.CHANNEL_PROPERTY, "SYSTEM.DEF.SVRCONN")
properties.Add(MQC.USER_ID_PROPERTY, Username)
properties.Add(MQC.PASSWORD_PROPERTY, Password)
properties.Add(MQC.PORT_PROPERTY, Port number)
Dim queueManager As MQQueueManager
'Attempt the connection
queueManager = New MQQueueManager(queueManagerName, properties)
Is this is the Managed connection type? Could you please provide me some more information on the Managed connection type and Packing of MQ dll in the .NET application
I will also check the user manual.
Advance Thanks & Regards,
Stalin |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Nov 12, 2009 7:15 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Stalin wrote: |
| Is this is the Managed connection type? Could you please provide me some more information on the Managed connection type and Packing of MQ dll in the .NET application |
No - if you don't specify TRANSPORT_PROPERTY then the code determines the connection type based on dll in use. These will resolve to client/XAclient/server as described in the documentation here.
You should also be aware that a managed connection has a number of restrictions which are also described in the documentation.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Stalin |
| Posted: Thu Nov 12, 2009 8:06 am Post subject: |
|
|
Novice
Joined: 21 Oct 2009
Posts: 19
|
Dear Vitor,
Thanks for the link.
In my .Net environment i referenced the amqmdnet.dll version 1.0.0.3.
But i could not find the constant MQC.TRANSPORT_MQSERIES_MANAGED.
Did i reference the wrong version of dll?
Advance Thanks & Regards,
Stalin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Nov 12, 2009 8:39 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Apply the most recent fixpack of MQ v6 to your build environment and then try again. |
|
| Back to top |
|
|
| Stalin |
| Posted: Mon Nov 16, 2009 12:35 am Post subject: |
|
|
Novice
Joined: 21 Oct 2009
Posts: 19
|
Thanks for all your suggestion and time on this thread.
I have installed IBM Websphere MQ Client for Windows 6.0.2.7 and referenced the amqmdnet.dll
Now MQC.TRANSPORT_MQSERIES_MANAGED is avaialble in .NET environment and i could able to send the
message to MQ server using Managed connection.
Regards,
Stalin |
|
| Back to top |
|
|
|
|
