on 08-11-2008 7:17 AM
Hi All,
I am using JDBC to RFC scenario. Both the adapters are working fine. Message IDs are creating in XI for mesages and the message content is correct in the sender JDBC adater, also the same message is deleivered to RFC adapter and CC monitoring is showing the message processed successfull, But in RFC adapter the message content is not having the data, it has only the structure of the message. So data is not coming to my R/3 system RFC.
Please tell me why the data is not coming to RFC adapter when the processing is successfull.
Regards,
Rookie.
I have mentioned wrong namespace in the JDBC sender adapter, because of which a wrong XML was generating.
Thanks ALL.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI Rookie,
You can check whether your file is picked up or not using Communication Channel Monitoring in RWB.
Try to log in to RWB and select Component Monitoring> Adapter Monitoring> CC Monitoring.
Provide the sender JDBC adapter and Business Service.
This should show you the step-by-step process of Integration Engine.
check the same for Receiver RFC Adapter
At least this should help you in tracking error.
Best Regards
Praveen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Is data Coming from ur Data base?
Plz check the same in SXMB_MONI............. in Inbound Messages--> Payloads
If yes.......... then take that payload & Test ur Message Mapping with that payload.
Thanks,
Mahi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Maheswari,
Yes data is coming properly from Database, when I tested my Message Mapping with this sender payload the following error is coming:
-
12:02:08 Start of test
Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)(:main:, row=1, col=8) -> com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2128) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2776) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) 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:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
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:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.engine.lib.xml.parser.XMLParser.scanPI(XMLParser.java:2128) at com.sap.engine.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2776) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2832) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8)
12:02:08 End of test
-
Hi Prateek,
when I am testing my message mapping w/o this payload i.e with default payload, testing is successfull.
So problem might be with Input Payload generated by Sender JDBC adapter, but I have designed my Data type according to the sender JDBC adapter and the XML generated from JDBC is as follows:
<?xml version="1.0" encoding="utf-8" ?>
- <ns:MT_<Name of Message Type>>
xmlns:ns="http://pspd.com/xi/<Scenario name>/XID">
- <row>
<field name>value</field name>
<field name>value</field name>
</row>
</ns:MT_<Name of Message Type>>
Please tell me whether this format is correct or not.
Hi,
Take the Inbound Payload from MONI and Test it in MApping Test TAB. then u will come to know the exact error.
Procedure to take the Payload
goto MONI-Double click on MessageInbound Message ( CENTRAL ) --Payloads ---Double click on MainDocument ( application/xml ) -Just Right Click on the second window-View Source
then now Copy this and paste it in Mapping Test
Regards
Seshaagiri
No the payload is containing only the structure of the INBOUND message not any content, same is reflecting in the RFC adapter message content in CC monitoring
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Check in sxmb_moni whether the payload is correct after the message mapping step in the pipeline.
Regards,
Prateek
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.