| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XA interface using JAVA |
« View previous topic :: View next topic » |
| Author |
Message
|
| rk400 |
 Posted: Sat Mar 15, 2003 12:17 am Post subject: XA interface using JAVA |
 |
|
Apprentice
Joined: 04 Mar 2003
Posts: 27
|
Hi,
I am running MQ server(5.2) and Oracle server(8.1.7) on win2k box. I am using MQ java API 5.2 to talk to MQ server.
What all should be configured for XA support??
Where can I get a document on java programming using XA???
thanx
RK |
|
| Back to top |
|
 |
| mqonnet |
| Posted: Sat Mar 15, 2003 6:43 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Check the following link.
http://www.developer.ibm.com/tech/faq/results/0,1322,1%253A401%253A407%253A35%253Amqjava,00.html#q35
When you have an external participant in your transactions you need define it accordingly. The co-ordination between the extranal co-ordinator and all the participants should be alike. And they all should be synchronous. All this happens when you configure them properly.
Check out Application programming guide. Ch 4, sample mq programs. There is a chapter called "database co-ordination sample". This explains your issue.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| Back to top |
|
|
| rk400 |
| Posted: Mon Mar 17, 2003 12:38 am Post subject: |
|
|
Apprentice
Joined: 04 Mar 2003
Posts: 27
|
Hi Kumar,
My basic question is can't we implement the 2 phase commit without XA??
Consiger the following statements.
1. Form message.
2. update DB that the message is sent and DBCOMMIT.
3. put the message in Q and MQcommit().
In the above 3 steps if db is not commited, No probs.. i will send the same message.
If mqcommit fails, i am catching the exception and udpating the db as message is not sent..
Is there any problem in by approach..
thanx
RK |
|
| Back to top |
|
|
| mqonnet |
| Posted: Mon Mar 17, 2003 5:58 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
Well, per my understanding. The main advantage of having an external transaction co-ordinator is that it does all that you are planning to do by yourself manually. And is more reliable than your app for sure.
But if there is a way out to handle this within your app, as you posted, i dont see any reason why you cant do that.
Cheers
Kumar
_________________
IBM Certified WebSphere MQ V5.3 Developer
IBM Certified WebSphere MQ V5.3 Solution Designer
IBM Certified WebSphere MQ V5.3 System Administrator |
|
| 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
|
|
|
|
