cancel
Showing results for 
Search instead for 
Did you mean: 

Testing HTTP to File scenario

Former Member
0 Kudos

Hey guys

i m testing a HTTP to file scenario for one of our clients and the test seems to be working fine when i test it in RWB under Integration Engine,MONI is chequered as well as i m getting the file on receiver side too.

but when i test it by making use of the HTTP client which i got from the followin link

/message/266750#266750 [original link is broken]

it gives and error saying http-status 404 not found.

the URL which is getting created is

http://scosap005.sap.com:50100/sap/xi/adapter_plain?namespace=urn%3ANOVInvoiceToSCO&interface=MI_Inv...

is this the same URL our client is gonna use to post the message to our XI server?

also why am i getting error in the second testing?

thanx

ahmad

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Ahmad -

Double check your http port - should be the icm http port, not the J2EE http port. You can confirm in TC SMICM and then Goto->Services. Use the http port listed there.

Regards,

Jin

Former Member
0 Kudos

Thanx Jin Shin

u give one line answers and that solves all the purpose:)

yeah i waz using different port

thanx for ur great help

ahmad

Answers (1)

Answers (1)

agasthuri_doss
Active Contributor
0 Kudos

Hi,

1) Did you maintain Client, userid, password, and lang information in SICF transaction -> sap/xi/engine ? Double click on service and check whether you have entered correct information.

2)Access the trace file and search for traces with severity ERROR, WARNING or stack traces.

If we do not find an error in the log file or the error message does not explain the problem sufficiently, access the default Trace. The default trace file contains detailed messages for developers. Extract the relevant trace information e.g. using the time stamp or the message ID.

If this does not explain the problem in more detail, increase the trace level and reproduce the problem. Then restart message processing using the message display tool. Mark the message and select repeat.

3)Check the Note-803145

4) 404 is an HTTP response code that indicates that the resource in question could not be found. Usually this is due to an incorrect URL check all URLs.

Regards

Agasthuri Doss

Former Member
0 Kudos

Hey

SICF and trace looks fine,one thing which might be helpful is that we have a firewall over the application server which lets messages coming only from certain ip and specific ports to pass through,now i m within the network so i dont have any problem when i test my scenario from the RWB but when i test it using the URL is it considered an internal communication or external communication,if its external then firewall wont let it pass through.

thanx

ahmad