This component is deployed as part of the standard toolkit installation. By default, there are no trigger actions set to fire on container startup, as these must be configured and registered manually.

1. Manually registering the Trigger Service

To manually register the example described in Configuring the Trigger Service (above) do the following:

Configure your environment with either Ganglia or Hawkeye as described in the GLUE RP documentation. This is necessary because the trigger service relies on polling the GLUE RP which is provided by either one of them. Note: Even without configuring Ganglia or Hawkeye, the GLUE RP is emitted by the scheduler configured for your environment, so this step is not strictly necessary.
Now you can start your container as you normally do by running:
```
$GLOBUS_LOCATION/bin/globus-start-container [-p port] [-nosec]
```

At this point, we're ready to make a registration with the TriggerRegistrationService by running a command similar to the following:

$GLOBUS_LOCATION/bin/mds-servicegroup-add \        
     $GLOBUS_LOCATION/etc/globus_wsrf_mds_trigger/trigger-registration-example.xml

You should see output similar to the following if your environment has been configured properly:

Processing configuration file...
INFO: Processed 1 registration entries
INFO: Successfully registered https://127.0.0.1:8443/wsrf/services/DefaultIndexService \
to servicegroup at https://127.0.0.1:8443/wsrf/services/TriggerRegistrationService

Prev		Next
Configuring	Home	Testing