1 / 7

Enhydra Shark Features, Architecture, Status

Enhydra Shark Features, Architecture, Status. Alfred Madl Together Teamlösungen GmbH. Features. Based purely on WfMC specifications XPDL, ToolAgent API, WDF,… JAWe Graphical editor Used as a library or a service POJO, Corba interfaces And more to come… No binding to only one environment.

ailish
Download Presentation

Enhydra Shark Features, Architecture, Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Enhydra SharkFeatures, Architecture, Status Alfred Madl Together Teamlösungen GmbH.

  2. Features • Based purely on WfMC specifications • XPDL, ToolAgent API, WDF,… • JAWe Graphical editor • Used as a library or a service • POJO, Corba interfaces • And more to come… • No binding to only one environment

  3. Features • Administration GUI • Supporting different scipting engines • Plug-In API for persistence • Optional caching • XPDL repository • Static and dynamic processes • …

  4. Architecture • Configurable framework approach • API‘s vs. implementations / adapters • Supporting extensions and replacements • Supporting but not needing XPDL extended attributes ! • Details in XPDL vs. mapping in the engine

  5. Architecture diagram • …

  6. Status • Beta 1 is public (Corba prototype) • WfMC XPDL as the native standard • New version already in CVS (POJO library) • Persistence layer with plugin API • Lightweight O/R mapping implemented (DODS) • Support for WfMC ToolAgents • Sample implementations (Java, JavaScript, Mail, Webservice…) • 3 scripting engines • Mapping for Agents and Participants • Optional LDAP support

  7. Plans 2004 • Separating more APIs, use of „Fractal“ • Dynamic instance access using WfMC WDF • Programatically (clients and agents) and with JAWe • Service wrappers (Corba, Webservice, EJB) • „Hooks“ by implementing a proprietary engine extension • Enitity beans persistence / external transactions • Cost-efficient programming • by great guys in Belgrade !

More Related