Use PROPCTL channel attribute to control
which message properties are included in a message that is sent from
a Version 7.5 queue manager to a
queue manager from an earlier version of WebSphere® MQ.
Table 1. Channel message property attribute
settings
PROPCTL |
Description |
ALL |
Use this option if applications connected
to the Version 6.0 queue manager are able
to process any properties placed in a message by a Version 7.5 application.
All properties
are sent to the Version 6.0 queue manager,
in addition to any name/value pairs placed in the MQRFH2 .
You
must consider two application design issues:
- An application connected to the Version 6.0 queue
manager must be able to process messages containing
MQRFH2 headers
generated on a Version 7.5 queue
manager.
- The application connected to the Version 6.0 queue
manager must process new message properties that are flagged with
MQPD_SUPPORT_REQUIRED correctly.
With the ALL channel option set, JMS
applications can interoperate between
WebSphere MQ Version 6.0 and Version 7.5 using the channel. New Version 7.5 applications using message
properties can interoperate with Version 6.0 applications,
depending on how the Version 6.0 application
handles MQRFH2 headers.
|
COMPAT |
Use this option to send message properties
to applications connected to a Version 6.0 queue
manager in some cases, but not all. Message properties are only sent
if two conditions are met:
- No property must be marked as requiring message property processing.
- At least one of the message properties must be in a
reserved folder;
see Note.
With the COMPAT channel option set, JMS applications
can interoperate between WebSphere MQ Version 6.0 and Version 7.5 using the channel.
The
channel is not available to every application using message properties,
only to those applications that use the reserved folders. The rules
concerning whether the message or the property is sent are:
- If the message has properties, but none of the properties are
associated with a
reserved folder, then no message properties
are sent.
- If any message property has been created in a
reserved property
folder, all message properties associated with the message are sent.
However:
- If any of the message properties are marked as support being required,
MQPD_SUPPORT_REQUIRED or MQPD_SUPPORT_REQUIRED_IF_LOCAL ,
the whole message is rejected. It is returned, discarded, or sent
to the dead letter queue according to the value of its report options.
- If no message properties are marked as support being required,
an individual property might not be sent. If any of the message property
descriptor fields are set to non-default values the individual property
is not sent. The message is still sent. An example of a non-default
property descriptor field value is
MQPD_USER_CONTEXT .
Note: The reserved folders names start with mcd. , jms. , usr. ,
or mqext. . These folders are created for applications
that use the JMS interface. In Version 7.5 any
name/value pairs that are placed in these folders are treated as message
properties.
Message properties are sent in an MQRFH2 header,
in addition to any name/value pairs placed in an MQRFH2 header.
Any name/value pairs placed in an MQRFH2 header are
sent as long as the message is not rejected.
|
NONE |
Use this option to prevent any message properties
being sent to applications connected to a Version 6.0 queue manager. An MQRFH2 that
contains name/value pairs and message properties is still sent, but
only with the name/value pairs.
With the NONE channel
option set, a JMS message is sent as a JMSTextMessage or
a JMSBytesMessage without any JMS message properties.
If it is possible for a Version 6.0 application
to ignore all properties set in a Version 7.5 application,
it can interoperate with it.
|