Integration between B2B and ESB error (DOM Parsing Exception in translator)

Hello,
We have configured a circuit that has the objective of sending a message to B2B and then the ESB dequeues that message from the IP_IN_QUEUE.
The problem is that for some reason, the ESB cannot read message using the AQ Adapter object.
The error is the following:
DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
The trace is the following:
ORABPEL-11211 DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable. at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:139) at oracle.tip.adapter.aq.database.MessageReader.translateFromNative(MessageReader.java:1179) at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:533) at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189) at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242) at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215) at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819) at java.lang.Thread.run(Thread.java:595) Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute. at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320) at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1609) at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1514) at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1447) at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1286) at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291) at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:134) ... 8 more
The Payload is the following:
<?xml version="1.0" ?><OMG_O19 xmlns="urn:oracle:integration:b2b:C023D5B231EF45519AA3D9929B4990E1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="HL7" Version="2.4" CreatedDate="2007-07-17T17:10:43" CreatedBy="ECXEngine_837" GUID="{D16D28B9-3821-4BCC-B4D9-0D92F8611BB5}"><Internal-Properties><Data-Structure Name="Message"><Lookup Name="MessageSendingApp">ALERT</Lookup><Lookup Name="MessageSendingAppUniversalID"></Lookup><Lookup Name="MessageSendingAppUniversalIDType"></Lookup><Lookup Name="MessageSendingFacility">CHVNG</Lookup><Lookup Name="MessageSendingFacilityUniversalID"></Lookup><Lookup Name="MessageSendingFacilityUniversalIDType"></Lookup><Lookup Name="MessageReceivingApp">RADIO</Lookup><Lookup Name="MessageReceivingAppUniversalID"></Lookup><Lookup Name="MessageReceivingAppUniversalIDType"></Lookup><Lookup Name="MessageReceivingFacility">CHVNG</Lookup><Lookup Name="MessageReceivingFacilityUniversalID"></Lookup><Lookup Name="MessageReceivingFacilityUniversalIDType"></Lookup><Lookup Name="MessageCode">OMG</Lookup><Lookup Name="TriggerEvent">O19</Lookup><Lookup Name="MessageStructure">OMG_O19</Lookup><Lookup Name="MessageVersion">2.4</Lookup><Lookup Name="InternatCodeID"></Lookup><Lookup Name="InternatCodeText"></Lookup><Lookup Name="InternatCodeSystem"></Lookup><Lookup Name="InternatCodeAlternateID"></Lookup><Lookup Name="InternatCodeAlternateText"></Lookup><Lookup Name="InternatCodeAlternateSystem"></Lookup><Lookup Name="InternationalVersionID"></Lookup><Lookup Name="InternationalVersionIDText"></Lookup><Lookup Name="InternationalVersionIDSystem"></Lookup><Lookup Name="InternationalVersionIDAlternateID"></Lookup><Lookup Name="InternationalVersionIDAlternateText"></Lookup><Lookup Name="InternationalVersionIDAlternateSystem"></Lookup><Lookup Name="Standard">HL7</Lookup><Property Name="MessageEncodingCharacters">^~\&</Property><Property Name="MessageSendingApp">ALERT</Property><Property Name="MessageSendingAppUniversalID"></Property><Property Name="MessageSendingAppUniversalIDType"></Property><Property Name="MessageSendingFacility">CHVNG</Property><Property Name="MessageSendingFacilityUniversalID"></Property><Property Name="MessageSendingFacilityUniversalIDType"></Property><Property Name="MessageReceivingApp">RADIO</Property><Property Name="MessageReceivingAppUniversalID"></Property><Property Name="MessageReceivingAppUniversalIDType"></Property><Property Name="MessageReceivingFacility">CHVNG</Property><Property Name="MessageReceivingFacilityUniversalID"></Property><Property Name="MessageReceivingFacilityUniversalIDType"></Property><Property Name="MessageDate">20070705161247+0000</Property><Property Name="MessageDateTimePrecision"></Property><Property Name="MessageSecurity"></Property><Property Name="MessageCode">OMG</Property><Property Name="TriggerEvent">O19</Property><Property Name="MessageStructure">OMG_O19</Property><Property Name="MessageControlID">1709</Property><Property Name="ProcessingID">P</Property><Property Name="ProcessingMode"></Property><Property Name="MessageVersion">2.4</Property><Property Name="InternatCodeID"></Property><Property Name="InternatCodeText"></Property><Property Name="InternatCodeSystem"></Property><Property Name="InternatCodeAlternateID"></Property><Property Name="InternatCodeAlternateText"></Property><Property Name="InternatCodeAlternateSystem"></Property><Property Name="InternationalVersionID"></Property><Property Name="InternationalVersionIDText"></Property><Property Name="InternationalVersionIDSystem"></Property><Property Name="InternationalVersionIDAlternateID"></Property><Property Name="InternationalVersionIDAlternateText"></Property><Property Name="InternationalVersionIDAlternateSystem"></Property><Property Name="SequenceNumber"></Property><Property Name="ContinuationPointer"></Property><Property Name="AcceptAckType"></Property><Property Name="AppAckType"></Property><Property Name="CountryCode"></Property><Property Name="CharacterSet"></Property><Property Name="LanguageID"></Property><Property Name="LanguageText"></Property><Property Name="LanguageSystem"></Property><Property Name="LanguageAlternateID"></Property><Property Name="LanguageAlternateText"></Property><Property Name="LanguageAlternateSystem"></Property><Property Name="AlternateCharacterSetSchema"></Property><Property Name="ConformanceStatementID"></Property><Property Name="MessageProfileNamespaceID"></Property><Property Name="MessageProfileUniversalID"></Property><Property Name="MessageProfileUniversalIDType"></Property><Property Name="DecimalSeparator"></Property><Property Name="ElementDelimiter">0x7c</Property><Property Name="ReleaseCharacter">0x5c</Property><Property Name="RepeatingSeparator">0x7e</Property><Property Name="SegmentDelimiter">0xd</Property><Property Name="SubcomponentDelimiter">0x26</Property><Property Name="SubelementDelimiter">0x5e</Property></Data-Structure></Internal-Properties><MSH><MSH.1>|</MSH.1><MSH.2>^~\&</MSH.2><MSH.3><HD.1>ALERT</HD.1></MSH.3><MSH.4><HD.1>CHVNG</HD.1></MSH.4><MSH.5><HD.1>RADIO</HD.1></MSH.5><MSH.6><HD.1>CHVNG</HD.1></MSH.6><MSH.7><TS.1>20070705161247+0000</TS.1></MSH.7><MSH.8 xsi:nil="true"></MSH.8><MSH.9><MSG.1>OMG</MSG.1><MSG.2>O19</MSG.2><MSG.3>OMG_O19</MSG.3></MSH.9><MSH.10>1709</MSH.10><MSH.11><PT.1>P</PT.1></MSH.11><MSH.12><VID.1>2.4</VID.1></MSH.12><MSH.13 xsi:nil="true"></MSH.13></MSH><Extra-
PID><Extra-
PID.1 xsi:nil="true"></Extra-
PID.1><Extra-
PID.2 xsi:nil="true"></Extra-
PID.2><Extra-
PID.3><Extra-
PID.3.1>390971</Extra-
PID.3.1><Extra-
PID.3.2 xsi:nil="true"></Extra-
PID.3.2><Extra-
PID.3.3 xsi:nil="true"></Extra-
PID.3.3><Extra-
PID.3.4>CHVNG</Extra-
PID.3.4><Extra-
PID.3.5>NS</Extra-
PID.3.5></Extra-
PID.3><Extra-
PID.4 xsi:nil="true"></Extra-
PID.4><Extra-
PID.5><Extra-
PID.5.1>Santos</Extra-
PID.5.1><Extra-
PID.5.2>Paula</Extra-
PID.5.2><Extra-
PID.5.3>Cristina Silva Lopes</Extra-
PID.5.3></Extra-
PID.5><Extra-
PID.6 xsi:nil="true"></Extra-
PID.6><Extra-
PID.7>19720117000000+0000</Extra-
PID.7><Extra-
PID.8 xsi:nil="true"></Extra-
PID.8><Extra-
PID.9 xsi:nil="true"></Extra-
PID.9><Extra-
PID.10 xsi:nil="true"></Extra-
PID.10><Extra-
PID.11><Extra-
PID.11.1>R Bernardino Costa 358 Bl D Hab 04</Extra-
PID.11.1><Extra-
PID.11.2 xsi:nil="true"></Extra-
PID.11.2><Extra-
PID.11.3>Valadares</Extra-
PID.11.3><Extra-
PID.11.4 xsi:nil="true"></Extra-
PID.11.4><Extra-
PID.11.5>4405</Extra-
PID.11.5></Extra-
PID.11><Extra-
PID.12 xsi:nil="true"></Extra-
PID.12><Extra-
PID.13 xsi:nil="true"></Extra-
PID.13><Extra-
PID.14 xsi:nil="true"></Extra-
PID.14><Extra-
PID.15 xsi:nil="true"></Extra-
PID.15><Extra-
PID.16 xsi:nil="true"></Extra-
PID.16><Extra-
PID.17 xsi:nil="true"></Extra-
PID.17><Extra-
PID.18>7011588</Extra-
PID.18><Extra-
PID.19 xsi:nil="true"></Extra-
PID.19></Extra-
PID><Extra-
PV1><Extra-
PV1.1 xsi:nil="true"></Extra-
PV1.1><Extra-
PV1.2>URG</Extra-
PV1.2><Extra-
PV1.3><Extra-
PV1.3.1>1</Extra-
PV1.3.1><Extra-
PV1.3.2 xsi:nil="true"></Extra-
PV1.3.2><Extra-
PV1.3.3 xsi:nil="true"></Extra-
PV1.3.3><Extra-
PV1.3.4>CHVNG</Extra-
PV1.3.4></Extra-
PV1.3><Extra-
PV1.4 xsi:nil="true"></Extra-
PV1.4><Extra-
PV1.5 xsi:nil="true"></Extra-
PV1.5><Extra-
PV1.6 xsi:nil="true"></Extra-
PV1.6><Extra-
PV1.7 xsi:nil="true"></Extra-
PV1.7><Extra-
PV1.8 xsi:nil="true"></Extra-
PV1.8><Extra-
PV1.9 xsi:nil="true"></Extra-
PV1.9><Extra-
PV1.10 xsi:nil="true"></Extra-
PV1.10><Extra-
PV1.11 xsi:nil="true"></Extra-
PV1.11><Extra-
PV1.12 xsi:nil="true"></Extra-
PV1.12><Extra-
PV1.13 xsi:nil="true"></Extra-
PV1.13><Extra-
PV1.14 xsi:nil="true"></Extra-
PV1.14><Extra-
PV1.15 xsi:nil="true"></Extra-
PV1.15><Extra-
PV1.16 xsi:nil="true"></Extra-
PV1.16><Extra-
PV1.17 xsi:nil="true"></Extra-
PV1.17><Extra-
PV1.18>URG</Extra-
PV1.18><Extra-
PV1.19><Extra-
PV1.19.1>7088430</Extra-
PV1.19.1><Extra-
PV1.19.2 xsi:nil="true"></Extra-
PV1.19.2><Extra-
PV1.19.3 xsi:nil="true"></Extra-
PV1.19.3><Extra-
PV1.19.4>SONHO</Extra-
PV1.19.4></Extra-
PV1.19><Extra-
PV1.20 xsi:nil="true"></Extra-
PV1.20><Extra-
PV1.21 xsi:nil="true"></Extra-
PV1.21><Extra-
PV1.22 xsi:nil="true"></Extra-
PV1.22><Extra-
PV1.23 xsi:nil="true"></Extra-
PV1.23><Extra-
PV1.24 xsi:nil="true"></Extra-
PV1.24><Extra-
PV1.25 xsi:nil="true"></Extra-
PV1.25><Extra-
PV1.26 xsi:nil="true"></Extra-
PV1.26><Extra-
PV1.27 xsi:nil="true"></Extra-
PV1.27><Extra-
PV1.28 xsi:nil="true"></Extra-
PV1.28><Extra-
PV1.29 xsi:nil="true"></Extra-
PV1.29><Extra-
PV1.30 xsi:nil="true"></Extra-
PV1.30><Extra-
PV1.31 xsi:nil="true"></Extra-
PV1.31><Extra-
PV1.32 xsi:nil="true"></Extra-
PV1.32><Extra-
PV1.33 xsi:nil="true"></Extra-
PV1.33><Extra-
PV1.34 xsi:nil="true"></Extra-
PV1.34><Extra-
PV1.35 xsi:nil="true"></Extra-
PV1.35><Extra-
PV1.36 xsi:nil="true"></Extra-
PV1.36><Extra-
PV1.37 xsi:nil="true"></Extra-
PV1.37><Extra-
PV1.38 xsi:nil="true"></Extra-
PV1.38><Extra-
PV1.39 xsi:nil="true"></Extra-
PV1.39><Extra-
PV1.40 xsi:nil="true"></Extra-
PV1.40><Extra-
PV1.41 xsi:nil="true"></Extra-
PV1.41><Extra-
PV1.42 xsi:nil="true"></Extra-
PV1.42><Extra-
PV1.43 xsi:nil="true"></Extra-
PV1.43><Extra-
PV1.44>20070705154838+0000</Extra-
PV1.44><Extra-
PV1.45 xsi:nil="true"></Extra-
PV1.45><Extra-
PV1.46 xsi:nil="true"></Extra-
PV1.46><Extra-
PV1.47 xsi:nil="true"></Extra-
PV1.47><Extra-
PV1.48 xsi:nil="true"></Extra-
PV1.48><Extra-
PV1.49 xsi:nil="true"></Extra-
PV1.49><Extra-
PV1.50 xsi:nil="true"></Extra-
PV1.50><Extra-
PV1.51>V</Extra-
PV1.51><Extra-
PV1.52 xsi:nil="true"></Extra-
PV1.52></Extra-
PV1><Extra-
ORC><Extra-
ORC.1>NW</Extra-
ORC.1><Extra-
ORC.2><Extra-
ORC.2.1>19013</Extra-
ORC.2.1><Extra-
ORC.2.2>ALERT</Extra-
ORC.2.2></Extra-
ORC.2><Extra-
ORC.3 xsi:nil="true"></Extra-
ORC.3><Extra-
ORC.4 xsi:nil="true"></Extra-
ORC.4><Extra-
ORC.5>NW</Extra-
ORC.5><Extra-
ORC.6 xsi:nil="true"></Extra-
ORC.6><Extra-
ORC.7 xsi:nil="true"></Extra-
ORC.7><Extra-
ORC.8 xsi:nil="true"></Extra-
ORC.8><Extra-
ORC.9 xsi:nil="true"></Extra-
ORC.9><Extra-
ORC.10 xsi:nil="true"></Extra-
ORC.10><Extra-
ORC.11 xsi:nil="true"></Extra-
ORC.11><Extra-
ORC.12><Extra-
ORC.12.1>4292</Extra-
ORC.12.1><Extra-
ORC.12.2>Martinez</Extra-
ORC.12.2><Extra-
ORC.12.3>Cristina</Extra-
ORC.12.3></Extra-
ORC.12><Extra-
ORC.13 xsi:nil="true"></Extra-
ORC.13></Extra-
ORC><Extra-
OBR><Extra-
OBR.1>1</Extra-
OBR.1><Extra-
OBR.2><Extra-
OBR.2.1>19013</Extra-
OBR.2.1><Extra-
OBR.2.2>ALERT</Extra-
OBR.2.2></Extra-
OBR.2><Extra-
OBR.3 xsi:nil="true"></Extra-
OBR.3><Extra-
OBR.4><Extra-
OBR.4.1>10781</Extra-
OBR.4.1><Extra-
OBR.4.2>M<escape V="XE3"/>o direita, duas incid<escape V="XEA"/>ncias</Extra-
OBR.4.2><Extra-
OBR.4.3>CHVNG</Extra-
OBR.4.3></Extra-
OBR.4><Extra-
OBR.5 xsi:nil="true"></Extra-
OBR.5><Extra-
OBR.6 xsi:nil="true"></Extra-
OBR.6><Extra-
OBR.7 xsi:nil="true"></Extra-
OBR.7><Extra-
OBR.8 xsi:nil="true"></Extra-
OBR.8><Extra-
OBR.9 xsi:nil="true"></Extra-
OBR.9><Extra-
OBR.10 xsi:nil="true"></Extra-
OBR.10><Extra-
OBR.11 xsi:nil="true"></Extra-
OBR.11><Extra-
OBR.12 xsi:nil="true"></Extra-
OBR.12><Extra-
OBR.13 xsi:nil="true"></Extra-
OBR.13><Extra-
OBR.14 xsi:nil="true"></Extra-
OBR.14><Extra-
OBR.15 xsi:nil="true"></Extra-
OBR.15><Extra-
OBR.16><Extra-
OBR.16.1>4292</Extra-
OBR.16.1><Extra-
OBR.16.2>Martinez</Extra-
OBR.16.2><Extra-
OBR.16.3>Cristina</Extra-
OBR.16.3></Extra-
OBR.16><Extra-
OBR.17 xsi:nil="true"></Extra-
OBR.17><Extra-
OBR.18 xsi:nil="true"></Extra-
OBR.18><Extra-
OBR.19 xsi:nil="true"></Extra-
OBR.19><Extra-
OBR.20 xsi:nil="true"></Extra-
OBR.20><Extra-
OBR.21 xsi:nil="true"></Extra-
OBR.21><Extra-
OBR.22 xsi:nil="true"></Extra-
OBR.22><Extra-
OBR.23 xsi:nil="true"></Extra-
OBR.23><Extra-
OBR.24 xsi:nil="true"></Extra-
OBR.24><Extra-
OBR.25 xsi:nil="true"></Extra-
OBR.25><Extra-
OBR.26 xsi:nil="true"></Extra-
OBR.26><Extra-
OBR.27><Extra-
OBR.27.1 xsi:nil="true"></Extra-
OBR.27.1><Extra-
OBR.27.2 xsi:nil="true"></Extra-
OBR.27.2><Extra-
OBR.27.3 xsi:nil="true"></Extra-
OBR.27.3><Extra-
OBR.27.4>20070705161237+0000</Extra-
OBR.27.4></Extra-
OBR.27><Extra-
OBR.28 xsi:nil="true"></Extra-
OBR.28></Extra-
OBR><Extra-
NTE><Extra-
NTE.1>1</Extra-
NTE.1><Extra-
NTE.2 xsi:nil="true"></Extra-
NTE.2></Extra-
NTE><Extra-
DG1><Extra-
DG1.1>1</Extra-
DG1.1><Extra-
DG1.2 xsi:nil="true"></Extra-
DG1.2><Extra-
DG1.3><Extra-
DG1.3.1>9233</Extra-
DG1.3.1><Extra-
DG1.3.2>Contusao De Dedo Da Mao</Extra-
DG1.3.2><Extra-
DG1.3.3>ICD9</Extra-
DG1.3.3></Extra-
DG1.3><Extra-
DG1.4 xsi:nil="true"></Extra-
DG1.4><Extra-
DG1.5 xsi:nil="true"></Extra-
DG1.5><Extra-
DG1.6>D</Extra-
DG1.6></Extra-
DG1></OMG_O19>
I think that the problem should be because of the "Extra" (eg. <Extra-
PID.1 xsi:nil="true">) word that B2B puts in every tag.
The strange thing is that, this already worked until two days ago....
What could it be?
Thanks for your help.
Best Regards,
Nuno Fernandes

