WebSphere MQ Client, V5.3 GA 1 README

Content

WebSphere MQ Client, V5.3 README
Welcome to IBM WebSphere MQ Client

This README file contains information you need to install IBM WebSphere MQ Client, as well as information that was not available for our printed publications.

Before You Install IBM WebSphere MQ Client

1. Information about installing
   
   See the book WebSphere MQ Clients, GC34-6058, which is provided on the documentation CD1. Hardware and software requirements are described in this book in "Chapter2. Preparing for installation".
   
   For instructions on installing the UNIX WebSphere MQ Clients from an installation image downloaded from IBM, see the section "Electronic Software Download installation" below.
   
   
2. WebSphere MQ online documentation
   
   The WebSphere MQ online documentation is available:
   
   In PDF format on the documentation CD1, in the /MSI//PDF directory.
   
   In compiled HTML format on the documentation CD1 in the /MSI//CHM directory. To view this, point your Web browser to the start.htm file in the CD-ROM file system.
   
   
3. Getting help
   
   See the section "Online information" in the WebSphere MQ Quick Beginnings book for your platform.
   
   The WebSphere MQ Web site is located at:
   
   http://www.ibm.com/software/integration/wmq/
   
   The SupportPac™ page is at:
   
   http://www.ibm.com/support/docview.wss?rs=977&uid=swg27007205
   
   For current information on known problems and available fixes, see the Support page of the WebSphere MQ Web site at:
   
   http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006037
   
   
4. Web documentation updates
   
   The latest updates to the Web-based WebSphere MQ documentation are now available from the WebSphere MQ Web site at:
   
   http://www.ibm.com/software/integration/wmq/library/
   
   
5. Online version of this file
   
   An online version of this readme file is maintained on the Web, and might contain additions made since this file was frozen on this media. The site is:
   
   http://www.ibm.com/support/docview.wss?rs=977&uid=swg27006917
   
   
6. General note for WebSphere MQ V5.3 AIX, Solaris, and HP-UX clients
   
   The client code supplied on the server and client CD includes support for Secure Sockets Layer (SSL). The SSL code includes administrative functions, so the installed size of the client is larger than that of the MQSeries V5.2 client. If you do not need the SSL functionality, the MQSeries V5.2 client operates with WebSphere MQ V5.3 servers and can be obtained from the WebSphere MQ SupportPac Web site.
   

Note that latest changes are shown in red and earlier changes are shown in blue.

The Change History is located at the bottom of the page.

Installing an IBM WebSphere MQ Client from Version 5.3 Products

A description of how to install an IBM WebSphere MQ client is in "Chapter 3. Installing client components from WebSphere MQ products and MQSeries Version 5 products (not z/OS)" in the WebSphere MQ Clients book, GC34-6058.

This readme file contains corrections and additions to that information, as shown below:

1. Add the following new section:
   
   Electronic Software Download installation
   
   These instructions apply to installing the UNIX WebSphere MQ Clients from an installation image downloaded from IBM. Use it with the Quick Beginnings or Clients book for this release. A version of the Quick Beginnings book is available from the download site; it has a description of 'WebSphere MQ V5.3 Install Doc'. The installation image is provided as a compressed tape archive (tar) file.
   
   Installation Steps
   

1. Copy the WebSphere MQ tar file to a suitable directory accessible to the machines where the software is to be installed. This directory must be on a file system with at least the amount of free space indicated below (this is in addition to the disk space required for the product, as detailed in the Quick Beginnings book):
MQ53ClientSSL_solaris.tar 200MB
MQ53ClientSSL_hpux.tar 200MB
MQ53ClientSSL_aix.tar 120MB

2. Make this directory the current directory and use the command:

tar -xvf .tar

to create the installation image.

3. After the operation succeeds, you can delete the .tar.

4. Use the WebSphere MQ Quick Beginnings book for your platform, or the Clients book, to install and configure the product. Replace any references to the CD drive by the directory used in the steps above. All other instructions remain the same.

2. In the section "Installing on HP-UX", subsection "Installation":

4b. The mqlicense script can be found at ./hpux11/MQClientwithSSL/mqlicense.sh

5. The command to start the installation procedure is:

swinstall -s /cdrom/hpux11/MQClientwithSSL/mqs530.v11

3. In the section "Installing on Solaris", subsection "Installation":

1. The second paragraph should read:

If the Volume Manager is running, the CD is mounted on /cdrom/MQ53Client1 automatically. If it is not running, mount the CD by typing the following commands:

mkdir -p /cdrom/MQ53Client1/
mount -F hsfs -r /dev/dsk/ /cdrom/MQ53Client1

substituting with the name of your CD-ROM drive.

2. The mqlicense.sh script can be found at
/cdrom/MQ53Client1/solaris/MQClientwithSSL/mqlicense.sh

