Edit | Attach | New | Raw | Delete | History | Print | Tools

Tomcat Integration

Although our JDBC and JMS connectors are 100% JNDI-compatible, Tomcat's JNDI configuration has always seemed to require some special wiring in order to make it work (and to make things worse: this wiring has changed across different Tomcat releases). These pages attempt to shed some light on this process, and give examples on how to do it. If you have any better ideas on this, please let us know. Thanks!

There are mainly two ways to configure Atomikos and Tomcat.

Per WAR file

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.

Globally

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.

Tomcat 5.5

Atomikos 3.2 and earlier

See Tomcat 5.5 Integration with Atomikos 3.2 or older to know how to configure this.

Atomikos 3.3 and later

See Tomcat55Integration33 to know how to configure this.

Tomcat 6

Atomikos 3.2 and earlier

See Tomcat6Integration to know how to configure this.

Atomikos 3.3 and later

See Tomcat6Integration33 to know how to configure this.

Atomikos 3.5.2 and later

See Tomcat6Integration35 to know how to configure this.

Atomikos 3.5.2 and later with lifecycle support

See Tomcat6Integration35Lifecycle to know how to configure this.

Tomcat 7

Atomikos 3.5.2 and later

See Tomcat7Integration35 to know how to configure this. spacer
Copyright © 2014 Atomikos BVBA. Transaction Management for Extreme Transaction Processing and SOA Environments serving ISV, Commercial, OEM and Open Source Markets
Site map RSS ATOM