11i Notification Mailer Setup and Testing - Definitive Step by Step Guide An Oracle White Paper April- 2002

Concurrent Manager uses this tool to notify users of completed requests.5.5. the WFMAIL process acts. The procedure has been tested out on Oracle Applications 11. wfmail. the process moves that mail to the DISCARD file.4 and 11. the mail is put to the UNPROCESSED file.5 with Embedded Workflow. Step-5 and Step-6 below. the executable expects certain parameters. How the Notification Mailer starts and what does it do ? The WFMAIL executable starts the WFMAIL process on the Server machine. they are moved to the PROCESSED File. The procedure has not been tested out on Standalone Workflow but it should still work on a standalone version of Workflow.cfg file. If there is an NID in the incoming mail.11i Notification Mailer Setup and Testing Definitive Step by Step Guide Purpose The purpose of this document is to systematically list out a procedure for setting up and testing the Notification Mailer with sendmail in UNIX.cfg file and its contents are discussed in detail in Step-3. The WFMAIL process keeps looking for rows in the WF_NOTIFICATIONS Table for Notifications with mail_status=ACTIVE. The WFMAIL process acts upon these mails in the UNPROCESSED file after which . . These parameters are supplied to the executable through the wfmail. If it cannot find an NID. Notification Mailer – What is it ? Notification Mailer is the tool used by Workflow to send and receive mails. The Notification Mailer makes use of the WFMAIL executable supplied with oracle applications. For the incoming mails that come to the location specified by the ACCOUNT parameter the WFMAIL process specifically looks for the NID (Notification ID) in the Mail body. For those notifications. by sending mail to the address specified by the TO_USER column. While starting up.

. is .8/bin /usr/ccs/bin /usr/sbin /usr/bin /ucb /etc ./.1. Step–1 Start off by checking whether the sendmail executable is there in the $PATH . To do this.5. it is clear that the executable is inside the folder /usr/lib.6/bin /usr /home9/apps/actappl/fnd/11.0.0/bin /home9/apps/actora/8. first you need to locate. $ pwd / $ find . If you get an output such as the above.profile file itself and login again into UNIX Then $echo $PATH Study the output of the above to ensure that /usr/lib included in the $PATH .0/bin /home9/apps/actappl/ad/11. -name sendmail -print . Since the $PATH environment variable is defined within the .profile file of the <applmgr> user. See the following sequence of commands to locate the folder $ pwd /home4/ora8i $ cd ..0./usr/lib/sendmail So from the above output. For this. /usr/ucb/cc /usr/bin The above output means that sendmail executable folder location is not appended to $PATH. you will need to add /usr/lib to the $PATH environment variable.6/bin /home9/apps/actcomn/util/jre/1. "ora8i" is the <applmgr> user.Starting up the Notification Mailer – Step by Step In the following discussion . it is advisable to modify the . login to UNIX as the <applmgr> user and issue the following command : $ which sendmail no sendmail in /home9/apps/actora/8. in which folder is the sendmail executable residing.5.

/var/mail is a typical example of this location. "/var/mail/ora8i": 1 message 1 new >N 1 venkat.kris Tue Apr 2 16:53 56/1792 Re: ? 1 This step-2 ensures that sendmail is working correctly for sending and receiving mails. So create 3 files at /var/mail as follows : $cd /var/mail $touch processed1 unprocessed1 discard1 . To test this reply has been received.0 Wed Sep 5 16:10:06 PDT 2001 Type ? for help. Step–3 Now you need to create 3 Files at a location. should reply as $ which sendmail /usr/lib/sendmail If the command $which sendmail finds the sendmail executable. Check that the mail has been duly received at the mailbox.krishnamoorthy@oracle. Then you can reply to this mail from your mailbox and should be received at the UNIX <applmgr> account. login as <applmgr> into UNIX and type mailx $ mailx mailx version 5.com hkld lkdf ghit <Terminate by typing in cntrl-D> $ This will send a mail to the specified address. which is readable and writeable by the <applmgr> user.This time follows : issuing the command again. then you can proceed to the next step-2 Step–2 Now test sendmail as follows : $ sendmail venkateswaran.

