cancel
Showing results for 
Search instead for 
Did you mean: 

HTTP response code 3rd party???

Former Member
0 Kudos

Hi all,

we have the scenario IDOC>XI>HTTP. When we post something we get a HTTP error code while the messages arrives good at the third party. The third party is now sending back the code:

"HTTP/1.0 200 OK\r\n"

"\r\n"

but our XI message is still going into error mode.

Does anyone has experience with this and knows what code the third party has to send back to the XI so that the message goes into successfull mode? Please notice that it is a third party application (WMS) so that it will not be a wrong server setting.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi all,

I am having a problem with sending an orders message through HTTP Adapter (my scenario is async IDOC->XI->HTTP). In SXMB_MONI for some reason the message is in status "Scheduled for Outbound Processing" and Q.Status field says "Queue Stopped".

Keep a live timeout is set to 30 and Proc.Timeout 60 for HTTP in SMICM.

I have:

- Target host

- Service Number (443)

- Path

- HTTP Proxy Host

- HTTP Proxy Port

- Username & Password

Did anyone have a similar problems?

-Mikko

stefan_grube
Active Contributor
0 Kudos

Could you post the error message of the SXMB_MONI?

Regards

Stefan

Former Member
0 Kudos

  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
- <!--  Call Adapter 
  --> 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
  <SAP:Category>XIAdapter</SAP:Category> 
  <SAP:Code area="PLAINHTTP_ADAPTER">ATTRIBUTE_CLIENT</SAP:Code> 
  <SAP:P1>402</SAP:P1> 
  <SAP:P2>ICM_HTTP_TIMEOUT</SAP:P2> 
  <SAP:P3 /> 
  <SAP:P4 /> 
  <SAP:AdditionalText /> 
  <SAP:ApplicationFaultMessage namespace="" /> 
  <SAP:Stack>HTTP client. Code 402 reason ICM_HTTP_TIMEOUT</SAP:Stack> 
  <SAP:Retry>M</SAP:Retry> 
  </SAP:Error>
stefan_grube
Active Contributor
0 Kudos

Hi Peter,

A timeout occurred. Are you sure, the server closes the connection after having sent the response?

Did you test the server with another client?

Regards

Stefan