on 01-25-2007 9:11 PM
All,
Newbie here. We are trying a simple file to file scenario - where xi picks up the file from a FTP location and maps the message and dumps it in another FTP location.
While we execute this example - we get the following error -
<b> "Transmitting the message to endpoint http://sandbox1.xxxx.com:54600/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 404 : Not Found."</b>
This is what it shows on the message audit log,
2007-01-25 14:51:11 Success Send binary file "profileinput.xml" from FTP server "166.151.310.200:/sap/work", size 476 bytes with QoS EO
2007-01-25 14:51:11 Success Application attempting to send an XI message asynchronously using connection AFW.
2007-01-25 14:51:11 Success Trying to put the message into the send queue.
2007-01-25 14:51:11 Success Message successfully put into the queue.
2007-01-25 14:51:11 Success The application sent the message asynchronously using connection AFW. Returning to application.
2007-01-25 14:51:11 Success The message was successfully retrieved from the send queue.
2007-01-25 14:51:11 Success Confirmation mode test found. File will be resent next time
2007-01-25 14:51:11 Success The message status set to DLNG.
2007-01-25 14:51:11 Error Transmitting the message to endpoint http://sandbox1.xxxx.com:54600/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 404 : Not Found.
2007-01-25 14:51:11 Success The asynchronous message was successfully scheduled to be delivered at Thu Jan 25 14:56:11 CST 2007.
What might be the issue? Any ideas? (im not able to see this message xml in the SXMB_MONI also.
Thanks.
Go in the SLD, select the business system related to your XI from the "Business Landscape". Then you have an URL, change the port from "54600" to "8046" (the HTTP port of the ABAP WAS).
Then restart the J2EE and it will work.
Regards,
Sandro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the replies. The problem is solved.
Can you tell me why we had to change the port from 54600 to 8046? The original IP was there on the SLD already - probably was configured by the installation team.
If you can give me some URLs or articles that explain this difference - that would be great!
Thanks.
Hi,
Check your pipeline URL defined in the SLD against the Business System for the XI server as it looks like this pipeline URL is incorrect.
Kind regards
Colin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
95 | |
11 | |
11 | |
10 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.