Problem in File to IDOC Scenario

[Former Member]

Hi,

I am trying to test the demo example for Flight Booking using the "File Sender to IDoc" Scenario. I have done all the settings. As a last step after I copy the file in
[XI-hostname]\sapmnt\trans\tmp\fileadapter\group[XX] as per the Demo example guide and activate the changes for File_Sender communication channel, no action is triggered.

The file remains in the directory. When I want to see if my adapter is fine and I check the Adapter Lists in the Adapter Monitoring, it shows only JPR Adapter and that too in RED.

Then I check the tracefiles and find this error.

Date : 04/05/2006

Time : 16:44:52:264

Category : /Applications/ExchangeInfrastructure/Directory

Message ID : 00B0D03E9B4F005A0000000D000001F4000410AB0985C603

Severity : Error

Location : XIDIR.com.sap.aii.ibdir.server.abapcache.ErrorHandler

Source Name : /Applications/ExchangeInfrastructure/Directory

Thread : SAPEngine_Application_Thread[impl:3]_3

Message : Failure at Cache-Refresh data consumption !!!

<?xml version="1.0" encoding="UTF-8"?>

<CacheRefreshError>

<EngineType>AE</EngineType>

<EngineName>af.aba.singdemo1</EngineName>

<RefreshMode>C</RefreshMode>

<Channel>

<PartyName></PartyName>

<ServiceName>XI_LEGACY_BS_00</ServiceName>

<ChannelName>File_Sender</ChannelName>

<ChannelObjectId>838401f3335236bbadd7086c6711b070</ChannelObjectId>

<ChannelError>

<Message>

Could not parse Channel 'File_Sender'(ObjectId: 838401f3335236bbadd7086c6711b070) AdapterType: File|http://sap.com/xi/XI/System|3b787a8035c111d6bbe0efe50a1145a5:

</Message>

<Trace>

com.sap.aii.af.service.cpa.CPAException: Schema not available for File|3b787a8035c111d6bbe0efe50a1145a5|http://sap.com/xi/XI/System.

at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.endElement(DirectoryDataSAXHandler.java:262)

at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler.endElement(SAXDocHandler.java:154)

at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1826)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1722)

at com.sap.engine.lib.xml.parser.XMLParser.scanContent(XMLParser.java:2298)

at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1719)

at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2701)

at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:162)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:126)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:136)

at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:209)

at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:270)

at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:331)

at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)

at javax.xml.parsers.SAXParser.parse(SAXParser.java:143)

at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataParser.updateCentralCache(DirectoryDataParser.java:54)

at com.sap.aii.af.service.cpa.impl.cache.CacheManager.updateCacheWithDirectoryData(CacheManager.java:713)

at com.sap.aii.af.service.cpa.impl.cache.CacheManager.performCacheUpdate(CacheManager.java:595)

at com.sap.aii.af.service.cpa.impl.cache.CacheManager$CacheUpdateRunnable.run(CacheManager.java:440)

at com.sap.engine.frame.core.thread.Task.run(Task.java:60)

at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:73)

at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:145)

</Trace>

</ChannelError>

</Channel>

</CacheRefreshError>

Datasource : 48696150:E:\usr\sap\ABA\DVEBMGS04\j2ee\cluster\server0\log\applications.log

Application : sap.com/com.sap.xi.directory

Argument Objs :

Arguments :

Dsr Component : singdemo1_ABA_48696150

Dsr Transaction : 72d10590c48011da8a7100b0d03e9b4f

Dsr User : Guest

Indent : 0

Level : 0

Message Code :

Message Type : 0

Relatives : XIDIR.com.sap.aii.ibdir.server.abapcache.ErrorHandler

Resource Bundlename :

Session : 3816

Source : /Applications/ExchangeInfrastructure/Directory

ThreadObject : SAPEngine_Application_Thread[impl:3]_3

Transaction : SAP J2EE Engine JTA Transaction : [2ffffffe7b5600a31]

User : XIAFUSER

Any help will be great.

Regards,

Shubham

[Former Member · Accepted solution]

Hi Shubham,

Update the CAPCache, through http://<host>:<port>/CPACache/refresh?mode=full, which will refresh the Adapter Cache. Then you can monitor all the Adapters, not only JPR.

Regards, Sreeni.

[Former Member · Accepted solution]

Hi Sreenivas/Manish,

Tried both suggestions, but it still does not show the adapter list.

Regards,

Shubham

[manish_bhalla2 · Accepted solution]

Hi Shubham,

Try re-activating the particular channel (adapter). You can do this by going into the change mode for the comm channel, making some small change (such as the text) and then saving and activating it.

Also, you might want to check that the particular adapter services are up& running in the J2EE engine. You can check this by logging on to the Visual Administrator, and then going to the relevane services.

Cheers

Manish

[Former Member · Accepted solution]

Hi Manish,

Thanks for your reply.

But I have already tried both the suggestions, but that not help. Until I am able to see the Adapter List, I will not be able to make sure that my Adapter is fine.

Is there some place we need to setup the connectivity to OSS or to sap? I am not able to understand this part

<ChannelError>

<Message>

Could not parse Channel 'File_Sender'(ObjectId: 838401f3335236bbadd7086c6711b070) AdapterType: File|http://sap.com/xi/XI/System|3b787a8035c111d6bbe0efe50a1145a5:

