PI Synchronous Message Empty Payload

[adnanmaqbool]

Dear All

I am trying successfactor Job Requisition scenario and trying to fetch MetaData.

I have tested Message Mapping , Operation Mapping in Integration repository with SOAP Message Sender System is returning and every thing working perfectly fine.

However there is no Payload, although successfactor log is showing correct SOAP Message , I am using SOAP AXIS Adapter.

This is a Synchronous Message , Request is reaching to SSF and SSF is also returning a response but PI is not showing any payload and also throwing XSLT Mapping error which is due to empty payload.

Error Message

SFSFAPIDictionaryDescribeSFObjectsExResult_Out_to_SFSFAPIDictionaryDescribeSFObjectsExResult_In</Trace>

  <Trace level="3" type="T">Mapping Steps 1 XSLT SFSF_DescribeEx_Response_Transformation</Trace>

  <Trace level="3" type="T">MTOM Attachments are Transferred to the Payload</Trace>

  <Trace level="1" type="T">Message has no payload.</Trace>

  <Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>

  <Trace level="2" type="T">Mode 0</Trace>

  <Trace level="2" type="T">Call XSLT processor with stylsheet SFSF_DescribeEx_Response_Transformation.xsl.</Trace>

  <Trace level="3" type="T">Method fatalError called, terminate transformation, because of Thrown: javax.xml.transform.TransformerException: org.xml.sax.SAXParseException: Premature end of file. at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:250) at com.sap.aii.ib.server.mapping.execution.AbstractMappingTransformer.transform

------------------------------------------------------------------------------------------------------

  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--  Call Adapter

  -->

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

  <SAP:Category>Application</SAP:Category>

  <SAP:Code area="MAPPING">TRANSFORMER_EXCEPTION</SAP:Code>

  <SAP:P1>SFSF_DescribeEx_Response_Transformation</SAP:P1>

  <SAP:P2>http://sap.com/xi/SFIHCM01/IC</SAP:P2>

  <SAP:P3>01666576-78e4-11e1-c35c-cf350a4290b1</SAP:P3>

  <SAP:P4>-1</SAP:P4>

  <SAP:AdditionalText />

  <SAP:Stack>TransformerException occurred during XSLT mapping SFSF_DescribeEx_Response_Transformation (http://sap.com/xi/SFIHCM01/IC, 01666576-78e4-11e1-c35c-cf350a4290b1, -1)</SAP:Stack>

  <SAP:Retry>M</SAP:Retry>

  </SAP:Error>

[adnanmaqbool · Accepted solution]

Further to above message, please see Response Inbound Message is having SOAP Header and SOAP Body but no Payload

[bhavesh_kantilal · Accepted solution]

Very Interesting. Your modules look Ok. Can you check the Audit Log of your SOAP Receiver Adapter? Is there something different there maybe?

Also - which version of PI are you on? If you are on the right version, maybe you can enable HTTP tracing to see what comes into PI from SFSF. You can do this after the trp module

Regards,

Bhavesh

[adnanmaqbool · Accepted solution]

Dear Kantilal

When I am adding this TraceHTTP parameter system is throwing following message.

- <SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

  <SAP:Category>XIAdapterFramework</SAP:Category>

  <SAP:Code area="MESSAGE">GENERAL</SAP:Code>

  <SAP:P1 />

  <SAP:P2 />

  <SAP:P3 />

  <SAP:P4 />

  <SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.lang.NullPointerException: while trying to invoke the method java.lang.String.length() of a null object loaded from local variable 'spec'</SAP:AdditionalText>

  <SAP:Stack />

  <SAP:Retry>M</SAP:Retry>

  </SAP:Error>

[adnanmaqbool · Accepted solution]

Issue has been resolved by using simple SOAP Adapter. I was trying with SOAP AXIS Adapter.

[bhavesh_kantilal]

Hello Adnan,

Can you share your receiver SOAP Adapter Module Configuration?

Also - how do you conclude that the response contains data from SF and that it is within PI that this is getting lost? If that is indeed the case, then this issue occurs because of some incorrect configuration in the SOAP adapter Axis Module Configuration.

Regards,

Bhavesh

[adnanmaqbool]

Dear Kantilal

I am able to see SOAP response generated by Success Factor SFAPI Log but its not visible in PI.

[adnanmaqbool]

Dear All

Any Tip.