lauraj
April 19 2010, 07:48 PM
Attached is an example of a custom event action that can be triggered on demand from the Event Manager.
This example action allows the user to set up predefined recipient groups that can be e-mailed. To use the script:
1. Extract the contents of the attached ZIP archive under the Traverse installation directory. This will create three new files under TRAVERSE_HOME\plugin\actions directory. One is the Perl script, and the other 2 are the configuration files in .xml format.
2. Modify the configuration files to reflect your environment. Each .xml file represents a different e-mail group. You will want to change only the following things:
a. The <name> field. This is how the action will be displayed on the Event Details console.
b. The first 4 parameters under the <parameters> tag. The other parameters will be automatically populated by the event information. The parameters you will provide will be:
--recipients=email1@company.com,email2@company.com
--mail-server=mail.company.com
--domain=company.com
--bve-host=bve01
Where "recipients" is a comma separated list of recipient names, "mail-server" reflects the FQDN of your mail server, "domain" reflects your domain address (company.com), and "bve-host" reflects the hostname of your BVE.
You can add multiple .xml files to reflect more groups.
3. Finally, restart the Correlation & Summary Engine and Web Application components of Traverse (summary.init and webapp.init on Linux installations).
Now when you navigate to the Event Manager and click on an event to open the Event Details, you will see the following 2 new entries in the drop-down list (assuming you kept the default names):
E-mail Group 1
E-mail Group 2
When one of these actions is triggered, no input is required from the user. The system will automatically e-mail the specified users from the .xml file.
A screenshot is attached to illustrate the example.
This example action allows the user to set up predefined recipient groups that can be e-mailed. To use the script:
1. Extract the contents of the attached ZIP archive under the Traverse installation directory. This will create three new files under TRAVERSE_HOME\plugin\actions directory. One is the Perl script, and the other 2 are the configuration files in .xml format.
2. Modify the configuration files to reflect your environment. Each .xml file represents a different e-mail group. You will want to change only the following things:
a. The <name> field. This is how the action will be displayed on the Event Details console.
b. The first 4 parameters under the <parameters> tag. The other parameters will be automatically populated by the event information. The parameters you will provide will be:
--recipients=email1@company.com,email2@company.com
--mail-server=mail.company.com
--domain=company.com
--bve-host=bve01
Where "recipients" is a comma separated list of recipient names, "mail-server" reflects the FQDN of your mail server, "domain" reflects your domain address (company.com), and "bve-host" reflects the hostname of your BVE.
You can add multiple .xml files to reflect more groups.
3. Finally, restart the Correlation & Summary Engine and Web Application components of Traverse (summary.init and webapp.init on Linux installations).
Now when you navigate to the Event Manager and click on an event to open the Event Details, you will see the following 2 new entries in the drop-down list (assuming you kept the default names):
E-mail Group 1
E-mail Group 2
When one of these actions is triggered, no input is required from the user. The system will automatically e-mail the specified users from the .xml file.
A screenshot is attached to illustrate the example.