The outbound WebSphere MQ Adapter parameters, accessed from the Connectivity Map, are described in the following section.
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 |
---|---|---|
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. |
|
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. |
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
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.