WebSphere MQ functions not supported by service integration

This topic describes WebSphere® MQ functions that are not supported by a service integration bus

WebSphere MQ functions not available

There are various functions available in a WebSphere MQ network that are not available on a service integration bus that has a WebSphere MQ link or a WebSphere MQ client link. 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. Confirmation of arrival/delivery.
  12. Cluster sender/receiver channels (and cluster workload exits), because a messaging engine cannot participate in a WebSphere MQ cluster.
  13. Server and requestor channels.
  14. API crossing exits.
  15. Data conversion exits.
  16. Channel exits.
  17. The equivalent to the MCAUSER and PUTAUTH fields of a channel.
  18. Networks based on NetBIOS, SPX or SNA.
  19. Message based command server.
  20. PCF (Programmable Canonical Form messages).
  21. 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.
  22. Dynamic queue name prefix length. Service integration all dynamic queue names with '_Q' and suffixes them with 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.
  23. Mark skip backout option.
  24. Signal option on a get request.
  25. Version 3 get message options structures.
  26. 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).
  27. 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.
  28. 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 may 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.

Differences from WebSphere MQ delivery options

While WebSphere MQ supports persistent and nonpersistent messages, service integration supports five delivery options (also known as qualities of service (QoS).

Outbound BEST_EFFORT_NONPERSISTENT, RELIABLE_NONPERSISTENT, and EXPRESS_NONPERSISTENT messages sent to a WebSphere MQ network, are sent as nonpersistent messages in the WebSphere MQ network. Outbound RELIABLE_PERSISTENT and ASSURED_PERSISTENT messages, when sent to a WebSphere MQ network, are sent as persistent messages.

For inbound messages from a WebSphere MQ network, the inbound nonpersistent reliability (with possible values of BEST_EFFORT_NONPERSISTENT, RELIABLE_NONPERSISTENT, and EXPRESS_NONPERSISTENT) and the inbound persistent reliability (with possible values of RELIABLE_PERSISTENT and ASSURED_PERSISTENT), fields of the MQLinkReceiver channel can be set to specify the service integration delivery options to be used for nonpersistent and persistent messages.

Similarly, for inbound messages from WebSphere MQ JMS clients, the inbound nonpersistent reliability and the inbound persistent reliability fields of the MQ client link can be set to control the message persistence.




Related tasks
Designing an application for interoperation with WebSphere MQ
Reference topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 9:00:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=rjc0049
File name: rjc0049_.html