The Mentor project: steps towards enterprise-wide workflow management

Wodtke, Dirk; Weißenfels, Jeanine; Weikum, Gerhard; Dittrich, Angelika Kotz

doi:10.1109/icde.1996.492206

Cited by 83 publications

(59 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…A serious limitation of these production workflow systems is that they typically use a centralized enactment service. Therefore, many recent research prototypes such as MENTOR (University of Saarland at Saarbrucken, [50]), METEOR (University of Georgia, [39,44]), MOBILE (University of Erlangen, [25]), and WASA (University of Muenster, [48]) focus on a distributed architecture. An interesting project focusing on the application of workflow technology to electronic commerce is the WIDE Project and the successor project CrossFlow [22].…”

Section: Discussion and Related Workmentioning

confidence: 99%

“…The WfMC recently published the Interoperability Wf-XML Binding [50]. Wf-XML is intended as a basis for concrete implementations of the WfMC's Interface 4 [30].…”

Section: Discussion and Related Workmentioning

confidence: 99%

“…There is also support for additional services. Very recently, the WfMC has issued a specification for Interface 4 of Figure 3 based on XML [50]. This specification is named Wf-XML and models the data transfer requirements among different workflow engines in XML.…”

Section: Architecturementioning

confidence: 99%

See 2 more Smart Citations

XML–Based Schema Definition for Support of Interorganizational Workflow

Aalst

Kumar

2003

Information Systems Research

131

View full text Add to dashboard Cite

The full potential of the web as a medium for electronic commerce can be realized only when multiple partners in a supply chain can route information among themselves in a seamless way. Commerce on the Internet is still far from being "friction-free" because business partners cannot exchange information about their business processes in an automated manner. In this paper, we propose the design for an eXchangeable Routing Language (XRL) using XML syntax. XML (eXtendible Markup Language) is a means for trading partners to exchange business data electronically. The novel contribution of our work is to show how XML can also be used to describe workflow process schemas to support flexible routing of documents in the Internet environment. The design of XRL is grounded in Petri nets, which is a wellknown formalism. By using this formalism, it is possible to analyze correctness and performance of workflows described in XRL. Architectures to facilitate inter-operation through loose and tight integration are also discussed. Examples illustrate how this approach can be used for implementing interorganizational electronic commerce applications. As a proof of concept we have also developed XRL/flower, a prototype implementation of a workflow management system based on XRL.

show abstract

Section: Discussion and Related Workmentioning

confidence: 99%

“…The WfMC recently published the Interoperability Wf-XML Binding [50]. Wf-XML is intended as a basis for concrete implementations of the WfMC's Interface 4 [30].…”

Section: Discussion and Related Workmentioning

confidence: 99%

See 1 more Smart Citation

XML–Based Schema Definition for Support of Interorganizational Workflow

Aalst

Kumar

2003

Information Systems Research

131

View full text Add to dashboard Cite

show abstract

“…Additionally, they can not quickly adapt to new business tasks of an enterprise. Earlier research approaches addressed these problems -especially distributed systems aspects -to some larger degree; examples are Mentor [30], WASA [29] and Mobile [2]. Some approaches also address specific aspects such as web integration [10,23], or virtual enterprises [18].…”

Section: Comparison With Other Workflow Approachesmentioning

confidence: 99%

Experiences with Business Object-Based Workflow Support

Strobel

Mittasch

1999

Distributed Applications and Interoperable Systems II

View full text Add to dashboard Cite

Currently, the OMG standardises business objects as a paradigm for encapsulating components of business functionality. This paper reviews this approach and discusses its basic requirements concerning a scaleable middleware platform with associated services. We show how higher-level workflow services can be provided and implemented using business objects as their basic building blocks. A generic architecture, language and runtime systems for distributed and decentralised workflow execution are presented. Particular emphasis is dedicated to the use of business objects and also to the integration of services such as naming, events and transactions. Especially performance aspects are becoming a decisive factor for the success of such component-based applications. Therefore, configuration management aspects and performance results of our implementation are also discussed.

show abstract

“…Clearly, the performance and robustness of a decentralized service orchestration would benefit from placing each orchestration engine as close as possible to the component services that it manages. But neither the above method nor other similar decentralized orchestration methods [14], [9], [5], [19], [3] help designers to optimize the communication overhead between component services. This paper presents a method for partitioning activities in an orchestration and assigning services to activities, in such a way as to minimize the communication overhead, while maximizing the QoS expressed in terms of combinations of properties such as time, cost, reliability, etc.…”

Section: Introductionmentioning

confidence: 99%

Optimized decentralization of composite web services

Fdhila¹,

Dumas²,

Godart³

2010

Proceedings of the 6th International ICST Conference on Collaborative Computing: Networking, Applications, Worksharing

View full text Add to dashboard Cite

Abstract-Composite services are usually specified by means of orchestration models that capture control and data-flow relations between activities. Concrete services are then assigned to each activity based on various criteria. In mainstream service orchestration platforms, the orchestration model is executed by a centralized orchestrator through which all interactions are channeled. This architecture is not optimal in terms of communication overhead and has the usual problems of a single point of failure. In previous work, we proposed a method for executing service orchestrations in a decentralized manner while fulfilling collocation and separation constraints. However, this and similar methods for decentralized orchestration do not seek to optimize the communication overhead between services participating in the orchestration. This paper presents a method for optimizing the selection of services assigned to activities in a service orchestration in terms of QoS properties and communication overhead. The method takes into account the communication cost between pairs of services, the amount of data that these services need to exchange in the orchestration, and the collocation and separation constraints imposed by the service providers.

show abstract

The Mentor project: steps towards enterprise-wide workflow management

Cited by 83 publications

References 19 publications

XML–Based Schema Definition for Support of Interorganizational Workflow

XML–Based Schema Definition for Support of Interorganizational Workflow

Experiences with Business Object-Based Workflow Support

Optimized decentralization of composite web services

Contact Info

Product

Resources

About