calling a RESTful service in SAP-PI using SOAP Axis adapter- synchronous interface

[Former Member]

Hi,

We have a requirement to do a synchronous http-post to a restful service. I have configured the SOAP axis adapter as per the screenshots provided in the SOAP axis FAQ guide. Unfortunately, the issue that I am facing is I am getting a message expired exception when I trigger the interface. Its a proxt to SOAP scenario. The proxy executes for 2-3 minutes and throws this exception. What I also noticed is that the adapter doesnt get called at all. When I check the comm channel, its status shows as "processing" and its not even gathering the data. Any help would be greatly appreciated.

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

- <!--

 Inbound 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.MessageExpiredException: Message 005056a9-0307-1ee1-aad2-07f82b64c18a(INBOUND) expired</SAP:AdditionalText>

<SAP:Stack />

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

</SAP:Error>

Thanks

[baskar_gopalakrishnan2 · Accepted solution]

MessageExpired Exception here is due to timeout issues. I would recommend you to do the following things..

a) Test the webservice using soapui or xmlspy and see any problem with the webservice.

b) See whether you specified target wsdl url as per the requirement.

C) Check whether you need to update SP based on  sap note for the axis adapter.

d) Check in SXI_MONITOR where do you get the message processing failed

e) Also go to RWB, monitor the communication channel and see any error you see?

Hope those things would help.  Provide more details if you could not solve this issue.

[Former Member · Accepted solution]

Thanks bhaskar. Above issue is resolved through cache refresh. Unfortunately, with the same interface, we are having trouble passing HTTP header using soap axis receiver adapter. we have sent a request to the service using fiddler and were able to get a response if we mention the content-type as text/xml or application/xml in the HTTP header.  If we dont mention that, we are getting the response as

<int>200<int> which is the same that we are getting when we call the service using PI SOAP Axis receiver adapter. I have referred to the FAQs and tried to configure dynamic configuration handler but that doesnt seem to work. I configured exactly like whats mentioned in axis adapter HOWTO guide.

I had one key as write http://sap.com/xi/XI/System/HTTP Content-Type

Location is header and the value for that Key is application/xml.

Apart from above, rest is exactly like whats in the HowToGuide.

I dont see the dynamic configuration call being made in SXMB_MONI

Just to see if its working, I tried the same configuration thats in the how to guide, with write http://sap.com/xi/XI/System/HTTP Session but that also doesnt seem to work.

Any help/ inputs will be greatly appreciated.

Thanks.

[Former Member · Accepted solution]

Hi,

Above issue is solved using Java mapping. However, it would be interesting to know how this can be achieved in PI communication channel using appropriate handlers.

Thanks !