How to connect to MQ on unix from .NET application?

[bond007]

Hi,
Am writing an .net windows application in which i have to connect to IBM MQ on remote machine running unix to post messages. This is a tool kinda thing for an enterprise application.

this is the code am using to connect to the MQ.

MQEnvironment.Hostname = hostName;
MQEnvironment.Port = port;
MQEnvironment.Channel = "SYSTEM.DEF.SVRCONN";
MQQueueManager qm=new MQQueueManager(queueMgr);

When i try to run the application it throws an exception in
MQQueueManager qm=new MQQueueManager(queueMgr);

Exception details :- CompCode 2 Reason 2035 ..from error code lookup i learnt that its MQRC_NOT_AUTHORIZED.
read somewhere that the user's credentials under whom application is run will be supplied for authorization automatically..if thats the case how is cross platform connectivity is possible...in my case mq client is on windows and
mq server is on unix.

Do i have to specify the userid,password for unix system to override this?
If so, how? MQQueueManager Class doesnt have a constructor that accepts userid/password as a parameter and MQEnvironment doesnt have a property for userid/password..
Am using Websphere Mq 5.3 ? Is the option to specify userid/password available in the latest version 6.0?

seems MQ classes for java have options to specify userid/password but .NET classes didnt.

am pulling my hair over this for the past 3 days...please help..

[Derek Wade]

I found that in V6 and V7 of the MQ Messaging Library for .NET, the readme file states:

(WMQ) User authentication for WMQ is performed by using the details of the
logged on user and not the information provided in the XMSC.USERID and
XMSC.PASSWORD fields. This is the current design intention for consistency
with WMQ. Please see the WMQ user documentation for further details of
authentication.

I found that if you "impersonate" a windows user at runtime that is the same username of the MQ server before creating the MQQueueManager, it works!

By adjusting this sample code from MS (http://support.microsoft.com/kb/306158) you can easily accomplish the impersonation.

I hope this helps others!

Derek Wade