on 11-21-2018 9:09 AM
Hi Experts,
I have a requirement where in I want to send alert email with fault details.
Scenario is web service to proxy Async. SAP will send fault in case of any exception to PI. How we can send email alert when a fault message received.
In the email body I need all the values from fault payload.
Any suggestions are welcome !!
Thanks,
Ashish
Thanks Evgeniy & Munniyappan for all the suggestions.
Let me try out CBMA if it works for my requirement.
Will update the outcome !!
Regards,
Ashish
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since it is custom proxy, you can send the mail from proxy code whenever application error happens.
or
in the mapping of fault message, you can send the mapping using java client.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Muniyappan!
Wouldn't you please describe how could we use fault mapping in asynchronous scenario?
Regards, Evgeniy.
Both are correct that Fault mapping does not come into play when async scenario is involved. It is applicable for only with sync scenario. I should have mentioned as sync scenario in my reply. I have overlooked the thread heading.
If we were to send alerts from Proxy then fault is not required at all.
My query is on the fault. Can we do it from PI or not.
Also, for async case , there is not fault mapping involved.
When fault error is raised in receiver proxy for asynchronous scenario, Error is persisted for only monitoring and no signal sent to PI.
It will not be possible to take any action from PI perspective. may be you can triger another proxy to mail interface if you are looking to send the mail from PI by sending the fault details as payload.
https://help.sap.com/saphelp_nw73/helpdata/en/dd/b7623c6369f454e10000000a114084/content.htm
If we were to send alerts from Proxy then fault is not required at all.
yeah. You can handle the exception and send the mail without raising the fault error. But raising fault error will be helpful to restart the message again. For example if the correct data is not present, fail the message and restart the message after the data correction.
If the requirement is to send mail, I am not sure if it makes any difference whethr it is sent from PI or ECC.
Raising fault error and sending mail also makes sense as it will immediately notifiy business, so that they can take action.
Another suggestion would be using below option. I have not tried this but author says it works for application error and system errors.
https://blogs.sap.com/2013/02/26/sap-pi-731-abap-proxy-monitoring-and-alerting-using-cbma/
Hi Ashish!
Regards, Evgeniy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ashish!
For example, to use Component Based Message Alerting functionality.
Regards, Evgeniy.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.