Similar Messages

Getting DOM Parsing Exception in translator while Dequeuing the message from JMS topic

Hi All,
Hope you all doing good.
I have an issue.
I am running on 11.1.1.5 SOA suite version on Linux.
In my aplication I have 4 projects which are connected by with topic/queue.
But in one of the communication, the JMS topic throws me the below error in the log, but dequeue happend perfectly fine and the application runs smoothly.
[ERROR] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@530c530c] [userId: <anonymous>
] [ecid: 5552564bd7cf9140:-117a2347:142149c715a:-8000-00000000069dd133,0] [APP: soa-infra] JMSAdapter <project1>
JmsConsumer_sendInboundMessage:[des
tination = <TOPIC NAME> subscriber = <Consumer project name>
Error (DOM Parsing Exception in translator.[[
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
) while preparing to send XMLRecord JmsXMLRecord
[ERROR] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@530c530c] [userId: <anonymous>
] [ecid: 5552564bd7cf9140:-117a2347:142149c715a:-8000-00000000069dd133,0] [APP: soa-infra] JMSAdapter <project name>
java.lang.Exception: DOM Parsing Exception in translator.
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
        at oracle.tip.adapter.jms.inbound.JmsConsumer.translateFromNative(JmsConsumer.java:603)
        at oracle.tip.adapter.jms.inbound.JmsConsumer.sendInboundMessage(JmsConsumer.java:403)
        at oracle.tip.adapter.jms.inbound.JmsConsumer.send(JmsConsumer.java:1161)
        at oracle.tip.adapter.jms.inbound.JmsConsumer.run(JmsConsumer.java:1048)
        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
But when I try putting the archived data on this topic, it throws me the same error but even dequeuing doesnt happen.
I have extracted the payload and validated against the xsd, it looks fine and even the validator doesnt throw me any error.
But I guess I am missing something, which I am immediately not getting.
Please let me know, if I am soemthing here which is causing this erro.
Thanks,
Chandru

I searched about this error, but no luck.
First time when the message dequeues, the consumer can consume the message but throws the error in the log.
But when I put the message back into queue from archive directory, the consumer doesnt consume message and throws me the same error.
Does anyone faced this sort of issue.
I checked my xsd throughly, and validated it externally. but didnt fine any error.
if anyone knows, suggest me how to resolve this issue.
thanks & regards
Chandru

DOM Parsing Exception in translator. Dequeuing is failing

Hi,
-> I am working on EDI HIPPA File Protocol.
-> My b2b configuration is working. I am getting the payload xml in IP_IN_QUEUE.
But ESB with AQAdaptor is failing giving the below Exception.
-> ORABPEL-11211 DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable. at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:202) at oracle.tip.adapter.aq.database.MessageReader.translateFromNative(MessageReader.java:1179) at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:533) at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189) at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242) at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215) at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:814) at java.lang.Thread.run(Thread.java:595) Caused by: oracle.xml.parser.v2.XMLParseException: Expected name instead of >. at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320) at oracle.xml.parser.v2.XMLReader.scanNameChars(XMLReader.java:1151) at oracle.xml.parser.v2.XMLReader.scanQName(XMLReader.java:1928) at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1276) at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291) at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:197)
-> I have taken the payload xml from rejectedMessages folder from SOA HOME and written a DOM Parser program
to parse that file.It is throwing org.xml.sax.SAXParseException.
-> I validated this xml with xsd I provide both in Oracle B2b config and in ESB using Altova software, it is throwing errors saying the xml is not valid.
-> So I understood that xml which is gettign generated is not the valid one.
Could you please tell me if I have to make any changes.
Thanks
Praveena

