Shark是如何遵循WFMC的Workflow Reference Model的

最新推荐文章于 2025-09-14 10:17:02 发布

原创最新推荐文章于 2025-09-14 10:17:02 发布 · 1.7k 阅读

CC 4.0 BY-SA版权

文章标签：

7 篇文章

订阅专栏

博客介绍Shark是遵循WFMC规范、具可扩展功能的工作流引擎，重点说明Shark系统遵循WFMC的Workflow Reference Model的方式，阐述了Shark Server及各接口对应的Shark系统功能模块，旨在让初学者直观理解。

众所周知，Shark是完全根据WFMC规范实施的，可扩展功能的工作流
引擎。那么Shark系统是如何遵循WFMC的Workflow Reference Model的呢？

首先，简单的介绍一下WFMC的Workflow Reference Model。

Working Groups		Objectives
Reference Model & Glossary		Specify a framework for workflow systems, identifying their characteristics, functions and interfaces. Development of standard terminology for workflow systems.
Process Definition Tools Interface (1)		Definition of a standard interface between process definition and modeling tools and the work flow engine(s).
Workflow Client Application Interface (2)		Definition of APIs for client applications to request services from the workflow engine to control the progression of processes, activities and work-items.
Invoked Application Interface (3)		A standard interface definition of APIs to allow the workflow engine to invoke a variety of applications, through common agent software.
Workflow Interoperability Interface (4)		Definition of workflow interoperability models and the corresponding standards to support interworking.
Administration & Monitoring Tools Interface (5)		The definition of monitoring and control functions.
Conformance		To develop the Coalition's policy on product conformance against its specifications and agree an approach to vendor certification.

接下来说明一下Shark是如何来实现这些接口的。

图中的Workflow Engine(s)对应Shark Server。
图中的Interface 1: Process Definition对应Shark Admin的Repository Management，Package Management和Worklist Management。
图中的Interface 2: Workflow Client Application对应Process Instantiation Management和Process Monitor。
图中的Interface 3: Invoked Applicaitons对应Application Mapping。
图中的Interface 4: Workflow Engine(s)对应其它的Shark Server。
图中的Interface 5: Administration & Monitoring Tools对应User Managementa。

以上的对应并不严格，这样做完全是为了给初学者一个比较直观的认识。不求严谨，只为理解。