The server based adapter relies on MQSeries Server running on Microsoft Windows Server. This design of this adapter guarantees reliable messaging
because it supports Microsoft Distributed Transaction Coordinator (MSDTC). The adapter supports clustered MQSeries Servers and clustered MQSeries Queue Managers, and also clustered BizTalk servers.
Full MQM (Queue Manager) functionality and performance.
Disconnect processing at the Windows MQM (Queue Manager)
Enterprise level scalability
Supports Transactional scenarios
Guarantees once and only once delivery of messages
The Client bases adapter is available to connect to Those MQ Servers which are not running on Windows machines. They might be running on UNIX/AIX etc.
If there is a requirement to communicate with a MQ server which is running over non windows serves, the solution is use MQSC adapter. In order to use this adapter you would need to install
HIS (Host Integration Server) from Microsoft. Refer
this dedicated MSDN article about MQ Adapters.
Does not require MQ Server to be on Windows Platform
Uses IBM Client MQI API
Provides direct access to non-windows MQM (Queue Manager)
Free non-transactional client (Base)
Sometime this problem occurs while setting the configuration data for the Queue Definition in Send Port or /Receive Location. This is indeed a permissions problem,
Error Code 2018-
sometime this error comes while configuring the MQ Queue details on send port / receive location.
This is caused because the Identity of the MQSAgent COM+ Application isn't in the 'mqm' windows group on MQ Server
Error Code (Reason code)
= 2195- This occurs because of MSDTC settings.
You need to enable the Network DTC Access, Allow Outbound and Allow Network Clients & Outbound for the client and the server respectively.
The MQSeries adapter uses MSDTC for transactions so it is absolute necessary to check below things before starting:
Ensure MQSAgent is installed on MQ Server; make sure to use the correct version of BizTalk Setup.
Make sure below are installed on the windows machine
If MQSAgent is on a Windows 2000 Server, ensure “No Authentication Required” is selected in the MSDTC Security Configuration dialog box.
Ensure Firewall are not blocking RPC ports
Enable support for XA transactions
Nice article. There is not much out there on the MQ Series. This is very helpful.
Thanks! Just created today,Need to perform some formatting and add hot fixes.
Great article, very useful for people looking for options to communicate with MQ Server.
Thanks! We are happy that it was useful for you.
Hi Naushad, very good article, i am facing some issues with MQSC adapter can you give your thoughts on that.