Shark工作流解决方案英文版（PPT）.pptVIP

* Shark kernel Implementation of special core kernel API A glue that bounds client API implementations and internal component implementations based on provided configuration. Handles the client requests by parsing XPDL definition, communicating with internal components and implementing its own logic to achieve the goal. The benefit of having kernel API * Kernel processing * Kernel processing (simplified) * Shark plug-in APIs Mandatory plug-in components and their purpose: Repository persistence component Instance persistence component Scripting component Optional plug-in components and their purpose: Assignment component UserGroup component ParticipantMapping component ToolAgent component ApplicationMapping component EventAudit component Logging component Caching component Security component * TWS - shark extensions TWS is shark extension that: Implements advanced APIs Extends shark kernel to interpret extended attributes Brings more useful implementations of plug-in APIs Brings more useful tool agent implementations Most important additional functionality: Possibility to use variables not defined in XPDL Possibility to have transient processes and variables (even the ones not defined in XPDL by the usage of special naming convention) Possibility to specify that all activities should not have special context, but to use the one of the process (for performance reasons) Possibility to specify a process or activity behavior per definition. API to “find out the future and the past”, and to navigate through process based on its XPDL definition * Swing Admin – process monitoring * WEB Client – worklist handling * Worklist handler Application that enables a human workflow participant to manage the work items which have been assigned to them Shark provides graphical Worklist Handlers: graphical swing worklist handle, WEB based worklist handler application Worklist handlers able to access shark through: POJO EJB WebService * Assignment manager What’s the purpos