Business process events are sent if monitoring is requested for the business process elements in WebSphere Integration Developer. A list of all the events that can be emitted by business processes can be found here.
Where:>>-BPC.BFM.BASE--BPCEventCode--processTemplateName--processTemplateValidFrom--+-| BPC.BFM.PROCESS.BASE |----+->< +-| BPC.BFM.ACTIVITY.BASE |---+ +-| BPC.BFM.LINK.STATUS |-----+ '-| BPC.BFM.VARIABLE.STATUS |-'
The name of event elements are in uppercase, for example BPC.BFM.BASE, and the names of extended data elements are in mixed case, for example, BPCEventCode. Except where indicated, all data elements are of the type string.
If WebSphere Business Integration Modeler is used to generate the Business Process Execution Language (BPEL) and the monitoring specification, the extension name can be extended by a hash character (#) followed by additional characters. Also, events that emit message data contain additional extendedDataElements. Refer to the documentation for WebSphere Business Integration Modeler for more information.
The following table describes all process events.
Code | Description | Extension name | Situation | Event nature |
---|---|---|---|---|
21000 | Process started | BPC.BFM.PROCESS.START | Start | ENTRY |
21001 | Process suspended | BPC.BFM.PROCESS.STATUS | Report | SUSPENDED |
21002 | Process resumed | BPC.BFM.PROCESS.STATUS | Report | RESUMED |
21004 | Process completed | BPC.BFM.PROCESS.STATUS | Stop | EXIT |
21005 | Process terminated | BPC.BFM.PROCESS.STATUS | Stop | TERMINATED |
21019 | Process restarted | BPC.BFM.PROCESS.START | Report | RESTARTED |
21020 | Process deleted | BPC.BFM.PROCESS.STATUS | Destroy | DELETED |
42001 | Process failed | BPC.BFM.PROCESS.FAILURE | Fail | FAILED |
42003 | Process compensating | BPC.BFM.PROCESS.STATUS | Report | COMPENSATING |
42004 | Process compensated | BPC.BFM.PROCESS.STATUS | Stop | COMPENSATED |
42009 | Process terminating | BPC.BFM.PROCESS.STATUS | Report | TERMINATING |
42010 | Process failing | BPC.BFM.PROCESS.STATUS | Report | FAILING |
42027 | Correlation set initialized | BPC.BFM.PROCESS.CORREL | Report | CORRELATION |
42041 | Process work item deleted | BPC.BFM.PROCESS.WISTATUS | Report | WI_DELETED |
42042 | Process work item created | BPC.BFM.PROCESS.WISTATUS | Report | WI_CREATED |
42046 | Process compensation failed | BPC.BFM.PROCESS.STATUS | Fail | COMPFAILED |
42047 | Process event received | BPC.BFM.PROCESS.STATUS | Report | EV_RECEIVED |
42049 | Process event escalated | BPC.BFM.PROCESS.ESCALATED | Report | EV_ESCALATED |
42056 | Process work item transferred | BPC.BFM.PROCESS.WITRANSFER | Report | WI_TRANSFERRED |
BPC.BFM.PROCESS.BASE >>-BPC.BFM.PROCESS.BASE--processInstanceExecutionState--| BPC.BFM.PROCESS.STATUS |->< BPC.BFM.PROCESS.STATUS |--BPC.BFM.PROCESS.STATUS--processTemplateId--processInstanceDescription--+-------------------------------------------------+--| +-BPC.BFM.PROCESS.CORREL--correlationSet----------+ +-BPC.BFM.PROCESS.ESCALATED--escalationName-------+ +-BPC.BFM.PROCESS.FAILURE--processFailedException-+ +-BPC.BFM.PROCESS.START--username-----------------+ | .----------. | | V | | +-BPC.BFM.PROCESS.WISTATUS----username-+----------+ '-BPC.BFM.PROCESS.WITRANSFER--current--target-----'
<?xml version="1.0"?> <correlationSet name=”correlation set name”> <property name=”property name” value=”property value”/>* </correlationSet>
The following table describes all activity events.
Code | Description | Extension name | Situation | Event nature |
---|---|---|---|---|
21006 | Activity ready | BPC.BFM.ACTIVITY.STATUS | Start | CREATED |
21007 | Activity started | For invoke activities: BPC.BFM.ACTIVITY.MESSAGE. For all other activity types: BPC.BFM.ACTIVITY.STATUS | Start | ENTRY |
21011 | Activity completed | For invoke, staff, receive, and reply activities: BPC.BFM.ACTIVITY.MESSAGE. For all other activity types: BPC.BFM.ACTIVITY.STATUS | Stop | EXIT |
21021 | Claim canceled | BPC.BFM.ACTIVITY.STATUS | Report | DEASSIGNED |
21022 | Activity claimed | BPC.BFM.ACTIVITY.CLAIM | Report | ASSIGNED |
21027 | Activity terminated | BPC.BFM.ACTIVITY.STATUS | Stop | TERMINATED |
21080 | Activity failed | BPC.BFM.ACTIVITY.FAILURE | Failed | FAILED |
21081 | Activity expired | BPC.BFM.ACTIVITY.STATUS | Report | EXPIRED |
42005 | Activity skipped | BPC.BFM.ACTIVITY.STATUS | Report | SKIPPED |
42012 | Activity output message set | BPC.BFM.ACTIVITY.MESSAGE | Report | OUTPUTSET |
42013 | Activity fault message set | BPC.BFM.ACTIVITY.MESSAGE | Report | FAULTSET |
42015 | Activity stopped | BPC.BFM.ACTIVITY.STATUS | Stop | STOPPED |
42031 | Activity force retried | BPC.BFM.ACTIVITY.STATUS | Report | FRETRIED |
42032 | Activity force completed | BPC.BFM.ACTIVITY.STATUS | Stop | FCOMPLETED |
42036 | Activity has message received | BPC.BFM.ACTIVITY.MESSAGE | Report | EXIT |
42037 | Loop condition true | BPC.BFM.ACTIVITY.STATUS | Report | CONDTRUE |
42038 | Loop condition false | BPC.BFM.ACTIVITY.STATUS | Report | CONDFALSE |
42039 | Work item deleted | BPC.BFM.ACTIVITY.WISTATUS | Report | WI_DELETED |
42040 | Work items created | BPC.BFM.ACTIVITY.WISTATUS | Report | WI_CREATED |
42050 | Activity escalated | BPC.BFM.ACTIVITY.ESCALATED | Report | ESCALATED |
42054 | Activity work items refreshed | BPC.BFM.ACTIVITY.WISTATUS | Report | WI_REFRESHED |
42055 | Work item transferred | BPC.BFM.ACTIVITY.WITRANSFER | Report | WI_TRANSFERRED |
42057 | For each - activity branches started | BPC.BFM.ACTIVITY.FOREACH | Report | BRANCHES_STARTED |
BPC.BFM.ACTIVITY.BASE >>-BPC.BFM.ACTIVITY.BASE--activityKind--state--bpelId--| BPC.BFM.ACTIVITY.STATUS |->< BPC.BFM.ACTIVITY.STATUS |--BPC.BFM.ACTIVITY.STATUS--+----------------------+--activityTemplateId--+-----------------------------+--+---------------------------------------------------+--| '-activityTemplateName-' '-activityInstanceDescription-' +-BPC.BFM.ACTIVITY.CLAIM--username--principal-------+ +-BPC.BFM.ACTIVITY.ESCALATED--escalationName--------+ +-BPC.BFM.ACTIVITY.FAILURE--activityFailedException-+ +-BPC.BFM.ACTIVITY.FOREACH--parallelBranchesStarted-+ | .----------------. | | V | | +-BPC.BFM.ACTIVITY.MESSAGE----+-message----+-+------+ | '-message_BO-' | | .----------. | | V | | +-BPC.BFM.ACTIVITY.WISTATUS----username-+-----------+ '-BPC.BFM.ACTIVITY.WITRANSFER--current--target------'
The following table describes all activity scope events.
Code | Description | Extension name | Situation | Event nature |
---|---|---|---|---|
42020 | Scope started | BPC.BFM.ACTIVITY.STATUS | Start | ENTRY |
42021 | Scope skipped | BPC.BFM.ACTIVITY.STATUS | Report | SKIPPED |
42022 | Scope failed | BPC.BFM.ACTIVITY.FAILURE | Fail | FAILED |
42023 | Scope terminating | BPC.BFM.ACTIVITY.STATUS | Report | FAILING |
42024 | Scope terminated | BPC.BFM.ACTIVITY.STATUS | Stop | TERMINATED |
42026 | Scope completed | BPC.BFM.ACTIVITY.STATUS | Stop | EXIT |
42043 | Scope compensating | BPC.BFM.ACTIVITY.STATUS | Report | COMPENSATING |
42044 | Scope compensated | BPC.BFM.ACTIVITY.STATUS | Stop | COMPENSATED |
42045 | Scope compensation failed | BPC.BFM.ACTIVITY.STATUS | Fail | COMPFAILED |
42048 | Scope event received | BPC.BFM.ACTIVITY.STATUS | Report | EV_RECEIVED |
42051 | Scope event escalated | BPC.BFM.ACTIVITY.ESCALATED | Report | EV_ESCALATED |
Activity scope events are a type of activity events, whose syntax is described above for BPC.BFM.ACTIVITY.STATUS.
The following table describes all link events.
Code | Description | Extension name | Situation | Event nature |
---|---|---|---|---|
21034 | Link evaluated true | BPC.BFM.LINK.STATUS | Report | CONDTRUE |
42000 | Link evaluated false | BPC.BFM.LINK.STATUS | Report | CONDFALSE |
BPC.BFM.LINK.STATUS >>-BPC.BFM.LINK.STATUS--+-------------+--+-------------+--flowBpelId->< '-elementName-' '-description-'
The following table describes the variable events.
Code | Description | Extension name | Situation | Event nature |
---|---|---|---|---|
21090 | Variable update | BPC.BFM.VARIABLE.STATUS | Report | CHANGED |
BPC.BFM.VARIABLE.STATUS >>-BPC.BFM.VARIABLE.STATUS--variableName--+-----------------+--bpelId->< +-variableData----+ '-variableData_BO-'
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)