1 person found this helpful
Are you using File Transport or the File Adapter. And, I assume you're talking about the proxy service. Currently, such capability does not exist, but, this seems like a good enhancement to have.
From what I understand from your use case, you have a proxy service that is polling the ftp server, and there are errors downstream (possibly from business services/pipeline) and the proxy service writes the file to the Error archive folder. And, you wish to have some automated means for a user-configured/system-wide alert that triggers an email whenever this happens. One question - how do wish to deal with flood control (e.g all messages getting errored out). Is there a threshold that you wish to configure?
Please let me know if my understanding of your problem is correct or not.
I am not sure if i understood your requirement properly , When OSB drops the file in the error folder , it means there is some error in the flow. ADD a global error handler and send the email notification fromy the error hanlder.
YOu can if else conditions for handling differnet types of error and for different type of notifications.
1 person found this helpful
Currently i do not think anything out of the box exists. But you can try one of the following
1) polling error directory again with another ftp proxy and using email business service send the alert
2) use wldf watches and notifications(link: http://docs.oracle.com/middleware/1213/wls/WLDFC/config_watch_notif.htm). verify the log message and send alert based on that.
You interpretation is correct, it is a proxy service that is polling the ftp server, and there are errors downstream (possibly from business services/pipeline) and the proxy service writes the file to the Error archive folder. The issue may not be an error on the flow, it maybe some Weblogic resource that is not available (we get BEA-381608 warning and the file is dropped on error folder on external server) or any other error downstream (possibly from business services/pipeline) as you mentioned. So the solution suggested by 991448 would not work, we already have error handler and notifications.
Regarding flood control, if I understand what you mean, there would be no issue. We can get as many emails as files going into error folders until the issue is solved.
Did you try the suggestions made by Ashok?
We evaluated the solutions:
1 - To add an extra proxy for each error folder would be too onerous. We have many error folders per server and many servers... It is simpler to set SCOM in each server to do this.
2 - We already use wldf watches and notifications, the issue is that we cannot guess every possible Error or Warning to watch for, we just find out which one to watch after the problem occurs. We want to be alerted for the problem in the first place, whatever the cause is.
Since OSB commands the process to move a file to the error folder, it would be logical to add an event to notify whenever this occurs, whatever the cause is... It would be a good enhancement to have!