2010
DOI: 10.1109/mic.2010.66
|View full text |Cite
|
Sign up to set email alerts
|

Comprehensive Monitoring of BPEL Processes

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
27
0

Year Published

2010
2010
2018
2018

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 48 publications
(30 citation statements)
references
References 7 publications
0
27
0
Order By: Relevance
“…SAP monitoring architecture, workflow or BPEL engine and (ii) ad-hoc instrumentation, e.g. through the development of event captors or other online process inspection techniques [2].…”
Section: Implementing the Methodologymentioning
confidence: 99%
See 2 more Smart Citations
“…SAP monitoring architecture, workflow or BPEL engine and (ii) ad-hoc instrumentation, e.g. through the development of event captors or other online process inspection techniques [2].…”
Section: Implementing the Methodologymentioning
confidence: 99%
“…Web service-based processes are intrinsically cross-organizational, since each orchestrated Web service can in principle be exposed by a different organization. In this context, we can distinguish between intrusive and non-intrusive monitoring [2,13]. The former involves the interleaving of service and monitoring activities at runtime, whereas the latter separates the business from the monitoring logic, since information relevant for monitoring can be captured non-intrusively while a process is executing, e.g.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…In the world of software programs monitoring, the monitoring variable is the target, for instance, of a watch for debugging. In business process monitoring, the monitoring variable may range from infrastructure-level data, such as timestamps of service calls [5], to application-level process data, such as the status of an activity or domain specific data produced by an activity [6][7]. Note that a value of the monitoring variable represents a single data element captured by MI during the execution of the business process, e.g.…”
Section: Monitoring Dimensions and Optionsmentioning
confidence: 99%
“…In a business setting, while in many cases we can make the hypothesis that monitoring is permanently enabled, defining anchoring points may be helpful when capturing and making available the values of MV to MC is very costly. Intrusive process monitoring [5] is an example of this scenario, since the execution of monitoring statements blocks and, therefore, delays, the execution of the process. In such a scenario, the MC may want to enable monitoring only when strictly necessary.…”
Section: Monitoring Dimensions and Optionsmentioning
confidence: 99%