cancel
Showing results for 
Search instead for 
Did you mean: 

Integration Server Coniguration

Former Member
0 Kudos

XI-Gurus!

We're trying to access the integration server using the file adapter. Polling the file from the source directory works fine but the file isn't transported to the integration server.

In the runtime workbench's message monitor I found an entry that we're using an "unsupported media type" in our message (HTTP code 415). The message has content-type "multipart/related).

Maybe we have a misconfigured integration engine?

I've looked up the configuration with TCODE "SICF". In the HTTP-Handler list there's only on entry "CL_XMS_HTTP_HANDLER".

Is it possible, that this handler doesn't support multipart messages?

Has anybody an idea about this error? Help is highly appreciated...

Regards,

Matthias

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

Ok, we found the reason:

In the HTTP service tree (TCODE SICF) the handler class "CL_HTTP_PLAIN_INBOUND" was configured for service node ".../sap/xi". It seems that this handler has overruled all the handlers in subnodes below.

Thanks to all!

Matthias

Former Member
0 Kudos

Does anybody know some documentation about these http services and the corresponding handler classes?

Thanks in advance!

Matthias

Former Member
0 Kudos

Anirban,

thanks for your quick answer! Your reffered document handles (in my opinion) with client access to the Integration Repository. In this trace file req_resp.trc only the requests for port 50000 are mentioned.

Our problem handles with sending HTTP-messages to the integration engine. The HTTP status code is only visible in the message log and not in a response page.

Thank you anyway, maybe you have another idea?

Cheers,

Matthias

Former Member
0 Kudos

Hi,

Did you have a look at this

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

This is for unsupported media type.

Regards,

Anirban.