Contents

Figures
Tables
About this book
What you need to know to understand this book
Terms used in this book
How to use this book
Summary of changes
Changes for this edition (GC34-6590-01)
Introduction to WebSphere MQ clients
Overview of WebSphere MQ clients
What is a WebSphere MQ client?
How the client connects to the server
What is an extended transactional client?
Why use WebSphere MQ clients?
What applications run on a WebSphere MQ client?
How do I set up a WebSphere MQ client?
Installing WebSphere MQ clients
Preparing for installation
Platform support for WebSphere MQ clients
Platform support for extended transactional clients
Applications on WebSphere MQ Version 6.0 clients
Communications
Performance considerations
Hardware and software requirements
AIX client: hardware and software required
HP-UX client: hardware and software required
Linux client: hardware and software required
Solaris client: hardware and software required
Windows client: hardware and software required
Installing client components
Installing a WebSphere MQ client and server system
Installing from an electronic software download
Installing WebSphere MQ clients on the same machine as the server
Uninstalling WebSphere MQ clients
Installing on AIX
Components for AIX
Installing without SSL support
Installing the extended transactional function
Migrating from an earlier version of WebSphere MQ for AIX
Changing the national language
Removing a WebSphere MQ client from AIX(R)
Migrating to and from the WebSphere MQ SSL support
Uninstalling the extended transactional function
Installing on HP-UX
Components for HP-UX
Installing the extended transactional function
Removing a WebSphere MQ client from HP-UX
Migrating to and from the WebSphere MQ SSL support
Uninstalling the extended transactional function
Installing on Linux
Installing the extended transactional function
Removing the WebSphere MQ client from Linux(R)
Migrating to and from the WebSphere MQ SSL support
Uninstalling the extended transactional function
Installing on Solaris
Components for Solaris
Installing the extended transactional function
Removing a WebSphere MQ client from Solaris
Migrating to and from the WebSphere MQ SSL support
Uninstalling the extended transactional function
Installing on Windows
Preparing to install the WebSphere MQ client
Installing the WebSphere MQ client
Other methods of installing the WebSphere MQ client
Uninstalling a WebSphere MQ client
Configuring communication links
Deciding which communication type to use
Defining a TCP/IP connection
Defining a TCP/IP connection on a WebSphere MQ client
Defining a TCP/IP connection on a WebSphere MQ server
TCP/IP connection limits
Defining an LU 6.2 connection
Defining an LU 6.2 connection on a WebSphere MQ client
Defining an LU 6.2 Connection on a WebSphere MQ server
Defining a NetBIOS connection
Defining an SPX connection
Configuring an extended transactional client
XA compliant transaction managers
The xa_open string
The XA switch structures
Configuring for CICS
Configuring for Tuxedo
Microsoft Transaction Server
WebSphere Application Server
Verifying the installation
The installation used for the example
What the example shows
Setting up the server
Setting up the server on UNIX and Windows systems
Setting up the server on i5/OS
Setting up the server on z/OS
Setting up the WebSphere MQ client
Defining a client-connection channel using MQSERVER
Defining a client-connection channel using WebSphere MQ Explorer
Putting a message on the queue
On the WebSphere MQ client workstation
Getting the message from the queue
On the WebSphere MQ client workstation
Ending verification
System administration
Setting up WebSphere MQ client security
Authentication
User IDs
Access control
Using channels
What is a channel?
Message Channels
MQI Channels
Defining MQI channels
Automatically defined channels
User defined channels
Creating one definition on the WebSphere MQ client and the other on the server
On the server
On the WebSphere MQ client
Creating both definitions on the server
Defining the server-connection channel
Defining the client-connection channel
Accessing client-connection channel definitions
Client channel definition table
Migrating to a later release level of WebSphere MQ
Channel exits
Path to exits
Connecting a client to a queue-sharing group
Connecting to a specific queue manager
Connecting to the generic interface
Stopping channels
The Secure Sockets Layer (SSL) on WebSphere MQ clients
Specifying that an MQI channel uses SSL
Specifying the location of LDAP servers that hold certificate revocation lists (CRLs)
When a WebSphere MQ client application issues an MQCONNX call
Using a client channel definition table
Using Active Directory on Windows
Renegotiating the secret key
Refreshing a client's view of the SSL key repository contents and SSL settings
Specifying that only FIPS-certified cryptography will be used
Using WebSphere MQ environment variables
MQCCSID
MQCHLLIB
MQCHLTAB
Using MQCHLLIB and MQCHLTAB on the server
MQIPADDRV
MQNAME
MQSERVER
TCP/IP default port
SPX default socket
Using MQSERVER
Canceling MQSERVER
MQSSLCRYP
MQSSLFIPS
MQSSLKEYR
MQSSLRESET
Application programming
Using the message queue interface (MQI)
Limiting the size of a message
Choosing client or server coded character set identifier (CCSID)
CCSID and encoding fields - multiple puts
Designing applications
Using MQINQ
Using syncpoint coordination
Using MQCONNX
Shared connection handles on MQCONNX
Building applications for WebSphere MQ clients
Running applications in the WebSphere MQ client environment
Triggering in the client environment
Process definition
Trigger monitor
CICS applications (non-z/OS)
Linking C applications with the WebSphere MQ client code
Linking C++ applications with the WebSphere MQ client code
Linking COBOL applications with the WebSphere MQ client code
Linking Visual Basic applications with the WebSphere MQ client code
Running applications on WebSphere MQ clients
Using environment variables
Using the MQCNO structure
Using DEFINE CHANNEL
Role of the client channel definition table
Multiple queue managers
Queue-sharing groups
Examples of MQCONN calls
What the examples demonstrate
Example 1. Queue manager name includes an asterisk (*)
Example 2. Queue manager name specified
Example 3. Queue manager name is blank or an asterisk (*)
Preparing and running extended transactional client applications
Preparing and running CICS and Tuxedo applications
Sample programs
Error log messages
Preparing and running Microsoft Transaction Server applications
Preparing and running WebSphere MQ JMS applications
Solving problems
WebSphere MQ client fails to make a connection
Stopping WebSphere MQ clients
Error messages with WebSphere MQ clients
Using trace on Windows
File names for trace files
How to examine First Failure Support Technology (FFST) files
Using trace on UNIX systems
File names for trace files
How to examine First Failure Support Technology (FFST) files
Using trace on AIX(R)
Appendixes
Appendix A. A review of transaction management
Appendix B. Notices
Trademarks
Index