File to HTTPs

[Former Member]

File to HTTPs is my scenario. It is Asynchronous.

I am Testing the scenario using Runtime workbench.

Quality of Service I am using "Exactly Once In order"

In the SXMB_Moni I am seeing the Success flag(Black) and in the next tab(ACK Status) it says "Acknowldgement Not Possible"

What does it mean?

[Former Member · Accepted solution]

Hi,

Certain type of adapters do not support acknowledgements. The tab shows the acknowledgement status for a message. For IDoc communication using Idoc adapter, you will be able to see whether the delvery was successful depending on the ack that comes back.

In your scenario, it just means that the adapter does not support acks.

Warm regards,

Venki.

[Former Member · Accepted solution]

Thanks venkitesh.

But in my scenario I am not looking for any kind of Acknowledgements at the first place. Its a stratight forward Asynchronous Scenario (File to HTTPS (asynchnronous)).

So why that message has to come first of all?

Thanks.

[Former Member]

Hi Mohini,

Ignore it, for that message is no acknowledgement supported.

But before you could ask me what does it meam by "no acknowledgement supported", below is the answer....

Receiver adapters support system acknowledgments if they are requested by the server. They are triggered if the message is processed successfully by the adapter. The receiver adapters do not support any application acknowledgments.

http://help.sap.com/saphelp_nw04/helpdata/en/8f/d906d01f77fa40a4c84683c3f8326f/content.htm

Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.

Regards,

Abhy

PN: Just one suggestion, try using Quality of Service as "EO"

[Former Member]

I tried with quality of service EO and I saw two Outputs in my MONI with successful Flag(black color)

In the inbound message(Response) the return code was

<Status code="400" text="Bad Request"

What does it mean?

[Former Member]

Hi,

Read this weblog (3 lines for you)

/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

Mickael

[Former Member]

Hi Mohini,

Check if the RFC you have created for the HTTP conenction is working properly during test.... 400 error would occur only when the ping is failing. Also check if the HTTP adapter settings are perfect in accordance with the receiver settings..

Since error code is 400, check this link,

http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html

it says, for http 400 - its a bad request.

'The request could not be understood by the server due to malformed syntax.'

If you have the XI trouble shooting guide see from page 54,and also try to:

1.Check that the port really is the ICM HTTP Port (transaction

SMICM) and not the J2EE port

2.If the port is wrong, change the pipeline URL in the SLD in

the business system of the Integration Server

3.Restart the J2EE Engine to reset the SLD buffer of the

Adapter Engine

Source- "XI troubleshooting guide"

Regards,

Abhy

[Former Member]

Now I used the Runtime WorkBench to execute my interface, and Initially I got a 403 Error Code.

I manaually changed the Server details in the Send to option then my scenario executed fine and I saw the job in the SXMB_Moni.

How to fix this Error? Any related OSS notes?

Thanks.

[Former Member]

Ignore this query please. Wrong question at the wrong place.

I appologize.