Worklist Manager Service Engine Architecture

The Worklist Manager Service Engine functions as part of a larger workflow, which can include multiple binding components, BPEL processes, and worklist tasks. The following diagram illustrates the general architecture of a Worklist Manager system.

The following describes the flow of data through a Worklist Manager system:

1. An external system or client sends a message to the workflow system.

2. The message is received through a binding component and is then processed through the Normalized Message Router (NMR) to the BPEL process.

3. When the BPEL process comes to the human task, it sends a request to the Worklist Manager Service Engine.

4. The Worklist Manager Service Engine writes the task to the Worklist Manager database, and waits for the task to be claimed and completed.

5. A WLM user claims and completes the task.

   • Each time a user changes the task status, the information is sent from the web client through the Java EE Service Engine and NMR to the Worklist Manager Service Engine, and the Worklist Manager Service Engine updates the database.

   • If email notifications are defined, email messages are sent out from the Worklist Manager Service Engine through the NMR and the Email Binding Component to the external email service. This happens each time a notification trigger event occurs.

6. Upon task completion, the Worklist Manager Service Engine sends a reply to the BPEL process. Additional notifications may be generated.

7. The BPEL process generates a message back out through the NMR and binding component to the external system or client.