Alerts not working for issue_HTTP 404 Not Found(Target web service unavailability)

[former_member323756]

Hello,

We have Proxy to SOAP synchronous scenario where we have done Message Based Alert configurations in SAP PI.

For Mapping issues, we are getting alerts to both recipients' email ids as well as Alert Inbox in RWB.

But when the target web service is not available , both Request and Response fail and we get following system error description in response message:

My question is why are we not getting any alert triggered for the same as in Alert Rule we have selected 'No Restriction' radio button so that all the errors are captured.

Please provide some inputs.

Regards,

Shikha Chaudhary

[former_member323756]

Some Basis corrections done due to error in RZ20. And now its working.

[pandey_anuj]

Hi Shikha,

Please check if your rule is configured to capture the adapter related alerts

Thanks,

Anuj

[former_member323756]

Hey Anuj,

That was very basic step. Configured for both adapter and integration engine issues.

Handled.

-Shikha

[Former Member]

Hi mate,

     Follow this steps, Iñaki Vila is in the correct way:

Regards.

[former_member323756]

Hello,

I believe you misunderstood the issue. The HTTP 404 is not for PI internal service/resource unavailability but for the target Web Application/Service downtime.

Both Alert Configuration and Alert Inbox in RWB are opening just perfect, all configurations done and working as expected for Mapping issues.

In Our Case,

R/3(Proxy) <-> PI <-> Web Application/Service(SOAP)

Test Case:

PI is not able to communicate with the target Web service(Resource) and hence both request and response message fail .HTTP 404 error is sent in Response message.

But No alert for this.

Regards,

Shikha

[Former Member]

Ok, have you checked that any one firewall is not stopping the alert message?

regards

[former_member323756]

Hey,

As I mentioned I am getting the alert for mapping error issues. I feel there should not be necessity of checking the firewall. Right?

-Shikha

[former_member182412]

Hi Shikha,

• May be the adapter framework errors are not working because of dumps, Check any dumps in ST22 for more details, the user will be PIRWBUSER
• Delete expired alerts from the system by running the report RSALERTPROC

Check question 8 and 12 in below SAP Note for more details.

SAP Note 913858 - XI Alerting: Troubleshooting

Check this SAP Note also:

1775389 - Alerts not generated in PI due to unconfirmed alerts

Try to send the test message from adapter engine using below URL:

http://host:port/AdapterFramework/alerting/ping.jsp

Regards,

Praveen.

[Former Member]

Shikha, I don't understand why you are so interested in a mapping error, an 404 error is related with communications, so please, focus your research in test and check all the mates`s suggestions.

Regards.

[former_member323756]

Hello,

The requirement was to capture both mapping as well as communication errors , hence the focus is right.

I have resolved my issue now. Thanks anyways.

Regards,

Shikha

[Former Member]

Hi Shikha,

Check the below parameters set in NWA--->Configurations--->Infrastructure--->java system properties ,  then go to services tab,  then look for XPI Service: AF Core.

Then in the properties tab, make sure that

          alerting.is active is true  

          alerting.target     is 0.

Regards,

Santhi

[former_member323756]

Hello Santhi,

Checked.They are both maintained correctly.

Any other input.

Regards,

Shikha

[Former Member]

Hi Shikha,

Make sure that you specified conditions in alert configurations(like,  service interface, namespace...etc) are given correct.

Some times we may type wrong can be the reason that the alert not getting raised.

Regards,

Santhi

[former_member323756]

Checked. The condition is correct. I request you to please focus that mapping errors are triggering alerts correctly.