Programming with WebSphere MQ base Java

Introduction for programmers
Why should I use the Java interface?
The WebSphere MQ classes for Java interface
Writing WebSphere MQ base Java applications
Connection differences
Client connections
Bindings mode
Defining which connection to use
Example application
Operations on queue managers
Setting up the WebSphere MQ environment
Connecting to a queue manager
Using a client channel definition table
Specifying a range of ports for client connections
Accessing queues and processes
Handling messages
Handling errors
Getting and setting attribute values
Multithreaded programs
Using channel exits
Using channel exits not written in Java
Using a sequence of channel send or receive exits
Channel compression
Connection pooling
Controlling the default connection pool
The default connection pool and multiple components
Supplying a different connection pool
Supplying your own ConnectionManager
JTA/JDBC coordination using WebSphere MQ base Java
Configuring JTA/JDBC coordination
Using JTA/JDBC coordination
Known problems and limitations
Secure Sockets Layer (SSL) support
Enabling SSL
Using the distinguished name of the queue manager
Using certificate revocation lists
Renegotiating the secret key used for encryption
Supplying a customized SSLSocketFactory
Making changes to the JSSE keystore or truststore
Error handling when using SSL
Running WebSphere MQ base Java applications
Tracing WebSphere MQ base Java programs
Environment-dependent behavior
Core details
Restrictions and variations for core classes
MQGMO_* values
MQPMRF_* values
MQPMO_* values
MQCNO_FASTPATH_BINDING
MQRO_* values
Miscellaneous differences with z/OS
Features outside the core
MQQueueManager constructor option
MQQueueManager.begin() method
MQGetMessageOptions fields
Distribution lists
MQPutMessageOptions fields
MQMD fields
Restrictions under CICS Transaction Server