Hi Dheeraj,
I did this, I have selected Oracle Integration B2B while generating the xsd, then saved the xsd and then saved ecs.
I gave these ecs and xsd file in my Oracle B2B configruation for Document protocol page.
Then also, I parsed the file which is generated.It is failing in parsing.
I can see that set of empty tags <></> are getting generated before <Segment-SE> tag and after <Loop-2000> as shown below:
</Loop-2100></Loop-2000>&lt&gt&lt/&gt<Segment-SE><Element-96>
(I don't why I am able to see symbols for tags when I am editing this message but once I save the message it is not shown in the forum.actually empty tags are getting geneated.)
I removed these empty tags and parsed it again, then it is parsed successfully.
Could you please tell me what I need to do for not generating these extra empty tags.
my xsd looks as below(pastign for this particular part:
<xsd:element name="Transaction-835">
<xsd:annotation>
<xsd:documentation>Health Care Claim Payment/Advice</xsd:documentation>
<xsd:documentation>This Draft Standard for Trial Use contains the format and establishes the data contents of the Health Care Claim Payment/Advice Transaction Set (835) for use within the context of the Electronic Data Interchange (EDI) environment. This transaction set can be used to make a payment, send an Explanation of Benefits (EOB) remittance advice, or make a payment and send an EOB remittance advice only from a health insurer to a health care provider either directly or via a financial institution.</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="Internal-Properties" minOccurs="0"/>
<xsd:element ref="Segment-ST"/>
<xsd:element ref="Segment-BPR"/>
<xsd:element ref="Segment-TRN"/>
<xsd:element ref="Segment-REF" minOccurs="0"/>
<xsd:element ref="Segment-DTM" minOccurs="0"/>
<xsd:choice maxOccurs="2" minOccurs="2">
<xsd:element ref="Loop-1000A"/>
<xsd:element ref="Loop-1000B"/>
</xsd:choice>
<xsd:element ref="Loop-2000" minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref="Segment-SE"/>
</xsd:sequence>
<xsd:attribute name="Type" default="Transaction" type="xsd:string"/>
<xsd:attribute name="XDataVersion" fixed="1.0" type="xsd:string"/>
<xsd:attribute name="Standard" fixed="HIPAA" type="xsd:string"/>
<xsd:attribute name="Version" default="V4010X091A1" type="xsd:string"/>
<xsd:attribute name="GUID" default="" type="xsd:string"/>
<xsd:attribute name="CreatedBy" type="xsd:string"/>
<xsd:attribute name="CreatedDate" type="xsd:dateTime"/>
</xsd:complexType>
</xsd:element>
Edited by: Praveena Paruchuru on Mar 10, 2009 6:33 AM
Edited by: Praveena Paruchuru on Mar 10, 2009 6:49 AM

DOM Parsing Exception in translator

Hi
We are hitting one issue in B2B/SOA 11g.
BPEL instance is not getting created in 11g. Messages are picked from B2B queue and BPEL is failing while dequeing.
It says that
DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Please make sure that the xml data is valid.
Is it due to large size of the message. I have seen the message size and it is more than 3 MB.
Pls help
Thanks
Simarjeet

Hi Anuj
I have analysed the issue in detail. B2B is not generating the payload for one of the message so dequeue is failing and message is rejected.
Say in one EDI file, we have 6 messages then B2B is able to create 6 separate messages while debatching but one of the message payload is empty. Error in log is
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
DOM Parsing Exception in translator.
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
     at oracle.tip.adapter.aq.v2.database.MessageConverter.translateMessageBytes(MessageConverter.java:510)
     at oracle.tip.adapter.aq.v2.database.MessageConverter.getSTRUCTPayload(MessageConverter.java:404)
     at oracle.tip.adapter.aq.v2.database.MessageConverter.getPayload(MessageConverter.java:139)
     at oracle.tip.adapter.aq.v2.database.XMLRecordMessageConverter.getRecord(XMLRecordMessageConverter.java:88)
     at oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.getInputRecord(AbstractDequeueAgent.java:236)
     at oracle.tip.adapter.aq.v2.database.AbstractDequeueAgent.run(AbstractDequeueAgent.java:101)
     at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
     at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
     at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: ORABPEL-11211
DOM Parsing Exception in translator.
DOM parsing exception in inbound XSD translator while parsing InputStream.
Please make sure that the xml data is valid.
     at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:607)
     at oracle.tip.adapter.aq.v2.database.MessageConverter.translateMessageBytes(MessageConverter.java:506)
     ... 8 more
Caused by: oracle.xml.parser.v2.XMLParseException: Start of root element expected.
     at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:323)
     at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:380)
     at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:321)
     at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:226)
     at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:601)
     ... 9 more
I have also tested the file using various modes unix/pc and ansi/utf-8 encoding. Is this issue related with performance tuning, tablespace etc?

Integration between OID and AD - Error

Hi gurus.
I am using the IDM 10.1.4 to integrate the OID with AD. I am with the follow error:
Trace Log Started at Thu Sep 20 17:36:37 BRT 2007
0 >= 0
java.lang.ArrayIndexOutOfBoundsException: 0 >= 0
     at java.util.Vector.elementAt(Vector.java:431)
     at javax.naming.NameImpl.get(NameImpl.java:534)
     at javax.naming.CompositeName.get(CompositeName.java:364)
     at oracle.ldap.odip.gsi.ActiveReader.getNextChange(ActiveReader.java:400)
     at oracle.ldap.odip.engine.AgentThread.mapExecute(AgentThread.java:634)
     at oracle.ldap.odip.engine.AgentThread.execMapping(AgentThread.java:376)
     at oracle.ldap.odip.engine.AgentThread.run(AgentThread.java:237)
DIP_OIDREADER_ERROR_GET_NEXT_CHANGE
java.lang.NullPointerException
     at oracle.ldap.odip.engine.Debug.logAudit(Debug.java:192)
     at oracle.ldap.odip.engine.Debug.logAudit(Debug.java:185)
     at oracle.ldap.odip.engine.AgentThread.mapExecute(AgentThread.java:821)
     at oracle.ldap.odip.engine.AgentThread.execMapping(AgentThread.java:376)
     at oracle.ldap.odip.engine.AgentThread.run(AgentThread.java:237)
null
ActiveImport:Error in Mapping Enginenull
ActiveImportError in executionjava.lang.NullPointerException
java.lang.NullPointerException
     at java.io.Writer.write(Writer.java:126)
     at java.io.PrintStream.write(PrintStream.java:303)
     at java.io.PrintStream.print(PrintStream.java:462)
     at java.io.PrintStream.println(PrintStream.java:599)
     at java.lang.Throwable.printStackTrace(Throwable.java:461)
     at oracle.ldap.odip.engine.ODIException.printStackTrace(ODIException.java:321)
     at oracle.ldap.odip.engine.AgentThread.execMapping(AgentThread.java:398)
     at oracle.ldap.odip.engine.AgentThread.run(AgentThread.java:237)
Updated Attributes
orclodipLastExecutionTime: 20070920173637
orclodipConDirLastAppliedChgNum: 0
orclOdipSynchronizationStatus: Mapping Failure, Agent Execution Not Attempted
orclOdipSynchronizationErrors: Mapping Failure, Agent Execution Not Attempted
Somebody can help me?
Thanks in advance.

Check your mapping file and see If there are any syntactical error.
Also check the output of the foll. command.
ldapsearch -p port -h host -D cn=orcladmin -w password -b "orclodipagentname=<profile_name>,cn=subscriber profile,cn=changelog subscriber,cn=oracle internet directory" -s base "objectclass=*"

JmsAdapter DOM Parsing Exception handling

Hi,
I'm currently facing a problem with the behaviour of the Jms Adapter.
Whenever a JMS message is put in the queue and that message is not XML valid, the Jms Adapter (consumer) throw the exception "DOM Parsing Exception in translator Exception".
That's fine, I understand that the message was not well formed. But what is not fine is that the underlying BPEL is not instanciated : meaning I can't handle the exception properly.
Is there a way to force the Jms Adapter not to crash on the DOM Parsing for the BPEL to be instanciated (and then being able to handle the exception there) ?
Or is there a way to handle the error thrown by the Jms Adapter itself ? How ?
I think I do have a workaround to this if there is no better option (if both above questions cannot be answered) but I would rather not implement it since it will involve some extra steps / complexity.
> It would be to check the "native format opaque schema" option and then use a java embedded to decode the base64 into a string for eventually parsing it.
regards,
mathieu

Hi Mathieu,
The messages that error out before being posted to the service infrastructure are referred to as rejected messages. For example, the Oracle File Adapter selects a file having data in CSV format and tries to translate it to XML format (using NXSD). If there is any error in the translation, this message is rejected and are not be posted to the target composite.
You can create rejection handlers to handle message errors. Message errors include those that occur during translation, correlation ID mismatch and XML parsing after message reception.
Docs on how to do that are here...
http://docs.oracle.com/cd/E28280_01/integration.1111/e10231/life_cycle.htm#CIAIICJJ
Cheers,
Vlad

Differentiation between B2B and A2A

Hi,
Can anybody give me a real time example between B2B and A2A in general and XI Perspective?
Points Assured
Regards,
B.Anandh

Anandha Krishnan
Here is some more info to top up
Think, Company A is dealing only with Legacy Systems or Java Based applications, but Company B cannot directly understand COmpany A's format. So the Integration Broker like XI will come into picture. While integrating Company A should know how feasible it can communicate with Company B.. More in technical, is thru WebServices Industry Standard Adapters(Seeburger EDI)/(SOAP)/Java Applications(JavaProxy)/.net Applications etc..
<i>Thanks 2 Krishnamoorthy P</i>
Also Check the following help doc
http://help.sap.com/saphelp_nw04s/helpdata/en/15/5f934249c30c31e10000000a1550b0/frameset.htm
regards
krishna

Is it a Bug? Integration between Dreamweaver and Fireworks is broken in somewhere?

I can not upload images related my topic here but you can see
it in the same topic at
http://www.fireworksguruforum.com/index.php?showtopic=14282
I use CS3 Suite. It is a big trouble for me in working on
real pages. Integration is broken in somewhere else and after that
point it becomes impossible to work on Fireworks through
Dreamweaver.
I've made test to show this trouble and I narrowed the
problem to the pictures as shown in the figures below,
1) In figure one I am creating a completely new Fireworks
file as arrow.png with two frames and one slice in it. After I am
saving it as .png I am exporting it as .html with images in /images
subfolder.
2) After saving and closing the file in Fireworks, in figure
two, I am opening the html in Dreamweaver and changing the page
properties by writing zeros to page margins and by changing the
default font.
-----I guess in this point something happens which breaks the
integration between FW and DW--------because;
3) In figure three I am opening the .png through Dreamweaver
(by "Edit") and changes the place and size of the slice a little
bit
4) When I press Done in Fireworks I see this picture in
figure four in Dreamweaver which shows integration between FW and
DW about table structure is broken. (In this point if I add any
behaviur to the slice DW doesn't recognize it, or any other change
in FW can not be recognized by DW)
5) In order to show this broken integration in table
sturucture, I am putting a new slice to png when Editing from DW in
FW.
6) When I click on Done in DW I see this picture on the
figure six. Beacuse FW doesn't have any effect on html's table
structure code.
I can not upload images related my topic here but you can see
it in the same topic at
http://www.fireworksguruforum.com/index.php?showtopic=14282

damlays wrote:
> I can not upload images related my topic here but you
can see it in the same
> topic at
>
http://www.fireworksguruforum.com/index.php?showtopic=14282
>
>
> I use CS3 Suite. It is a big trouble for me in working
on real pages.
> Integration is broken in somewhere else and after that
point it becomes
> impossible to work on Fireworks through Dreamweaver.
>
> I've made test to show this trouble and I narrowed the
problem to the pictures
> as shown in the figures below,
>
> 1) In figure one I am creating a completely new
Fireworks file as arrow.png
> with two frames and one slice in it. After I am saving
it as .png I am
> exporting it as .html with images in /images subfolder.
>
> 2) After saving and closing the file in Fireworks, in
figure two, I am opening
> the html in Dreamweaver and changing the page properties
by writing zeros to
> page margins and by changing the default font.
>
> -----I guess in this point something happens which
breaks the integration
> between FW and DW--------because;
>
> 3) In figure three I am opening the .png through
Dreamweaver (by "Edit") and
> changes the place and size of the slice a little bit
>
> 4) When I press Done in Fireworks I see this picture in
figure four in
> Dreamweaver which shows integration between FW and DW
about table structure is
> broken. (In this point if I add any behaviur to the
slice DW doesn't recognize
> it, or any other change in FW can not be recognized by
DW)
>
> 5) In order to show this broken integration in table
sturucture, I am putting
> a new slice to png when Editing from DW in FW.
>
> 6) When I click on Done in DW I see this picture on the
figure six. Beacuse FW
> doesn't have any effect on html's table structure code.
>
>
> I can not upload images related my topic here but you
can see it in the same
> topic at
>
http://www.fireworksguruforum.com/index.php?showtopic=14282
>
>
>
I can reproduce your results, but I don't consider this a
bug; just a
limitation of Roundtrip editing.
You can't add or change slices without re-exporting the html
from
Fireworks. Roundtrip is for image editing, not for altering
the table
structure. If I edit, and re-export, my table remains intact.
If you want to edit the slices and resulting html, open the
PNG file
independently of Dreamweaver, change your slices and images
and then
choose File > Update HTML (this option is not available
when in
Roundtrip mode). FW will ask you to locate the html file.
When located,
you will have the options of
Replace Images and Their HTML - replaces the previous
Fireworks HTML.
Update Images Only - overwrites only the images.
As an aside, the rigid table created by FW is rarely
desirable for a
production web site.
HTH
Jim Babbage - .:Community MX:. & .:Adobe Community
Expert:.
http://www.communityMX.com/
CommunityMX - Free Resources:
http://www.communitymx.com/free.cfm
.:Adobe Community Expert for Fireworks:.
Adobe Community Expert
http://tinyurl.com/2a7dyp
.:Author:.
Lynda.com -
http://movielibrary.lynda.com/authors/author/?aid=188
Peachpit Press -
http://www.peachpit.com/authors/bio.aspx?a=d98ed798-5ef0-45a8-a70d-4b35fa14c9a4
Layers Magazine -
http://www.layersmagazine.com/author/jim-babbage

