| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JCA and MQ |
« View previous topic :: View next topic » |
| Author |
Message
|
| George Carey |
 Posted: Mon Jun 02, 2008 3:23 pm Post subject: JCA and MQ |
 |
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
From the IBM MQSeries V6 Information Center:
"The WebSphere MQ resource adapter
The J2EE Connector Architecture (JCA) provides a standard way of connecting applications running in a J2EE environment to an Enterprise Information System (EIS) such as WebSphere MQ or DB2. The WebSphere MQ resource adapter implements the JCA 1.5 interfaces, and allows JMS applications and message driven beans (MDBs), running in an application server, to access the resources of a WebSphere MQ queue manager. The resource adapter supports both the point-to-point domain and the publish/subscribe domain.
The WebSphere MQ resource adapter supports two types of communication between an application and a queue manager: ..."
Does the IBM WSMQ Resource Adapter give any J2EE 1.4 compliant app server a 2PhaseCommit capability for app server EJBs to remote external MQ QMGR(i.e. MQ Client connection) or is the ETC product still needed to allow a 2PhaseCommit work, say between MQ Q and a DB. (note not WAS but say OC4J app server)??
TIA
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Jun 02, 2008 7:28 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20696
Location: LI,NY
|
If you read further in the manual it states that (IIRC) (from memory):
For WAS (WebSphere Application Server V 6.x) the ETC client is not needed.
For any other J2EE app server the etc client is needed if the MQServer is not local to the appserver (i.e. on the same machine) and in a "bindings" (vs client) connection.
I'd rely on the documentation here... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| George Carey |
| Posted: Tue Jun 03, 2008 9:54 am Post subject: IIRC |
|
|
Knight
Joined: 29 Jan 2007
Posts: 500
Location: DC
|
Yes, youir memory is correct under the paragraph titled:
Installation of the WebSphere MQ resource adapter
is the following info for transactional connections:
| Quote: |
Distributed transactions are supported by default in bindings mode but, in client mode, they are supported only in the following cases:
If you are using WebSphere Application Server, Version 6.0. For any other application server, if the extended transactional client JAR file, com.ibm.mqetclient.jar, is in the class path Table 2 summarizes the support for non-transacted and transacted connections. For an explanation of client and bindings modes, see Connection options.
Table 2.
Support for non-transacted and transacted connections
Type of connection ..... Non-transacted connections ....Transacted connections
Client mode ...................Supported by default ..............Supported if you are using WebSphere Application Server, Version 6.0 or if com.ibm.mqetclient.jar is in the class path
Bindings mode ...............Supported if the JNI libraries .....Supported if the JNI libraries are in the System Path
.....................................are in the System Path
The WebSphere MQ resource adapter and the version of WebSphere MQ Java used by the resource adapter must be at the same release level. |
Wonder if MQ V7.0 is same or changed ?
_________________
"Truth is ... grasping the virtually unconditioned",
Bernard F. Lonergan S.J.
(from book titled "Insight" subtitled "A Study of Human Understanding") |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
