Table of Contents
The Aggregator Framework is the software framework on which WS MDS services (currently, the WS MDS Index and WS MDS Trigger services) are built. The aggregator framework collects data from an aggregator source and sends that data to an aggregator sink for processing. Aggregator sources distributed with the Globus Toolkit include modules that query service data, acquire data through subscription/notification, and execute programs to generate data. Aggregator sinks include modules that implement the WS MDS Index service interface and the WS MDS Trigger service interface.
Features new in release GT 4.0
- Ported to use WSRF mechanisms (previously used OGSI).
- Additional sources which collect information by polling and by execution of local scripts.
- Management of aggregations is now performed over the wire through WS ServiceGroup APIs.
Other Supported Features
- Collects information from grid resources using pluggable aggregation sources.
- Delivers collected information to pluggable sinks.
- Manages creation and destruction of individual aggregation registrations.
Usability improvements for WS MDS Aggregator Framework:
- While the aggregator concept is not new to GT4, the MDS4 aggregator implementation is. In comparison to GT3, the aggregator framework has been rewritten to support the WSRF model and generalized to support a more flexible plug-in environment.
- Also different from the GT3 aggregator, service to service aggregation sessions are now established exclusively through Service Group registrations, and the lifetime of these aggregations is managed via WSRF Resource Lifetime functions.
Protocol changes since GT version 3.2
- The aggregator framework is a complete reimplementation of the MDS3 aggregator framework using WSRF rather than OGSI protocols.
- No wireside compatibility with MDS3 aggregator framework.
- Architectural similarity should make porting straightforward.
API changes since GT version 3.2
- APIs entirely rewritten, so no API compatibility.
- Architectural similarity should make porting straightforward.
Exception changes since GT version 3.2
- See API changes above.
Schema changes since GT version 3.2
- Registration interface uses WSRF rather than OGSI schemas.
- New per-source and per-sink configuration schemas.
Aggregator Framework depends on the following GT components:
- Java WS Core
Aggregator Framework depends on the following 3rd party software:
- None
Associated standards for WS MDS Aggregator Framework:
- WS-ResourceProperties (WSRF-RP)
- WS-ResourceLifetime (WSRF-RL)
- WS-ServiceGroup (WSRF-SG)
- WS-BaseNotification
- WS-Topics
Click here for more information about this component.