on 04-23-2014 9:11 AM
Dear all,
I am working with a synchronous HTTP <-> PI <-> RFC on PI 7.31.
In the scenario I am using the validation by adapter option.
When I am using the HTTP adapter and classic configuration, in case of invalid payload being sent I am receiving back a clear error from the parser:
After changing the scenario to integrated configuration using the HTTP AAE adapter, I am receiving a response to the same error in such a way:
As you can see after changing to HTTP AAE I am not receiving a clear parser error back. Instead a generic internal server error is being thrown.
This is a disadvantage for the Sender who does not know which part of his message was in error.
Maybe somebody can give me a hint how to get back the parser message on the HTTP AAE adapter instead of the generic message.
Hi Peter
I get exactly the same problem.
Did you find a solution?
Best regards
Allan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your responses!
Yes I am sure that the application is working in the same way on both configurations. Only the response message differs (detailed validation error message vs. generic HTTP 500 message).
In both cases I have activated the "Validation by Adapter" option in ICO and Sender agreement and the validation of the request message is failing (I am sending an invalid enum value). If I send a correct request message, it is being processed fine on both configurations.
In fact if we check the PI logs in NWA, we can also find the detailed validation error for the HTTP_AAE adapter, it is just not sent out with the response message.
It is contained in the following log location:
/Applications/ExchangeInfrastructure | |||
com.sap.aii.utilxi.xmlvalidation.impl.XMLSyntaxValidatorImpl | |||
sap.com/com.sap.aii.af.app |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter,
can you verify that the system is indeed producing the same error? It might be a different one in HTTP_AAE case. In which step is the detailed error information lost?
Regards,
Jörg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Peter,
You generally get this error 'ERROR_IN_MODULECHAIN' when there is something wrong with the build, configuration or HTTP_AAE invocation from the sender side. I would suggest you to revisit your build and verify the sender parameters (Interface name, Business System/Component etc.)
If you're able to make the build/call consistent, you will get the errors in the form you're expecting.
Regards,
Abhishek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.