the Notification Mailer creates a file in the Folder /tmp. and it will throw an error. It is permissions for .tmp file before mailer.After doing the above step verify the permissions for these 3 files : $ ls -l -rw-r--r-1 ora8i dba 0 Mar 28 -rw-r--r-1 ora8i dba 0 Mar 28 -rw-r--r-1 ora8i dba 0 Mar 28 ownership and file 15:39 discard1 15:23 processed1 15:40 unprocessed1 Ensure that <applmgr> user is the owner of these 3 files (notice that ora8i is the owner in the above output) and has privileges -rw-r--r-.cfg file : UNPROCESS = /var/mail/unprocessed1 PROCESS = /var/mail/processed1 DISCARD = /var/mail/discard1 Step–4 While working.tmp. dba 0 Apr 2 18:56 wfmlrwf.tmp If the file exists and is owned by a different user.tmp. the WFMAIL process temporary file wfmlrwf.on these 3 files (as given above in the output). $cd /tmp $cd .. The name of this wfmlrwf. $ls –l starting up the will create the needs it.on this $cd /tmp $ls -l wfmlrwf. you need to remove the file wfmlrwf.tmp If you remove the wfmlrwf. login to UNIX as the user who created the file and remove it. So. Otherwise the WFMAIL process will not be able to write the temporary file. as given above. $rm wfmlrwf.tmp. The following will be now the setting for the parameters in the wfmail. if exists ensure that the <applmgr> user owns it <applmgr> user has permissions -rw-r--r-.tmp -rw-r--r-1 ora8i temporary file is the file and the file. Check up at the folder /tmp. as and when it to be ensured that <applmgr> user has write the folder /tmp as follows.

cfg file. Now you can proceed to make a wfmail. If you are configuring the Notification mailer service to startup from a user other than the <applmgr> user. the mails with an NID are directed to the UNPROCESSED file and others to the DISCARD file.drwxrwxrwt 9 sys sys 6438 Apr 2 19:16 tmp Notice drwxrwxrwt permissions in the output above. The sample wfmail. And modify ACCOUNT parameter in the wfmail.cfg file actually points to a file inside the Folder /var/mail. Step–6 The first 5 steps complete the preparatory steps. $cd /var/mail $touch ora8i $ls –l -rw-rw---1 ora8i mail 1216 Apr 20 12:41 ora8i This file (in this case ora8i) is important because all the incoming mails for the <applmgr> user are received into this file. in this case the file name is ora8i. . Do not forget to change the APPS password. which will be used by the WFMAIL process. Here are the minimum parameters and the corresponding representative values that you need to make the mailer work : Connect provides the Database login information for the mailer process. then ensure that there is a file by the same name as the user name in the folder /var/mail. And the resulting ACCOUNT parameter will be /var/mail/ora8i. Step–5 The ACCOUNT parameter in the wfmail.cfg file supplied by the installer can be located at $FND_TOP/resource folder. As explained earlier.cfg file accordingly. The name of the file is same as the name of the <applmgr> user. So. Then from this file the WFMAIL process will read the incoming mails for the user. Modify this file appropriately. This is the default setting for /tmp folder and so it is sufficient if you merely verify it. if you have modified it. to suit your environment.

cfg file. Then navigate to the Folder where the SHUTDOWN parameter is pointing to (In this Example. it is /var/mail). ACCOUNT=/var/mail/ora8i The FROM parameter is the "From" field in mails sent from the mailer. SHUTDOWN=/var/mail/shutdown1 For the above value of the SHUTDOWN parameter. SHUTDOWN is a very important parameter. IDLE=20 This can be given any value piled up. from where by one. The WFMAIL process is shutdown smoothly in a very peculiar way. Then create a SHUTDOWN file by the same name given for this parameter in the wfmail. You need to login to the UNIX Server where WFMAIL Service is running as the user who started the WFMAIL service. FROM=Oracle Workflow When messages get Queue.CONNECT=apps/apps@ACT Step-5 above gives the details of the ACCOUNT parameter. It points to the location of the shutdown file. but is mandatory. you can do the following to stop the WFMAIL service : $cd /var/mail $touch shutdown1 . they need to be put into a the mailer can pick up the messages one outbound SMTP queues can be retained as of 1. Number of the default value QUEUE=1 NODE is the mailer Node name. NODE=wf IDLE is in seconds and means that WFMAIL process will act every IDLE seconds.

