WebSphere MQ Adapter Connectivity
Map Properties
The WebSphere MQ Adapter’s Properties are organized as follows:
Note – Creating customized individual OTD configuration settings can
override the default Adapter OTD configuration settings.
Inbound WebSphere MQ Adapter Connectivity Map Properties
The inbound WebSphere MQ Adapter parameters, accessed from the Connectivity
Map, are organized into the following sections:
Inbound WebSphere MQ Adapter Settings
The Inbound WebSphere MQ Adapter Settings section of the WebSphere MQ
Adapter Connectivity Map properties contains the top-level parameters displayed
in the following table.
Table 1–21 Connectivity Map - Inbound WebSphere
MQ Adapter Settings
Name
|
Description
|
Required Value
|
Queue Name
|
Specifies the name of the queue from which messages are picked up (subscribed).
Note –
Inbound mode Adapters will not function if a non-local queue is
specified. Non-local queues include alias queues and local queue definitions
to remote queues. This limitation applies only applies to polling/receive
mode Adapters, not outbound Adapters used to retrieve messages.
|
The name of the WebSphere MQ queue.
The configured default is default.
|
Maximum Message Size
|
Specifies the maximum message size that the Adapter is able to get from
a queue. A value of zero (0) instructs the Adapter to use the MQ-provided
default size. If you specify a non-zero value, and a message on the queue
is larger than this value, one of the following will occur:
If the MQC.MQGMO_ACCEPT_TRUNCATED_MSG property is
set to True, the Adapter processes as much
of the message from the queue as possible, producing a truncated message.
If the MQC.MQGMO_ACCEPT_TRUNCATED_MSG property is
set to False, the Adapter leaves the message
on the queue and raises an MQException with a completion code of MQCC_WARNING,
and with a reason code of MQRC_TRUNCATED_MSG_FAILED.
|
A number indicating the maximum message size in bytes.
The configured default is 0 (use
the MQ defined default size).
|
Schedule Interval
|
Specifies the polling interval in milliseconds at which the subscribed
queue is polled for messages. This is the duration of the pause, in milliseconds,
between attempts to get messages from the queue.
|
The number of milliseconds at which the queue is polled.
The configured default is 5000 (or
5 seconds).
|
Security Exit
|
Specifies the optional, package qualified name of a user-defined class
that implements the com.ibm.mq.MQSecurityExit interface.
WebSphere MQ invokes an instance of the class whenever the Adapter attempts
to connect to the queue manager. The named class must include a default constructor.
This parameter is only used for client connections. Security Exits are
not applicable to bindings connections.
For more information about Security Exits, see the IBM document, WebSphere MQ Using Java (CSQZAW09) regarding MQSecurityExit.
|
The name of the user-defined class. This property also requires an assigned
value for the Security Exit Jar Classpath property.
|
Security Exit JAR Classpath
|
Specifies the absolute path to the JAR file that contains the named
Security Exit. This property is required if the Security Exit is specified.
The specified JAR is packaged into the application (EAR) file that is
generated during Project activation. If the specified JAR cannot be accessed
or found, the activation will fail.
If this property value is left blank, you must ensure that a JAR file
containing the Security Exit is made accessible to the runtime Environment
prior deploying the Project (for example, by manually copying the JAR file
into the Integration Server’s lib directory prior to or during the Deployment
Process).
For more information about Security Exits, see the IBM document, WebSphere MQ Using Java (CSQZAW09) regarding MQSecurityExit.
|
The absolute path for the JAR file that contains the named Security
Exit class.
|
Inbound WebSphere MQ Adapter Settings with GetMessageOptions
and matchOptions
The Inbound Adapter Settings with GetMessageOptions and matchOptions
section of the WebSphere MQ Adapter Connectivity Map properties contains the
top-level parameters displayed in the following table.
Table 1–22 Connectivity Map - Inbound WebSphere
MQ Adapter Settings with GetMessageOptions and matchOptions
Name
|
Description
|
Required Value
|
correlationId
|
Specifies the correlation identifier of the message to be retrieved.
Normally the queue manager returns the first message with a message identifier
and correlation identifier that matches the identifiers specified.
|
The correlation identifier of the message.
|
groupId
|
Specifies the byte string that identifies the message group to which
the physical message belongs.
|
A byte string that indicates the message group.
|
messageId
|
For an MQGET call, this field specifies the message identifier of the
message to be retrieved. Normally, the queue manager returns the first message
with a message identifier and correlation identifier that matches those identifiers
specified.
For an MQPUT call, this specifies the message identifier to use.
|
The message identifier.
|
messageSequenceNumber
|
Specifies the sequence number of a logical message within a group.
|
The sequence number of the logical message within a group.
The configured default is 1.
|
MQMO_MATCH_CORREL_ID
|
Specifies that the retrieved message must have a correlation identifier
that matches the value of the correlationId parameter.
The values are:
-
True: Indicates that the
message must have a matching correlation identifier.
-
False: Indicates that the
correlation identifier is ignored and any correlation identifier will be accepted.
This match is in addition to any other matches that may apply
(for example, the message identifier).
|
True or False.
The configured default is False.
|
MQMO_MATCH_GROUP_ID
|
Specifies that the retrieved message must have a group identifier that
matches the value of the groupId parameter.
The values are:
-
True: Indicates that the
message must have a matching group identifier.
-
False: Indicates that the
group identifier is ignored and any group identifier is accepted.
This
match is in addition to any other matches that may apply (for example, the
correlation identifier).
|
True or False.
The configured default is False.
|
MQMO_MATCH_MSG_ID
|
Specifies that the retrieved message must have a message identifier
that matches the value of the messageId parameter.
The values are:
-
True: Indicates that the
message must have a matching message identifier.
-
False: Indicates that the
message identifier is ignored and any message identifier is accepted.
This match is in addition to any other matches that may apply (for example,
the correlation identifier).
|
True or False.
The configured default is False.
|
MQMO_MATCH_MSG_SEQ_NUMBER
|
Specifies that the retrieved message must have a message sequence number
that matches the value of the messageSequenceNumber parameter.
The values are:
-
True: Indicates that the
message must have a matching message sequence number.
-
False: Indicates that the
message sequence number is ignored and any message sequence number is accepted.
This match is in addition to any other matches that may apply (for example,
the group identifier).
|
True or False.
The configured default is False.
|
MQMO_NONE
|
Specifies that no matches are to be used in selecting the message to
be returned. All messages on the queue are eligible for retrieval (subject
to some MQGMO_ options...).
|
True or False.
The configured default is True.
|
Inbound WebSphere MQ Adapter Settings with GetMessageOptions
and options
The Inbound Adapter Settings with GetMessageOptions and options section
of the WebSphere MQ Adapter Connectivity Map properties contains the top-level
parameters displayed in the following table.
Table 1–23 Connectivity Map - Inbound Adapter
Settings with GetMessageOptions and options
Name
|
Description
|
Required Value
|
MQGMO_ACCEPT_TRUNCATED_MSG
|
Specifies whether a truncated message is accepted as a complete message.
If the message buffer is too small to hold the complete message, this option
allows the MQGET call to fill the buffer with as much as it can hold and complete
its processing. Without this option, in the given situation, the MQGET call
will still be filled to capacity, but the processing will not be considered
completed. The values are:
|
True or False.
The configured default is True.
|
MQGMO_FAIL_IF_QUIESCING
|
Forces the MQGET call to fail if the queue manager is in the quiescing
state. The values are:
|
True or False.
The configured default is True.
|
MQGMO_SYNCPOINT
|
Forces the MQGET call to get the message under syncpoint control; the
message is marked as being unavailable to other applications, but it is deleted
from the queue only when the unit of work is committed. The message is made
available again if the unit of work is backed out. The values are:
-
True: Indicates that calling
MQGET gets the message under syncpoint control.
-
False: Indicates that MQGET,
when called does not get the message under syncpoint control.
|
True or False.
The configured default is False.
|
MQGMO_SYNCPOINT_IF_PERSISTENT
|
Forces the MQGET call to get the message under syncpoint control if
the message is persistent. The values are:
-
True: Indicates that calling
MQGET gets the message under syncpoint control if the message is persistent.
-
False: Indicates that MQGET,
when called does not get the message under syncpoint control if the message
is persistent.
|
True or False.
The configured default is False.
|
MQGMO_COMPLETE_MSG
|
Specifies that only a complete logical message can be returned by calling
MQGET. If the logical message is segmented, the queue manager reassembles
the segments and returns the complete logical message to the application;
the fact that the logical message was segmented is not apparent to the Adapter.
The values are:
|
True or False.
The configured default is False.
|
MQGMO_WAIT
|
Specifies that an MQ GET call waits (block and/or suspend) until a message
becomes available in the queue. The values are:
|
True or False.
The configured default is False.
|
waitInterval
|
Specifies how long (in milliseconds) an MQ GET call waits for a message
to become available in the queue. This parameter is used in conjunction with
MQGMO_WAIT. If MQGMO_WAIT
is set to false, waitInterval is not used.
Specifying a negative value indicates that the wait will last indefinitely.
Setting this value to a negative number causes the polling Adapter to
execute MQ GET calls with a wait interval of MQWI_UNLIMITED. With this type of get call, the Adapter will block
indefinitely until a suitable message is available. If the Integration Server
(in association with the Application Server) is commanded to shut down or
restart while the Adapter is still blocked, the Integration Server will not
be able to proceed until the Adapter is unblocked by the availability of a
suitable MQ message.
The same limitation affects the non-polling use of the Adapter. The
WebSphere MQ Adapter’s OTD GMO structure exposes a method named setUnlimitedWait() to Java Collaborations that, when
used, sets the waitInterval to the value MQWI_UNLIMITED. If using setUnlimitedWait() causes the Adapter to block indefinitely during a subsequent get
call, the Integration Server will be unable to shut down until the Adapter
is unblocked.
|
A number indicating the period of time, in milliseconds, that an MQ
GET call waits for a message to become available in the queue.
The configured default is 0.
|
Outbound WebSphere MQ Adapter XA Connectivity Map
Properties
The outbound WebSphere MQ Adapter XA parameters, accessed from the Connectivity
Map, are contained in the following section.
Outbound WebSphere MQ Adapter (XA) Settings
The Outbound Adapter (XA) Settings section of the WebSphere MQ Adapter
Connectivity Map properties contains the top-level parameters displayed in
the following table.
Table 1–24 Connectivity Map - Outbound Adapter
Settings
Name
|
Description
|
Required Value
|
Queue Name
|
Specifies the name of queue to which the message is published. This
parameter is optional. The queue name may also be specified manually in the
Business Process or Collaboration that effects the put.
|
The queue name to which the message is retrieved or published.
|
Security Exit
|
Specifies the optional, package qualified name of a user-defined class
that implements the com.ibm.mq.MQSecurityExit interface.
WebSphere MQ invokes an instance of the class whenever the Adapter attempts
to connect to the queue manager. The named class must include a default constructor.
This parameter is only used for client connections. Security Exits are
not applicable to bindings connections.
For more information about Security Exits, see the IBM document, WebSphere MQ Using Java (CSQZAW09) regarding MQSecurityExit.
|
The name of the user-defined class. This property also requires an assigned
value for the Security Exit JAR Classpath property.
|
Security Exit JAR
Classpath
|
Specifies the absolute path to the JAR file that contains the named
Security Exit. This property is required if the Security Exit is specified.
The specified JAR is packaged into the application (EAR) file that is
generated during Project activation. If the specified JAR cannot be accessed
or found, the activation will fail.
If this property value is left blank, you must ensure that a JAR file
containing the Security Exit is made accessible to the runtime Environment
prior deploying the Project (for example, by manually copying the JAR file
into the Integration Server’s lib directory prior to or during the Deployment
Process).
For more information about Security Exits, see the IBM document, WebSphere MQ Using Java (CSQZAW09) regarding MQSecurityExit.
|
The absolute path for the JAR file that contains the named Security
Exit class.
|
Outbound WebSphere MQ Adapter (XA) Settings with
Queue Open Options
The Outbound Adapter Settings with Queue Open Options section of the
WebSphere MQ Adapter Connectivity Map properties contains the top-level parameters
displayed in the following table. These properties apply specifically to the MQOPEN calls.
Table 1–25 Connectivity Map - Outbound Adapter
Settings with Queue Open Options
Name
|
Description
|
Required Value
|
MQOO_ALTERNATE_USER_AUTHORITY
|
Specifies whether an alternate user identifier is used to check the
authorization for the open.
True indicates that and alternate
user identifier is used.
|
True or False.
The configured default is False.
|
MQOO_BIND_AS_Q_DEF
|
Specifies whether the binding used for the queue handle is taken from
the DefBind queue attribute.
True indicates that the binding used
is taken from DefBind queue attribute.
|
True or False.
The configured default is False.
|
MQOO_BIND_NOT_FIXED
|
Specifies whether the local queue manager binds the queue handle to
a particular instance of the destination queue, when the object being opened
is a cluster queue.
True indicates that the local queue
manager will bind to a specific destination.
This option is ignored when specified for a queue that is not a cluster
queue.
|
True or False.
The configured default is False.
|
MQOO_BIND_ON_OPEN
|
Specifies whether the local queue manager binds the queue handle to
a particular instance of the destination queue, when the object being opened
is a cluster queue.
True indicates that the local queue
manager will not bind to a specific destination.
This option is ignored when specified for a queue that is not a cluster
queue.
|
True or False.
The configured default is False.
|
MQOO_BROWSE
|
Specifies whether the queue is opened to browse messages.
True indicates that the queue is
open for use with MQGET calls with the following options:
|
True or False.
The configured default is False.
|
MQOO_FAIL_IF_QUIESCING
|
Specifies whether the MQOPEN call fails when the queue manager is in
quiescing state. Used to control authorization checking.
True indicates that the MQOPEN call
will fail if queue manager is quiescing.
|
True or False.
The configured default is False.
|
MQOO_INPUT_AS_Q_DEF
|
Specifies whether the queue is opened to browse messages using the queue-defined
default.
True indicates that the queue is
open for use with subsequent MQGET calls.
Note –
The value of this parameter is ignored when the Adapter is operating
in automatic connection mode, because the Adapter must be capable of both
receiving and sending messages.
|
True or False.
The configured default is True.
|
MQOO_INPUT_EXCLUSIVE
|
Specifies whether the queue is opened to get messages with exclusive
access.
True indicates that the queue is
open for use with subsequent MQGET calls. Calls will fail with reason code
MQRC_OBJECT_IN_USE if the queue is currently used (open) by this or another
application for input of any type.
|
True or False.
The configured default is False.
|
MQOO_INPUT_SHARED
|
Specifies whether the queue is opened to get messages with shared access.
True indicates that the queue is
open for use with subsequent MQGET calls. Calls will succeed, even when the
queue is currently used (open) by this or another application for input of
any type.
|
True or False.
The configured default is False.
|
MQOO_INQUIRE
|
Specifies whether the object is opened to inquire attributes.
True indicates that the queue, name
list, process definition, or queue manager is open for use with subsequent
MQINQ calls.
|
True or False.
The configured default is True.
|
MQOO_OUTPUT
|
Specifies whether the object is opened to put messages.
True indicates that MQOPEN call can
succeed, even if the InhibitPut queue attribute is set to MQQA_PUT_INHIBITED
(though subsequent MQPUT calls will fail).
Note –
The value of this parameter is ignored when the Adapter is operating
in automatic connection mode, because the Adapter must be capable of both
receiving and sending messages.
|
True or False.
The configured default is True.
|
MQOO_PASS_ALL_CONTEXT
|
Specifies whether to allow all context to pass.
True indicates that the MQPMO_PASS_ALL_CONTEXT
option is specified in the PutMsgOpts parameter when a message is put on a
queue, and gives the message identity and origin context information from
an input queue opened with the MQOO_SAVE_ALL_CONTEXT option.
True also indicates that MQOO_PASS_IDENTITY_CONTEXT
is implied and does not need to be specified.
|
True or False.
The configured default is False.
|
MQOO_PASS_IDENTITY_CONTEXT
|
Specifies whether to allow identity context to pass.
True indicates that the MQPMO_PASS_IDENTITY_CONTEXT
option to be specified in the PutMsgOpts parameter
when a message is put on a queue. This gives the message the identity context
information from an input queue opened with the MQOO_SAVE_ALL_CONTEXT option.
True indicates that the MQOO_OUTPUT
option must be specified.
|
True or False.
The configured default is False.
|
MQOO_RESOLVE_NAMES
|
Specifies MQOO_RESOLVE_NAMES.
Select True if you want to use the
resolved queue manager name and resolved queue name attributes of the ImqQueue
class.
|
True or False.
The configured default is False.
|
MQOO_SAVE_ALL_CONTEXT
|
Specifies whether to save context when message is retrieved.
True indicates that context is saved.
Context information is associated with this queue handle and set from the
context of any message retrieved using this handle.
|
True or False.
The configured default is False.
|
MQOO_SET
|
Specifies whether the queue is open to set attributes.
True indicates that the queue is
open to set attributes and for use with subsequent MQSET calls.
|
True or False.
The configured default is False.
|
MQOO_SET_ALL_CONTEXT
|
Specifies whether to allow all context to be set.
True indicates that all context can
be set. The MQPMO_SET_ALL_CONTEXT option is specified in the PutMsgOpts parameter
when a message is put on a queue. Gives the identity and origin context information
contained in the MsgDesc parameter specified on the MQPUT or MQPUT1 call to
the message.
|
True or False.
The configured default is False.
|
MQOO_SET_IDENTITY_CONTEXT
|
Specifies whether to allow identity context to be set.
True indicates that identity context
can be set. The MQPMO_SET_IDENTITY_CONTEXT option can be specified in the
PutMsgOpts parameter when a message is put on a queue. Gives the identity
and origin context information contained in the MsgDesc parameter specified
on the MQPUT or MQPUT1 call to the message.
|
True or False.
The configured default is False.
|
Outbound WebSphere MQ Adapter Connectivity Map Properties
The outbound WebSphere MQ Adapter parameters, accessed from the Connectivity
Map, are described in the following section.
Outbound WebSphere MQ Adapter Settings
The Outbound Adapter Settings section of the WebSphere MQ Adapter Connectivity
Map properties contains the top-level parameters displayed in the following
table.
Table 1–26 Connectivity Map - Outbound Adapter
Settings with GetMessageOptions and options
Name
|
Description
|
Required Value
|
Queue Name
|
Specifies the name of queue to which the message is published. This
parameter is optional. The queue name may also be specified manually in the
Business Process or Collaboration that effects the put.
|
The queue name to which the message is retrieved or published.
|
Security Exit
|
Specifies the optional, package qualified name of a user-defined class
that implements the com.ibm.mq.MQSecurityExit interface.
WebSphere MQ invokes an instance of the class whenever the Adapter attempts
to connect to the queue manager. The named class must include a default constructor.
This parameter is only used for client connections. Security Exits are
not applicable to bindings connections.
For more information about Security Exits, see the IBM document, WebSphere MQ Using Java (CSQZAW09) regarding MQSecurityExit.
|
The name of the user-defined class. This property also requires an assigned
value for the Security Exit JAR Classpath property.
|
Security Exit JAR Classpath
|
Specifies the absolute path to the JAR file that contains the named
Security Exit. This property is required if the Security Exit is specified.
The specified JAR is packaged into the application (EAR) file that is
generated during Project activation. If the specified JAR cannot be accessed
or found, the activation will fail.
If this property value is left blank, you must ensure that a JAR file
containing the Security Exit is made accessible to the runtime Environment
prior deploying the Project (for example, by manually copying the JAR file
into the Integration Server’s lib directory prior to or during the Deployment
Process).
For more information about Security Exits, see the IBM document, WebSphere MQ Using Java (CSQZAW09) regarding MQSecurityExit.
|
The absolute path for the JAR file that contains the named Security
Exit class.
|
Outbound WebSphere MQ Adapter Settings with Queue
Open Options
The Outbound Adapter Settings with Queue Open Options section of the
WebSphere MQ Adapter Connectivity Map properties contains the top-level parameters
displayed in the following table. These properties apply specifically to the MQOPEN calls.
Table 1–27 Connectivity Map - Outbound Adapter
Settings with Queue Open Options
Name
|
Description
|
Required Value
|
MQOO_ALTERNATE_USER_AUTHORITY
|
Specifies whether an alternate user identifier is used to check the
authorization for the open.
True indicates that and alternate
user identifier is used.
|
True or False.
The configured default is False.
|
MQOO_BIND_AS_Q_DEF
|
Specifies whether the binding used for the queue handle is taken from
the DefBind queue attribute.
True indicates that the binding used
is taken from DefBind queue attribute.
|
True or False.
The configured default is False.
|
MQOO_BIND_NOT_FIXED
|
Specifies whether the local queue manager binds the queue handle to
a particular instance of the destination queue, when the object being opened
is a cluster queue.
True indicates that the local queue
manager will bind to a specific destination.
This option is ignored when specified for a queue that is not a cluster
queue.
|
True or False.
The configured default is False.
|
MQOO_BIND_ON_OPEN
|
Specifies whether the local queue manager binds the queue handle to
a particular instance of the destination queue, when the object being opened
is a cluster queue.
True indicates that the local queue
manager will not bind to a specific destination.
This option is ignored when specified for a queue that is not a cluster
queue.
|
True or False.
The configured default is False.
|
MQOO_BROWSE
|
Specifies whether the queue is opened to browse messages.
True indicates that the queue is
open for use with MQGET calls with the following options:
|
True or False.
The configured default is False.
|
MQOO_FAIL_IF_QUIESCING
|
Specifies whether the MQOPEN call fails when the queue manager is in
quiescing state. Used to control authorization checking.
True indicates that the MQOPEN call
will fail if queue manager is quiescing.
|
True or False.
The configured default is False.
|
MQOO_INPUT_AS_Q_DEF
|
Specifies whether the queue is opened to browse messages using the queue-defined
default.
True indicates that the queue is
open for use with subsequent MQGET calls.
Note –
The value of this parameter is ignored when the Adapter is operating
in automatic connection mode, because the Adapter must be capable of both
receiving and sending messages.
|
True or False.
The configured default is True.
|
MQOO_INPUT_EXCLUSIVE
|
Specifies whether the queue is opened to get messages with exclusive
access.
True indicates that the queue is
open for use with subsequent MQGET calls. Calls will fail with reason code
MQRC_OBJECT_IN_USE if the queue is currently used (open) by this or another
application for input of any type.
|
True or False.
The configured default is False.
|
MQOO_INPUT_SHARED
|
Specifies whether the queue is opened to get messages with shared access.
True indicates that the queue is
open for use with subsequent MQGET calls. Calls will succeed, even when the
queue is currently used (open) by this or another application for input of
any type.
|
True or False.
The configured default is False.
|
MQOO_INQUIRE
|
Specifies whether the object is opened to inquire attributes.
True indicates that the queue, name
list, process definition, or queue manager is open for use with subsequent
MQINQ calls.
|
True or False.
The configured default is True.
|
MQOO_OUTPUT
|
Specifies whether the object is opened to put messages.
True indicates that MQOPEN call can
succeed, even if the InhibitPut queue attribute is set to MQQA_PUT_INHIBITED
(though subsequent MQPUT calls will fail).
Note –
The value of this parameter is ignored when the Adapter is operating
in automatic connection mode, because the Adapter must be capable of both
receiving and sending messages.
|
True or False.
The configured default is True.
|
MQOO_PASS_ALL_CONTEXT
|
Specifies whether to allow all context to pass.
True indicates that the MQPMO_PASS_ALL_CONTEXT
option is specified in the PutMsgOpts parameter when a message is put on a
queue, and gives the message identity and origin context information from
an input queue opened with the MQOO_SAVE_ALL_CONTEXT option.
True also indicates that MQOO_PASS_IDENTITY_CONTEXT
is implied and does not need to be specified.
|
True or False.
The configured default is False.
|
MQOO_PASS_IDENTITY_CONTEXT
|
Specifies whether to allow identity context to pass.
True indicates that the MQPMO_PASS_IDENTITY_CONTEXT
option to be specified in the PutMsgOpts parameter when a message is put on
a queue. This gives the message the identity context information from an input
queue opened with the MQOO_SAVE_ALL_CONTEXT option.
True indicates that the MQOO_OUTPUT
option must be specified.
|
True or False.
The configured default is False.
|
MQOO_RESOLVE_NAMES
|
Specifies MQOO_RESOLVE_NAMES.
Select True if you want to use the
resolved queue manager name and resolved queue name attributes of the ImqQueue
class.
|
True or False.
The configured default is False.
|
MQOO_SAVE_ALL_CONTEXT
|
Specifies whether to save context when message is retrieved.
True indicates that context is saved.
Context information is associated with this queue handle and set from the
context of any message retrieved using this handle.
|
True or False.
The configured default is False.
|
MQOO_SET
|
Specifies whether the queue is open to set attributes.
True indicates that the queue is
open to set attributes and for use with subsequent MQSET calls.
|
True or False.
The configured default is False.
|
MQOO_SET_ALL_CONTEXT
|
Specifies whether to allow all context to be set.
True indicates that all context can
be set. The MQPMO_SET_ALL_CONTEXT option is specified in the PutMsgOpts parameter
when a message is put on a queue. Gives the identity and origin context information
contained in the MsgDesc parameter specified on the MQPUT or MQPUT1 call to
the message.
|
True or False.
The configured default is False.
|
MQOO_SET_IDENTITY_CONTEXT
|
Specifies whether to allow identity context to be set.
True indicates that identity context
can be set. The MQPMO_SET_IDENTITY_CONTEXT option can be specified in the
PutMsgOpts parameter when a message is put on a queue. Gives the identity
and origin context information contained in the MsgDesc parameter specified
on the MQPUT or MQPUT1 call to the message.
|
True or False.
The configured default is False.
|
Running XA Transactions in Client (Outbound) Mode
The outbound WebSphere MQ Adapter supports XA transactions with WebSphere
MQ Manager servers running on Solaris, AIX, HP-UX, Linux or Windows (not supported
for OS/400 or z/OS). If your Sun Java Composite Application Platform Suite
is installed on a different computer than your WebSphere MQ server, XA mode
requires that you first install the WebSphere MQ base client, and then the
WebSphere MQ Extended Transactional client, on the Application Server.
The transaction manager of the WebSphere MQ Adapter in XA mode, runs
in the Sun Integration Server. The Integration Server (IS) requires two JAR
files, com.ibm.mq.jar and com.ibm.mqetclient.jar, to be added to the Integration
Server classpath..
The IBM document WebSphere MQ External Transactional Clients,
provides information on distributed XA transactions and limitations, such
as WebSphere MQ API that cannot be issued in XA mode.
According to IBM, when using the WebSphere MQ Extended Transactional
client, a client application can be connected to only one queue manager at
a time within a single thread. This restriction applies to the WebSphere MQ
Extended Transactional client. (The WebSphere MQ base client can be connected
to more than one queue manager concurrently within a single thread.) For the
WebSphere MQ Adapter this means, in one deployment, you are only allowed to
have one outbound XA mode Adapter connecting to a WebSphere MQ external system.
You cannot have multiple XA outbound connections to different WebSphere MQ
external systems and expect the Integration Server Transactional manager to
handle XA transaction for multiple WebSphere MQ queue managers.