Index Changes

Difference between version and version     

Back to IEPKPI, or IEPKPI Info


At line 1 changed 3 lines.
__IEP Process to Measure KPIs__
The following section describes how one can use IEP to create a process that measures KPI for bpel service engine.
The Event interface in BPEL monitoring can give the message structure.
! __IEP Process to Measure KPIs__
----
The following section describes how to use IEP SE to create a process that measures KPI(Key Performance Indicator) for [BPEL SE |http://wiki.open-esb.java.net/Wiki.jsp?page=BPELSE].
Refer [BPEL SE Monitoring |http://wiki.open-esb.java.net/Wiki.jsp?page=BPELSEEventListener] for event structures and interfaces.
At line 5 changed 2 lines.
For Activity monitoring we will capture Activity Start and Activity Finished events as two input streams.
ActivityStart and ActvityFinished.
For __Activity Monitoring__ we will capture ''Activity Start'' and ''Activity Finished'' events as two input streams.
At line 10 changed 1 line.
the event structure is same for ActivityFinished.
the event structures for ActivityFinished and ActivityStart are same. The BPEL engine event sender takes care of the type of event to stream mapping through different end points.
At line 12 changed 2 lines.
the next step is to create a time based buckets for these events so that relations are based on a finite size of events. In the sample project the time based window is used for this purpose with window size of 5 hours.
We combined the result from these time based buckets into a relation map like following
Next step is to create time based buckets for these events so that relation is based on a finite size of events. In the sample project the time based window is used for this purpose with window size of 5 hours.
Then combine the result from these time based buckets into a relation map as following
At line 22 changed 1 line.
Next step is to aggregate the relation into required groups as following
the elapsed time from start to end is calculated as an expression in Relation map as timeGap.
At line 25 added 2 lines.
Next step is to aggregate the relation into required groups and and statistics as following .
At line 28 added 1 line.
The map collects MIN , MAX , AVERAGE of the time gap based on instance id and engine id.
At line 26 changed 1 line.
After the aggregation with required groupings is available we'll save the result into an Output Global table as following which will then can be accessed to see the KPIs.
After the aggregation with required groupings and statistics is available we'll save the results into an Output Global table which can be accessed to see the KPIs.
At line 36 added 4 lines.
----
----
For BPEL __Instance level KPI monitoring__ ''BPInstance Start'' and ''BPInstance Complete'' events are captured by using two Input Stream Operators,
BPInsatnceStartEventStream and BPInstanceComplete, the message structure follows the instance event generated by BPEL engine.
At line 33 removed 3 lines.
For BPEL Instance level KPI monitoring BPInstance Start and BPInstance Complete events are captured by using two Input Stream Operators
BPInsatnceStartEventStream and BPInstanceComplete the message structure follows the instance event generated by BPEL engine.
At line 38 changed 1 line.
Rest of the IEP process design is same as that of Activity monitoring with time based buckets and a relation map followed by an relation aggregator to aggregate time elapsed into required categories. The result are saved into a global table to be accessed by other applications.
Rest of the IEP process design is same as that of Activity monitoring with time based buckets and a relation map followed by a relation aggregation to aggregate time elapsed into required categories. The results are saved into a global table to be accessed by other applications.
At line 47 added 3 lines.
* [IEP Process Source Code |KPIs.zip]

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This page (revision-14) was last changed on 25-Feb-08 17:54 PM, -0800 by Rahul Dwivedi