Introduction
The ENHYDRA SHARK project delivers a workflow server in a different way. ENHYDRA Shark is an extensible workflow engine framework, which includes a standard implementation based on WFMC specification, which uses XPDL (without any own new extension) as its own workflow process definition format, using WFMC's "ToolAgents" API The execution form of the server-side of the system activity. ENHYDRA JAWE Graphics XPDL editor can be used to generate XPDL process definitions for Enhydra Shark! Toolagents can be used in JavaScript, JDBC access, EJB access, pure Java class, CORBA call, email, webservice call, etc ...
The storage of the flow and the active instance is done by a configurable persistence API. The standard used by the persistence layer is a lightweight ENHYDRA DODS O / R MAPPING tool. More heavyweight J2EE EJB persistent layer selection schemes are shown below. Each single component (persistent layer, transaction management, scripting engine, process library ...) can be used for its standard implementation or expand / replace it by the project specific module. In this way, Enhydra Shark can be used as a simple "Java Library", Corba ORB or Web service located in the Servlet or Swing application or running in J2EE container (support session bean API, and for EJB persistence). The workflow engine core provides a configurable LRU cache for the active workflow objects in high load environments. Cache can be turned off at cluster deployment.
When the workflow runs, the WFMC WDF API specification will be used to attach the JAWE editor or the SelfWritten program on the runtime instance information and even modify the instance. Using this method, ENHYDRA Shark supports dynamic workflow mechanisms, which can modify itself to support more complex workflow environments or organization's abnormalities. Typically, SWING-based management GUI can be used to manage jobs. JMX extensions and HTML-based management clients can also be managed. Other APIs can be used for knowledge base access, log, knowledge base, event notification, and scripting engine adapters designed for transition evaluation. ObjectWeb Workflow Working Group in December 2003, the new ObjectWeb Workflow Workflow Working Group was held. The goal of this meeting is to determine the viable collaboration rules between "Enhydra Shark", "COW", and "Bonita" in "Enhydra Shark", "COW" and "Bonita". The consensus reached is that the APIs of these components should follow their standards (WFMC, OMG, BPEL). These components will be part of the future independent workflow engine project. All components will not depend on a specific operating environment (Swing, Servlets, J2EE / EJB, CORBA ...). To select a universal component model ("glue"), the currently very likely suggestion is "Fractal". The new message list has been established to facilitate the discussion of the daily workflow workgroup matters and support between projects. This list can be found on http://www.objectWeb.org/wws/info/wow. Other reached consensus is a universal editor that uses ENHYDRA JAWE as an XPDL-based process-defined process.
Research on WFMC WDF (Workflow Definition Function) will indicate whether the API is suitable for process and activity instances. If WDF is the preferred choice for API, JAWE will support this API to make graphical viewing and instance modifications during operation. The following list lists are listed below: model library mapping modules, including map flow and activity instance persistence of Toolagents, Scripting Language / Engines, and Participants (users and groups) (Based on Enyhdra Dods, Speedo, EJB's,. ..) Script Engine Adapter / Package, which is suitable for process conversion evaluation of different scripting languages (JavaScript, Python, ...). Active Process and Activity Instance Runtime Cache (PERSEUS?) Transaction Management (GOTM?) Toolagents Dispresent, Dynamic Participant Mapping Notification API (Jabber, JMS, ...) Log (System Log and Management Activity Log) DEADLINE Management (DEADLINES), Duration Duration (DURATIONS), ...) Realization ENHYDRA Shark architecture (ESAARTZ, J2EE TIMER SERVICES, ...) ENHYDRA SHARK architecture
According to the above-mentioned Shark assembly, the current ENHYDRA Shark architecture target is shown below.
(Please note! Quote, transfer this article to indicate the original translator: rosen Jiang and the source: http://blog.9cbs.net/rosen
