file2file-receiver-comm channel-incorrect ftp server

[Former Member]

Hello,

The scenario is file (xml) to file (xml) to jumpstart the learning process.

config details:-

a) sender

ftp file "/xi_input.dat" from server 10.20.30.98

processing mode: "delete"

b) receiver

ftp file "/xi_output.dat" to server 10:20:30:98

file construction mode: "create"

Expected result:-

file at sender should be read by XI and deleted. Output file should be created by XI.

Acheived result:-

SXMB_MONI status is "processed successfully-(white black flag). XI read sender file "xi_input.dat" and it was deleted as requested in the config. But there was no output file "/xi_output.dat". Then chaged the FTP server at receiver to 10.20.30.98. This resulted in creation of /xi_output.dat

Question:-

Though I got the desired result, I was unable to find the error from SXMB_MONI by myself.

I could manage to debug and find the sequence of actions, here it goes:-

tointerfacename->service->channel->file adapter->ftp mode

but there is no trace about why /xi_output.dat is not created via ftp (due to typo error in server name).

Please look at the log and advise why SXMB_MONI didn't report this error? or point me how to debug better.

<SAP:ToInterfaceName>mi_name_in</SAP:ToInterfaceName>

<SAP:ToInterfaceNamespace>urn://file2file_2</SAP:ToInterfaceNamespace>

- <SAP:OutboundBindingAttributes>

<SAP:AdapterTypeData xmlns:SAP="http://sap.com/xi/XI/Message/30" />

</SAP:OutboundBindingAttributes>

- <SAP:HeaderMapping>

<SAP:FieldMapping xmlns:SAP="http://sap.com/xi/XI/Message/30" />

</SAP:HeaderMapping>

- <SAP:ChannelEntry version="30">

<SAP:PartyName xmlns:SAP="http://sap.com/xi/XI/Message/30" />

<SAP:ServiceName xmlns:SAP="http://sap.com/xi/XI/Message/30">sevice</SAP:ServiceName>

<SAP:ChannelName xmlns:SAP="http://sap.com/xi/XI/Message/30">cc_in</SAP:ChannelName>

<SAP:AdapterName xmlns:SAP="http://sap.com/xi/XI/Message/30">File</SAP:AdapterName>

<SAP:AdapterNamespace xmlns:SAP="http://sap.com/xi/XI/Message/30">http://sap.com/xi/XI/System</SAP:AdapterNamespace>

<SAP:AdapterSWCV xmlns:SAP="http://sap.com/xi/XI/Message/30">3B787A8035C111D6BBE0EFE50A1145A5</SAP:AdapterSWCV>

<SAP:AdapterEngineType xmlns:SAP="http://sap.com/xi/XI/Message/30">AE</SAP:AdapterEngineType>

<SAP:AdapterEngineName xmlns:SAP="http://sap.com/xi/XI/Message/30" />

<SAP:MessageProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">File</SAP:MessageProtocol>

<SAP:MessageProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30">3.0.0527</SAP:MessageProtocolVersion>

<SAP:TransportProtocol xmlns:SAP="http://sap.com/xi/XI/Message/30">FTP</SAP:TransportProtocol>

<SAP:TransportProtocolVersion xmlns:SAP="http://sap.com/xi/XI/Message/30" />

[Former Member · Accepted solution]

basically sxmb_moni shows errors on integration engine.

First thing when ever you create any communication channel, you need to go to component monitoring --> adapter monitoring and check whether your CC is in green or red. It shows if there is any error.

Then you can do debugging from run timw workbench(RWB) in message monitoring, or you can indivdually debug each component using component monitoring

[Former Member]

thanks for the inputs. I awarded points as well.

the issue is fixed.

I will get with basis why comm channel is still red though it is working

[prabhu_s2]

Hi Shan

This error/log can be traced in CC monitoring in RWB. SXI_MONITOR will throw an error if there is one reported in the IE.

thkx

Prabhu

[Former Member]

Hi,

Change the extension of the input file(.xml)and upload it.

Regards

Madhu

[Former Member]

Hi,

Change the file name from xi_input.dat to xi_input.xml

also rename the file in the source directory, save the file type "as all files" and file name as xi_input.xml

Cheers,

Nagesh.....

[Former Member]

When you monitor adapter engine messages, not all statuses available return results since they only exist in ABAP. They are the following statuses: "Branched", "Application error, "Changed manually", "Repeat attempt" and "Unknown". On the other hand, the "Delivering" and "Holding" statuses only exist in the adapter engine but not in the Integration Engine (ABAP).

thanks-Gopal

[Former Member]

Thanks. The error is exactly what I was looking for.

In RTW->CC->log

Error Attempt to process file failed with Error occurred while connecting to the FTP server "10:20:40:92:21": java.net.UnknownHostException: 10:20:40:92

Now RTW still has red for receiver communication channel with the note

"In the Last 4 Hours Server 0 50_40103 Communication channel is correctly configured and started "

I performed stop and start to the communication channel it results in red status. However it is creating the file without problems.

Any way to make communicaton channel green?

[Former Member]

hmm...if you give valid IP address, save, activate it, then it should show green in communication channel.

--Archana