1 / 14

Transaction and Rule Support for Workflow Management - A Retrospective on the WIDE Architecture

Transaction and Rule Support for Workflow Management - A Retrospective on the WIDE Architecture. Paul Grefen CS Department & CTIT University of Twente. W orkflow on I ntelligent D istributed database E nvironment. WIDE Approach. Extended transaction support Loose global transactions (saga)

locke
Download Presentation

Transaction and Rule Support for Workflow Management - A Retrospective on the WIDE Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Transaction and Rule Supportfor Workflow Management -A Retrospective on the WIDE Architecture Paul GrefenCS Department & CTIT University of Twente

  2. Workflow on IntelligentDistributed databaseEnvironment

  3. WIDE Approach

  4. Extended transaction support • Loose global transactions (saga) • Strict local transactions (nested) • Active rule support • Decoupled execution mode • Workflow, data, external, time events • Data support • Object-oriented client interface • Relational server interface • IDL-SQL/C++ compiler support DBMS Extensions

  5. Advanced data support versus workflow support • reusability of advanced data support • Extended transaction support versusactive rule support • orthogonal and flexible semantics • adaptability of transaction/rule support • WIDE integrated workflow system vs.commercial DBMS • portability of WIDE WFMS Orthogonal Architecture

  6. orthogonality orthogonality Distribution Overall WIDE Architecture

  7. CORBA OCI Transaction Support

  8. Active Rule Support

  9. Commercial RDBMS (Oracle 7.2) • Robust basic data support • Flat ACID transactions, basic triggers • Client/Server coupling (OCI) • CORBA (ILU) • Flexible distribution • Transparent communication Infrastructure

  10. Functionality • Does the system do what was intended? • Performance • Does the system offer reasonable performance? • Maintainability • Is the system easy to implement and modify? Looking Back at the Design

  11. Local transaction functionality • Limited flexibility for atomicity control • Limited transactional multi-DB access • X/Open TPM extension helps • Rule execution functionality • Decoupled rule execution model • Orthogonal transaction/rule semantics • Limited intra-business transaction rules Functionality in Retrospect

  12. C/S connection to DBMS critical • Large numbers of small transactions • Physical channel creation expensive • Reuse already created channels • Keep channels in channel pool • Modification local to LTI • Further extensions possible: • channel creation in idle time • statistical forecasting of channel usage Performance in Retrospect

  13. Software development in 3 organizations • Sema (ES), POLI (IT), UT (NL) • High level of flexibility required • Orthogonal architecture design • Standard internal module architectures • CORBA/IDL interface specification • Empty Shell integration • Complexity may lead to semantic problems though …. Maintainability in Retrospect

  14. Transfer of WIDE technology to FORO commercial WFMS(SEMA) • Use of transaction concepts in cross-organizational contexts(UT, CrossFlow project) • Unbundling of active rule engine functionality for non-WFM purposes(POLI, SEMA) • Book on WIDE developments(Kluwer Academic, January ‘99) Further Developments

More Related