D2 8 Enhydra Shark
- 1. Enhydra Shark Version 2.0 Architecture and features WfMC Forum Poland 2007
- 2. Introduction The enhydra.org family EAF XMLC DODS Octopus Demos Kelp etc. WfMC Forum Poland 2007
- 3. Enhydra Workflow Projects Enhydra JaWE Java Workflow Editor Enhydra Shark Workflow Engine WfMC Forum Poland 2007
- 4. Enhydra JaWE - TWE WfMC Forum Poland 2007
- 5. Enhydra JaWE WfMC compliance Graphical application for XPDL process definition modelling Makes creating and changing XPDL easy Uses swim lanes to represent participants of the process Every XPDL element has property panel for editing its properties Final output of modelling process is a XML file based on XPDL schema XPDL files created by JaWE can be interpreted by any XPDL workflow engine. Accomplished three main goals: Graphical representation of process definition Export of process definition to XPDL Import of any valid XPDL and its graphical representation WfMC Forum Poland 2007
- 6. Enhydra JaWE WfMC Forum Poland 2007
- 7. Enhydra Shark - TWS WfMC Forum Poland 2007
- 8. Workflow Reference Model - Components & Interfaces Interface 1 Interface 2 Interface 3 Interface 4 Interface 5 WfMC Forum Poland 2007 Ja WE Shark Server Process Definition Tool Workflow Enactment Service Workflow Client Applications Invoked Applications Other Workflow Enactment Service Administration & Monitoring tools Admin and WH Clients Shark Tool Agents
- 9. Enhydra Shark Short description Workflow engine that executes processes based on XPDL definition library implemented in Java embedded into CLI/GUI/WEB/EJB applications deployed as CORBA/WEB/RMI/JEE service/application WfMC Forum Poland 2007
- 10. Features Supports automated, manual and mixed workflow processes Extensible work item allocation algorithms Activities are automated through extensible system of Tool Agents Human interactions are managed through work items Work-list API allows client app to manage work items Can be used in cluster scenario Requires relational database Supports many DB vendors ... WfMC Forum Poland 2007
- 11. Three main layers WfMC Forum Poland 2007
- 12. Client application API Client application have several APIs to communicate with Shark OMG WfMC Interface 2 XPDL Package Administration XPDL Browser Execution Administration Filter Builder and Miscellaneous WfMC Forum Poland 2007
- 13. Internal organization components and “framework” Mandatory and optional components Additional (3rd party) requirements WfMC Forum Poland 2007
- 14. Components and “framework” Each component has an API defined and at least one/default implementation Configuration is plain property file, where component implementation may expect additional property values Shark kernel is itself a component, and follows the same rules Default kernel neither expects, nor processes XPDL extended attributes WfMC Forum Poland 2007
- 15. Mandatory components Kernel Instance persistence Repository persistence Script API WfMC Forum Poland 2007
- 16. Optional components Event Audits Assignment Logging Caching Security Tool Agent Application mapping Participant mapping User Group WfMC Forum Poland 2007
- 17. Shark Kernel Shark kernel part is also an implementation of special core kernel API, which is the main internal component API. It is a glue that bounds client API implementations and internal component implementations based on provided configuration. Kernel handles the client requests by parsing XPDL definition, communicating with internal components and implementing its own logic to achieve the goal. WfMC Forum Poland 2007
- 18. Internal interaction WfMC Forum Poland 2007
- 19. Internal interaction (simplified) WfMC Forum Poland 2007
- 20. Assignment Manager Assignment manager job is to return a list of user Ids which should be assigned to particular activity instance. AssignmentManager interface has only 4 methods There are several assignment manager implementations coming with Shark: StandardAssignmentManager: tries to generate list of users based on ParticipantMapping and UserGroup information HistoryRelatedAssignmentManager: reads several ext. attributes. where one can specify if activity should be assigned to the user that previously executed such activity (in the case of loops) or to the user that previously executed some other activity. If no ext. attributes. specified behaves like Standard implementation XPDLStraightParticipantMappingAssignmentManager: returns only one user Id which is the same to the Id of the XPDL Participant WfMC Forum Poland 2007
- 21. Tool Agents WfMC Forum Poland 2007
- 22. Tool Agents when tool activity is about to execute its tool, shark kernel gets the current value of variables specified as actual parameters (in the case actual parameter is an expression, it evaluates expression using current values of all process variables), and provides these values to a DefaultToolAgent DefaultToolAgent reads an ext. attrib. ToolAgentClass (from Application definition) and delegates a call to appropriate tool agent specified by this attribute, which is in this sample BshToolAgent BshToolAgent reads additional extended attribute Script, and evaluates this script using variables provided by kernel, and updates their value. At the end, kernel reads-back the variables which type is OUT or INOUT and updates process instance variables. WfMC Forum Poland 2007
- 23. Standards WfMC + OMG JTA support XForms XPIL – XML Process Instance Language WfMC Forum Poland 2007
- 24. Demo applications Console command line Visual - swing graphical user interface http/web HTML + XForms + CSS WfMC Forum Poland 2007
- 25. Swing (GUI) Administration WfMC Forum Poland 2007
- 26. Shark Web Client WfMC Forum Poland 2007
- 27. Summary Summary Roadmap XPDL 2.0 XForms EJB 3 WfMC Forum Poland 2007