Software Links
Getting Started
- Doc Structure
- A Globus Primer
- Globus Is Modular!
- Quickstart
- Installing GT
- Platform Notes
- GT Developer's Guide
- GT User's Guide (coming soon)
- Migrating from GT2
- Migrating from GT3
Reference
- Best Practices
- Coding Guidelines
- API docs
- Public Interfaces (coming soon)
- Resource Properties
- Samples
- Glossary
- Performance Studies (coming soon)
Manuals
Common Runtime
Security
- Non-WS (General) Security
- WS Java Security
- Message-level
- Authz Framework
- CAS
- Delegation Service
- MyProxy
- GSI-OpenSSH
- SimpleCA
- SGAS
Data Mgt
MDS4
Execution Mgt
Table of Contents
The Archive Service retrieves and stores snapshot or state information from Web Services (Grid Resources) at specified time intervals. If desired, a virtual organization can deploy one or more Archive Services to collect data on all of the Grid resources available within that virtual organization so that their usage or published information can be tracked over time.
Features new in release 4.1.3
Based on WSRF rather than OGSI
- Aggregated data is published through WS-Resource Properties mechanisms
- The Aggregator Framework module (basis of the archive 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 archive 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
- None.
The following problems and limitations are known to exist for the MDS4 Archive Service at the time of the 4.1.3 release:
The Archive Service depends on the following GT components:
The Archive Service depends on the following 3rd party software:
- None
Tested Platforms for MDS4 Archive Service:
- Linux on i386
- Windows XP
- Linux on PPC
Tested containers for MDS4 Archive Service:
- Java WS Core container
- Tomcat 5.0.28
Protocol changes since GT version 4.0.5
- Generally incompatible with the GT 3.x archive service as the service has been remodelled to use WSRF instead of OGSI.
API changes since GT version 4.0.5
- The Aggregator Framework API used internally has retained the general flavor of the GT 3.2 Aggregator Framework API, but is not directly compatible with it.
Schema changes since GT version 4.0.5
- Schemas used for configuration and publishing are conceptually similar but are not compatible, primarily due to WSRF remodelling.
Associated standards for MDS4 Archive Service:
- WS-ResourceProperties (WSRF-RP)
- WS-ResourceLifetime (WSRF-RL)
- WS-ServiceGroup (WSRF-SG)
- WS-BaseFaults (WSRF-BF)
- WS-BaseNotification
- WS-Topics
See Archive Servicefor more information about this component.