This content has been marked as final. Show 6 replies
Only SYSTEM_CODE and PROCESS_NAME are derived from the EBM Header using the following XPath expressions:
The SERVICE_NAME is the name of the BPEL component in the faulting SOA composite. In the case of a mediator component it's the name of the SOA composite.
Finally, the ERROR_CODE comes from the SOA stack and depends on the actual error situation.
I tried to send notification using feature available in AIA FP whenever remote and binding fault happened to user SysAdmin creatred in Admin console under user & groups.
I have done the below configuration
1. Made entry in AIA console under error notification (Error code : blank service name: SampleBpel system code : sys process name: SampleBpel Role: SysAdmin FYIRole: SysAdmin).
2. configured email driver properties and work flow notification properties.
3. made entry in http://localhost:7001/sdpmessaging/userprefs-ui/ with user logged in SysAdmin and entered mail-id.
4. Populated EBM Header with the below values
5.Included fault-policies and fault-bindings.xml in project.
when testing the project with negative scenario generates the remote fault. I am able to see fault data i.e EBM Header in AIAReadJMSNotificationProcess.
But it is unable to send notification for the user created (SysAdmin).
It is showing the default user values
Message ID (Recipient) b89bc86bc0a805f10110c4aa3d93719f (USER:AIAIntegrationAdmin)
Overall Status Failed
Status Code ENGINE_PROCESSING_FAILURE
Status Message User could not be resolved to device addresses. Please see the log file for details.
Timestamp Dec 20, 2012 7:28:56 PM IST
Gateway Message ID
Driver Instance Name
Application Name soa-infra
Application Instance Name
It is unable to send notification to the user SysAdmin
Can you provide solution how can i send notification to user created (SysAdmin)?
what are the EBM Header values that need to be populated for sending notification to user created (SysAdmin)?
I tried the same setup and the same payload and it picks the user from the configuration row as expected. So I can only conclude your setup is somehow different from what you describe.
You can enable debugging for the EH code by adding the switch -Daia.debug=true to the JVM startup parameters. This will give you some detailed output in the server out file that should help to understand why it is not able to pick the record that you entered.