File to file scenario problems

[Former Member]

Hi all,

not so far ago I install XI and it was seems to me that I did all post installation steps.

But when I try to do <a href="https://wiki.sdn.sap.com/wiki/display/XI/FLAT%20FILE%20TO%20FLAT%20FILE">File to File scenario</a>, I receive error in audit log:

-

---

SOAPFault received from Integration Server. ErrorCode/Category: XIServer/IN_BIND_WRONG_ADPT; Params: File; AdditionalText: ; ApplicationFaultMessage: ; ErrorStack: Sender agreement found belongs to adapter File; however, current adapter is 'XI'

Transmitting the message to endpoint http://<xiserver>:8001/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during conversion of XI message.

-

---

(<xiserver> - name of my server)

Please help. Any ideas?

Maxim.

[former_member192343 · Accepted solution]

and don't you want to try this file to file scenario?

https://websmp209.sap-ag.de/~sapdownload/011000358700003165752005E/SP14_SimpleCasesV11.pdf

its more clear

[Former Member · Accepted solution]

I just now try this scenario and get the same error.

How can I send (mail or something else) you screenshots?

[former_member192343 · Accepted solution]

protz (&#1072;) mail.ru

[prabhu_s2 · Accepted solution]

Max

check for pipe line URL value .... must be HTTP port <8xxx>. check

pls gothru the complete replies in the above threads

Message was edited by:

Prabhu S

[Former Member · Accepted solution]

Thank to all! and special thanks for Prabhu S!

I found where was the problem, I have different patch levels of SAP Basis and Java XI tools. So when I install patches for SAP Basis it become to work!

Once more thanks.

Maxim

[former_member192343]

HI

don't you have any other scenarios with same sender agrement or something else?

[Former Member]

No. this is the first scenario in this system.

[former_member192343]

can you send me printscrenn of scenario

tab scenario, double click on the name of scenario and prinscreen

[Former Member]

Hi Maxim,

In addition to Rajeev's reply, I will also add that please check your sender comm channel and the used adapter once again. From the given error it seems that you have used wrong adapter for ex. XI adapter instead of File adapter. Please check that you are using File adapter at sender side comm channel and File adapter at receiver side as well in receiver comm channel. Also check that in the Sender agreement you have used the correct comm channel that belongs to sender side.

Also check the source and target directory path. If the error countinues then go through the <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/flat%20file%20to%20flat%20file&">file to File Scenario</a> again and check that you have followed each step.

Regards,

Subhasha Ranjan

[Former Member]

hi,

I think Adapters are not properly installed.

regards

manoj

[Former Member]

How could it happens?

How do you think where are problems?

[Former Member]

HI,

See the error ,Received HTTP response code 500 : Error during conversion of XI message.

Due to the above error only i suggested..

Check there are some possible ways ..If it is usefull ony..

Regards

Chilla..

[Former Member]

Hi Maxim,

just in ID, see the declaration of your sender comm channel - whether it is file or xi...it should be File adapter........if it is a file adapter, go to SXI_CACHE transaction, do a cache refresh.....again test your scenario.....

Thanks,

Rajeev Gupta

[Former Member]

Hi,

I declare it like file adapter. Just now did cache refresh, but it doesn't help.

Maxim

[Former Member]

Hi Maxim,

after doing cache refresh, did you again test your scenario by putting source file again......what is the error msg now.....

Thanks,

Rajeev Gupta

[Former Member]

Rajeev,

of course I test scenario after cache refresh. Error is still the same.

Maxim.

[Former Member]

Hi Maxim,

i think your problem is you configured file-file scenario... then it was working fine.......after that in some other scenario, you have created a XI adapter comm channel in ID with the same name as your sender File adapter in your this scenario.....

just check your ID, do you have a XI adapter comm channel with the same name as your sender File adapter in your this scenario.....if yes, then make your XI adapter inactive........make your file adapter active.........activate these changes...

now test your scenario....now your this problem may be solved.

Thanks,

Rajeev Gupta

Message was edited by:

RAJEEV GUPTA

[Former Member]

Rajeev,

unfortunaly it is the first scenario in this XI system. So there are no other comm. channels.

Maxim.

Thanks for help.

[former_member192343]

Hi Max, skagi po russki v chem problema

[Former Member]

can check your adapter status in RWB i feel that your adapter engine is not configured properly .

[Former Member]

in RWB adapter engine is green....

[Former Member]

Hi Mikhail,

priatno uslishat rodnoi rech

Problema v tom chto ne rabotaet scenarii "file to file". Pri etom ishodniy file podtagivaetsy no konechniy ne poyavlyetsa. V message monitore Ya vigu oshibku:

SOAPFault received from Integration Server. ErrorCode/Category: XIServer/IN_BIND_WRONG_ADPT; Params: File; AdditionalText: ; ApplicationFaultMessage: ; ErrorStack: Sender agreement found belongs to adapter File; however, current adapter is 'XI'

Transmitting the message to endpoint http://<xiserver>:8001/sap/xi/engine?type=entry using connection AFW failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: Received HTTP response code 500 : Error during conversion of XI message.

&#1052;&#1072;&#1082;&#1089;&#1080;&#1084;.

[Former Member]

HI,

HTTP response code : 500 Internal Server Errors

Description: The server encountered an unexpected condition which prevented it from fulfilling the request.

Possible Tips: Have a look into SAP Notes – 804124, 807000

From Notes :

<i>The problem can be solved in most cases by forcing the XI self-registration to use fully qualified host names.

For XI Integration Builder, Integration Engine and Runtime Workbench, you accomplish this by entering fully qualified host names in the XI Exchange Profile, then initiating a new self-registration (restarting the J2EE engine).

For the Adapter Engine, the approach is different: Change the properties "SLD.selfregistration.httpPort", "SLD.selfregistration.httpsPort" and "SLD.selfregistration.hostName" of the J2EE service SAP XI AF CPA Cache. Enter the fully qualified host name under which the Adapter Engine can be reached from all relevant network domains. Do this in the Visual Administrator of the J2EE Engine. Then restart the applications "com.sap.aii.af.cpa.app" and "com.sap aii.af.app", or restart the complete J2EE engine. This triggers a new Adapter Engine self-registration.

Go in the Integration Server (IS) to transaction "SXI_CACHE -> Goto -> Adapter-Engine-Cache" and delete the old Adapter Engine cache entries. After that the cache is refreshed from SLD as soon as a new message in sent to the respective Adapter Engine.

Check: After restart, navigate in SLD through "Content Maintenance -> XIAdapter Framework" to your Adapter Engine. As part of the "associated instances" you find e.g. at "XI Adapter Service XIRA -> Associated Instances -> Port for XIRA of af.<SID>.<hostname>" the new URL with the fully qualified host name</i>

Regards

Chilla..

<i>Points rewarded if it id usefull..</i>

[Former Member]

Hi Chandra,

I already read this note, but my XI server is not in domain yet, so its FQN =name.

So it seems to me that this note is not for my problem?

Maxim.

[bhavesh_kantilal]

Hi,

In your Sender Adapter, did you create the sender adapter as a file adapter?

Regards

Bhavesh

[Former Member]

Hi,

Yes.