WFMAIL process uses the tags defined in this file at the time of response processing. the following would be the contents of a valid WFMAIL.Note that this is the only way to smoothly stop the WFMAIL Service.cfg file CONNECT=apps/apps@ACT ACCOUNT=/var/mail/ora8i FROM=Oracle Workflow QUEUE=1 NODE=wf IDLE=20 .5. LOG= /home9/apps/actappl/fnd/11. A typical entry from the tagfile is given below : ERROR "-.5. REPLYTO is the UNIX mail address of the <applmgr> user.5. the tag that gets added to the response mail will be “-.0/resource/wfmail.Unsent message follows --" So.log DEBUG=Y TAGFILE is supplied by the Oracle Applications Installer. there are 9 such entries in the tagfile. REPLYTO=ora8i@insn056q. when ERROR results. UNPROCESS and PROCESS parameters are as explained in Step-3 above. DISCARD=/var/mail/discard1 PROCESS=/var/mail/processed1 UNPROCESS=/var/mail/unprocessed1 It is recommended to include the following 2 parameters.idc. This is an important parameter and will be used by the mailer to sent back replies. It can be located inside the $FND_TOP/resource Folder.oracle.com DISCARD.Unsent message follows –“ In 11. to enable debugging. Step–7 Consolidating the parameters explained in the previous Step-6.

These messages are vital in diagnosis.krishnamoorthy@oracle. the WFMAIL executable will HOLD this UNIX session. Mailer . this method of Startup is suitable.0/resource/wfmail. So. From the $ prompt of the UNIX applmgr user.com DISCARD=/var/mail/discard1 PROCESS=/var/mail/processed1 UNPROCESS=/var/mail/unprocessed1 SHUTDOWN=/var/mail/shutdown DEBUG=Y LOG=/home9/apps/actappl/fnd/11. The above 8 steps will enable the Notification startup . So. once you have established a working mailer setup.5. ( It will appear to hang ! ) If you choose to start the Notification Mailer as a concurrent request. This is because. is recommended.cfg file. The following is the command : $cd $FND_TOP/resource $WFMAIL apps/apps@ACT 0 Y $FND_TOP/resource/wfmail. The next step will be to test the setup.tag Step–8 Having made a valid wfmail.oracle. as the Mailer processes any notification request. As a concurrent request The first method of starting up the mailer from the UNIX command prompt.idc. 2. resort to this method.log TAGFILE=/home9/apps/actappl/fnd/11. There are 2 ways of starting up the mailer service : 1. So.5.cfg The downside of this method is. you can now proceed to start up the Notification mailer.TEST_ADDRESS=venkateswaran.0/resource/wfmail. then you will not have an UNIX session to see the progress OR to see any debugging information necessary for diagnosis. if you are setting up the Notification Mailer for the first time. basically you will not be able to do anything from this UNIX session console.com REPLYTO=ora8i@insn056q. it will also display progress messages and errors on the UNIX session console.

say "Active Responsibilities" and choose to notify the User created at Step-1 : Notify ==> Options Button Name field. Later.Testing the Notification Mailer There are 2 ways of testing the setup : 1. 2. Before doing either of the 2 tests. are not tested. If you do not have the Workflow builder. By submitting a concurrent request 2. specifying to notify the user created in Step-1 Concurrent ==>Requests ==>Submit a New Request ==>Single Request Choose the Name of an Example Request . you will have to be content with this test of the Mailer. this test only tests "sending" the mail from the mailer. Now submit a request. The downside of this approach being that. STEVE) While creating this user. ensure that the Notification Mailer has started and is running on the Applications Server. (Ex. the test is very simple and that it can be done without using the Workflow Builder. to test the working of the Notification Mailer setup. Security ==> User ==> Define. 1. take care to input the correct E-mail address of this user at the E-mail field. first of all login to Oracle Applications as SYSADMIN/SYSADMIN and create a new user and Save. enter STEVE. By using a simple Workflow process. an E-mail will be sent to this user. receiving the mail by the Mailer and the appropriate routing on receipt of a mail. Testing by submitting a concurrent request The advantage of testing the Mailer using this Test is that. To do this. in the same page ==> Against .

This is also the test recommended by the Oracle Support team. After Step-2. Testing the Mailer using a simple Workflow model This method of testing is the comprehensive way of testing the Notification Mailer setup. which specifies the NID (Ex. 21462).oracle. At this point.Sending 'OPEN' for NID 21462 If there are no error messages at the UNIX console accompanying the above line. then it is certain that the mail has been correctly sent to STEVE.zip supptest26. inspect the request log for a line. proceed to submit the Request by clicking on Submit button. To do this Test.3. Once the submitted request completes. Issue the following SQL as apps/apps user to confirm that the Notification with this NID has 'status' as 'CLOSED' : SQL>SELECT status.mail_status from WF_NOTIFICATIONS WHERE notification_id=21462 CLOSED SENT This completes this Test and tests that the Mailer is working for sending mails. if you see the UNIX session running the Mailer. User STEVE can check his Mailbox at the E-mail address given in Step-1 for the receipt of the mail.com/apps/patchsets/AOL/SCRIPTS/WORKFLOW/GENERIC/11i/ The File to be downloaded is supptest26.zip supplies 2 files : . you can see a line such as the following : 01-04-2002 16:24:56 . The test can be downloaded from the following URL : ftp://oracle-ftp. you need to have the Workflow builder installed on a Windows client machine. NID is the Notification ID generated by the Mailer.

first of all login to Oracle Applications as SYSADMIN/SYSADMIN and create a new user and Save. which is the simplest item type one can think of. Only then. A Readme file. Step by step instructions to carry out this Testing 1. The supptest26. STEVE) While creating this user.(Steps 2 & 3 in the Readme File) 3.wft file defines an item type called SUPPTEST. to verify) corresponding to the user created in Step-1. To do this. Then we proceed to open the Workflow Builder and establish a Database connection as user apps/apps. 2. we can assign the Role to the testing Notifications to be sent from this item type. A *. to test the working of the Notification Mailer setup. Steps mentioned in this Readme file are referred to. a mail will be sent to this user. from the mailer.wft This file defines the workflow process. Create an Oracle Applications user to whom Notifications will be sent for testing. Later. when the item type is run.1. see Step-1 in the Readme File. So. . in the following instructions. to do this testing of the Mailer. Follow Step-4 in the Readme to accomplish the Loading of this Role from the Database to this Workflow Builder session. the mails generated by the Item Type will be directed to this Role (Meaning. Also. This Readme file contains step-by-step instructions for doing the test. which can be used to do this test. 2. A Role will get created in the Database (You can Query the WF_USERS and WF_ROLES view. input the correct E-mail address of this user at the E-mail field.wft file by name supptest26. That Role will have to be loaded into the Workflow Builder session. to the user created in Step-1) . (Ex. Security ==> User ==> Define.

wft file into this Workflow Builder session. which modification in turn will enable us to sent the Notification to the user that was created in Step-1.wft item type in a Workflow Builder session is to modify it. To do this. we need to run the "Support Test Process" from the SQL prompt. except that it should NOT have been used before for this type. In this case. To run any Workflow process from the SQL prompt . Step-8 in the Readme explains the details of loading this file back into the Database. The next step is to open the supptest26.wft file. This is the INTERNAL NAME of the item type "Support Item Type". follow Step-5 and Step-6 of the Readme. we go to the "properties" of the "Support Test Notification" icon on the workflow process diagram. To do this. do not end the Workflow builder session. You will still need it to find out the parameters that are to be passed to WFRUN.4. and appropriately modify its performer value.SQL (next step) Having loaded the appropriately modified SUPPTEST item type back into the Database. Step-7 in the Readme details the steps involved. The above set of steps. Oracle Applications supplies an SQL file called WFRUN. That only will confirm whether the mailer setup is working or not. This SQL file takes in 3 parameters. It can be now loaded back into the Database. After the above 6 steps. 5. you can get this by doing the following on the Workflow Builder Navigator : Support Test Item Type ==> Mouse Right Click ==> Properties ==> Internal Name ( You will find that SUPPTEST is the value in this case) The second parameter <item_key> can be any number.SQL. complete the modifications to be made on the supptest26. This file can be located at $FND_TOP/sql. The very purpose of opening the supptest26. . <item_type> is the first parameter. 6.

SQL is to be used to VERIFY THE STATUS of the SUPPTEST item type. Otherwise. the above information about the 3 parameters . WFSTATUS.SQL. follow Step-10 in the Readme. As suggested in the Readme Step-11. Output while the process is still ACTIVE 14-APR-02 19:22:59 ROOT/Support Test Process ACTIVE #NULL <== 14-APR-02 19:22:59 Support Test Process/Start COMPLETE #NULL 14-APR-02 19:22:59 Support Test Process/Support Test Notificatio COMPLETE REJECTED VENKAT n 14-APR-02 19:34:38 Support Test Process/Support Test Notificatio NOTIFIED VENKAT <== 2. will be helpful. you can get this by doing the following on the Workflow Builder Navigator : Processes ==> Support Test Process ==> Mouse Right Click ==> Properties ==> Internal Name (You will find that SUPPTEST_PROCESS is the value in this case ) If you either modify the Item Type or decide to create your own testing workflow process. The following WFSTATUS.SQL shows a typical output from running the 1. The value of this parameter is the INTERNAL NAME of the "Support Test Process". to RUN the SUPPTEST item type using WFRUN. In this case. Output while the process has been COMPLETED 14-APR-02 19:22:59 ROOT/Support Test Process COMPLETE #NULL <== 14-APR-02 19:22:59 Support Test Process/Start COMPLETE #NULL .<process_name> is the 3rd parameter.

If you do see a Yellow warning bar. make sure that you don't have a yellow bar on the client machine. Solution => The solution in this case is to download the jinitiator from the same server from where you are accessing Oracle Applications using the URL. . in the first case. Otherwise. If you are using concurrent request to test the Notification mailer setup. As stated earlier.cfg file. it is recommended to start the mailer from the UNIX command prompt for ease in diagnosis.14-APR-02 19:22:59 Support Test Process/Support Test Notificatio COMPLETE REJECTED VENKAT n 14-APR-02 19:34:38 Support Test Process/Support Test Notificatio COMPLETE REJECTED VENKAT n 14-APR-02 19:37:41 Support Test Process/End COMPLETE #NULL <== You can see from the above output that. Remove the existing jinitiator by going through Start ==> Settings ==> Control Panel ==> Add/Remove Programs. it is clear that VENKAT has been NOTIFIED and reply action is pending from his mailbox. Now when you access Oracle Applications afresh. Once you get an output such as this. Also start the mailer. And the last line confirms that the process has ended.SQL to Oracle Support for Troubleshooting. jinitiator will get downloaded from your server and will show no Yellow bar. 1. In the second case.From the 4th line. Trouble shooting Listed below is a set of errors that you may encounter while configuring the Notification Mailer. the ROOT Process is showing COMPLETE status (See the first line). stating DEBUG=Y and LOG=<log_file_name> in the wfmail. the ROOT Process is showing that it is ACTIVE (See the first line). you need to send the output of WFSTATUS. then mails may not get sent. you can be sure that the Notification Mailer is up and running correctly.

WF_MAIL".WFMLRSLOOP_FAIL . 3.1 4.( But they should be in HTML Format so that you can respond ! ) Solution => Go to the Workflow Home page through Oracle Applications as SYSADMIN user.207: Could not open file '/tmp/wfmlrwf.210: Oracle Error: ORA-20002: 3102: Item Type '' does not exist. mailer is exiting. Review Step-4 under "Setting up the Notification Mailer" section in this document and conform to the points in that step.5.SetContext(:n). . .tmp' Solution => This problem arises because the WFMAIL executable is not able to write to the temporary file '/tmp/wfmlrwf. then you might get the following error on the UNIX session where you started the WFMAIL Service : . line 2206 ORA-06512: at line 1 .2. But the received mails have "ACCEPT" and "REJECT" tags in text Format.2206: Mail service could not send mail message. ORA-06512: at "APPS. You might get the following error on the UNIX session where you started the WFMAIL Service. . . you need to Apply patch 2021605 as per Note:165058. to solve this. end.tmp'.2320: Setting context failed for notification 19805.5 . SQL text: begin WF_MAIL. You have the following scenario : Mails are correctly received.2009: Fatal error. $ Solution => In 11.Sending 'OPEN' for NID 19805 wferr: . when it tries to send the mail : 14-APR-2002 18:44:06 . If you have not followed this document in setting up the Notification Mailer. and modify "Send me Electronic mail notifications" to either “HTML Mail” OR “Plain Text mail with HTML Attachments” . And the mailer will crash.

You can query up the Database views WF_USERS. WF_NOTIFICATIONS and WF_ROLES . then the problem is mostly in the Item type definition. To isolate whether a problem arises due to the mailer or due to an item type supplied by any Oracle Applications Module. . 6. you can run the test mentioned under "TESTING THE MAILER USING A SIMPLE WORKFLOW MODEL" in this document.5. In issuing SQL queries against these views. use the Notification ID (NID) as the search criteria. If it works correctly. for general troubleshooting.

A. [Add trademarks here] are trademarks o f Oracle Corporation.506. Oracle Corporation does not provide any warranties covering and specifically disclaims any liability in connection with this document.11i Notification Mailer Setup and Testing . Oracle is a registered trademark and Enabling the Information Age. CA 94065 U. Worldwide Inquiries: 415.V.Definitive Step by Step Guide May 2002 Author: Venketeswaran. This document is provided for informational purposes only and the information herein is subject to change without notice. Madhu Sudhan (UNIX) Copyright © Oracle Corporation 2002 All Rights Reserved Printed in the U.7000 Fax 415. Please report any errors herein to Oracle Corporation.K Contributing Authors: Prashanth Naik (Testing).S.S.7200 Copyright © Oracle Corporation 1995 All Rights Reserved . Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores.A.506.

Sign up to vote on this title
UsefulNot useful