The IBM Message Service Client for C/C++ offers C/C++ users an Application Programming Interface (API) that is consistent with the Java™ Message Service (JMS) API.
The IBM Message Service Client for C/C++ ("XMS C/C++") renders the Java Message Service (JMS) API in the C/C++ languages. 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 Business Integration Message Brokers and WebSphere Application Server messaging environments with little or no rework.
A .NET implementation of this SupportPac is also available, IA9H: IBM Message Service Client for .NET. This can be downloaded as a Cat3 SupportPac here.
The XMS Clients create new integration possibilities by extending WebSphere messaging to customers who have, for example, standardized on C/C++ as their client platform, or who want to use messaging to integrate with new .NET or J2EE applications.
Skill Level Required
To use this SupportPac you need the following skills, knowledge, and experience:
» C or C++ application programming skills.
» 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
• Support added for WebSphere MQ v8.0.
• Support added for Visual Studio 2010.
• Support added for TLS 1.2.
• Support added for WebSphere MQ v7.5.
• Support on additional platforms
XMS is supported on additional flavours of Windows, Linux, AIX and Solaris operating systems. Please refer the readme for the complete list of platforms supported.
In addition, several fixes have been applied to resolve issues highlighted from continued testing and customer feedback.
Author: WebSphere Messaging Clients Project Team, Bangalore
Released: 28May04 (as Cat2)
Last Updated: 17Sep13
Current Version: 2.0.3
»Please note that the version number shown in the right-hand pane is the version of the WebSphere MQ or WebSphere Message Broker 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 Message Broker 6.1 with Fix Pack 10 onwards
IBM WebSphere MQ 7.0.1 + Fix pack 7 onwards
IBM WebSphere MQ 7.1.0 (See Note 2)
IBM WebSphere MQ 7.5 (See Note 3)
IBM WebSphere Application Server 126.96.36.199 onwards
IBM WebSphere Process Server 6 onwards
IBM WebSphere ESB 6 onwards
IBM WebSphere Application Server 188.8.131.52 onwards
IBM WebSphere Application Server 184.108.40.206 onwards
NOTE 1: If using WebSphere MQ, the machine used to run the XMS application must be installed with the WebSphere MQ Client V220.127.116.11 or 18.104.22.168 or later (these libraries are pre-installed on machines with a local queue manager of an appropriate level). These support 'client' mode connections to V7.0.1 and V7.1 queue managers or 'bindings' mode connection to local queue managers. With MQ multiple version installation capabilities, it is also possible to use the XMS in ‘bindings’ mode with MQ V7.0.1 queue managers connected with MQ V7.1.0 libraries. To use multiple MQ installations and XMS on that, please reference XMS and MQ V7.1 documentation
NOTE 2: If XMS is used with WebSphere MQ V22.214.171.124, then need to apply the fix for MQ using APAR IV12953 (link -> http://www.ibm.com/support/docview.wss?uid=swg1IV12953). Please contact MQ Level 2 or Level 3 for getting the fix.
NOTE 3: When using XMS with WebSphere MQ v7.5, an XMS application might not throw any exception if it attempts to put a message whose size is greater than the MaxMessageLength of the queue, WebSphere MQ APAR IC91685 must be applied to resolve the exception. Refer to the APAR details here http://www.ibm.com/support/docview.wss?uid=swg1IC91865. Please contact IBM Support for getting the fix.
|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 ia94.pdf file should be viewed using Acrobat® Reader®, available from http://www.adobe.com/products/acrobat/readstep2.html
The ia94.doc.zip file contains HTML which can be viewed either standalone or within an Eclipse environment. Please see ia94.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
Please download the drivers below with fixes for the following APARs (IV55981,IV52603,IV52601,IV52608,IV52607).
|Download||RELEASE DATE||LANGUAGE||SIZE(Bytes)||Download Options|
|ia94.zip||17 Sep 2013||US English||58000000||HTTPS|
|Latest fixes||11 Sep 2014||US English||111||HTTP|
Technical Support for the IBM WebSphere Message Service Client for C/C++ 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.1 product.