Thursday, January 8, 2009

How to capture invalid Email address & lot of others things

After a long hiatus from writing in the blog, I am back;
Problem is that, it is difficult to decide whether the post will add value or is it something known to everyone, except me!

This was an interesting issue. What appeared to be a relatively straightforward work, stretched beyond 2 days with no end in sight.
There is a metalink note how to handle this 456378.1
However, this did not mention how to enable the Event - I did not see any way to enable. A little digging showed me that "Create Events" button has to be enabled. Enabled it myself using "FND: Diagnostics" option.
Once the oracle.apps.wf.notification.send.failure event was enabled, ensured that I created a malformed email address. Then created a test email by going to OAM->Workflow Manager -> Service Components -> "NotificationMailer"->View Details -> Test Email. selected my role and that is it. Now Oracle will generate an invalid email address or so I thought.
However, I found that the Notification was still in MAIL Status.
This led to question is the Background Engine on? I need to turn on the Background engine with all the three parameters as Y. No problem. But I need to know the Item type before I can start. Only problem is what is the Workflow Item Type? All I had was the Notification.
The Table WF_ITEM_TYPES_VL carries the Item_Type and is linked to WF_NOTIFICATIONS (WF_ITEM_TYPES_VL.NAME = WF_NOTIFICATIONS.MESSAGE_TYPE) .

I was able to see in the Mailer Log , that Workflow mailer has attempted to send a notification several times. all of them ended up with an error message: "451 Timeout waiting for client input"

No comments: