xml authentication via http

[Former Member]

Hello,

so the problem starts when one of our production interfaces tries to authenticate with sap me over the http protocol via a xml line. this is the line:

19.07.11 09:16:51:205 : url: http://172.17.120.220:50000/manufacturing-xml/com/sap/me/integration/xchange/client/ProductionInterf...;

19.07.11 09:16:51:205 : conn: sun.net.www.protocol.http.HttpURLConnection:http://172.17.120.220:50000/manufacturing-xml/com/sap/me/integration/xchange/client/ProductionInterface.jsp?site=TEST3&login=XML&password=password?message=<PRODUCTION_REQUEST><PARAMETRIC><SITE>TEST3</SITE><SFC>EE110614146641</SFC><TYPE>MANUAL</TYPE><RESOURCE>AOI001</RESOURCE><PROGRAM_ID>6374-TOPPOWER</PROGRAM_ID><PROGRAM_REV>1</PROGRAM_REV><USER>XML</USER><TEST_STATUS>pass</TEST_STATUS></PARAMETRIC></PRODUCTION_REQUEST>

boldThe xml messages via url are working but the question is should it work with authentication in the xml message?

we are getting this error in response to the query over http:

19.07.11 09:16:51:314 : line: <SFDM_ERROR>

19.07.11 09:16:51:330 : line: <MESSAGE> Login XML is not valid for site TEST3 (Message 18612) </MESSAGE>

19.07.11 09:16:51:330 : line: </SFDM_ERROR>

[alexander_teslyuk · Accepted solution]

Hi Tarvi,

Please check out this thread:

which refers to the same error message.

Regards,

Alex.

[Former Member · Accepted solution]

Hi,

im familiar with that post and looked it through before posting here. Seems like Nordebrink had problems when sending too many DX_REQUEST xml tags. WE on the otherhand are sending none at all.

as you can see from the logs i posted the xml-string sent to sap me via http is this:

sun.net.www.protocol.http.HttpURLConnection:http://172.17.120.220:50000/manufacturing-xml/com/sap/me/integration/xchange/client/ProductionInterface.jsp?site=TEST3&login=XML&password=password?message=<PRODUCTION_REQUEST><PARAMETRIC><SITE>TEST3</SITE><SFC>EE110614146641</SFC><TYPE>MANUAL</TYPE><RESOURCE>AOI001</RESOURCE><PROGRAM_ID>6374-TOPPOWER</PROGRAM_ID><PROGRAM_REV>1</PROGRAM_REV><USER>XML</USER><TEST_STATUS>pass</TEST_STATUS></PARAMETRIC></PRODUCTION_REQUEST>

now, this string works without authentication in the admin-xml interface, but not via http in a browser.

so your suggestion is to create a ticket for this?

[alexander_teslyuk · Accepted solution]

Hi Tarvi!

DX_REQUEST xml tag is required for XChange interface. Please note that XChange interface is different from Shop Floor XML Interface, which does not require DX_REQUEST xml tag.

So, it works fine when you send the request from

https://host:port/manufacturing-xml/com/sap/me/integration/xchange/test/Test.jsp ,

but fails in

http://host:port/manufacturing-xml/com/sap/me/integration/xchange/client/ProductionInterface.jsp

am I right?

Have you checked 'Allow Remote Legacy Access' and 'Enable Collaboration Action Messages' System Rules?

Regards,

Alex.

Edited by: Alexander Teslyuk on Jul 19, 2011 12:43 PM

[Former Member · Accepted solution]

Hi,

well, we are making a production request not dx_request. Cause we need to send start/stop/complete tags.

as i understand there are 2 different kinds of requests. one is the production one and the other is the data exchange one. for data exchange xml strings we are using dx_request tags and they all work correctly but for the production one we are using PRODUCTION_REQUEST tags.

so as i understand you explained how to fix the data exchange authentication xml string but not the production one.

regards,

[Former Member · Accepted solution]

Hi

Just a quick recap:

Messages work with authentication when we use built in XML sender (production-XML).

Messages work with authentication when we use one of our developers HTTP post tool.

Messages do not work when we try to sent the XML directly from iExplorer address bar with authentication. The string is visible above.

Mentioned system rules are set to true.

The question is is the authentication supposed to work when using IE address bar like shown for XML transfer?

Br,

Jennsen

[sergiy_katerinich · Accepted solution]

Yes, it is.

Could you please replace

?message

with

&message

and re-send the new request?

Regards,

Sergiy

[Former Member · Accepted solution]

Hi

Now it seems to work. I inform our external interface designer and let him to the change and then test again.

Thanks a lot.

Br,

Jennsen