| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Difference between Server and Client WebSphereMQ API librari |
« View previous topic :: View next topic » |
| Author |
Message
|
| sivadharsan |
 Posted: Wed Jan 15, 2003 6:57 pm Post subject: Difference between Server and Client WebSphereMQ API librari |
 |
|
Newbie
Joined: 14 Jan 2003
Posts: 7
|
| What are the difference between Server and Client side WebSphereMQ API libraries? |
|
| Back to top |
|
 |
| kolban |
| Posted: Thu Jan 16, 2003 4:51 am Post subject: |
|
|
Grand Master
Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA
|
The server libraries require that your application runs on the same machine as the queue manager and provide super-fast connectivity to the queue manager.
The client libraries allow your application to run on a remote machine and provide connectivity to the queue manager over a network connection. |
|
| Back to top |
|
|
| sivadharsan |
| Posted: Thu Jan 16, 2003 5:30 am Post subject: |
|
|
Newbie
Joined: 14 Jan 2003
Posts: 7
|
| Is there any specific API differences between Server and client? |
|
| Back to top |
|
|
| fschofer |
| Posted: Thu Jan 16, 2003 6:41 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
The Client API does not support 2 Phase Commit
You can not use MQBEGIN with MQ Client
Websphere MQ Client PDF:
Using syncpoint coordination
Within WebSphere MQ, one of the roles of the queue manager is syncpoint control
within an application. If an application runs on an WebSphere MQ client, it can
issue MQCMIT and MQBACK, but the scope of the syncpoint control is limited to
the MQI resources.
Applications running in the full queue manager environment on the server can
coordinate multiple resources (for example databases) via a transaction monitor.
On the server you can use the Transaction Monitor supplied with the Version 5.1
and above MQSeries products, or another transaction monitor such as CICS. You
cannot use a transaction monitor with a client application. The WebSphere MQ
verb MQBEGIN is not valid in a client environment. |
|
| 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
|
|
|
|
