Wednesday, September 26, 2018

Oracle Workflow Notification Mailer



Posted in November
 
Print This Post

On popular request from my readers, I need to take a break from Oracle Identity Management Updates and need to Update on Oracle Workflow Notification Mailer.

Oracle Workflow in itself is a Product which is tough to cover in this blog but I am going to cover few important & frequently used components from Oracle Apps DBA point of view which is Workflow Notification Mailer .

Currently with OWF.H (Oracle Work Flow Minipack H) or 11.5.10 Oracle Applications Uses Java Mailer& before that it used to be C Mailer. Some of you who are on 11.5.8 or lower version might still be using wfmail.cfg under FND_TOP . Configuration is quite simple via OAM (Oracle Application Manager) provided you or your unix team setup inbound & outbound mails set up correctly. Notification Mailer will inturn use Operating System command/mail for inbound(for receiving mail) & outbound(for sending mails). At end of this post you can find few metalink notes which cover all things you require to configure Workflow Notification Mailer.
In 11.5.10 Java Notification Mailer is available out of the box , you simply need to configure via Oracle Application Manager .
Below metalink Notes should be enough to configure Workflow Notification Mailer& troubleshooting Mailer ..

Related Links

Metalink Note #

268085.1 Configuring the Oracle Workflow 2.6/11i.OWF.H Java-based Notification Mailer with Oracle Applications 11i

164871.1 Configuring the Workflow Notification Mailer in Oracle Applications Manager 11i

172174.1 WF 2.6: Oracle Workflow Notification Mailer Architecture in Release 11i


Posted in December 27th, 2007



On popular demand from readers, I am going to cover Workflow Notification Mailer in Oracle Applications R12/12i.
Workflow notification mailer setup in R12 is similar to 11i ( In both release 11i (OWF.H and higher in 11i) & R12 are Java Mailer)
* Previous version of Notification Mailer in 11i was based on C also called as C Mailer

Things to note
1. You use Oracle Application Manager (OAM) to configure Workflow Notification Mailer.
2. There are two kind of Notification (Outbound & Inbound) in Workflow Mailer
3. For Outbound Notification, CM (Concurrent Manager) node should be able to connect to SMTP (Simple Mail Transfer Protocol) server/relay.
4. For Inbound Notification (Optional), CM node should be able to connect to IMAP (Internet Message Access Protocol) Server.
5. Log file for Workflow Mailer Notification are at $APPLCSF/$APPLLOG/FNDC*.txt
6. Workflow Notification Mailer in background run as Concurrent Manager (Workflow Mailer Service, Workflow Agent Listener Service)
7. If you don’t wish to send mail notification to end user (from Dev/Test instance) then configure Test Address in configuration screen.


Step to configure Workflow Notification Mailer

1. Login to Apps R12 with System Administrator Reponsibility
2. under Workflow : Oracle Applications Manager click on Workflow Manager

If this is first time you are configuring Workflow Notification Mailer in Oracle Apps R12/12i you will see Notification Mailers as unavailable as shown in screenshot

Click on Notification Mailers

In next screen (as shown below, click on Edit Button)

Here you have option to select Inbound notification setup or Just outgoing Notification Setup.

Provide SMTP Server Name (ensure that CM node should be able to connect to SMTP Server or SMTP Relay)

Uncheck Inbound Processing (from above screen), if you don’t wish to configure Inbound Notification Mailer.

If you wish to configure Inbound Notification as well then ensure IMAP Server should be configured with a valid user (create Inbox, Processed & Discard folder for this User)

Click on Apply button to finish configuration, at this stage Notification Mailer will test SMTP Server& IMAP Server connectivity.

For Advanced setup, click on Advanced at top right of configuration screen.
Metalink Notes for Notification Mailer
1. 453137.1 Oracle Workflow Best Practices Release 12 and Release 11i
2. 274764.1 Oracle Workflow Cartridge Workflow Java Mailer Setup Test
3. 433359.1 Tracking Workflow Notification Event Messages
4. 456921.1 Queries Related to Alert and Mailer Integration Post RUP4
5. 454706.1 How to Stop mails from Workflow Notification Mailer


Posted in July 16th, 2008



Here are steps/events for Oracle Workflow Notification Outbound Processing(eMail from Oracle Applications Workflow to Users)

1.When workflow Engine determines that a notification message must be sent, it raises an event in BES (Business Event System) oracle.apps.wf.notifications.send
Event is raised with Notification ID (NID) as event key

2. There is seeded subscription to this Event

