Skip Headers
Oracle Workflow Administrator's Guide
Release 2.6.3.5
Part Number B12160-02
|
|
|
|
|
|
|
|
|
Previous |
Next |
|
Contents |
Index |
Glossary |
Step 8 Implementing Notification Mailers
A notification mailer is a Java program that performs e-mail send and response processing for the Oracle Workflow Notification System, using the JavaMail API. You need to implement one or more notification mailers only if you want to have your workflow users receive their notifications by e-mail, as well as from the Worklist Web pages.
Context: You need to perform this step only once.
See: Managing Notification Mailers
See: Setting Up Notification Mailers
See: Outbound Notification Mailer Processing
See: Inbound Notification Mailer Processing
See: Wireless Notifications
See: Full MIME Support
See: Notification Preferences
See: Plain Text E-mail
See: HTML-Formatted E-mail with Attachments
See: HTML-Formatted E-mail
See: Plain Text E-mail with an HTML Attachment
See: E-mail Notification Security
See: Handling Mailer Errors
See: Reviewing Notifications via Electronic Mail, Oracle Workflow User's Guide
See: Defining Rules for Automatic Notification Processing, Oracle Workflow User's Guide
See: Standard Agents, Oracle Workflow Developer's Guide
Managing Notification Mailers
The notification mailer program is defined as a service component type in the Generic Service Component Framework. This framework helps to simplify and automate the management of background Java services. For more information about managing service components, please refer to the Oracle Applications Manager online help or the Oracle Enterprise Manager online help.
Oracle Workflow provides one seeded notification mailer service component, called Workflow Notification Mailer. Most of the configuration parameters for this mailer are set to default values. You can enter the remaining required parameters using the Oracle Workflow Configuration Assistant for the standalone version of Oracle Workflow. For Oracle Applications, you can enter several of the remaining required parameters using AutoConfig and then simply enter the e-mail inbox password after installation in order to complete the configuration of the Workflow Notification Mailer. If the mail servers and Business Event System components used by the notification mailers are set up, and the service component container to which the Workflow Notification Mailer belongs is started, the seeded notification mailer automatically starts running once its configuration is complete. Alternatively, if you only want to send outbound messages and do not need to receive inbound messages, you only need to set the inbound thread count to zero and enter placeholder values for the inbound configuration parameters after installation.
You cannot delete the seeded Workflow Notification Mailer or edit its name, assigned agents, correlation ID value, or container. However, if necessary you can optionally update other configuration parameters, schedule control events, or manually choose control commands to start, stop, suspend, resume, or refresh this notification mailer.
You can also optionally create additional notification mailer service components. For example, you can create a notification mailer that processes only messages that belong to a particular workflow item type. You can also configure any notification mailer service component to process only inbound messages, or only outbound messages.
You associate inbound and outbound mailers with each other by assigning them the same mailer node name. You can optionally assign the same node name to multiple outbound mailers, but you must not assign the same node name to more than one mailer that performs inbound processing.
- If you create an outbound-only mailer, but you still want to perform response processing for e-mail responses to the outbound messages it sends, you should create exactly one other mailer with the same node name that does perform inbound message processing. Otherwise, there will be no inbound mailer that can process incoming responses to outbound messages sent by this outbound mailer.
- If you only want to implement outbound message processing, without inbound e-mail response processing, then you can configure an outbound-only mailer without creating a corresponding inbound mailer. In this case you should configure the mailer to use message templates for response-required notifications that do not request a response by e-mail, but instead direct recipients to respond from the Notification Details Web page. For example, you can configure the mailer to send response-required notifications using the Workflow View From UI message template, which is an alternative template provided by Oracle Workflow in the System: Mailer item type, or create your own custom message templates. The outbound-only mailer can still use the standard message templates to send outbound summary notifications or For Your Information (FYI) notifications that do not require a response.
- If you create an inbound-only mailer, you should create at least one outbound mailer with the same node name. Otherwise, no inbound response messages will be marked with that node name and this inbound mailer will have no messages to process.
Note: The node name for each node must be unique. However, multiple outbound mailers and one inbound mailer can share the same node. The maximum length for a node name is eight characters, and the node name cannot include any spaces or any of the following characters: left bracket ([), right bracket (]), slash (/), or at sign (@).
Service components must be hosted by a service component container. If you create custom notification mailer service components, you can assign them to the seeded container for notification mailers.
- In Oracle Applications, a service component container is implemented as a Generic Service Management (GSM) service. The seeded container for notification mailers is named Workflow Mailer Service.
- In standalone Oracle Workflow, a service component container is implemented as a servlet within an OC4J instance. The seeded container for notification mailers is named WFMLRSVC, within an OC4J instance named OC4J_Workflow_Component_Container.
In Oracle Applications only, based on the volume to be handled by the seeded container, you can also choose to create your own custom containers as GSM services in Oracle Applications Manager. If you create a custom GSM service in OAM, you can copy the service parameters from the seeded Workflow Mailer Service to your new service in order to specify how to run the new service. For more information about notification mailer configuration options, please refer to the Oracle Applications Manager online help or the Oracle Enterprise Manager online help.
See: Setting Up Notification Mailers
Copyright © 2003, 2004, Oracle. All rights reserved.