Extend the transaction boundary of the transaction manager embedded in a JDBC compliant database to other resources which can support two-phase commit semantics such as XAResources

Where you multiplex the users application table and the transaction log in the same JDBC local transaction.

LLR
===
Resource 2 provides Coordinator

Resource1 (xar1::prepare() // sync 1
Resource2 (ds1::insert(tmLog)
ds1::commit() // sync 2)
Resource 1 (xar1::commit(); // sync 3)
Resource 1 (ds1::delete(tmLog))
ds1::commit() // sync 4 (potentally lazy)

XA
==
Resource 1 (xar1::prepare(); // sync 1)
Resource 2 (xar2::prepare(); // sync 2)
Coordinator (insert(tmLog) // sync 3)
Resource 1 (xar1::commit() // sync 4)
Resource 2 (xar2::commit() // sync 5)
Coordinator (delete(tmLog) // sync 6 (potentally lazy))