3a.
Type pkgadd -d /cdrom/MQ53Client1/solaris/MQClientwithSSL/mqs530.img

4. In the section "Installing on Windows", note that you cannot install the client for Microsoft Windows 98 from the server CD. You must use the client CD.

Other Amendments to the Clients Book

1. In Chapter 2, in the section "AIX client: hardware and software required", subsection "Optional software", note that a DCE-threaded WebSphere MQ client application cannot be run over SSL on AIX, Solaris, and HP_UX. Because TxSeries uses DCE threads, it cannot run as a WebSphere MQ client that uses SSL on AIX, Solaris, and HP_UX.
   
2. In Chapter 8, add the following new section:
   
   Client channel definitions using the Active Directory
   
   On Windows systems with Active Directory support, you can use the setmqscp command to configure and administer support for publishing client connection channel definitions in an Active Directory. See the WebSphere MQ System Administration Guide for information on using this command, and the command syntax.
   
   
3. Add the following new chapter
   
   Secure Sockets Layer (SSL) on WebSphere MQ clients
   WebSphere MQ does not support SSL on the Windows 98 client.
   
   SSL channels
   
   There are three ways of specifying that a channel uses SSL. In order of decreasing precedence, they are:
   
   1 When your application makes an MQCONNX call
   2 Using the client channel definition table
   3 Using the Active Directory (on Windows systems with Active Directory support)
   
   You cannot use the MQSERVER environment variable to specify that a channel uses SSL.
   
   LDAP CRL (certificate revocation list) definitions on WebSphere MQ clients
   
   There are three ways of defining an LDAP CRL on a WebSphere MQ client.
   In order of decreasing precedence, they are:
   
   1 When your application makes an MQCONNX call
   2 Using the client channel definition table
   3 Using the Active Directory (on Windows systems with Active Directory support)
   
   These methods are explained below.
   
   MQCONNX
   
   On an MQCONNX call, the MQSCO structure, in conjunction with the SSL fields in MQCD, allows an application running as a WebSphere MQ client to specify configuration options that control the use of SSL for the client connection.
   
   You can also use the MQAIR structure. MQAIR allows a WebSphere MQ client to specify authentication information that is to be used for the client connection. Each MQAIR structure contains an authentication information record containing the information needed to access a single LDAP CRL server. The MQSCO structure points to the first record in the array of MQAIR records.
   
   Both MQSCO and MQAIR are input parameters to the MQCONNX call. For more information, and the data structure details for MQSCO and MQAIR, see the WebSphere MQ Application Programming Reference.
   

Client channel definition table

1. Platforms other than z/OS
   
   When you define a client-connection (CLNTCONN) SSL channel, if the SSLCRLNamelist queue manager attribute is set, any CRL information current on the queue manager system on which the channel is defined is included with the resulting client channel definition. If further CRL information is added or the CRL information is altered or deleted, the change is reflected in the client channel definition table on the queue manager system. If the SSLCRLNamelist queue manager attribute is set to blank, all the CRL information is removed from the client channel definition table.
   
   If a client channel definition table containing CRL information is moved to a client system, the same CRL server information is used at both the queue manager and client ends of the channel.
   
   You can use different CRL information at the two ends of a channel, by temporarily setting up the queue manager system with the client CRL information and then copying the client channel definition table to the client system. This CRL information then applies on the client system. The queue manager system then alters its CRL information to what it requires for itself.
   
   When LDAP CRL information is added to an existing client channel definition table, the information is added to the end of the table, and existing channel definitions in the table are not affected. If these
   existing channel definitions are from MQSeries systems before WebSphere MQ 5.3, they can continue to be used by the appropriate MQSeries clients. Note that MQSeries Version 5.2 and earlier clients fail in a controlled manner if they encounter LDAP CRL information.
   
   
2. z/OS
   
   The client channel definition table is constructed using the MAKECLNT option of the COMMAND function of the CSQUTIL utility. This includes information from any DISPLAY AUTHINFO commands in the input data, in addition to any client-connection channel information. It does not depend on any current queue manager attributes, and is not updated dynamically.
   
   Using the Active Directory
   
   On Windows systems with Active Directory support, use the setmqcrl command to configure and administer support for publishing LDAP CRL definitions in the Active Directory. See the WebSphere MQ System Administration Guide for information on using this command, and the command syntax.
   

Trademarks
The following terms are trademarks of the IBM Corporation in the United States, or other countries, or both:

IBM MQSeries SupportPac TXSeries WebSphere

ActiveX, Microsoft, Visual Basic, Visual C++, Windows, and Windows NT are trademarks or registered trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.




Change History

Last Updated: 8 October 2005

• 8 October 2005: Moved information from static page