Author |
Message
|
nMQWF |
Posted: Thu Dec 15, 2005 10:40 pm Post subject: MQ Workflow transaction support |
|
|
 Apprentice
Joined: 02 Oct 2005 Posts: 27
|
Hi,
MQ Workflow is not providing transaction support. So when I am trying to close a work item, it gets closed and after that if there is any exception in the application those changes are getting rolled back as they are all DB updates and DB2 provides transaction support.
After this, the application shows workitem as incomplete but the workitem is no longer available in worklist.
Can someone suggest a work around for this problem.
Thanks in Advance |
|
Back to top |
|
 |
nMQWF |
Posted: Sun Dec 18, 2005 11:16 pm Post subject: |
|
|
 Apprentice
Joined: 02 Oct 2005 Posts: 27
|
Any suggestions for the same ???
Thanks in Advance... |
|
Back to top |
|
 |
sanathkumar |
Posted: Mon Dec 19, 2005 7:50 am Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003 Posts: 27
|
Hi,
My suggestion is call first all DB Updates and then call Workflow calls to close workitem. If some exception occures in application or DB rolled back, then do not call workflow calls to close workitem.In that way we can avoid your problem. If you do not get any problem in application or DB updates then call the closing the workitem in MQ Workflow.
I know this is not ur permanent solution but it helps. We are following same like We will call application stuff first any DB Updates/Inserts and later check-in the workitem.
Cheers,
sanath |
|
Back to top |
|
 |
fidelio |
Posted: Mon Dec 19, 2005 9:00 am Post subject: |
|
|
Apprentice
Joined: 14 Sep 2005 Posts: 45 Location: AttainBPM
|
How are you integrating with DB2? Have you written a UPES implementation, have you written your own client, or are you using the fat or Web client? UPES implementations are MQ programs - which provides transaction coordination support with DB2. If you have written a client implementation, you might want to consider changing to a UPES since there is much less overhead in WF (no need to logon and refresh worklists and issue check-out/check-in). |
|
Back to top |
|
 |
nMQWF |
Posted: Mon Dec 19, 2005 10:05 pm Post subject: |
|
|
 Apprentice
Joined: 02 Oct 2005 Posts: 27
|
Thanx Sanath,
But we have one more problem there.
In our implementation we are using IBM Content Manager
and IBM Directory server also which also do not support XA transaction.
There are some transactions in which all these are involved.
There is a problem when all these tools are involved.
Thanx in Advance |
|
Back to top |
|
 |
nMQWF |
Posted: Tue Jan 03, 2006 4:10 am Post subject: |
|
|
 Apprentice
Joined: 02 Oct 2005 Posts: 27
|
Hello All,
First of all
Happy New Year
Any suggestions on my problem ??
Thanx in Advance |
|
Back to top |
|
 |
|