JBoss Transaction Service (JBossTS) assures complete, accurate business
transactions for any Java based applications, including those written for the
Java EE and EJB frameworks.
JBossTS is a 100% Java implementation of a
distributed transaction management system
based on the Sun Microsystems Java EE Java Transaction Service (JTS) standard.
Our implementation of the JTS utilizes the Object Management Group's (OMG) Object
Transaction Service (OTS) model for transaction interoperability as recommended
in the Java EE and EJB standards. Although any JTS-compliant product will allow
Java objects to participate in transactions, one of the key features of JBossTS
is it's 100% Java implementation. This allows JBossTS to support fully distributed
transactions that can be coordinated by distributed parties.
JBossTS runs can be run both as an embedded distributed service of an application
server (e.g. JBossAS), affording the user all the added benefits of the
application server environment such as real-time load balancing, unlimited linear
scalability and unmatched fault tolerance that allows you to deliver an always-on
solution to your customers. It is also available as a free-standing Java Transaction
Service.
In addition to providing full compliance with the latest version of the JTS
specification, JBossTS leads the market in providing many advanced features such
as fully distributed transactions and ORB portability with POA support.
JBossTS is tested on HP-UX 11i, Red Hat Linux, Windows Server 2003,
and Sun Solaris 10, using Sun's JDK 5. It should howerver work on any system with JDK 5 or 6.
The Java Transaction API support for JBossTS comes in two flavours:
- a purely local implementation, that does not require an ORB, but obviously
requires all coordinated resources to reside within the same JVM.
- a fully distributed implementation.
Key features
- full compliant with the JTA 1.1 specification:
- Purely local (ORB-less) JTA offers the fastest JTA performance
- JDBC support
- XA compliance
- JDBC drivers for database access with full transaction support
- Automatic crash recovery for XAResources
- compliance with the JTS specification and OTS 1.2 specification from the
OMG
- Distributed JTA implementation
- support for distributed transactions (utilizing two-phase commit)
- POA ORB support
- interposition
- transaction heuristics
- distributed transaction manager (co-located with the transaction initiator)
or transaction manager server
- checked/unchecked transaction behaviour
- supports both flat and nested transaction models, with nested-aware
resources and resource adapters
- independent concurrency control system with support for type-specific
concurrency control
- support for CosTransaction::Current
- direct and indirect transaction management
- synchronization interface
- explicit and implicit transaction context propagation
- automatic crash recovery
- multi-thread aware
- transactional objects (TO) for Java
- ORB independence via the ORB portability layer
This trail map will help you get started with running JBoss transaction service product.
It is structured as follows:
In addition to the trails listed above, a set of trails giving more explanation on concept around
transaction processing and standards, and also a quick access to section explaining how to configure JBossTS
are listed in the section "Additional Trails".
Note:When running the local JTS transactions part of the trailmap, you will need to start
the recovery manager: java com.arjuna.ats.arjuna.recovery.RecoveryManager -test