Table of Contents
The Aggregator Framework is the software framework on which WS MDS services (currently, the Index, Trigger and Archive 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 Index, Trigger and Archive Services interfaces.
Features new in release GT 4.2.0
- The mds-servicegroup-add command no longer requires the -s or -e arguments
- The mds-set-multiple-termination-time command has been created to aid in lifetime management of service group entry resources created via mds-servicegroup-add
Other Supported Features
- Collects information from grid resources using pluggable aggregation sources which collect information by polling, subscription, and by execution of local scripts.
- Delivers collected information to pluggable information sinks.
- Management of individual aggregations is now performed over the wire through WS ServiceGroup APIs.
- The QueryAggregatorSource and SubscriptionAggregatorSource now attempt to detect when the data source EPR is local to the current container instance, and if so set the connection properties to use local transport.
- Added a service level configuration option for suppressing the publication of aggregator configuration elements in aggregator service group registry entries. In other words, the Service Group "Content" Resource Property will contain only the aggregated data.
The mds-servicegroup-add command no longer requires the dummy -s or -e arguments
The mds-set-multiple-termination-time command has been added to aid in management of service group entry resources created via mds-servicegroup-add
The
QueryAggregatorSourceandSubscriptionAggregatorSourcenow attempt to detect when the data source EPR is local to the current container instance and, if so, set the connection properties to use local transport.Added a service level configuration option for suppressing the publication of aggregator configuration elements in aggregator service group registry entries. In other words, the Service Group Entry
ContentResource Property will contain only the aggregated data.Due to changes in the final version of the WS-ServiceGroup specification, the XML structure of a ServiceGroupEntry's
ContentResource Property is no longer directly mapped to the AggregatorContent type. Instead, the AggregatorContent type is now represented as a child element of the WS-SGContentelement.
- Bug 2432: Aggregator sample config file should have tls-style urls
- Bug 2388: rejected add() leaves incomplete state behind which then upsets the sweeper
- Bug 2384: remove stack trace from execution source error
- Bug 2377: support multiple aggregator sources in one aggregator
- Bug 2157: Aggregator entries do not implement WS-Resource Lifetime resource properties
- Bug 2145: query source waits entire reg period before making first request
- Bug 2105: flatten schema in CVS
- Bug 2097: IndexDefaultWidgetTest registers same widget many times
- Bug 2087: getresourceproperty poll source does not tolerate whitespace in RP name
- 2082: index and aggregator stub generation is generating metrics stubs
- 2191: AggregatingServiceGroupEntries do not implement Service Group EPR properly
- All fixed Aggregator Framework bugs and enhancement requests
- 2339: Registered services connection refused messages
- 2398: index service does not appear to have wsrf-query support (any more)
- 2850: WS MDS logs to INFO when DEBUG should be used
- 2958: WS-MDS Aggregator Junit test execution has no results
- 2963: need to create libexec/aggrexec dir as part of MDS install
The following problems and limitations are known to exist for WS MDS Aggregator Framework at the time of the 4.2.0 release:
- 2082: index and aggregator stub generation is generating metrics stubs
- 2191: AggregatingServiceGroupEntries do not implement Service Group EPR properly
- 2339: Registered services connection refused messages
- 2398: index service does not appear to have wsrf-query support (any more)
- All open aggregator bug reports and enhancement requests
- 2807: execution aggregator source junit test needs some work
- 3150: AggregatingServiceGroup* needs to provide Resource.Remove...
- 3177: AggregatingServiceGroup EntrySweeper interval needs to be...
- All open aggregator bug reports and enhancement requests
Aggregator Framework depends on the following GT components:
- Java WS Core
Aggregator Framework depends on the following 3rd party software:
- None
Protocol changes since GT version 4.0.x
- The Aggregator Framework is affected by the Java WS Core protocol changes (see the Java WS Core Release Notes for details)
API changes since GT version 4.0.x
- None. Aggregator sources and execution information providers written for GT version 4.0.x should continue to work in this version.
Schema changes since GT version 4.0.x
- See the Java WS Core Release Notes.
Associated standards for WS MDS Aggregator Framework:
- WS-ResourceProperties (WSRF-RP)
- WS-ResourceLifetime (WSRF-RL)
- WS-ServiceGroup (WSRF-SG)
- WS-BaseNotification
- WS-Topics
See Aggregator Framework for more information about this component.