Task Audit Logging
Tasks are created in Designer and run on My webMethods Server. You can log two types of audit data for tasks:
For all tasks, you can use task log entries to track the following:
When tasks are queued.
When users accept or release tasks, suspend and resume tasks, and complete or cancel tasks.
Whether tasks completed successfully, failed, or expired.
Task Engines log audit data for tasks and send the data to Integration Server. The Task Engine is a feature installed on every My webMethods Server that runs tasks. For detailed information on the Task Engine and instructions on setting up task logging, see webMethods Task Engine User’s Guide.
Users perform the actions listed above from the task list in My webMethods. For instructions on performing actions on tasks, see webMethods Task Engine User’s Guide.
For tasks that are called from business processes, you can write business process log entries. Tasks called from business processes are run as business process steps, so you can log the same data for a task that you can log for any other business step (see
Business Process Audit Logging, above).
Process Engines log all business process entries.