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
Before you begin:
The Trigger Service has been rewritten and restructured for the most recent 4.1.3 version to allow for a number of improvements including the following new features:
- Individual triggers may be created without restarting the container.
- Once created, triggers can be enabled/activated or disabled/deactivated without restarting the container.
- The parameters which define the trigger can be edited individually, in real-time, without restarting the container.
Other Supported Features
- Uses the Aggregator Framework to monitor XML data 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
Tested Platforms for MDS4 Trigger Service
- Linux on i386
Tested containers for MDS4 Trigger Service:
- Java WS Core container
The Trigger Service is a new component for GT 4.1.3 and so has no compatibility statement.
The Trigger Service depends on the following GT components:
The Trigger Service depends on the following 3rd party software:
- None
The security considerations for the Aggregator Framework also apply to the Trigger Service:
By default, the aggregator sources do not use authentication credentials -- they retrieve information using anonymous SSL authentication or no authentication at all, and thus retrieve only publicly-available information. If a user or administrator changes that configuration so that a service's aggregator source uses credentials to acquire non-privileged data, then that user or administrator must configure the service's aggregator sink to limit access to authorized users.