Hi
*Current Event plan Proposed to monitor a BPEL Process (The Weekly Update)*
Last couple of weeks I was working on planing what are the events needed to
be monitored by BAM and making
an event plan for the project. In this project we have already had two event
listener classes, one which implements the BpelEventListener interface and
the other which implements MessageExchangeInterceptor interface. At the
begining theplan was to use either one of them to track events, but as the
requirements were identified I decided to use both these implementationsas
they track different events of a BPEL process.
The Event plan is as follows;
Mainly the events are gathered from six activity phases of a BPEL process;
Process Invoked Event
when a new BPEL process is invoked an event will be generated.
Under this event there will be
attributes like Process Name and time stamp value to uniquely
identify the process invocation.
New instance creation of a process
This event will get invoked when a new instance of the BPEL
process is being created. This event contains
attributes like the name of the process, the time stamp value to get the
created time, an instance id to uniquely identify the created
instance and the current operation of the process .
Starting the newly created Instance
This event get invoked when a created instance get started. this event holds
attributes like process name, time stamp value, the instance id to
identify the started instance.
Message Exchange of an Instance
This event get triggered when a process instance has received a message at
any level; like for the invocation of an instance, invocation of a scope and
an actvity. This event contains attributes like process name , time stamp,
instance id, the current operation of the process which receives the message
and an message exchange id which is a string to identify a message received.
Partner service invocation from a process
when the bpel process calls for an external web service this event will get
triggered. A bpel process is linked with an partner service through a
partner link,therefore this event contains information about this partner
link mostly. This event contains process name, time stamp, instance id,
partner link id and the name of the partner service invoked.
A Failure of an Activity
when any kind of failure occured at an Activity of a process this event will
get triggered. Either it is a system failure or a failure in the BPEL
process this event will get triggered. This event contains information like
process Id, time stamp, instance id, the activity id of the Activity which
got failed and the reason for the failure.
Successful completion of the process instance
This get invoked when a process instance completes its instance life cycle
and no failure occured. This event contains basic attributes like Process
Id, time stamp and Instance Id.
These generated events has been able to publish as WS-Events successfully
after writing an event publisher class following the New BAM Data
publisher.This is the latest Event plan that I have come up with, request
any suggestions or modifications on this. From here onwards the project
needed to be continue towards using these published events on BAM, kindly
request suggestions for the next phases of the project.
Thank You
IsuruW
_______________________________________________
Carbon-dev mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
