Overview of Configuration Management Server-Side Triggers
Configuration management server-side triggers execute in response to an action on the Integrity Lifecycle Manager client, and reside on the Integrity Lifecycle Manager server where they are executed.
Server-side triggers are administered through the file system of the Integrity Lifecycle Manager server and are enabled by default through > > in the Integrity Lifecycle Manager administration client.
Some uses for configuration management server-side triggers include:
• Send an e-mail to the change package creator, reviewer, or watcher if change package review is enabled
• Apply a label to a revision with the name of the user who checked in the revision
• Prevent users from adding members of a certain file type
• Ensure change package entries occur on the same development path for a change package
• Send an e-mail to the configuration management administrator when configuration management projects or subprojects are added or dropped
Restarting Integrity Lifecycle Manager server
Once you have created the event triggers and updated the events definition file, you can restart the Integrity Lifecycle Manager server to have the triggers take effect immediately.
For more information on running the Integrity Lifecycle Manager server, see the Running Integrity Lifecycle Manager server topic in the Install and Configuration documentation.
Related Links