3. Event is placed on WF_DEFERRED agent

4.Event is dequeued from WF_DEFERRED and subscription is processed

5. Subscription places event message to WF_NOTIFICATION_OUT agent.

6.Notification Mailer dequeues message from WF_NOTIFICATION_OUT agent and
6.1convert XML representation of notification into MIME encoded message (Multi-purpose Internet Mail Extensions) and
6.2 Send message by SMTP (Simple Mail Transfer Protocol) to intended user (If Test Address/Override Address is set then email is sent to Test Address

 

E-Mail Notification is sent if all below conditions are true
a) Notification status is OPEN or CANCELED   and
b) Notification mail_status is MAIL or INVALID  and
c) Recipient Role has a valid e-mail address and Notification Preference is in the format MAIL%
d) Workflow Deferred Agent Listener is running
e) Workflow Notification Mailer is running

To check a) & b) run below query
SELECT status, mail_status  FROM wf_notifications WHERE notification_id = ‘&NID’;

mail_status >> SENT means mail has gone out of mailer to user

To check c) run below query
SELECT email_address, nvl(WF_PREF.get_pref(name, ‘MAILTYPE’),notification_preference)
FROM wf_roles
WHERE name = upper(’&recipient_role’);

To check d) & e) Use OAM (Oracle Application Manager)

.

Reference


How to troubleshoot outbound Workflow Notification Mailer Issues in Oracle E-Business Suite 11i/R12 coming soon


Posted in October 23rd, 2008



If you want to see workflow details (owned by other users) or status diagram in Oracle Applications 11i/R12 then you should belong to one of responsibilities/user listed under WF_ADMIN_ROLE.

By default (in 11i & R12) this role is set to user sysadmin (In old versions 11.5.8 or prior, it used to set to *)

If you wish to change WF_ADMIN_ROLE, as per most of metalink notes either

1. Change it via Workflow Administrator Web Applications responsibility (Login as sysadmin >> Workflow Administrator Web Applications >> Administration)

or update table
2. SQL> update wf_resources set text=’&Enter_Admin_Name’ where name=’WF_ADMIN_ROLE’;

to set it to everyone, use
SQL> update wf_resources set text=’*’ where name=’WF_ADMIN_ROLE’;


Problem with above solution
- Execution of Autoconfig will override above settings. Autoconfig will pick value against parameter s_wf_admin_role (default value SYSADMIN) from context file $CONTEXT_FILE
.

Correct way to set Workflow Administrator Role

1. First identify Workflow Role Name associated with User or Responsibility.

A. For setting Admin Role to specific user
SQL> select name from apps.wf_roles where DISPLAY_NAME like ‘&USER_NAME’  and ORIG_SYSTEM=’FND_USR’;

B. For setting it to a responsibility (so that all users with that responsibility can view other user’s Workflow)
SQL> select name from apps.wf_roles where DISPLAY_NAME like ‘&Responsibility_Name’ and ORIG_SYSTEM=’FND_RESP’;

SQL> select name from apps.wf_roles where DISPLAY_NAME like ‘System Administrator‘;  (output for System Administrator responsibility should look like)FND_RESP|SYSADMIN|SYSTEM_ADMINISTRATOR|STANDARD

SQL> select name from apps.wf_roles where DISPLAY_NAME like ‘Application Developer‘; (output for Application Developer responsibility should look like)
FND_RESP|FND|APPLICATION_DEVELOPER|STANDARD

2. Update context file ($CONTEXT_FILE) variable s_wf_admin_role (If you don’t see this parameter in context file then apply latest Autoconfig Patch) to value from above query

For Sysadmin User - Set it to SYSADMIN

For System Administrator Responsibility - Set it to
FND_RESP|SYSADMIN|SYSTEM_ADMINISTRATOR|STANDARD 

For Application Developer Responsibility - Set it to FND_RESP|FND|APPLICATION_DEVELOPER|STANDARD 

3. Run Autoconfig -
$OAD_TOP/admin/scripts/$CONTEXT_NAME/adautocfg.sh (11i)
$ADMIN_SCRIPTS_HOME/adautocfg.sh (R12)


Posted in November 20th, 2008



 SQL> SELECT COMPONENT_STATUS from APPS.FND_SVC_COMPONENTS
where COMPONENT_ID=10006;


 

No comments:

Post a Comment

[ERROR]: The value of s_patch_service_name is not set correctly in atleast one of the context files.

[ERROR]: The value of s_patch_service_name is not set correctly in atleast one of the context files. I got the issue below wh...