Notification Mailer

The Notification Mailer is a program that performs e-mail send and response processing for the Oracle Workflow Notification System. You need to implement the Notification Mailer only if you wish to have your workflow users receive their notifications via e-mail, as well as from the Notifications Worklist web page. The Notification Mailer polls the database for messages that have to be sent, dequeues these messages from the SMTP advanced queue, and performs the following action for each message:

The Notification Mailer also processes responses by interpreting the text of messages mailed to its response mail account and calling the appropriate notification response function to complete the notification.

The e-mail notifications are based on standard templates defined in the System: Mailer item type, which can be customized using the Oracle Workflow Builder. The templates describe the syntax the reply should follow and list the information needed to confirm the notification. The generated e-mail message also includes any custom site information, the due date, and any information necessary to process the response.

Once you set up the Notification Mailer to run, it continually polls the database for messages to send and checks its response mail account for responses to process. You do not have to do anything else unless you have a need to reload the configuration parameters by either suspending and resuming, verifying, or stopping and restarting the Notification Mailer.

Two Notification Mailer service instances are defined in Oracle Workflow Manager by default, the Workflow Mailer for detail notifications and the Workflow Summary Mailer for summary notifications.

After completing the remaining configuration parameters, you can start these Notification Mailers to handle e-mail processing for your Workflow users.

Service Instances for Workflow Mailer

This page shows the service instances for the Notification Mailer. For each service instance, the list displays the name, overall status, activated or deactivated state, node on which the Notification Mailer is running, number of actual processes, and number of target processes. Click any column heading to sort the list by that column.

Navigation: Applications Dashboard > (pull-down menu) Workflow Manager > (B) Go > Notification Mailer

Edit Notification Mailer

This page lets you edit the general properties, work shifts, and nodes for a Notification Mailer service instance. After you finish making changes, click the OK button to save your work. You can also click the Cancel button to return to the previous page without saving any changes.

General

Work Shifts

This region lets you assign work shifts to your Notification Mailer. A work shift defines the dates and times the Notification Mailer can run, as well as the number of processes the Notification Mailer can start running during the work shift.

For each work shift, the list shows the name, description, and minimum number of operating system processes.

Nodes

If you are operating in a parallel concurrent processing environment and you want your Notification Mailer to operate on a specific node, select the name of the node.

The primary node, if available, is the node on which your Notification Mailer operates. If the primary node or the database instance on it goes down, your Notification Mailer migrates to its secondary node. Your Notification Mailer migrates back to its primary node when that node becomes available.

Nodes must be previously registered with Oracle Applications, using the Nodes form in Oracle Applications.

Notification Mailer Status

This page displays status details for the selected Notification Mailer service instance.

Navigation: Applications Dashboard > (pull-down menu) Workflow Manager > (B) Go > Notification Mailer > (B) View Status

General

Processes

To control the running of the Notification Mailer service instance, click the button for the command you want to execute. Buttons are available for the following commands:

Notification Mailer Processes

This page shows details about the processes for the selected Notification Mailer service instance. For each process, the list displays the status, operating system process identifier (SPID), auditing session identifier (AUDSID), Oracle server process identifier (Oracle SPID), running request ID, and start date and time. Click any column heading to sort the list by that column.

Navigation: Applications Dashboard > (pull-down menu) Workflow Manager > (B) Go > Notification Mailer > (B) View Processes

Notification Mailer Configuration Wizard

The Notification Mailer Configuration Wizard lets you configure the selected Notification Mailer service instance by entering parameters, defining tags to assign statuses to unusual messages, sending a test message, and reviewing a summary of configuration information.

Navigation: Applications Dashboard > (pull-down menu) Workflow Manager > (B) Go > Notification Mailer > (B) Configuration

Parameters

This page lets you enter general, e-mail, send, and receive parameters. You must set parameters marked with an asterisk (*) to appropriate values for your environment before you can run the Notification Mailer.

General

E-mail

Send

%s -t -F "%s" < %s

In the Sendmail command line, the first %s is replaced with the sendmail command, the second %s is replaced with the value of the From parameter, and the third %s is replaced with the name of the temporary file. These three substitutions must occur, and must be in this order. However, you can use the Sendmail Arguments parameter to customize other arguments in the command line, as long as the three substitutions occur in the correct order.

Note: If you do not specify the path to the Sendmail executable in your PATH environment variable, you can include the path
in the Sendmail Arguments parameter instead. For example, you could set SENDMAIL_ARG to the following value:

/usr/lib/%s t F "%s" < %s

Receive

Tags

This page lets you enter strings of text found in unusual messages and the status you want to assign to a message response if it contains any of those strings. Unusual messages include bounced or returned messages and auto-reply messages such as those sent by vacation daemons, mass mailing lists, and so on. Since different mail systems vary in how they identify bounced, undeliverable, or otherwise invalid messages, you can use a tag file to specify how your mail system identifies those stray messages and how you want the Notification Mailer to handle those messages should it come across them.

Oracle Workflow provides several predefined tags for text commonly found in undeliverable or auto-reply messages. For each tag, the list displays the pattern, which is the string of text to look for in the From: line, Subject: line, or body of the message, and the action, which is the status to assign to the message if that pattern is found. The Notification Mailer handles messages according to these status values as follows:

You can define additional tags for other patterns you want the Notification Mailer to handle automatically.

Attention: Only a message response that contains a notification ID is checked against the tags. If the Notification Mailer receives a message response that does not contain a notification ID, it moves the message response to the discard file and sends a 'Warning' message to the sender that it received unsolicited mail.

Attention: It is important that you uniquely identify bounced messages and auto-replies by defining tags to distinguish them from normal responses. If you do not identify bounced and auto-reply messages, the Notification Mailer can mistake these as invalid responses, send an 'Invalid' message and continue to wait for a reply. In both cases a perpetual loop would occur where the Notification Mailer keeps sending out an 'Invalid' message and the 'Invalid' message bounces back or is auto-replied.

Attention: If a message response matches more than one string in the tag file, it gets tagged with the status of the first string it matches in the file. That is, the Notification Mailer performs a top to bottom comparison against the tag file. Due to this behavior, you should prioritize your strings listing the ERROR tags first, followed by the UNAVAIL and then IGNORE tags.

Test

The Test page lets you test the configuration by sending a sample notification message. Select the recipient role to which the message should be sent, and click the Send Test Message button. Then check the Notifications Worklist or the e-mail account for the recipient role, depending on the role's notification preference, to verify that the test message was received. The test message does not require a response, so you can close it after reviewing it. However, you can optionally respond with a comment to acknowledge the message.

Note: The settings you define for the configuration parameters determine how the test message is sent. For example, if you specify an e-mail address in the Test Address parameter, that address overrides the e-mail address of the recipient role and the test message is sent to the test address instead. Also, if you select the Autoclose FYI parameter, the test message is automatically closed and does not appear in the Notifications Worklist unless you display your closed messages.

Summary

In the Summary page, you can review the configuration parameter values and the tags that you defined for this Notification Mailer service instance.