GT 3.9.4 WS MDS Aggregator: Developer's Guide
- Introduction
- Architecture and design overview
- Public interface
- Usage scenarios
- Tutorials
- [missing links]
- Security considerations
- Troubleshooting
- Related Documentation
Introduction
The aggregator framework allows pluggable data sources and sinks to be written and connected together. Generally a source collects data from or about a particular grid resource, and passes it to a sink which does something interesting with it.
The sources and sinks supplied with the toolkit are:
| Name | Description | Class |
|---|---|---|
| Query | The query source collects information from a registered resource by using WS-Resource Properties polling mechanisms (the GetResourceProperty, GetResourceProperties and QueryResourceProperties operations). Polls are made periodically, with both the period and target Resource Properties specified in the registration message. | org.globus.mds.aggregator.impl.QueryAggregatorSource |
| Subscription | The subscription source collects information from a registered resource using WS-Notification mechanisms. Data is delivered when property values change, rather than periodically. | org.globus.mds.aggregator.impl.SubscriptionAggregatorSource |
| Execution | The execution source collects information about (not necessarily from) a registered resource by execution of a local executable, which is passed as input the identity of the registered resource. Details of the interface between the execution source and local executables are in the domain specific interfaces section of the aggregator public interface guide. | org.globus.mds.aggregator.impl.ExecutionAggregatorSource |
| Servicegroup sink / Index service | The servicegroup sink (used by the Index Service) publishes received data as content in the AggregatingServiceGroup entry used to manage the registration. This data can therefore be retrieved by querying the index for its 'entries' resource property. |
|---|---|
| Trigger service | The trigger service provides an aggregator sink which receives data, applies tests to that data, and if the tests match, runs a specified executable. See the trigger service documentation for more information. |
[link to General Toolkit Developer's Guide for coding guidelines, porting guide, etc.]
Architecture and design overview
[link to architecture and design docs]
Public interface
The semantics and syntax of the APIs and WSDL for the component, along with descriptions of domain-specific structured interface data, can be found in the public interface guide.
Usage scenarios
[describe how to use the programatic interfaces of the component, provide examples]
Tutorials
[add links to any tutorials - if no tutorials, say "There are no tutorials available at this time"]
Security considerations
[describe security considerations relevant for this component]
Troubleshooting
[help for common problems developers may experience]
Related Documentation
[could link to pdfs and whitepapers about protocols, etc re: the component]