Otherwise, your application should be unchanged. It is also possible for XA and non-XA transactions to coexist in the same Berkeley DB environment.
Recovery is completed in two steps.
Any transactions that were prepared, but neither completed nor aborted, are restored to their prepared state so that they may be aborted or committed via the Tuxedo recovery mechanisms. After each resource manager has recovered, then Tuxedo recovery may begin. It should issue a commit or abort for each one, and only after having completed each transaction will normal processing resume. Finally, standard log file archival and catastrophic recovery procedures should occur independently of XA operation.