• DocumentCode
    1366801
  • Title

    Customizing transaction models and mechanisms in a programmable environment supporting reliable workflow automation

  • Author

    Georgakopoulos, Dimitrios ; Hornick, Mark F. ; Manola, Frank

  • Author_Institution
    GTE Labs. Inc., Waltham, MA, USA
  • Volume
    8
  • Issue
    4
  • fYear
    1996
  • fDate
    8/1/1996 12:00:00 AM
  • Firstpage
    630
  • Lastpage
    649
  • Abstract
    A Transaction Specification and Management Environment (TSME) is a programmable system that supports implementation-independent specification of application-specific extended transaction models (ETMs) and configuration of transaction management mechanisms (TMMs) to enforce specified ETMs. The TSME can ensure correctness and reliability while allowing the functionality required by workflows and other advanced applications that require access to multiple heterogeneous, autonomous, and/or distributed (HAD) systems. To support ETM specification, the TSME provides a transaction specification language that describes dependencies between transactions. Unlike other ETM specification languages, TSME´s dependency descriptors use a common set of primitives, and are enforceable, i.e., can be evaluated at any time during transaction execution to determine whether operations issued violate ETM specifications. To determine whether an ETM can be enforced in a specific HAD system environment, the TSME supports specification of the transactional capabilities of HAD systems, and comparison of these with ETM specifications to determine mismatches. To enforce ETMs that are more restrictive than those supported by the union of the transactional capabilities of HAD systems, the TSME provides a collection of transactional services. These services are programmable and configurable, i.e., they accept instructions that change their behavior as required by an ETM and can be combined in specific ways to create a run-time TMM capable of enforcing the ETM. We discuss the TSME in the context of a distributed object management system. We give ETM specification examples and describe corresponding TMM configurations for a telecommunications application
  • Keywords
    distributed databases; distributed processing; object-oriented databases; office automation; open systems; specification languages; transaction processing; Transaction Specification and Management Environment; application-specific extended transaction models; correctness; dependency descriptors; distributed object management system; functionality; implementation-independent specification; programmable environment; programmable transaction management mechanisms; reliability; reliable workflow automation; specification languages; telecommunications application; transaction dependencies; transaction management mechanisms; transaction management toolkits; transaction model specification; transaction models; transactional capabilities; transactional services; transactional workflows; Application software; Automation; Business communication; Computer architecture; Concurrent computing; Costs; Distributed computing; Environmental management; Runtime; Specification languages;
  • fLanguage
    English
  • Journal_Title
    Knowledge and Data Engineering, IEEE Transactions on
  • Publisher
    ieee
  • ISSN
    1041-4347
  • Type

    jour

  • DOI
    10.1109/69.536255
  • Filename
    536255