This SupportPac contains all the IBM WebSphere MQ V7.0 client components.
A WebSphere MQ client is part of the product that can be installed on its own, on a separate machine from the base product and server. You can run a WebSphere MQ application on a WebSphere MQ client and it can interact, by means of a communications protocol, with one or more WebSphere MQ servers and connect to their queue managers. The servers to which the client connects may or may not be part of a cluster.
WebSphere MQ Family Platforms provides a list of which platforms are supported as WebSphere MQ Clients and/or Servers.
An application that you want to run in the WebSphere MQ client environment must first be linked with the relevant client library. When the application issues an MQI call, the WebSphere MQ client code directs the request to a queue manager, where it is processed and from where a reply is sent back to the client. The link between the application and the client code is established dynamically at runtime. The MQI is available to applications running on the client platform; the queues and other WebSphere MQ objects are held on a queue manager that you have installed on a server machine.
• Why use WebSphere MQ clients?
» Using WebSphere MQ clients is an efficient way of implementing WebSphere MQ messaging and queuing.
» You can have an application that uses the MQI running on one machine and the queue manager running on a different machine, either physical or virtual. The benefits of doing this are:
- There is no need for a full WebSphere MQ implementation on the client machine.
- Hardware requirements on the client system are reduced.
- System administration requirements are reduced.
- A WebSphere MQ application, running on a client can connect to multiple queue managers on different systems.
- Alternative channels using different transmission protocols may be used.
• What applications run on a WebSphere MQ client?» Applications running within application servers that are certified as having passed the J2EE 1.4 (or later) Compatibility Test Suite can use the WebSphere MQ resource adapter provided in the SupportPac.
» The full MQI is supported in the client environment and this enables almost any WebSphere MQ application to be relinked to run on a WebSphere MQ client. Link the application on the WebSphere MQ client to the MQIC library, rather than to the MQI library. The exceptions are:
- An application that uses global transactions; that is, it requires sync point coordination with resource managers other than the queue manager.
- Get(signal) on z/OS.
» Applications which are built using various programming languages including C, C++, .NET (Windows systems only), COBOL, Java and JMS.
» Applications running within application servers that are certified as having passed the J2EE 1.4 (or later) Compatibility Test Suite can use the WebSphere MQ resource adapter provided in the SupportPac.
Note: An application running on a WebSphere MQ client may connect to more than one queue manager concurrently, or use a queue manager name with an asterisk (*) on an MQCONN or MQCONNX call. The application will have to be changed if you want to link to the queue manager libraries instead of the client libraries, as this function will not be available.
RELATED MESSAGE SERVICE CLIENTS
These IBM Message Service Clients offer C/C++ and .NET users an Application Programming Interface (API) that is consistent with the Java Message Service (JMS) API. Applications created using these clients can be used to exchange messages between other XMS 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.
Please click here for more information and download on:
IBM Message Service Client for C/C++ (SupportPac IA94)
Please click here for more information and download on:
IBM Message Service Client for .NET(SupportPac IA9H)
New in this Release
Brings the existing Clients to v126.96.36.199.
Skill Level Required
Users should be familiar with the IBM WebSphere MQ product family in general and have particular skills on the platform for which this client is intended.
Author: WebSphere MQ Development, Hursley
Last updated: 08Apr14
Current Version: 188.8.131.52
»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.
Click for the WebSphere MQ V7.1 Clients and WebSphere MQ V7.5 Clients.
To view the complete portfolio of WebSphere MQ SupportPacs please visit the WebSphere MQ SupportPacs homepage.
This client will inter operate with all the currently supported WebSphere MQ server products, provided the functions used are common to the release of server and client
To install a Unix Client:
1. Logon as root, create an empty directory (with sufficient space to receive the download file) and make it current.
2. Download mqc7_platform to this directory. (Where 'platform' replace with specific ie, AIX, HP-UX)
3. Execute uncompress -fv mqc7_platform.
4. Execute tar -xvf mqc7_platform.
5. Execute rm mqc7_platform.
6. Follow the instructions provided in the readme file to complete the installation of the client.
To install the client on a Windows machine download the zip file and extract the content. From the Windows subdirectory created run the setup.exe program.
Important information for Windows users
When upgrading the clients installation from previous levels to a WMQ V184.108.40.206 level, the mqclient.ini file in WebSphere MQ installation directory is removed. To overcome this problem, please take a backup of the mqclient.ini file from the WebSphere MQ installation directory (by default in C:\Program Files\IBM\WebSphere MQ) before upgrading the clients using the 220.127.116.11 client installer, and copy it back after the install has completed.
More information about installing clients can be found in the WebSphere MQ Clients manual GC34-6590 which can be downloaded from the InfoCenter.
|Download||RELEASE DATE||LANGUAGE||SIZE(Bytes)||Download Options|
|18.104.22.168 Clients||08 Apr 2014||US English||111||HTTP|
|22.214.171.124 Clients||23 Oct 2013||US English||111||HTTP|
|126.96.36.199 Clients||03 May 2013||US English||111||HTTP|
|188.8.131.52 Clients||23 Aug 2012||US English||111||HTTP|
|184.108.40.206 Clients||05 Mar 2012||US English||111||HTTPS|
|220.127.116.11 Clients||28 Nov 2011||US English||111||HTTPS|
|18.104.22.168 Clients||01 Aug 2011||US English||111||HTTPS|
|22.214.171.124 Clients||27 Apr 2011||US English||111||HTTPS|
|126.96.36.199 Clients||26 Jan 2011||US English||111||HTTP|
|188.8.131.52 Clients||25 Aug 2010||US English||111||HTTP|
|184.108.40.206 Clients||18 May 2010||US English||111||HTTP|
|220.127.116.11 Clients||15 Jan 2010||US English||111||HTTP|
|18.104.22.168 Clients||28 Aug 2009||US English||111||HTTP|
|22.214.171.124 Clients||11 May 2009||US English||111||HTTP|
|126.96.36.199 Clients||20 Jan 2009||US English||111||HTTP|
|188.8.131.52 Clients||18 Jun 2008||US English||111||HTTP|
Category 3 WebSphere MQ SupportPacs are supplied under the standard terms and conditions provided by the International Program License Agreement (IPLA) and thus, carry program defect service for WebSphere MQ customers. 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, and you have a current license for a WebSphere MQ server product, you may request Program Services by reporting the problem via the same defect reporting channel you employ for the WebSphere MQ server product(s) on which you are using the SupportPac. No proof of entitlement is required to use this SupportPac.
Service is available for the v7 version of this SupportPac for as long as the WebSphere MQ for V7.0 server product is supported by service. Refer to the WebSphere product lifecycle pages for the relevant service information. It is only supported with MQ platforms which are themselves supported.