Hi
I have a strange pbm with my fileadapter after SP14..Normally without File content conversion, the adapter works fine and is able to send the XML message to Integration engine..But in a Content conversion mode(from a delimited flat file), I dont see any message in the adapter engine nor the integration engine..
In the RWB adapter monitor I just see this msg,
Sender Adapter v2300 for Party '', Service 'FileSender':
Configured at 2005-11-14 15:10:54 EET
History:
- 2005-11-14 15:25:54 EET: Polling interval started. Length: 60.000 s
- 2005-11-14 15:25:54 EET: Processing finished successfully
- 2005-11-14 15:25:54 EET: Processing started
- 2005-11-14 15:24:54 EET: Polling interval started. Length: 60.000 s
- 2005-11-14 15:24:54 EET: Processing finished successfully
which is the minute-by-min polling trace.
I am not able to capture the error or success message for the file picked up anywhere?? Source file has disappeared from the directory.There is no entry in message monitor for adapter engine and integration engine.neither do i see any in SXMB_MONI..Where could the msg go???
I dont see any msgs being stuck in the queue too..
Regards
Message was edited by: Sriram Vasudevan
4 Answers
-
Nov 14, 2005 at 03:21 PM
Hi Sriram,
I think there might be a problem in connection from the adapter engine to integration pipeline.In SXI_CACHE ,Goto AECACHE and you should be getting a URL pointing to AE.
Otherwise check the port in the XI business system in the SLD wether IE pipeline entry is proper and make it in sync with sxmb_adm and port should be abap stack port 8000 or 8005.
And also try viewing the visual admin logs .
Use this https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2308. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
Add comment
-
Nov 15, 2005 at 11:40 AM
I feel it is something to do with connection parameters from AE to the pipeline.The files might be picked up by the adapter and would not be able to deliver it to IE.Just check the exchange profile parameters too.
Add comment
-
Former MemberNov 16, 2005 at 10:19 AMHi Sriram ,
You could be facing this issue because the adapter is picking up the file, and trying to process it, but is not able to recognise the key fields... and thus not able to create an output XML. Check if the conversion parameter values (especially the Key Field Values) you have specified are in quotes. If so, then remove the quotes and try again.
Cheers
Manish
Add comment
-
Former MemberNov 16, 2005 at 10:34 PM
Well, we found our problem ( Dede Logan and I ).
When you are trying to find a file in the sender comm. channel that is on the mainframe, you can't put just anything in the directory field in SP14 like you could in SP12. You have to put the FTP user ID in the directory field if it is a file from the mainframe. We did this and it worked. Note - This ended up being a mainframe issue and had nothing to do with File Content conversion. I know this probably does not solve Sriram's issue, who started this thread, but it is some free mainframe advice anyway.
Add comment
Add comment