http response code 2xx caused adapter error

[Former Member]

I just do a demo for salesforce bulk api. I use receiver HTTP_AAE channel to post the data.

I got HttpAdapterException: STATUS_CODE_NOT_OK-Created.

Acctually, the data is uploaded to the salesforce server. It is successful. After a few minuts, there are more than three documents have been created on the salesforce server. That means the adapter send document several times.(It thouth the message is failed.)

I use other rest client to post the data, the reponse is 201 created

I go through the http status document, it told me that 2xx is the successful response code.

Why SAP thought 2xx is a failed response.

I just go through the sap code. They just think 200 is the successful code. Other response code will raise an error.

[Former Member]

Can you try sending via SOAP protocol?

Enable option 'Do not use SOAP envelope' and keep SOAP Action as blank.

[Bhargavakrishna]

Hi,

Set the right Content Type in HTTP receiver adapter.

HTTP status

200 OK

Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request the response will contain an entity describing or containing the result of the action.

201 Created

The request has been fulfilled and resulted in a new resource being created.

Regards

Bhargava krishna

[Former Member]

I'm not sure. Maybe will raise the error---not a soap message or no soap action find

We choose plain http adapter, the pure soap adapter cannot replace http adapter, but axis soap can, but it not support proxy.

[Former Member]

Hi Justin,

You can use standard SOAP adapter to replace HTTP adapter without SOAP Action. To avoid SOAP Envelope being wrapped across the message we check the option 'DO not use the SOAP Envelope'. We have been using this option to perform multi-mapping (split mapping) for HTTP receivers as multi mapping is only supported in adapters in adapter engine.

I am just guessing that SOAP adapter might not face this issue of 201 status. So you can give it a try.

Hope this helps.

Regards,

Anurag

[Former Member]

Hi, Anurag

I follow your suggestion. And not success.

We use https.

any further config?