Our built-in Tomcat integration is certified to work with Tomcat (6 and 7). Available only to customers; buy now if you want to save a lot of configuration hassle and get a working fail-safe config right away.
Various members of our community have suggested different approaches as explained below. Keep in mind that none of these have been certified to work (in fact, most of them have glitches that expose risks concerning recovery of pending transactions).
You can get Atomikos running locally inside your web application. In this case you have multiple web applications the transaction manager will be replicated and need to access its own transaction logs.
See Tomcat 5.5 self-contained WAR to know how to configure this. Those guidelines are also valid for Tomcat 6.
You can install Atomikos in such a way that it integrates with Tomcat the J2EE way. In that case you only have one transaction manager shared by all web applications with a single set of transaction logs like in any classic full-blown J2EE server.
See Tomcat 5.5 Integration with Atomikos 3.2 or older to know how to configure this.
See Tomcat55Integration33 to know how to configure this.
See Tomcat6Integration to know how to configure this.
See Tomcat6Integration33 to know how to configure this.
See Tomcat6Integration35 to know how to configure this.
See Tomcat6Integration35Lifecycle to know how to configure this.
See Tomcat7Integration35 to know how to configure this.