A reference architecture for cooperative transaction processing systems

Rolf de By, Aarno Lehtola, Olli Pihlajamaa, Jari Veijalainen, Jürgen Wäsch

    Research output: Book/ReportReport

    Abstract

    This report presents a reference architecture for cooperative transaction processing systems. The architecture was developed in the ESPRIT III basic research project TransCoop (EP8012). The reference architecture provides a general framework, which covers the architectural needs of three application domains, namely cooperative authoring, design for manufacturing, and workflow management. The architecture may have many instantiations in concrete cooperative transaction processing systems. Some components or functionalities can be pruned if they are not needed in a particular implementation of the architecture. The components of the architecture interact through protocols defined in terms of function calls. The embedded data flows comply with an object model common to all components. In practice, the functions can be implemented in many ways, as long as the external behaviour complies with the specifications. The protocols may span over a computer network, i.e. both distributed and centralized realizations are possible. The requirements analysis of the three application domains has pointed out that cooperative applications are developed iteratively. The development process is fairly isolated from the execution phase and results in a specification which may be instantiated in a run-time environment many times. Thus, the reference architecture consists of two major components, a specification environment and a run-time environment. The specification environment contains tools for editing application scenarios, verifying and simulating them, and compiling them into representations used by the run-time environment. The run-time environment has a transaction management support system as its central component. It has a homogeneous interface to agents and to an object storage interface mapper, through which it interacts with its environment. The transaction management support system supervises many concurrent cooperative scenario instances guaranteeing the transactional properties specified for them. An agent of the run-time environment may have the pure functionality of a client towards the transaction management support system, whereas in certain cooperative scenarios they may behave as servers towards it. There are agents representing end-users of the applications. Some agents represent remote sites, while others represent programs which either use - or are used by - the cooperative scenarios. The run-time environment can be replicated and the instances can be made to cooperate. The architecture is scalable.
    Original languageEnglish
    Place of PublicationEspoo
    PublisherVTT Technical Research Centre of Finland
    Number of pages103
    ISBN (Print)951-38-4849-3
    Publication statusPublished - 1995
    MoE publication typeNot Eligible

    Publication series

    SeriesVTT Tiedotteita - Meddelanden - Research Notes
    Number1694
    ISSN1235-0605

    Fingerprint

    Specifications
    Processing
    Network protocols
    Computer networks
    Servers
    Concretes

    Keywords

    • architecture
    • software
    • computer programs
    • cooperation
    • cooperative systems
    • transactions
    • wordflows
    • design
    • authoring

    Cite this

    de By, R., Lehtola, A., Pihlajamaa, O., Veijalainen, J., & Wäsch, J. (1995). A reference architecture for cooperative transaction processing systems. Espoo: VTT Technical Research Centre of Finland. VTT Tiedotteita - Meddelanden - Research Notes, No. 1694
    de By, Rolf ; Lehtola, Aarno ; Pihlajamaa, Olli ; Veijalainen, Jari ; Wäsch, Jürgen. / A reference architecture for cooperative transaction processing systems. Espoo : VTT Technical Research Centre of Finland, 1995. 103 p. (VTT Tiedotteita - Meddelanden - Research Notes; No. 1694).
    @book{34e61ca08d844fa1a4c5a5d9a28f7a74,
    title = "A reference architecture for cooperative transaction processing systems",
    abstract = "This report presents a reference architecture for cooperative transaction processing systems. The architecture was developed in the ESPRIT III basic research project TransCoop (EP8012). The reference architecture provides a general framework, which covers the architectural needs of three application domains, namely cooperative authoring, design for manufacturing, and workflow management. The architecture may have many instantiations in concrete cooperative transaction processing systems. Some components or functionalities can be pruned if they are not needed in a particular implementation of the architecture. The components of the architecture interact through protocols defined in terms of function calls. The embedded data flows comply with an object model common to all components. In practice, the functions can be implemented in many ways, as long as the external behaviour complies with the specifications. The protocols may span over a computer network, i.e. both distributed and centralized realizations are possible. The requirements analysis of the three application domains has pointed out that cooperative applications are developed iteratively. The development process is fairly isolated from the execution phase and results in a specification which may be instantiated in a run-time environment many times. Thus, the reference architecture consists of two major components, a specification environment and a run-time environment. The specification environment contains tools for editing application scenarios, verifying and simulating them, and compiling them into representations used by the run-time environment. The run-time environment has a transaction management support system as its central component. It has a homogeneous interface to agents and to an object storage interface mapper, through which it interacts with its environment. The transaction management support system supervises many concurrent cooperative scenario instances guaranteeing the transactional properties specified for them. An agent of the run-time environment may have the pure functionality of a client towards the transaction management support system, whereas in certain cooperative scenarios they may behave as servers towards it. There are agents representing end-users of the applications. Some agents represent remote sites, while others represent programs which either use - or are used by - the cooperative scenarios. The run-time environment can be replicated and the instances can be made to cooperate. The architecture is scalable.",
    keywords = "architecture, software, computer programs, cooperation, cooperative systems, transactions, wordflows, design, authoring",
    author = "{de By}, Rolf and Aarno Lehtola and Olli Pihlajamaa and Jari Veijalainen and J{\"u}rgen W{\"a}sch",
    year = "1995",
    language = "English",
    isbn = "951-38-4849-3",
    series = "VTT Tiedotteita - Meddelanden - Research Notes",
    publisher = "VTT Technical Research Centre of Finland",
    number = "1694",
    address = "Finland",

    }

    de By, R, Lehtola, A, Pihlajamaa, O, Veijalainen, J & Wäsch, J 1995, A reference architecture for cooperative transaction processing systems. VTT Tiedotteita - Meddelanden - Research Notes, no. 1694, VTT Technical Research Centre of Finland, Espoo.

    A reference architecture for cooperative transaction processing systems. / de By, Rolf; Lehtola, Aarno; Pihlajamaa, Olli; Veijalainen, Jari; Wäsch, Jürgen.

    Espoo : VTT Technical Research Centre of Finland, 1995. 103 p. (VTT Tiedotteita - Meddelanden - Research Notes; No. 1694).

    Research output: Book/ReportReport

    TY - BOOK

    T1 - A reference architecture for cooperative transaction processing systems

    AU - de By, Rolf

    AU - Lehtola, Aarno

    AU - Pihlajamaa, Olli

    AU - Veijalainen, Jari

    AU - Wäsch, Jürgen

    PY - 1995

    Y1 - 1995

    N2 - This report presents a reference architecture for cooperative transaction processing systems. The architecture was developed in the ESPRIT III basic research project TransCoop (EP8012). The reference architecture provides a general framework, which covers the architectural needs of three application domains, namely cooperative authoring, design for manufacturing, and workflow management. The architecture may have many instantiations in concrete cooperative transaction processing systems. Some components or functionalities can be pruned if they are not needed in a particular implementation of the architecture. The components of the architecture interact through protocols defined in terms of function calls. The embedded data flows comply with an object model common to all components. In practice, the functions can be implemented in many ways, as long as the external behaviour complies with the specifications. The protocols may span over a computer network, i.e. both distributed and centralized realizations are possible. The requirements analysis of the three application domains has pointed out that cooperative applications are developed iteratively. The development process is fairly isolated from the execution phase and results in a specification which may be instantiated in a run-time environment many times. Thus, the reference architecture consists of two major components, a specification environment and a run-time environment. The specification environment contains tools for editing application scenarios, verifying and simulating them, and compiling them into representations used by the run-time environment. The run-time environment has a transaction management support system as its central component. It has a homogeneous interface to agents and to an object storage interface mapper, through which it interacts with its environment. The transaction management support system supervises many concurrent cooperative scenario instances guaranteeing the transactional properties specified for them. An agent of the run-time environment may have the pure functionality of a client towards the transaction management support system, whereas in certain cooperative scenarios they may behave as servers towards it. There are agents representing end-users of the applications. Some agents represent remote sites, while others represent programs which either use - or are used by - the cooperative scenarios. The run-time environment can be replicated and the instances can be made to cooperate. The architecture is scalable.

    AB - This report presents a reference architecture for cooperative transaction processing systems. The architecture was developed in the ESPRIT III basic research project TransCoop (EP8012). The reference architecture provides a general framework, which covers the architectural needs of three application domains, namely cooperative authoring, design for manufacturing, and workflow management. The architecture may have many instantiations in concrete cooperative transaction processing systems. Some components or functionalities can be pruned if they are not needed in a particular implementation of the architecture. The components of the architecture interact through protocols defined in terms of function calls. The embedded data flows comply with an object model common to all components. In practice, the functions can be implemented in many ways, as long as the external behaviour complies with the specifications. The protocols may span over a computer network, i.e. both distributed and centralized realizations are possible. The requirements analysis of the three application domains has pointed out that cooperative applications are developed iteratively. The development process is fairly isolated from the execution phase and results in a specification which may be instantiated in a run-time environment many times. Thus, the reference architecture consists of two major components, a specification environment and a run-time environment. The specification environment contains tools for editing application scenarios, verifying and simulating them, and compiling them into representations used by the run-time environment. The run-time environment has a transaction management support system as its central component. It has a homogeneous interface to agents and to an object storage interface mapper, through which it interacts with its environment. The transaction management support system supervises many concurrent cooperative scenario instances guaranteeing the transactional properties specified for them. An agent of the run-time environment may have the pure functionality of a client towards the transaction management support system, whereas in certain cooperative scenarios they may behave as servers towards it. There are agents representing end-users of the applications. Some agents represent remote sites, while others represent programs which either use - or are used by - the cooperative scenarios. The run-time environment can be replicated and the instances can be made to cooperate. The architecture is scalable.

    KW - architecture

    KW - software

    KW - computer programs

    KW - cooperation

    KW - cooperative systems

    KW - transactions

    KW - wordflows

    KW - design

    KW - authoring

    M3 - Report

    SN - 951-38-4849-3

    T3 - VTT Tiedotteita - Meddelanden - Research Notes

    BT - A reference architecture for cooperative transaction processing systems

    PB - VTT Technical Research Centre of Finland

    CY - Espoo

    ER -

    de By R, Lehtola A, Pihlajamaa O, Veijalainen J, Wäsch J. A reference architecture for cooperative transaction processing systems. Espoo: VTT Technical Research Centre of Finland, 1995. 103 p. (VTT Tiedotteita - Meddelanden - Research Notes; No. 1694).