Please consult the YAWL javadoc for more details of the complete functionality

Please consult the yawl javadoc for more details of

This preview shows page 37 - 39 out of 100 pages.

Please consult the YAWL javadoc for more details of the complete functionality set offered by Interface A. 4.5.2 Interface E Interface E provides access to the Engine’s process logs. The are two output formats returned by the various methods of the interface, the majority are in plain XML, but case histories can also be retrieved in the OpenXES format, allowing the log output to be directly imported into the ProM process mining tool 5 . To access Interface E, the YLogGatewayClient class needs to be added to your Custom Service (from the pack- age org.yawlfoundation.yawl.engine.interfce.interfaceE ). An example of using Interface E is shown in Listing 4.13; note in particular that the Engine’s Interface E URI ends with the path /yawl/logGateway . The boolean argument in the getSpecificationXESLog method, when true, includes all variable data value changes in the output returned. There are numerous methods to retrieve logged data for such things as: all the events of a particular case. all the events for a particular task instance. all the task instances of a particular case. all the task instances of a task definition. the data type for a particular data item (complex types included). all the events of all cases instantiated from a particular specification. all the cases started and/or cancelled by a particular Custom Service. 5 Page 37 of 100
Image of page 37
1 public class MyService extends InterfaceBWebsideController 2 implements I n t e r f a c e X S e r v i c e { Listing 4.14: Implementing the Interface X Java Interface (example) and many more. Please consult the Interface E javadoc for more details. 4.5.3 Interface X This section provides a technical overview of the structure and use of Interface X - an interface through which certain milestone notifications are passed during the execution of a process instance where a process exception may have occurred or may be tested for. Interface X has been designed to allow the Engine to notify Custom Services of certain milestone events during the execution of a process instance providing services the ability to dynamically check for, capture and handle process exceptions. An example of a service which utilises Interface X is the Worklet Exception Service , which has been part of YAWL distributions since the YAWL Beta 8 release. However ,the use of Interface X is not limited to exception handling requirements, but is structured for ‘generic application’ - that is, it can be applied by a variety of services that can make use of milestone notifications during process executions. Setup To receive and react to event notifications via Interface X, a Custom Service needs to: 1. Implement the InterfaceX Service (java) interface. An example of how to implement the required java interface can be seen in Listing 4.14.
Image of page 38
Image of page 39

You've reached the end of your free preview.

Want to read all 100 pages?

  • Spring '17
  • Sui
  • yawl

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture