RCV file adapter error:

[Former Member]

hello all,

i am trying a simple jdbc to file scenario. the jdbc adapter picks up a record from the db table successfully, but the file is not posted.

1. in the adapter monitor, i see this msg:

Receiver Adapter v2307 for Party '', Service 'x1s':

Configured at 2006-06-21 08:25:17 PDT

No message processing until now

2. in the message monitoring the status is waiting for some messages and system error for few messages.( i tried resending them but there was a java null lang exception)

3. i tested my message mapping, interface mapping everything works fine.

4. i went to ID -- tools -- test configuration: it showed an error in my interface mapping as below:

Interface Mapping

I am not sure wht the problem is , can anybody advice.

Thanks

[bhavesh_kantilal]

hi aarthi,

from thge info being displayed in your JDBC adapter, I dont think the JDBC adapter is able to select rows from your DB.

Check the Select query in your Sender JDBC adapter and check if it actually returns data.

regards,

bhavesh

[Former Member]

hi bhavesh,

my jdbc adapter successfully picks a record from the db, the problem is it is not posting as a file in the target directory.( i can see the recordbeing picked up from the table in my MONI)

kavitha,

i tested my intf mapping, it is excuting successfully:but i see this ifo

09:18:30 Start of test

Call method execute of the application Java mapping com.sap.xi.tf._JHI_LOAD_DELTA_to_File_

Java mapping com/sap/xi/tf/_JHI_LOAD_DELTA_to_File_ completed. (execute() of com.sap.xi.tf._JHI_LOAD_DELTA_to_File_

Executed successfully

09:18:30 End of test

[bhavesh_kantilal]

Aarthi,

in that case, copy the incoming payload in SXMB_MONI and use it to test your Interface Mapping in the IR.

Increate the trace level and test your interface. WIll help us know the reason of your problem.

ALso, can you post the SOurce Datatype that you hve created along with the select query.

Regards,

Bhavesh

[Former Member]

Hi Bhavesh,

the source xml with my select query is :

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

- <ns:JHI_LOAD_DELTA_Request_MT xmlns:ns="urn:www.jameshardie.com/JDBCTOFile">

- <row>

<ID>DST000024628</ID>

<SCHED_NUM>BPLTL</SCHED_NUM>

</row>

</ns:JHI_LOAD_DELTA_Request_MT>

when i test in my interface mapping: it fails due to parser error,:

10:26:09 Start of test

Call method execute of the application Java mapping com.sap.xi.tf._JHI_LOAD_DELTA_to_File_

Error during appliction Java mapping com/sap/xi/tf/_JHI_LOAD_DELTA_to_File_

com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:37) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:63) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:105) at com.sap.aii.ibrep.server.mapping.ibrun.RepJavaMapping.execute(RepJavaMapping.java:73) at com.sap.aii.ibrep.server.mapping.ibrun.RepMappingHandler.run(RepMappingHandler.java:80) at com.sap.aii.ibrep.server.mapping.rt.MappingHandlerAdapter.run(MappingHandlerAdapter.java:107) at com.sap.aii.ibrep.server.mapping.ServerMapService.transformInterfaceMapping(ServerMapService.java:127) at com.sap.aii.ibrep.server.mapping.ServerMapService.transform(ServerMapService.java:104) at com.sap.aii.ibrep.sbeans.mapping.MapServiceBean.transform(MapServiceBean.java:40) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0.transform(MapServiceRemoteObjectImpl0.java:131) at com.sap.aii.ibrep.sbeans.mapping.MapServiceRemoteObjectImpl0p4_Skel.dispatch(MapServiceRemoteObjectImpl0p4_Skel.java:104) at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:304) at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:193) at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:122) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:130) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3)(:main:, row=2, col=3) -> com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2733) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2778) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) -

---

at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:128) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:68) Caused by: com.sap.engine.lib.xml.parser.ParserException: XMLParser: No data allowed here: (hex) 2d, 20, 3c(:main:, row:2, col:3) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2733) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2778) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:227) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:141) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:156) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:259) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:276) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:338) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 3 more

10:26:09 End of test

from a previous forum discussion, i found out that the MONI payload is missing ns0 ( in namespace) so i went to jdbc adapter and changed the doument name and namespace with ns0, if i do that the adapter is not picking up the record at all

[moorthy]

Aarthi,

Did you check your input xml data given to Interface Mapping is valid one ? Save this xml into a notepad and save it as .xml and open in browser and check is it well-formed or not..

Also you can validate thru XML editors. So there is some problem with message structure here.

Regards,

Moorthy

[Former Member]

hello krishnamoorthy,

i saved the xml as .xml file and tried to open it , ther ewas a error, so i went to source and i removed the '-' sign from the source that was occuring as below and saved it, it opened fine.

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

- <ns:JHI_LOAD_DELTA_Request_MT xmlns:ns="urn:www.jameshardie.com/JDBCTOFile">

- <row>

<ID>DST000024628</ID>

<SCHED_NUM>BPLTL</SCHED_NUM>

</row>

</ns:JHI_LOAD_DELTA_Request_MT>

so the problem is with the XML generated, so how i can produce the XML without the extra '-' sign.

[moorthy]

In runtime it wil not give any problem. It is taken care by XI .. But when you manually test it, then you need to remove that special chars and proceed the testing. Now test in Interface mapping and check the result

Also you can save the file from SXMB_MONI ->window1/2 ...

Anyway-

-Activate the Interface Determination with correct Inbound Interface and also Reciever Agreement

-Refresh the cache in SXI_CACHE

-and test the scenario.

Regards,

Moorthy

[Former Member]

hi,

i tested the intf mapping and i am getting the error below:

11:09:01 Start of test

Call method execute of the application Java mapping com.sap.xi.tf._JHI_LOAD_DELTA_to_File_

Cannot produce target element /ns0:FILE_Response_MT/ROW. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd

11:09:02 End of test

i guess the namespace (ns0) is causing the problem

[moorthy]

<i>i guess the namespace (ns0) is causing the problem</i> >>This will not give problem in the mapping.

/people/michal.krawczyk2/blog/2005/09/16/xi-how-to-test-your-mapping-in-real-life-scenarios

-Moorthy

[bhavesh_kantilal]

Hi Aarthi,

<i>from a previous forum discussion, i found out that the MONI payload is missing ns0 ( in namespace) so i went to jdbc adapter and changed the doument name and namespace with ns0, if i do that the adapter is not picking up the record at all</i>

You do not have to create ns0 , it happens implicitly,

<b>Document Message Type : JHI_LOAD_DELTA_Request_MT

Document Namespace : www.jameshardie.com/JDBCTOFile</b>;

The error message clearly states that the source message format dooes not match with the input. So, edit your Source Dataype to be in the format that you get in the incoming payload.

Regards,

Bhavesh

[Former Member]

Hi,

Check your interface mapping again. Have you specified correct interfaces?

-Kavita