Overview of IDP E-Mailer

You can also manage subscribers who have sent or received problem traffic by sending them an e-mail message that gives them information about the problem detected. The SRC application library provides a demonstration application, named IDP E-Mailer, that uses the gateway extension feature for Dynamic Service Activator to send e-mail notifications to subscribers. For information about developing gateway clients that use the gateway extension, see Overview of the Web Services Gateway.

The SRC software lets you map an IP address, which IDP identifies to be associated with problem traffic, to a subscriber so that a message can be sent to the subscriber. In the sample application, you specify a domain to append to subscriber names to formulate an e-mail address. In a production implementation, you could integrate information from a customer database to gain access to actual e-mail addresses. You can use the sample IDP E-Mailer as a basis for an application specific to your environment.

The idpemail.war file comprises the files for the IDP E-Mailer servlet. You can locate this file on the SRC application library CD in the /webapp directory. You can deploy the file as it is as a demonstration application, or you can customize the files in the WAR file. The SRC application library supplies complete source code for the IDP E-Mailer servlet in the WEB-INF/src directory in the idpemail.war file.

How IDP E-Mailer Responds to Incidents Reported by IDP

When an incident activates the IDP E-Mailer application for a subscriber, the following arguments are provided to the application in the following order:

1. Source of the incident
2. Destination of the incident
3. Description of the incident

The application uses this information when it creates the e-mail message.

The demonstration IDP E-Mailer application is a servlet that maps a subscriber’s IP address (for addresses identified as the source or destination of detrimental traffic) to an e-mail address and then sends e-mail to the designated subscriber in the following manner:

1. Uses NIC to locate the SAE that manages the specified IP address.
2. Uses the SAE CORBA remote API to obtain the subscriber session for the IP address.
3. If the subscriber session is active, obtains the login name associated with the subscriber session.
4. Creates the e-mail address by appending a domain name that is specified in the IDP E-Mailer configuration to the subscriber login name. For example, for a domain specified as mycompany.com, and a subscriber login of ChrisB, the e-mail address would be ChrisB@mycompany.com.
5. Creates a message that includes the text received from IDP that specifies the IP address of the source of the detrimental traffic received, or the destination of the detrimental traffic being sent, and a description of the incident.
6. Sends the message.

The configuration for IDP E-Mailer specifies:

• Text to appear on the subject line of the e-mail
• Introductory text to appear in the body of an e-mail message for detrimental traffic sent by the subscriber
• Introductory text to appear in the body of an e-mail message for detrimental traffic sent to the subscriber

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.