worklist handler The Resource Service FMS W Provides the resource perspective

Worklist handler the resource service fms w provides

This preview shows page 3 - 7 out of 14 pages.

worklist handler) - - The Resource Service (FMS-W) - Provides the resource perspective for specifications Completely separate from the engine - Basic role is to allocate work items to resources for processing - 4 primary components 1. Resource Manager: handles all the resource patterns 2. Worklist: a web-based user interface 3. Forms Connector: show either custom designed or dynamically generated forms for work items 4. Codelet Server: for executing codelets - - The YAWL Editor - It is a desktop application for the creation and verification of process specifications (models) - It communicates with a YAWL Engine to get a list of available YAWL Services
Image of page 3
- It also communicates with a YAWL Resource Service to get lists of the various organizational resources available, so that selected resources can be associated with particular tasks - It allows upload and download of YAWL models to/from the YAWL Engine - - YAWL – The Language - Extension of Petri Nets and Workflow nets - Cancellations (“Reset nets”) - Multiple instances - Synchronization of active brances (“OR splits/joins”) - Formal and precise semantics - - Identify Automation Boundaries - Automated Tasks Performed by the WfMS or external service - Manual Tasks Done by humans Without knowledge/support of the WfMS - User Tasks Done by humans Coordinated/supported by the WfMS - - Dealing with Manual Tasks - Tasks not “seen” by the WfMS cannot be managed - Some tasks cannot or should not be automated by the WfMS - - Complete the Process Model (RED) - Exceptions Identify any and all errors that can occur in your process and how to handle them - Resource Perspective Describe organizational resources and structures Define rules for assigning organizational resources to process activities - Data Perspective Describe information flowing through the process Describe information flowing in and out of the activities Describe any data-based decision rules - - YAWL Components Distribution - Each component (editor, workflow engine, resource service, other services) can run on a different computer - Typically, the Workflow Engine and Resource Service run on the same computer (“YAWL Server”) - Each YAWL installation contains all components
Image of page 4
- Operating your YAWL Server - Use the YAWL control panel to start or stop your own YAWL server - You can only access your own YAWL server from your own computer - Not so useful for actual workflow management but useful for workflow development - - Configuring your YAWL Editor - The editor needs to know which computer the engine and resource service run on It needs a list of available services from the engine (so you can use these in your process) It needs a list of available resources from the resources from the resource service (so you can use these in your process) “localhost” and port is 8080 - - Class 14 - - - - Branching Constructs - AND Split Parallel Split, initiation of parallel threads - OR Split Multi-choice, thread of control is passed to one or more outgoing branches - XOR Split
Image of page 5
Exclusive choice,
Image of page 6
Image of page 7

You've reached the end of your free preview.

Want to read all 14 pages?

  • Winter '16
  • Business, Work Item, WFMS, YAWL editor, YAWL Engine, YAWL Resource Service

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture