Setting Up Administrator Alerts for Email Marketing

This topic describes how to configure the Email Marketing Server to send email alerts to the administrator if the Email Marketing components malfunction.

To enable administrator alerts for a component, you must set the relevant properties in the log4j2.properties file for the component. Each of the abnormality conditions that generates an alert is defined in the log4j2.properties file for a particular package or class, as is the alert level. For example, the following condition triggers an Error alert when an error occurs in the OnPremiseAppListener class:

Note: The rollinguniquenumber will be the incremental value of the highest value used in the file.

logger.rolling<rollinguniquenumber>.name = com.siebel.sem.esd.integrated.OnPremiseAppListener
logger.rolling<rollinguniquenumber>.level = ERROR
logger.rolling<rollinguniquenumber>.additivity = false
logger.rolling<rollinguniquenumber>.appenderRef.rolling.ref = RollingFile

By default, the following predefined abnormality conditions trigger an alert for an Email Marketing Server component:

• Component is unable to communicate with the Marketing server

• Component is restarted

• Component failed to write to the queue

• Component is not licensed

• Component is unable to communicate with the MTA

Alert levels can be set to the following values: INFO, DEBUG, TRACE, WARNING, ERROR, or FATAL. The Email Marketing Server generates alerts for the ERROR level and above, but you can configure the alert level for each SMTP class.

The following procedure describes how to enable administrator alerts.

To configure administrator alerts

1. To send administrator alerts for either the ESD, the BHD, or the CTD components, navigate to the log4j2.properties file in the component installation directory for the daemon you want to configure.

2. Locate the # IT Alerts settings section of the file.

3. Uncomment the parameters shown in the following table, then enter values similar to those shown.

   Note: To send alerts from all three daemons, you must update these parameters in the log4j2.properties file of each component.

   Property	Description
   appender.smtp.from= CHANGE_ME	Defines the From Address that is used to generate the alerts.
   appender.smtp.Host=CHANGE_ME	Defines the SMTP host name that is used to send the alerts. This SMTP host must be different to the MTA's SMTP that is used to send marketing emails.
   appender.smtp.to= CHANGE_ME	Defines the recipient of the alerts.

4. Stop and restart the relevant component for the changes to the log4j2.properties file to take effect.