GT 4.0 WS MDS Trigger Service: Fact Sheet

Table of Contents

1. Brief component overview
2. Summary of features
3. Usability summary
4. Backward compatibility summary
5. Technology dependencies
6. Tested platforms
7. Associated standards
8. For More Information

1. Brief component overview

The Trigger Service collects data from resources on the grid and, if administrator defined rules match, can perform various actions. An example use is to send email when queue length on a compute resource goes over a threshold value.

2. Summary of features

Features new in release 4.0

  • Not applicable

Other Supported Features

  • Monitors resource properties for matching trigger conditions
  • When a trigger condition matches, fires a customizable action: for example, sends email to an administrator.
  • Monitored services are managed through service group-based registration API, allowing use of many of the same clients that can be used in the Index Service.

Deprecated Features

  • Not applicable

3. Usability summary

Usability improvements for WS MDS Trigger:

  • >The MDS Trigger Service is new for the Globus Toolkit 4 release.

4. Backward compatibility summary

The Trigger Service is a new component for GT 4.0 and so has no compatibility statement.

5. Technology dependencies

The Trigger Service depends on the following GT components:

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

  • None

6. Tested platforms

Tested Platforms for WS-MDS Trigger Service

  • Linux on i386
  • Windows XP

Tested containers for WS-MDS Trigger Service:

  • Java WS Core container
  • Tomcat 5.0.28

7. Associated standards

Associated standards for WS MDS Trigger:

  • WS-ResourceProperties (WSRF-RP)
  • WS-ResourceLifetime (WSRF-RL)
  • WS-ServiceGroup (WSRF-SG)
  • WS-BaseFaults (WSRF-BF)
  • WS-BaseNotification
  • WS-Topics

8. For More Information

Click here for more information about this component.