Before you run this sample, make sure that security is enabled for WebSphere® Process Server and that the users and groups are created as required, for example, by using the script ADDUSERS2.BAT as described in the in the Introduction section.
To run this sample, use the Business Process Choreographer Explorer.
To start BPC Explorer in the integrated test environment of your WebSphere® Integration Developer, follow these steps:
To start BPC Explorer on WebSphere Process Server, follow these steps:
http://yourhost:yourport/bpc
.Note: Replace yourhost
with your server's internet address and replace yourport
with the port of your server's HTTP transport,
for example
If security is enabled, the BPC Explorer opens with a login screen:
The BPC Explorer opens:
To start the helpdesk process, perform the following steps:
hdA
, be sure to enter the user ID in mixed case exactly as shown.The Currently Valid Process Templates view is displayed:
The Process Input Message view opens:
To work with the HelpDeskRequest task, perform the following steps:
hdA
(case sensitive).The My To-dos view opens:
The HelpDeskRequest task is in the state Ready.
hdteamlead
userid.hdmanager
userid.In the previous steps, user hdA
has caused the creation of several escalation items by missing the time thresholds specified in the process template.
To display the escalation items, perform the following steps:
hdteamlead
(case sensitive).The My Escalations list is displayed for the particular user ID:
You may repeat these steps for the userids qualitymanager
and hdmanager
to inspect the other escalation items that were created.
The process template definition used in this sample has enabled the flag "Automatically delete the process after completion". Thus, to delete the process it is sufficient to complete the HelpDeskRequest task. The deletion of the task will as well trigger the deletion of all dependent escalation items. To complete the task, perform the following steps:
hdA
. The My Tasks view opens again.The Task Message view is displayed:
The My Tasks view is displayed. The task has been removed from the list. In addition, all escalations and the process instance have been deleted.
Inspect the SystemOut.log of your WebSphere Process Server. The notification event handler writes output similar to the following lines to the SystemOut.log:
[5/15/09 15:56:10:078 CEST] 00000054 SystemOut O --- Notification event received: May 15, 2009 3:56:10 PM
[5/15/09 15:56:10:078 CEST] 00000054 SystemOut O Task template name: HelpDeskRequest
[5/15/09 15:56:10:078 CEST] 00000054 SystemOut O Task name: HelpDeskRequest
[5/15/09 15:56:10:078 CEST] 00000054 SystemOut O Event handler name: Escalations
[5/15/09 15:56:10:078 CEST] 00000054 SystemOut O Is escalated: true
[5/15/09 15:56:10:078 CEST] 00000054 SystemOut O Notification event received.
[5/15/09 15:56:10:078 CEST] 00000054 SystemOut O Escalation name: NotFinishedAfterFourMinutesEvent
[5/15/09 15:56:10:078 CEST] 00000054 SystemOut O Duration until escalated: 4minutes
[5/15/09 15:56:10:078 CEST] 00000054 SystemOut O Duration until repeated: 2minutes
[5/15/09 15:56:10:078 CEST] 00000054 SystemOut O --- End notification event
If you run the integrated WebSphere Test Environment, you can see this information in the Server Logs view: