See: Description
Interface | Description |
---|---|
NativeErrorHandler |
Handle errors from native WMQ when consuming messages.
|
Class | Description |
---|---|
AbstractNativeErrorHandler |
Abstract implementation of
NativeErrorHandler |
AttachedConnection |
Connection implementation that uses the native WebsphereMQ API.
|
DetachedConnection |
Connection implementation that uses the native WebsphereMQ client.
|
ForwardingNativeConsumerErrorHandler |
A
NativeErrorHandler implementation for errors on consuming. |
MessageOptions |
Options handling queue access and MQMessage options when getting or putting messages on a MQQueue
|
MQMessageAccessor | |
MQMessageFactory |
MQMessageFactory for creating MQMessageInstance instances.
|
MQMessageOptionsAccessor | |
NativeConnection |
Abstract Connection implementation that uses the native WebsphereMQ client.
|
NativeConsumer |
MessageConsumer implementation that uses the WebsphereMQ native client.
|
NativeProducer |
MessageProducer implementation that uses the WebsphereMQ native client.
|
Enum | Description |
---|---|
MQMessageFactory.MQMessageInstance |
Types of MQMEssage.
|
Provides adapter connectivity to WebsphereMQ based on the native MQ API.
You will need to have installed and configured the WebsphereMQ Client software for your platform. The jars from the WebsphereMQ Client software should be copied into the adapter's lib directory.
The default message options that are used are sensible for most requirements, and there should be no reason to change those values. If changes are required, then access to the WebsphereMQ Information center will help when trying to find out the correct integer values to configure. Alternatively, decompiling the MQC.class in com.ibm.mq will give you the literal values associated with each constant.