The IBM Message Service Client for .NET offers .NET users an Application Programming Interface (API) that is consistent with the Java Message Service (JMS) API.
Notice: This SupportPac is now withdrawn, due to end of support for WebSphere MQ v7.0. It will be archived on 31 December 2015.
The IBM Message Service Client for .NET ("XMS .NET") renders the Java Message Service (JMS) API in a managed .NET environment. It brings the benefits of JMS - a standard, abstracted messaging API for pub/sub and point-to-point messaging, as well as externally administered objects - to the non-Java world.
Applications created in this way can be used to exchange messages between other Message Service Client applications, JMS applications or native WebSphere MQ applications and can easily be migrated between WebSphere MQ, WebSphere Message Brokers and WebSphere Application Server messaging environments with little or no rework.
A C/C++ implementation of this SupportPac is also available, IBM Message Service Client for C/C++. This can be downloaded as a Category 3 SupportPac here.
If your XMS .NET application intends to connects to WebSphere MQ v7.1 or later queue manager, then it is recommended to use the XMS .NET that is installed as part of WebSphere MQ v7.1 or later. The XMS .NET which is installed as part of WebSphere MQ 7.1 or later also provides connectivity to WebSphere Message Broker v6 and Default Messaging provider of WebSphere Application Server v6.0 or later.
XMS .NET available from this website should be downloaded only if your application intends to connect to WebSphere MQ v.7.0.1 + Maintenance packs or to use XMS .NET with WebSphere Message Broker (WMB) or WebSphere Application Server (WAS). Refer to the Prerequisites section for the supported versions.
The XMS .Net performance report with WebSphere MQ 7.1 as message provider is also available as SupportPac MP7K.
The XMS .Net Performance Harness tool which is used to measure the application performance is available here.
The XMS Clients create new integration possibilities by extending WebSphere messaging to customers who have, for example, standardized on .NET as their client platform, or who want to use messaging to integrate legacy C++ applications with new J2EE applications.
For a brief overview about features and usages of XMS please refer to the following document: XMS .NET - An Overview.
Skill Level Required
To use this SupportPac you will need the following skills, knowledge, and experience:
• Application programming skills in one of the .NET languages.
• A working knowledge of the operating system that you are using.
• Experience in using TCP/IP as a communications protocol.
• Some knowledge of the concepts and terminology associated with the WebSphere Messaging products with which you intend to communicate.
• Some knowledge of the Java Message Service Specification, Version 1.1.
New in this Release
• Updated for WebSphere MQ v220.127.116.11.
• APAR updates for v18.104.22.168 have been added. Details of the latest fixes plus previous releases can be found here.
Please see product readme (below) for further details.
Author: WebSphere Messaging Clients Development Team, Bangalore
Released: 11Apr06 (as Cat 2)
Current Version: 22.214.171.124
»Please note that the version number shown in the right-hand pane is the version of the WebSphere MQ or WebSphere MB product that this SupportPac applies to. The date is the last webpage refresh.
To view the complete portfolio of WebSphere MQ SupportPacs please visit the WebSphere MQ SupportPacs homepage.
This SupportPac requires that ONE of the following servers is available:
IBM WebSphere Business Integration Message Broker 5 Fix Pack 4 onwards
IBM WebSphere Message Broker 6
IBM WebSphere MQ 126.96.36.199 and above
IBM WebSphere Application Server 188.8.131.52 onwards
IBM WebSphere Process Server 6
IBM WebSphere ESB 6
NOTE 1: If using WebSphere MQ, the machine used to run the XMS application must be installed with the WebSphere MQ Client V184.108.40.206 or later (these libraries are pre-installed on machines with a local queue manager of an appropriate level). These support 'client' mode connections to V5.3, V6.0 and V7.0 queue managers or 'bindings' mode connection to a local queue manager of an appropriate level.
|WebSphere MQ V7 Clients (MQC7)||US English||111|
To install the SupportPac, please follow the instructions in the accompanying readme.txt file.
The documentation for this SupportPac is available in two formats.
• The ia9h.pdf file should be viewed using Acrobat® Reader®, available from http://www.adobe.com/products/acrobat/readstep2.html
• The ia9h.doc.zip file contains HTML which can be viewed either stand-alone or within an Eclipse environment. Please see ia9h.doc.readme.html for more details of using the documentation in this format.
The product installer downloads are divided into five types, according to the license agreement under which the product will be used. Please review the following table to help select the required package. Please note, restrictions exist for the use of the product under each license. For example, products licensed for IBM WebSphere Process Server and IBM WebSphere ESB are only supported for use with those products. Please see the full terms of the license for further details.
IBM WebSphere Process Server for distributed OS - WPS License
IBM WebSphere Process Server for z/OS - WPS z/OS License
IBM WebSphere ESB for distributed OS - WESB License
IBM WebSphere ESB for z/OS - WESB z/OS License
All other servers - Standard License
|Download||RELEASE DATE||LANGUAGE||SIZE(Bytes)||Download Options|
|ia9h_1.2.7.zip||08 Jul 2010||US English||3900000||HTTPS|
|ia9h_220.127.116.11.zip||03 Sep 2009||US English||1350000||HTTPS|
|ia9h_18.104.22.168.zip||26 Jan 2010||US English||1350000||HTTPS|
|ia9h_22.214.171.124.zip||04 Jun 2010||US English||1350000||HTTPS|
|ia9h_126.96.36.199.zip||29 Sep 2010||US English||1350000||HTTPS|
|ia9h_188.8.131.52.zip||04 Feb 2011||US English||1350000||HTTPS|
|ia9h_184.108.40.206.zip||17 May 2011||US English||1350000||HTTPS|
|ia9h_220.127.116.11.zip||18 Aug 2011||US English||1350000||HTTPS|
|ia9h_18.104.22.168.zip||13 Dec 2011||US English||1350000||HTTPS|
|ia9h_22.214.171.124.zip||04 Apr 2012||US English||1350000||HTTPS|
|ia9h_126.96.36.199.zip||23 Aug 2012||US English||1350000||HTTPS|
|ia9h_188.8.131.52.zip||08 May 2013||US English||1350000||HTTPS|
|ia9h_184.108.40.206.zip||21 Oct 2013||US English||111||HTTPS|
|ia9h_220.127.116.11.zip||08 Apr 2014||US English||111||HTTPS|
|ia9h_18.104.22.168.zip||13 Aug 2015||US English||111||HTTPS|
Technical Support for the IBM WebSphere Message Service Client for .NET SupportPac is supplied under the standard terms and conditions provided by the International Program License Agreement. Please read the IPLA and LI files that accompany the SupportPac, to ensure you understand the conditions under which the SupportPac is provided.
If you encounter what you believe to be a defect with the SupportPac you may request Program Services, by reporting the problem via the same defect reporting channel you use for the WebSphere MQ product. This requires an active service agreement for the WebSphere MQ product. The End of Service date for this SupportPac is the same as the WebSphere MQ v7.0 product. Refer to the WebSphere product lifecycle pages for the relevant service information. It is only supported with MQ platforms which are themselves supported.