Error in file to file scenario.

[Former Member]

Hi,

I am trying to implement a simple integration scenario in XI, where we pick an XML file and then post an Idoc into SAP based on the contents.

When executing the scenario the file adapter is picking up the file , but then it results in some Java connection error.

Here is the error log I got.

2006-01-02 15:03:25 Success Application attempting to send an XI message asynchronously using connection AFW.

2006-01-02 15:03:25 Success Trying to put the message into the send queue.

2006-01-02 15:03:25 Success Message successfully put into the queue.

2006-01-02 15:03:25 Success The application sent the message asynchronously using connection AFW. Returning to application.

2006-01-02 15:03:25 Success The message was successfully retrieved from the send queue.

2006-01-02 15:03:25 Success File "
10.31.8.215\xifile\outbound\xi_output1.txt" set to 'read-only' after processing

2006-01-02 15:03:25 Success The message status set to DLNG.

<b>2006-01-02 15:03:46 Error Transmitting the message to endpoint http://10.31.8.213:8000/sap/xi/engine?type=entry using connection AFW failed, due to: java.net.ConnectException: Connection timed out: connect.</b>

The IP of our integration server is : 10.31.8.215 but in the error message I find the endpoint ip comes as : 10.31.8.213.

Can anyone suggest what could be the reason behind this error. I think during installation some wrong IP might have got entered, but I am unable to trace out the location where IP addresses for file addresses can be checked.

This error I am getting only while using file adapter to read a file. While writing a file its working perfectly.

Regards

Praveen.

[former_member184154 · Accepted solution]

There are several places in which you can correct this URL. The most important is in SLD (and the only one I'm finding now :-).

Go to SLD, Business Landascape and select your XI instance. In the properties, you can find "Pipeline URL", which is the one Adapter Framework uses to send XML messages to the Integration Engine.

Maybe a J2EE instance (or whole) restart could be helpful after this change.

Let me know.

Alex

[Former Member · Accepted solution]

Thanks Alex,

It worked.

Regards

Praveen