Administration Guide for Oracle Self-Service E-Billing > Configuring Jobs > Billing Job Types >

Configuring a Notifier Job

The Notifier job extracts the email address registered for each bill-ready account and composes a single, consolidated email for the address. The Notifier job then sends the composed email to the recipients.

To send queued email messages, you must run Notifier after any job that was configured to generate email notifications. You can configure Notifier to run for all notification types or for one particular type of message only, such as:

• Payment reminders
• A payment is due
• A statement is ready
• A user's credit card expires
• User enrolls in an account
• User updates a personal profile
• User creates, updates or deletes a payment account
• User makes an instant payment
• User schedules a one-time or recurring payment

The types of notifications you can send are listed in the Notifier task parameters.

The Notifier job sends email based on entries that are stored in the MESSENGER_GROUP_TABLE table in the OLTP database, composes the correct email message based on email templates, and sends it to the users to whom the messages are addressed.

The Notifier job consists of two tasks:

• NotificationComposer
• NotificationDispatch

Configuring the NotificationComposer Task

The NotifierComposer task extracts the email address registered for each bill-ready account and composes a single, consolidated email for the address. It writes the email message to the location specified and stores the name of the email file and the email address in MESSENGER_QUEUE_TABLE.

This task references the MESSENGER_GROUP_TABLE table. For each entry with a value in MESSAGE_TYPE matching the Message type parameter value, the task composes the corresponding email message and stores the composed message in the local message repository. The repository file directory is specified in the EDX_HOME/xma/config/com/edocs/common/notification/notification.xma.xml file, in the GlobalConfigurationBean section with the bean configuration property value of mailQueueStorageDirectory. In the path, EDX_HOME is the directory where you installed Oracle Self-Service E-Billing. The location of the message file is in the MESSENGER_QUEUE_TABLE table.

To send and receive email, you must configure the Notification.xma.xml file for the email address and password (mail.user and mail.password values).

To configure the Notification.xma.xml file

• Edit the notification.xma.xml file, found in the EDX_HOME/xma/config/com/edocs/common/notification directory. Specify the mail.user and mail.password values:

  <prop key="mail.host">stbeehive.yourcompanydomain.com</prop>

  <prop key="mail.transport.protocol">SMTP</prop>

  <!-- For requiring authentication mail server -->

  <prop key="mail.smtp.auth">true</prop>

  <prop key="mail.user">eBillingAdmin_WW@yourcompanydomain</prop>

  <prop key="mail.password">eBilling603</prop>

  <!-- For SSL connection mail server-->

  <prop key="mail.smtp.socketFactory.class">javax.net.ssl.SSLSocketFactory</prop>

  <prop key="mail.smtp.socketFactory.port">465</prop>

  </props>

Parameters for Configuring the NotificationComposer Task

Table 6 describes the configuration parameters for the NotificationComposer task.

Table 7 Describes the valid message types you can specify in the Message type field for the NotificationComposer task.

Parameters for Configuring the NotificationDispatcher Task

The NotificationDispatcher task sends email messages that are prepared by the NotificationComposer task to the corresponding end users. The detail implementation logic can vary depending upon the implementation Java class provided by the input parameter value.

The default implementation class is com.edocs.common.notification.queue.QueueDispatcher. In this implementation it looks for entries that are stored in MESSENGER_QUEUE_TABLE and sends email to the user for each entry. If email sending fails, then the message entry stays in the MESSENGER_QUEUE_TABLE until it is sent in the next attempt. Based on the task parameter value, the entry can be removed from the table and from the message repository after the message is sent successfully.

Table 8 describes the configuration parameters for the NotificationDispatcher task.