</Message>

<Trace>

com.sap.aii.af.service.cpa.CPAException: Schema not available for File|3b787a8035c111d6bbe0efe50a1145a5|http://sap.com/xi/XI/System.

at com.sap.aii.af.service.cpa.impl.cache.directory.DirectoryDataSAXHandler.endElement(DirectoryDataSAXHandler.java:262)

at com.sap.engine.lib.xml.parser.handlers.SAXDocHandler

What does this mean? Why does it tries to get the information from http://sap.com/xi/XI/System?

Any inputs will be great.

Regards,

Shubham

[manish_bhalla2 · Accepted solution]

Hi Shubham,

Remiport the latest version of the SAP BASIS Software Component from the SLD. The metadata for all the adapters is stored in the namespace http://sap.com/xi/XI/System.

Cheers

Manish

[Former Member · Accepted solution]

Hi Manish,

I updated the same and now when I activate the changes in my File_Sender communication channel its still not working.

I checked the Message Monitoring and the message fails to get delivered.

Here is the Message Audit Log.

-

---

2006-04-11 13:21:51 Success Channel File_Sender: Send binary file "
singdemo1\sapmnt\trans\tmp\fileadapter\group00\Booking00.xml". Size 526 with QoS EO

2006-04-11 13:21:54 Success Application attempting to send an XI message asynchronously using connection AFW.

2006-04-11 13:21:55 Success Trying to put the message into the send queue.

2006-04-11 13:21:56 Success Message successfully put into the queue.

2006-04-11 13:21:56 Success The application sent the message asynchronously using connection AFW. Returning to application.

2006-04-11 13:21:56 Success Confirmation mode test found. File will be resent next time

2006-04-11 13:21:56 Success The message was successfully retrieved from the send queue.

2006-04-11 13:21:57 Success The message status set to DLNG.

2006-04-11 13:23:01 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.

2006-04-11 13:23:03 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:28:01 GMT+08:00 2006.

2006-04-11 13:23:06 Success The message status set to WAIT.

2006-04-11 13:28:02 Success Retrying to send message. Retry: 1

2006-04-11 13:28:02 Success The message was successfully retrieved from the send queue.

2006-04-11 13:28:02 Success The message status set to DLNG.

2006-04-11 13:29:04 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.

2006-04-11 13:29:04 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:34:04 GMT+08:00 2006.

2006-04-11 13:29:04 Success The message status set to WAIT.

2006-04-11 13:34:12 Success Retrying to send message. Retry: 2

2006-04-11 13:34:12 Success The message was successfully retrieved from the send queue.

2006-04-11 13:34:12 Success The message status set to DLNG.

2006-04-11 13:35:15 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.

2006-04-11 13:35:15 Success The asynchronous message was successfully scheduled to be delivered at Tue Apr 11 13:40:15 GMT+08:00 2006.

2006-04-11 13:35:15 Success The message status set to WAIT.

2006-04-11 13:40:15 Success Retrying to send message. Retry: 3

2006-04-11 13:40:15 Success The message was successfully retrieved from the send queue.

2006-04-11 13:40:15 Success The message status set to DLNG.

2006-04-11 13:41:17 Error Transmitting the message to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW failed, due to: Received HTTP response code 500 : Timeout.

2006-04-11 13:41:17 Error The message status set to NDLV.

-

---

What can be the problems?

Regards,

Shubham

[manish_bhalla2 · Accepted solution]

Hi Shubham,

It seems that the entry pipeline itself is timing out. You should check if the XI service is active?

Activate all the services under:

Transaction SICF : default host/sap/xi

Also check to see that the HTTP service is running (transaction SMICM -> Goto -> Services

Cheers

Manish

[Former Member · Accepted solution]

Hi Manish,

I checked the service and it was active.

I restarted my Server then and now the message was delivered succesfully.

2006-04-11 16:04:20 Success Channel File_Sender: Send binary file "
singdemo1\sapmnt\trans\tmp\fileadapter\group00\Booking00.xml". Size 526 with QoS EO

2006-04-11 16:04:20 Success Application attempting to send an XI message asynchronously using connection AFW.

2006-04-11 16:04:20 Success Trying to put the message into the send queue.

2006-04-11 16:04:20 Success Message successfully put into the queue.

2006-04-11 16:04:20 Success The application sent the message asynchronously using connection AFW. Returning to application.

2006-04-11 16:04:20 Success Confirmation mode test found. File will be resent next time

2006-04-11 16:04:20 Success The message was successfully retrieved from the send queue.

2006-04-11 16:04:20 Success The message status set to DLNG.

2006-04-11 16:04:21 Success The message was successfully transmitted to endpoint http://singdemo1:8004/sap/xi/engine?type=entry using connection AFW.

2006-04-11 16:04:21 Success The message status set to DLVD.

But I think it was not recieved by the IS as the file is still lying the directory. What else I need to check?

Thanks and Regards,

Shubham

[manish_bhalla2 · Accepted solution]

Hi Shubham,

Check your adapter config. You have set the Processing Mode to 'Test'. Change that and it should work fine.

Cheers

Manish

[Former Member]

Closing as was unable to solve.

[manish_bhalla2]

Hi Shubham,

Go to transaction SXI_CACHE on your XI box and manually refresh the cache.

Cheers

Manish