Using ATMI and tuxedo to institue distributed transactions across multiple DBs

Question

I am creating the framework for a given application that needs to ensure that data
integrity is maintained spanning multiple databases not necessarily within an
instance of weblogic. In other words, I need to basically have 2 phase commit
"internet transactions" between a given coordinator and n participants without
having any real knowlegde of their internal system.
Originally I was thinking of using Weblogic but it appears that I may need to
have all my particular data stores registered with my weblogic instance. This
cannot be the case as I will not have access to that information for the other
participating sytems.
I next thought I would write my own TP...ouch. Everytime I get through another
iteration I kept hitting the same issue of falling into an infinite loop trying
to ensure that my coordinator and the set of participants were each able to perform
the directed action.
My next attempt has led me to the world of ATMI. Would ATMI be able to help me
here. Granted I am using JAVA so I am assuming that I would have to use CORBA
to make the calls but will ATMI enable me to truly manage and create distributed
transactions across multiple databases. Please, any advice at all would be greatly
appreciated.
Thanks
Chris

Answer 1

Andy
I will not have multiple instances of weblogic as I cannot enfore that
the other participants involved in the transaction have weblogic as
their application server. That being said, I may not have the choice
but to use WTC.
Does this make more sense?
Andy Piper <[email protected]> wrote in message news:<[email protected]>...
"Chris" <[email protected]> writes:
I am creating the framework for a given application that needs to ensure that data
integrity is maintained spanning multiple databases not necessarily within an
instance of weblogic. In other words, I need to basically have 2 phase commit
"internet transactions" between a given coordinator and n participants without
having any real knowlegde of their internal system.
Originally I was thinking of using Weblogic but it appears that I may need to
have all my particular data stores registered with my weblogic instance. This
cannot be the case as I will not have access to that information for the other
participating sytems.I don't really understand this. From 6.0 onwards you can do 2PC
between weblogic instances, so as long as the things you are calling
are transaction (EJBs for instance) it should all work out fine.
I next thought I would write my own TP...ouch. Everytime I get through another
iteration I kept hitting the same issue of falling into an infinite loop trying
to ensure that my coordinator and the set of participants were each able to perform
the directed action.
My next attempt has led me to the world of ATMI. Would ATMI be able to help me
here. Granted I am using JAVA so I am assuming that I would have to use CORBA
to make the calls but will ATMI enable me to truly manage and create distributed
transactions across multiple databases. Please, any advice at all would be greatly
appreciated.I don't see that ATMI would give you anything different. Transaction
management Tux is fairly similar to WebLogic (it was written by the
same people). If you are trying to do interposed transactions
(i.e. multiple co-ordinators) then WTC would give you this but it is
only a beta feature in WLS 6.1. Using Tux domain gateways would also
give you interposed behaviour but would require you write your servers
in C or C++ ....
andy