Exotica/FMQM: A Persistent Message-Based Architecture for Distributed Workflow Management

  • G. Alonso
  • C. Mohan
  • R. Günthör
  • D. Agrawal
  • A. El Abbadi
  • M. Kamath
Part of the IFIP — The International Federation for Information Processing book series (IFIPAICT)


In the past few years there has been an increasing interest in workflow applications as a way of supporting complex business processes in modern corporations. Given the nature of the environment and the technology involved, workflow applications are inherently distributed and pose many interesting challenges to the system designer. In most cases, a client/server architecture is used in which knowledge about the processes being executed is centralized in one node to facilitate monitoring, auditing, and to simplify synchronization. In this paper, we explore a novel distributed architecture, Exotica/FMQM, for workflow systems in which the need for such a centralized database is eliminated. Instead, we use persistent messages as the means to store the information relevant to the execution of a business process. Our approach is to completely distribute the execution of a process so individual nodes are independent. The advantages of this approach are increased resilience to failures and greater scalability and flexibility of the system configuration.


Workflow Management Systems Distributed Systems reliability scalability. 


  1. Barbara, D., Mehrota, S., and Rusinkiewicz, M. (1994). INCAS: A Computation Model for Dynamic Workflows in Autonomous Distributed Environments. Technical report, Matsushita Information Technology Laboratory.Google Scholar
  2. Chandy, K. and Lamport, L. (1985). Distributed Snapshots: determining Global States of Distributed Systems. ACM Transactions on Computer Systems, 3 (1): 63–75.CrossRefGoogle Scholar
  3. Dayal, U., Hsu, M., and Ladin, R. (1990). Organizing Long-running Activities with Triggers and Transactions. In Proceedings of ACM SIGMOD 1990 International Conference on Management of Data, pages 204–214.Google Scholar
  4. Dayal, U., Hsu, M., and Ladin, R. (1991). A Transaction Model for Long-running Activities. In Proceedings of the Sixteenth International Conference on Very Large Databases, pages 113–122.Google Scholar
  5. Frye, C. (1994). Move to Workflow Provokes Business Process Scrutiny. Software Magazine, pages 77–89.Google Scholar
  6. Garcia-Molina, H., Gawlick, D., Klein, J., Kleissner, K., and Salem, K. (1990). Coordinating Multi-transaction Activities. Technical Report CS-TR-247–90, Department of Computer Science, Princeton University.Google Scholar
  7. Goldberg, Y., Safran, M., and Shapiro, E. (1992). Active Mail–A Framework for Implementing Groupware. In Proc. of the Conference on Computer-Supported Cooperative Work (CSCW), pages 281–288, Toronto, Canada.Google Scholar
  8. Hollinsworth, D. (1994). The workflow reference model. Technical Report TC00–1003, Workflow Management Coalition. Accessible via: IBM (1993). Message Queue Interface: Technical Reference. IBM. Document No. SC33–0850–01.Google Scholar
  9. IBM (1995a). FlowMark – Managing Your Workflow, Version 2.1. IBM. Document No. SH19–8243–00.Google Scholar
  10. IBM (1995b). FlowMark - Modeling Workflow, Version 2.1. IBM. Document No. SH198241–00.Google Scholar
  11. IBM (1995c). FlowMark - Programming Guide, Version 2.1. IBM. Document No. SH198240–00.Google Scholar
  12. IBM (1995d). FlowMark for OS/2: Installation and Maintenance. IBM. Document No. SH19–8244–00.Google Scholar
  13. Kreifelts, T., Hinrichs, E., Klein, K., Seuffert, P., and Woetzel, G. (1991). Experiences with the DOMINO Office Procedure System. In Proceedings ECSCW ‘81,pages 117130. Amsterdam.Google Scholar
  14. Kreifelts, T. and Woetzel, G. (1986). Distribution and Exception Handling in an Office Procedure System. In Office Systems: Methods and Tools, Proc. IFIP WG 8.4 Work. Conf. on Methods and Tools for Office Systems, pages 197–208. October, 22–24, Pisa, Italy.Google Scholar
  15. Leymann, F. and Altenhuber, W. (1994). Managing Business Processes as an Information Resource. IBM Systems Journal, 33 (2): 326–348.CrossRefGoogle Scholar
  16. Leymann, F. and Roller, D. (1994). Business Processes Management with FlowMark. In Proc. 39th IEEE Computer Society Int’l Conference (CompCon), Digest of Papers, pages 230–233, San Francisco, California. IEEE.Google Scholar
  17. Malone, T., Grant, K., Lai, K., Rao, R., and Rosenblitt, D. (1987). Semistructured Messages Are Surprisingly Useful for Computer-Supported Coordination. ACM Transactions on Office Information Systems, 5 (2): 115–131.CrossRefGoogle Scholar
  18. McCarthy, D. and Sarin, S. (1993). Workflow and Transactions in InConcert. Bulletin of the Technical Committee on Data Engineering, 16(2). IEEE Computer Society.Google Scholar
  19. Medina-Mora, R., Wong, H., and Flores, P. (1993). ActionWorkflow as the Enterprise Integration Technology. Bulletin of the Technical Committee on Data Engineering, 16(2). IEEE Computer Society.Google Scholar
  20. Misra, J. (1983). Detecting termination of distributed Computations Using Markers. In ACM Proceedings of the Symposium on Principles od Distributed Computing, pages 290–294.Google Scholar
  21. Mohan, C. and Dievendorf£, R. (1994). Recent Work on Distributed Commit Protocols, and Recoverable Messaging and Queuing. Bulletin of the Technical Committee on Data Engineering,17(1):22–28. IEEE Computer Society.Google Scholar
  22. Sheth, A. (1994). On Multi-system Applications and Transactional Workflows, Belicore’s projects PROMP and METEOR. Collection of papers and reports from Bellcore.Google Scholar
  23. Tomlison, C., Attie, P., Cannata, P., Meredith, G., Sheth, A., Singh, M., and Woelk, D. (1993). Workflow Support in Carnot. Bulletin of the Technical Committee on Data Engineering, 16(2). IEEE Computer Society.Google Scholar
  24. Tsichritzis, D. (1982). Form Management. Communications of the ACM, 25 (7): 453–478.CrossRefGoogle Scholar
  25. Waechter, H. and Reuter, A. (1992). The ConTract Model. In Elmagarmid, A., editor, Database Transaction Models for Advanced Applications, chapter 7, pages 219–263. Morgan Kaufmann Publishers, San Mateo.Google Scholar
  26. Walk, K. (1993). Workflow Management Concepts, a White Paper. Technical report, IBM Vienna Software Development Laboratory, Austria.Google Scholar

Copyright information

© Springer Science+Business Media Dordrecht 1995

Authors and Affiliations

  • G. Alonso
    • 1
  • C. Mohan
    • 1
  • R. Günthör
    • 1
  • D. Agrawal
    • 2
  • A. El Abbadi
    • 2
  • M. Kamath
    • 3
  1. 1.IBM Almaden Research CenterSan JoseUSA
  2. 2.Computer Science DepartmentUC Santa BarbaraSanta BarbaraUSA
  3. 3.Computer Science DepartmentUM at AmherstAmherstUSA

Personalised recommendations