WebSphere MQ functions not supported by service integration

There are various functions available in a WebSphere MQ network that are not available on a service integration bus.

The following list helps you identify those functions but it is given as guidance rather than a complete definition. Functions not supported include:

1. Native MQ client (this includes client applications that make use of the base MQ classes for Java) attach.

2. Message segmentation.

3. Message grouping.

4. The MQMD Offset. Original length, MsgFlags, MsgSeqNumber, and GroupId fields are not supported because Message grouping and message segmentation are not supported.

5. Distribution lists.

6. Reference messages.

7. Triggering.

8. Alternate user authority.

9. Pass/set identity context.

10. In a program, setting the attributes of a queue (that is, the equivalent function of MQSET).

11. Cluster sender/receiver channels (and cluster workload exits), because a messaging engine cannot participate in a WebSphere MQ cluster.

12. Server and requestor channels.

13. API crossing exits.

14. Data conversion exits.

15. Channel exits.

16. The equivalent to the MCAUSER and PUTAUTH fields of a channel.

17. Networks based on NetBIOS, SPX or SNA.

18. Message based command server.

19. PCF (Programmable Canonical Form messages).

20. Model queues. Service integration does not allow you to define model queues of a given name. Service integration technology supports only one model queue called the SYSTEM.DEFAULT.MODEL.QUEUE.

21. Dynamic queue name prefix length. Service integration suffixes all dynamic queue names with "_Q" and a unique id. This restricts the name specified in the dynamic queue name field of the Object Descriptor to up to 12 chars. If this name is greater than 12 characters, then it is truncated to 12 characters. In service integration, it is not possible to create a dynamic queue with the full name specified in the dynamic queue name field of the Object Descriptor.

22. Mark skip backout option.

23. Signal option on a get request.

24. Version 3 get message options structures.

25. All queue properties (the properties of a service integration destination do not map, one for one, to the properties of a WebSphere MQ local queue, for example).

26. Poisoned messages. Service integration bus local destination definitions have a maximum failed deliveries count (that is, the equivalent to the WebSphere MQ BackoutThreshold value) but there is no equivalent of the WebSphere MQ backout requeue queue name. In service integration technology, poisoned messages are instead backed out to an exception destination. Additionally, in service integration technology, when the number of times an application backs out a poisoned message is equal to the maximum failed deliveries count, the message is automatically backed out to an ExceptionDestination. If there is more than one message in the current unit of recovery, only the poisoned message is backed out to the ExceptionDestination. The remainder of the messages in the unit of recovery are backed out to the destination from which they were read.

27. A strict limitation of 48 bytes on the name of a queue. Service integration bus destination names can be greater than 48 bytes in length. If a destination name is to be returned to a WebSphere MQ JMS application, then it is important to use 48 byte destination lengths. Though, in some cases, it might be feasible to define an alias destination with a name length of up to 48 bytes to map to a local destination with a name of length greater than 48 bytes.

Reference topic