things such as when the workflow begins execution and when it ends,
when each activity within the workflow is entered and exited, and
more. This can be useful for gathering statistics about technical or
business aspects of workflows, such as measurements of order
fulfillment time, or maintaining a database with information about
every running workflow, allowing real-time querying of this data, or
other things. Exactly what tracking information is produced is
controlled by developer-defined profiles, and the information is by
default written to a SQL Server database. (This can be changed,
however, since tracking is partially implemented by a replaceable
runtime service in a workflow's host application.)
WWF's tracking facility is relatively simple. While it does provide
the interfaces needed to define and collect tracking data, no tools
are provided to display this information. There's also no standard
mechanism to send notifications based on tracking data. Rather than
providing a complete service akin to the Business Activity Monitoring
component in BizTalk Server, WWF provides a foundation that ISVs and
others can build on.
No comments:
Post a Comment