Solved: Validation on 7.31 AAE HTTP adapter does not deliv...

former_member198060 · ‎04-23-2014

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:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
- <Error>
- <Details>
- <![CDATA[
<SAP:Error><SAP:Category>XIServer</SAP:Category><SAP:Code>XML_VALIDATION_INB.CX_XMS_SYSERR_VALIDATION</SAP:Code><SAP:P1>com.sap.aii.utilxi.xmlvalidation.impl.XMLValidationException: XML Validation for payload with root element name message_root , target namespace http://www.root.net Failed!Errors Encountered During Parsing
1.cvc-enumeration-valid: Value 'fufu' is not facet-valid with respect to enumeration '[TECL, STRD]'. It must be a value from the enumeration.
2.cvc-type.3.1.3: The value 'fufu' of element 'RapidPriority' is not valid.
</SAP:P1><SAP:P2>XML Validation for payload with root element name message_root , target namespace http://www.root.net Failed!Errors Encountered During Parsing
1.cvc-enumeration-valid: Value 'fufu' is not facet-valid with respect to enumeration '[TECL, STRD]'. It must be a value from the enumeration.
2.cvc-type.3.1.3: The value 'fufu' of element 'RapidPriority' is not valid.
</SAP:P2><SAP:P3>Schema Not Available in Cache, try to validation with file system schemas. Validation With File System schemas also Failed. XML Validation for payload with root element name message_root , target namespace http://www.root.net Failed!Errors Encountered During Parsing
1.cvc-enumeration-valid: Value 'fufu' is not facet-valid with respect to enumeration '[TECL, STRD]'. It must be a value from the enumeration.
2.cvc-type.3.1.3: The value 'fufu' of element 'RapidPriority' is not valid.
</SAP:P3><SAP:AdditionalText>not used at the moment.</SAP:AdditionalText><SAP:Stack>System error occurred during XML validation</SAP:Stack></SAP:Error>
]]>
</Details>
</Error>

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:

<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
- <Error>
- <Details>
- <![CDATA[
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Error Report</title>
<style>
td {font-family : Arial, Tahoma, Helvetica, sans-serif; font-size : 14px;}
A:link {color : #0059AA;}
A:visited {color : #999999;}
A:active {color : #999999;}
</style>
</head>
<body marginwidth="0" marginheight="0" leftmargin="0" topmargin="0" rightmargin="0">
<table width="100%" cellspacing="0" cellpadding="0" border="0" align="left" height="75">
<tr bgcolor="#FFFFFF">
<td align="left" colspan="2" height="48"> 500 Internal Server Error</td>
</tr>
<tr bgcolor="#3F73A3">
<td height="23" width="84"><img width=1 height=1 border=0 alt=""></td>
<td height="23"><img width=1 height=1 border=0 alt=""></td>
<td align="right" height="23">SAP NetWeaver Application Server </td>
</tr>
<tr bgcolor="#9DCDFD">
<td height="4" colspan="3"><img width=1 height=1 border=0 alt=""></td>
</tr>
</table>
Error: ERROR_IN_MODULECHAIN;ERROR_IN_MODULECHAIN, senderChannel '2da99c2347883de1901ec9bd42dbf208': Catching exception calling messaging system
<a href="https://wiki.sdn.sap.com/wiki/x/wIN3Cw">SAP Technology Troubleshooting Guide</a>
<table>
<tr>
<td valign="top"> Details:</td>
<td valign="top"><PRE>No details available.</PRE></td>
</tr>
</table>
</body>
</html>
]]>
</Details>
</Error>

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.

Former Member · ‎10-01-2014

Hi Peter

I get exactly the same problem.

Did you find a solution?

Best regards

Allan

former_member198060 · ‎04-23-2014

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:

Category:			/Applications/ExchangeInfrastructure
Location:			com.sap.aii.utilxi.xmlvalidation.impl.XMLSyntaxValidatorImpl
Application:			sap.com/com.sap.aii.af.app

Former Member · ‎04-23-2014

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

abranjan · ‎04-23-2014

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

Validation on 7.31 AAE HTTP adapter does not deliver detailed error

Accepted Solutions (1)

Accepted Solutions (1)

Answers (3)

Answers (3)

Re: "Failed to update setup engine executables. Pr...

Re: Timer showing while sending the mails from SAP

Re: Best practice to connect to multiple databases...

SAP Hana Calculation view input parameter from JPA...

Re: Adaptation error in sap mdg ui screen customer