| • |
Architected for the coordination of new and existing applications |
| • |
Specifically designed for loosely coupled, heterogeneous environments |
| • |
Coordination engine is independent of the underlying communications
protocol |
| • |
Simple Java API and programming model that is easy to code and implement |
| • |
Provides traditional transactional QoS - reliable coordination and
failure recovery |
| • |
Support for fully recoverable applications
(confirmed outcomes and service checkpointing) |
| • |
Flexible resource management - applications control whether they lock
resources and, if so when and for how long |
| • |
Enables use of compensation techniques |
| • |
Provides tracking of transaction events |
| • |
Provides early detection of failures in transaction participants |
| • |
Software has minimal impact on existing applications |
| • |
Non-intrusive, flexible model fits easily with existing business
processes |
| • |
Implements OASIS BTP and WS-C+T |
| • |
Support for
multiple, concurrent long running transactions with little or no
performance degradation (Transactional Application Node Passivation) |
|
Benefits
|
| • |
Cohesions reduces the cost of implementing, maintaining and supporting
application coordination in heterogeneous environments |
| • |
Immediate reduction in manual data checking, reconciliation and
repair costs |
| • |
No need for non-repeatable, expensive hand-coded error handling |
| • |
Extends the benefits of existing transactional systems further into
the enterprise |
| • |
Lower integration costs for a transactional solution |
| • |
Improves the management of application coordination |
| • |
Ease of use and flexibility of coding skills required makes finding
maintenance and support resources an easier and cheaper task |
| • |
An open, standards based solution, providing ease of integration
with current and future systems and technologies |
| • |
Customer is protected from the business transaction interoperability
standards flux |
sitemap | contact | webinar
