State and events for web services: a comparison of five WS-resource framework and WS-notification implementations

Grid and sensor web technologies for environmental monitoring

“…Traditionally, the implementation of such properties requires translation between XML Schema and Java code. However, the XML Schema of the SOS and related standards, in particular GML (Humphrey et al 2005), is a very complex one, and there are no available program tools able to generate Java classes from it. We have solved this problem by storing service capabilities and sensor descriptions data as Document Object Model (DOM) Element objects, and using custom serialization for this class provided by the Axis framework that is used by the Globus Toolkit.…”

“…Many Sensor Web fea- -Sensors discovery could be performed through the combination of Index Service and Trigger Service; -High-level access to XML description of the sensors and services could be made through queries to the Index Service; -Grid platform provides a convenient way for the implementation of notifications and event triggering using corresponding platform components (Humphrey et al 2005); -Reliable File Transfer (RFT) service (Allcock et al 2005) provides reliable data transfer for large volumes of data; -Globus Security Infrastructure (Welch et al 2003) provides enforcement of data and services access policies in a very flexible way allowing implementation of desired security policy.…”

HAND: Highly Available Dynamic Deployment Infrastructure for Globus Toolkit 4

“…With the introduction of OGSA [11], the focus of Grid computing moved from legacy computing-intensive applications to service-oriented computing based on open standards. Globus Toolkit (GT) development has tracked this trend, with GT4 [10,12] building on the Web Service Resource Framework (WSRF) specifications to provide an efficient, extensible, stateful, and flexible Grid middleware.…”

“…Also, we increased the JVM memory to 1G by adding the '-Xms64m -Xmx1024m' parameter. Figure 6 presents the experimental results in the different service-level (10,200, 400, and 600 services) environment. In this figure, HAND-C is our container-level implementation, HAND-S is the service-level implementation, and TOMCAT denotes the Apache Tomcat hosting environment.…”

Reusable Cost-Based Scheduling of Grid Workflows Operating on Higher-Order Components

“…We use Higher-Order Components (HOCs [11]) -reusable components that are customizable for particular applications using parameters which may be either data or code. HOCs include the configuration required to run on top of a standard Grid middleware [13] and can be remotely accessed via Web Services. Thereby, HOCs abstract over the technical features of the Grid platform and allow their users to concentrate on their applications.…”