2005
DOI: 10.1007/s10723-005-9015-3
|View full text |Cite
|
Sign up to set email alerts
|

Grid Service Orchestration Using the Business Process Execution Language (BPEL)

Abstract: Modern scientific applications often need to be distributed across Grids. Increasingly applications rely on services, such as job submission, data transfer or data portal services. We refer to such services as Grid services. While the invocation of Grid services could be hard coded in theory, scientific users want to orchestrate service invocations more flexibly. In enterprise applications, the orchestration of web services is achieved using emerging orchestration standards, most notably the Business Process E… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

1
67
0

Year Published

2007
2007
2012
2012

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 131 publications
(77 citation statements)
references
References 16 publications
1
67
0
Order By: Relevance
“…The appropriateness of BPEL is also examined and confirmed in [20][21][22]. These works mainly focus on scientific workflows and rely on extending or adapting BPEL, thus creating dialects.…”
Section: Related Workmentioning
confidence: 99%
“…The appropriateness of BPEL is also examined and confirmed in [20][21][22]. These works mainly focus on scientific workflows and rely on extending or adapting BPEL, thus creating dialects.…”
Section: Related Workmentioning
confidence: 99%
“…In comparison to the work on OMII-BPEL [6], CRESS has similar goals for practical grid service orchestration -though there are some differences. OMII-BPEL is focused on pragmatic support for modelling, enactment and monitoring large-scale scientific workflows.…”
Section: Implementation Structurementioning
confidence: 99%
“…This shows that when the number of process instances increases in ActiveBPEL, the number of threads may go well beyond what most systems can handle, eventually making the workflow to be aborted. Also users may run in to deadlocks if they try to limit the size of the thread pool of the servlet container [13]. The above study concludes by deciding that the scalability of ActiveBPEL is limited only by the limited hardware resources, which will be not an acceptable remark for an embeddable engine.…”
Section: Related Workmentioning
confidence: 99%
“…Interesting study about the scalability of ActiveBPEL engine has been presented in an earlier study [13].According to that ActiveBPEL engine requires two OS threads for the creation of a new BPEL process instance. This shows that when the number of process instances increases in ActiveBPEL, the number of threads may go well beyond what most systems can handle, eventually making the workflow to be aborted.…”
Section: Related Workmentioning
confidence: 99%