Why were no attributes in the Error received from Adapter Framework (AF)?

[Former Member]

Hi All,

We have a local processing scenario where we use the Integration Configuration through Advanced Adapter Engine to download attachment using Sender Mail Adapter from Lotus Notes Mail and Upload the file attachment into an FTP using Receiver File Adapter. As part of our testing we deliberately set the Sender Mail Adapter to produce error by changing the configuration like setting a wrong URL to simulate downtime on Lotus Notes. The error shows up in the RWB CommChannel and an error record is received from AF to send Alert. When the alert tries to find the alert rule it is unable to do so because the condition (Component, Interface and Namespace) values are empty "*Find rule for (From:::: To::::)" This is from the report SXMSALERT_LOGREADER.

The (From:::: To::::) should contain the Sender Component, Interface and Namespace as FROM, and Receiver Component, Interface and Namespace as TO but they are not picked up from the Mail Adapter because there are no message/payload yet but I am expecting at least the Component to be included.

The result of the empty (From:::: To::::) will be a "*No matching rule found" and no alert is sent.

Do anyone had the same issue? Is this a possible bug in PI?

Please let me know if you need additional detail.

Regards,

Orlando

[former_member194786]

Hi Orlando,

When the sender channel reads any message, it would be able to determine the Sender service, Interface and namespace from Sender agreement. It is not dependent on the payload.

To generate the alert for such, you can modify the alert rule to check only for the Sender serice, interface and namespace.

Hope this helps.

Regards,

Sanjeev.