GT 3.9.4 WS MDS Index Service: Developer's Guide

Introduction

[introduction to developers with reference 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"]

Feature summary

Features new in release 3.9.4

  • Based on WSRF rather than OGSI
    • Aggregated data is published through WS-Resource Properties mechanisms
    • The aggregator module (basis of the index service) collects data from monitored resources using WS-Resource Properties collection mechanisms, including the base WS-Resource Properties poll operations and WS-Notification.
  • Persistent configuration of aggregations has been refactored. The service no longer has its own config file for specifying aggregations. Instead a separate client is used to make appropriate registrations. This client may be started alongside the container for the equivalent effect. The client may also be deployed elsewhere to support resource-side configuration (providing similar functionality to the GT3.2 RegistryPublishProvider) or at a third location.

Other Supported Features

  • The index appears as a ServiceGroup (defined in WSRF) which lists registered resources alongside dynamically collected information from those resources. This information can be examined using (for example) XPath queries to discover resources that match desired constraints.

Deprecated Features

  • Support for Xindice and aggregated data persistence has been removed.
  • The ability to specify default aggregations in service config file has been removed (see item in 'New Features').
  • Non-ServiceGroupRegistration methods for managing aggregations have been removed; the equivalent functionality is available through the ServiceGroupRegistration port type which is available in both GT3.2 and GT 3.9.3.0 versions of the index service.

Tested platforms

Tested Platforms for [component name]

  • platform #1
  • ...
  • platform #n

Backward compatibility summary

Protocol changes since GT version 3.2

  • Generally incompatible with the GT3.2 index service as the service has been remodelled to use WSRF instead of OGSI.

API changes since GT version 3.2

  • The aggregator API used internally has retained the general flavor of the GT3.2 aggregator API, but is not directly compatible with it.

Schema changes since GT version 3.2

  • Schemas used for configuration and publishing are conceptually similar but are not compatible, primarily due to WSRF remodelling.

Technology dependencies

The Index Service depends on the following GT components:

  • WSRF Core

The Index Service depends on the following 3rd party software:

  • None

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]