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.
Connectivity Map - Outbound Adapter Settings with GetMessageOptions and options
|
|
|
|
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. |
|
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.
Connectivity Map - Outbound Adapter Settings with Queue Open Options
|
|
|
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.