What is the main difference between BPEL and ESB

Hi all,
I am making use ESB in my application .Where the my client application calls ESB and inturn the ESB calls the BPEL process .
I want to know the differences between BPEL and ESB,I came to know that ESB can do messaging and routing ,where my BPEL process can also do the same thing .
I came to know form a vendor that ESB is used for connecting to multiple end points ,where as my BPEL process can also do this.
SO what is main purpose of using ESB ?
Cheers,
Kalyan.
Message was edited by:
patti

Hi,
Look for the blog entry dated 1st october 2007.
URL:
http://abhishek-soablog.blogspot.com
Cheers,
Abhi...

Forcing HTTP comm between BPEL and ESB

Hi all,
for demo purposes, I'd like to disable the internal and non-HTTP communication between BPEL and ESB when both are deployed on same OC4J container.
I do not want to modify any WSDL but, if possible, disable somehow such internal communication. AFAIK, there was a property named "optSoapShortcut" in 10.1.2 but it no longer exists in 10.1.3.
Any clues?
TIA

Hi.
Sometime ago I tried to work with a BPEL property named preferredBindings, but it didn't work at all.
WSM Gateway is bypassed when WSDL has SOAP and JCA binding. How to choose??
I don't know if I came across a bug, but in theory I believe this is something like this:
To indicate you want ESB binding:
<property name="preferredBindings">http://www.oracle.com/esb/</property>
To indicate you want SOAP binding (I'm not sure):
<property name="preferredBindings">http://schemas.xmlsoap.org/wsdl/soap/</property>
Please let me know about your results.
Regards.
Denis

Can we have different products between B2B and B2C

Hi Experts,
I have one basic question. Can we maintain the different products between B2B and B2C users. Because we have requirement is B2B users should get all the products, but B2C users should get limited products. Is there way we can setup like this to meet the requirements. Please let me know. Thank you very much in advance.
With Regards,
Sudheer.

You do this by creating two Product Catalogs (PCAT_B2C and PCAT_B2B, for example) Then, in ShopAdmin you assign the B2C site to PCAT_B2C and the B2B to the PCAT_B2B.
Another possibility, although not very user friendly is to use one PCAT and allow B2B users to add items to their cart directly, even thought they're not in the PCAT. The drawback here is that they MUST know the exact number and they can not search for them. I can give more info on this if you feel it might work for you, but it is not a very good option as a general rule.

Can any one send procedure for integration between XI and Geographic inform

can any one send procedure for integration between XI and Geographic information System(GIS).
Please clarify ASAP..
Thanks

Hi,
Please see the below links
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d53af8ca-0801-0010-08b0-dce9e02130a8
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d53af8ca-0801-0010-08b0-dce9e02130a8
GIS VS XI
Regards
Chilla..
Points rewarded if it is usefull..<i></i>

How does the integration between CRM and SD occur

How does the integration between CRM and SD occur? Is only via ALE and are there config steps in CRM to ensure the correct data mapping between CRM and SD?
So, if I create an order or quote in CRM how is it then created in SD? Or do they share the same data store.
thanks

Hi John,
Here is good documentation regarding Data Exchange for Sales Transactions: the CRM Enterprise and the ERP System are two different repositories, If you create the Sales Order in CRM then they will be replicated into SD (using CRM Middleware, BDoc's)
http://help.sap.com/saphelp_crm60/helpdata/en/52/2d0c38941e5666e10000009b38f8cf/frameset.htm
Also you can check the best practice guide for CRM 2007 there you have plenty of information
http://help.sap.com/bp_crmv12007/CRM_DE/HTML/index.htm
Hope this help,
Regards,
Ramon

Business Process & Integration between FI and CML

Hi,
Could you please brief about Business Process & Integration between FI and CML.
Thanks in advance
Prabhakar

Any Inputs please for CML

Integration between Hr and SD

hai sap family memebers,
Can anybody lit me the integration between hr and sd
as per as my knowledge
xd02--> we can integrate hr an sd
if any thing new plz let me know
all the best
madhu

Hi Madhu,
I think Integration will also happen through Infotype 0900 (Sales Data).
Here we will assign Employee to Sales Organization, Sales Office and Sales Group
Thanks
Uday

Integration between B2B and ESB error (DOM Parsing Exception in translator)

Similar Messages

Maybe you are looking for