Business process events

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.

The following tables show the situation-dependent data for the following business process events:
The columns are as follows:
Code
Contains the number of the event. The value is written to the Common Base Event as an extended data element with the name BPCEventCode.
Extension name
Contains the string value that is used as the value of the extensionName attribute of the Common Base Event.

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.

Situation
Refers to the situation name of the business process event. For details of situations, see Situations in business process events.
Event nature
A pointer to the event situation for a business process element in the EventNature parameter, as they are displayed in WebSphere® Integration Developer.
ECS current ID
ECS parent ID
Contain the identifiers of the event correlation spheres. These values are written to the Common Base Event as the context data elements ECSCurrentID and ECSParentID.

Process events

For process events:
  • The ESCcurrentID provides the ID of the process instance.
  • The ECSParentID is the ECSCurrentID before the process instance start event of the current process.
Code Description Extension name Situation Event nature
21000 Process started BPC.BFM.PROCESS.START1 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.STATUS Report RESTARTED
21020 Process deleted BPC.BFM.PROCESS.STATUS Destroy DELETED
42001 Process failed BPC.BFM.PROCESS.FAILURE2 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.CORREL3 Report CORRELATION
42041 Process work item deleted BPC.BFM.PROCESS.WISTATUS1 Report WI_DELETED
42042 Process work item created BPC.BFM.PROCESS.WISTATUS1 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.STATUS Report EV_ESCALATED
Note:
  1. The following extended data element is added to the event:
    username
    The names of the users who are associated with the event
  2. The following extended data element is added to the event:
    processFailedException
    The exception that caused the process to fail
  3. The following extended data element is added to the event:
    correlationSet
    The content is added as an XML fragment of type hexBinary

Activity events

For activity events:
  • The ESCcurrentID provides the ID of the activity.
  • The ECSParentID provides the ID of the containing process.
Code Description Extension name Situation Event nature
21006 Activity ready BPC.BFM.ACTIVITY.STATUS Start CREATED
21007 Activity started For invoke operations: BPC.BFM.ACTIVITY.MESSAGE1. For all other operation types: BPC.BFM.ACTIVITY.STATUS Start ENTRY
21011 Activity completed For invoke, staff, receive, and reply operations: BPC.BFM.ACTIVITY.MESSAGE1. For all other operation types: BPC.BFM.ACTIVITY.STATUS Stop EXIT
21021 Claim canceled BPC.BFM.ACTIVITY.STATUS Report DEASSIGNED
21022 Activity claimed BPC.BFM.ACTIVITY.CLAIM2 Report ASSIGNED
21027 Activity terminated BPC.BFM.ACTIVITY.STATUS Stop TERMINATED
21080 Activity failed BPC.BFM.ACTIVITY.FAILURE3 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.MESSAGE1 Report OUTPUTSET
42013 Activity fault message set BPC.BFM.ACTIVITY.MESSAGE1 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.MESSAGE1 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.WISTATUS4 Report WI_DELETED
42040 Work items created BPC.BFM.ACTIVITY.WISTATUS4 Report WI_CREATED
42050 Activity escalated BPC.BFM.ACTIVITY.STATUS Report ESCALATED
42054 Activity work items refreshed BPC.BFM.ACTIVITY.WISTATUS4 Report WI_REFRESHED
42055 Work item transferred BPC.BFM.ACTIVITY.WITRANSFER5 Report WI_TRANSFERRED
Note:
  1. The following extended data element is added to the event:
    message or message_BO
    The input or the output message as a string or Business Object (BO) representation
  2. The following extended data element can be added more than once to the event:
    username
    The names of the users who are associated with the event
  3. The following extended data element is added to the event:
    activityFailedException
    The exception that caused the activity to fail
  4. The following extended data element is added to the event:
    username
    The names of the users who are associated with the event
  5. The following extended data elements are added to the event:
    current
    The name of the current owner of the work item
    target
    The name of the new owner of the work item

Scope events

For scope events:
  • The ESCcurrentID provides the ID of the scope.
  • The ECSParentID provides the ID of the containing process.
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.FAILURE1 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.STATUS Report EV_ESCALATED
Note:
  1. The following extended data element is added to the event:
    activityFailedException
    The exception that caused the activity to fail

Link events

For link events:
  • The ESCcurrentID provides the ID of the source activity of the link.
  • The ECSParentID provides the ID of the containing process.
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

Variable event

For the variable event:
  • The ESCcurrentID provides the ID of the containing scope or process.
  • The ECSParentID is the ECSCurrentID before the process instance start event of the current process.
Code Description Extension name Situation Event nature
21090 Variable update BPC.BFM.VARIABLE.STATUS Report CHANGED

Terms of use | | Broken links

Last updated: Tue Dec 06 04:14:40 2005

(c) Copyright IBM Corporation 2005.
This information center is powered by Eclipse technology (http://www.eclipse.org)