See: Description
Interface | Description |
---|---|
NativeErrorHandler |
Handle errors from native WMQ when consuming messages.
|
Class | Description |
---|---|
AbstractNativeErrorHandler |
Abstract implementation of
NativeErrorHandler |
AttachedConnection | Deprecated
since 3.11.1 without replacement since IBM recommend you use JMS instead
|
DetachedConnection | Deprecated
since 3.11.1 without replacement since IBM recommend you use JMS instead
|
ForwardingNativeConsumerErrorHandler | Deprecated
since 3.11.1 without replacement since IBM recommend you use JMS instead
|
MessageOptions | Deprecated |
MQMessageAccessor | |
MQMessageFactory |
MQMessageFactory for creating MQMessageInstance instances.
|
MQMessageOptionsAccessor | |
NativeConnection | Deprecated
since 3.11.1 without replacement since IBM recommend you use JMS instead
|
NativeConsumer | Deprecated
since 3.11.1 without replacement since IBM recommend you use JMS instead
|
NativeProducer | Deprecated
since 3.11.1 without replacement since IBM recommend you use JMS instead
|
Enum | Description |
---|---|
MQMessageFactory.MQMessageInstance |
Types of MQMEssage.
|
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.