GT 4.0 WS MDS Trigger Service: User's Guide

1. Introduction

The WS MDS Trigger Service collects information about Grid resources and can be configured to execute a program if the collected data meets certain conditions.

End-users will typically interact with the Trigger Service indirectly, using some mechanism specific to the triggered executable program (for example, an executable program may send mail to an end-user or write a structured log file that will later be read by some other program).

2. Command-line tools

The Trigger Service itself does not have any command-line clients for end users; instead, the trigger service is configured to run an executable program to take some action (for example, send mail to a set of users, or write a log entry to a file).

The mds-servicegroup-add command in the Aggregator Framework is used to configure the Trigger Service to collect information from various sources.

3. Graphical user interfaces

There is no GUI specifically for the Trigger Service. The release contains WebMDS which can be used to display the status of resources registered to a Trigger Service in a normal web browser.

4. Troubleshooting

The Trigger Service does not have any end-user clients. General troubleshooting information can be found in the GT 4.0 Java WS Core User's Guide.

5. Usage statistics collection by the Globus Alliance (4.0.5+)

Starting with 4.0.5, the following usage statistics are sent by default in a UDP packet each time a registration is made to an Index Service or Trigger Service:

  • Service name
  • Total number of registrations
  • Number of current registrations
  • Time that the aggregator resource was created

If you wish to disable this feature, please see the Java WS Core System Administrator's Guide section on Usage Statistics Configuration for instructions.

Also, please see our policy statement on the collection of usage statistics.