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

GEMLCA: Running Legacy Code Applications as Grid Services

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
47
0

Year Published

2006
2006
2014
2014

Publication Types

Select...
5
4
1

Relationship

4
6

Authors

Journals

citations
Cited by 100 publications
(51 citation statements)
references
References 19 publications
0
47
0
Order By: Relevance
“…The GEMLCA [9] service has several internal (e.g. a Globus Toolkit 4 (GT4) service container) and external dependencies (e.g.…”
Section: Methodsmentioning
confidence: 99%
“…The GEMLCA [9] service has several internal (e.g. a Globus Toolkit 4 (GT4) service container) and external dependencies (e.g.…”
Section: Methodsmentioning
confidence: 99%
“…OGSA-BES basic execution service implementations and JSDL job submission description language repositories) or other generic application wrappers (e.g. Application Hosting Environment (AHE) [4], Grid Execution Management for Legacy Code Application (GEMLCA) [5], Generic Application Service Factory (gFac) [9]). A specific interface is tuned for the application and written by either the application developers or by the user community.…”
Section: Service and Application Deployment Issuesmentioning
confidence: 99%
“…Examples of such systems include LGF [11] which wraps legacy code as Globus 4 services on a fine-grained level, or GEMLCA [12], which offers a more coarse-grained approach. However, they are limited to a single middleware suite, such as Globus 4.…”
Section: Related Workmentioning
confidence: 99%