ESB Error Hospital and Rejection Handlers

Hi,
I am getting confused with ESB Error Hospital and ESB Rejection Handlers? Can anyone of you explain me what is this?
Thanks,
Gomathi

Rejection Handlers are used for adapters such as file adapter. When these fail during the invokation of the ESB, you can perform some operation, e.g. call a BPEL process. The default is to write to a default directory. But no notifications are made.
The error hospital is an error handlers for when the process fails in flight. This allows use to send notifications and retry if required, etc.
Here is a good doc on the subject.
http://www.oracle.com/technology/products/integration/esb/files/esb-transactions-errorhandling.pdf
cheers
James

Similar Messages

ESB error handling and notification features

Hello everyone,
I am newbie to oracle SOA ESB. I am an oracle apps guy.
This being my first post to this forum, I have a lot of questions. :-)
For a small intergration requirement, we are looking for a good integration tool
Some requirements are:
1) Flat files will be generated by concurrent programs on oracle apps which need to be transferred to legacy systems.
2) Pick the data from apps tables and insert them into another database. Not much translation required.
After some research, found ESB to be a good fit.
Before actually start using it, we wanted to do a couple of POCs.
So far we are using shell scripts for ftp process. We opted for an integration tool to have DB to DB transmission. Apart from this we need better error handling and error notification mechanism.
Some error conditions:
1) Unavailability of ftp server or Database server.
2) Permission issues. Say some files may not have read, write, deletion permissions. They need to be caught and notified.
3) Mandatory field missing while inserting data which is read from a flat file into a DB table etc..
My initial thoughts on error handling are:
Connection error: To retry for connection errors. If the retry fails send notification via email and also write the failed connection details into an error log file(apart from the server log file).
Data mismatch: NOtification to be sent with the error details.
I would like to know What happens to the file if the destination ftp server is unavailable while ESB is trying to FTP the file. Will ESB retain the file with itself and FTP the file once the ftp server is up?
In BPEL I could see try catch blocks which can be used to handle the errors and thus send notifications.
ESB documents introduced terms like error hospital related to error handling but I was not able to figure out a way of implementing them. As I am not well versed with XML and WSDL I am probably unable to use the fault tab which is in the routing service. I feel Oracle could have given some samples that explain about ESB error handling.
Also to my dismay, adapter docs say that there is a limitation of 7MB size for ftping. Although our file sizes often fall below this size, I would want to know if there is any workaround to over come this size constraint.
I think I put a lot of stuff in a single post and may be in the most haphazard way. Please bear with me.
Please suggest me of some documents if any related to my questions.
Would be really great if you can give me a straight forward solution to all the above problems
Hope this forum would be a great help to me.
Cheers,
Robert.

I have worked on a few SOA Apps implementations. Some successful and some not so. It really comes down to the type of integrations.
But I would say the majority of your integration will be batch as this is what eBus is all about. If this is the case then I would recommend Oracle Data Integrator. If you go Oracle Data Integrator Suite it includes Service Bus and BPEL. ODI has an eBusiness Suite adapter as well.
The good thing about ODI is that you can use it for data conversion, that conversion can then be reused once live, so the conversion is not throw away.
In SOA 10.1.3.4 the limit of 7MB has been resolved but you must be using the file / FTP adapter for input and out, from the sounds of it you want to call concurrent programs so this probably wouldn't work.
cheers
James

Esb error handling

hi all,
is there any sample ESB project implementing error hospital there? i found many sites and blogs for BPEL error hospital but none for ESB. mention any site or blog for ESB error hospital sample project.
Thanks,
Terry

hi all,
is there any sample ESB project implementing error hospital there? i found many sites and blogs for BPEL error hospital but none for ESB. mention any site or blog for ESB error hospital sample project.
Thanks,
Terry

What is error Hospital ?

Hi All,
I am new to SOA Suite, Can anyone shed some light on Error Hospital and how to configure with Fusion ? Any tutorials or useful links are appreciated.
cheers
Srini

Error Hospital might seem like vaporware but in ESB and BPEL they mean 2 different things.
For ESB have a look at this link.
http://www.oracle.com/technology/products/integration/esb/files/esb-transactions-errorhandling.pdf
The error hospital is configured out of the box but the functionality only work when invoking asynchronouse messages. And you need to manually resubmit. If you require additional functionality then to need to make some customisations.
If you want the error hospital in BPEL there is additional functionality have a look at this link and look at the section BPEL Fault Framework
http://www.oracle.com/technology/products/ias/bpel/pdf/10133technotes.pdf
hope this helps
James

Error Hospital java action : How to use getVariableData

Hi all,
I'm playing with Error Hospital and try to use the getVariableData of the IFaultRecoveryContext class. I use something like :
iFaultRecoveryContext.getVariableData("inputVariable","payload","/client:BPELProcessTestPLProcessRequest/client:lastname");
to get the lastname value of my current BPEL instance. But the result I get is oracle.xml.parser.v2.XMLElement@f6fd93
Is anyone know how to get the value ?
Thanks

I finally found a solution ... I cast the line :
((Node)iFaultRecoveryContext.getVariableData("inputVariable","payload","/client:BPELProcessTestPLProcessRequest/client:lastname")).getFirstChild().getNodeValue();
Thanks for your help

Error Handling in BPEL & ESB - Rejection Handlers

Hi guys
I have been trying to evaluate various ways for handling errors/exceptions in BPEL and ESB in Oracle SOA Suite 10.1.3.4 (Basic installation).
What i have found is that in ESB, errors can be handled at two levels: ESB routing service errors using ERROR_TOPIC and Adapter errors using RejectionHandlers. AND
in BPEL errors can be handled using in built try/catch (calling error hospital from the catch) and adapter erros using RejectionHandlers.
I tried using Rejection handlers (bpel, wsif, file) in BPEL and ESB. In BPEL they all are working fine when registered in bpel.xml.
But in ESB only the file handler is working. What i did in ESB is:
I set up an ESB which is polling a file adapter and simply putting the data into a table in database.
Then i created a BPEL (or a Webservice) which is based on http://localhost:8888/orabpel/xmllib/jca/RejectionMessage.wsdl file, taking
{http://xmlns.oracle.com/pcbpel/errorHandling}RejectedMessage as input.
Then I registered Rejection Handler in ESB's file adapter's .esbsvc (or Enpoint property- rejectedMessageHandlers):
"wsif://http//localhost8888/Error_Service/RejectionHandlerPort?wsdl|handleRejection|message"OR "bpel://default:welcome1|BPEL_Error_Handler|handleRejection|message"
I generated error in ESB by changing a column name of the table
For bpel rejection handler:
i was getting error: "<ERROR> <default.collaxa.cube.activation> <AdapterFramework::Inbound> Rejection handler failed
Error while trying to hand off bad message to Rejection handler bpel://default|BPELProcess2|handleRejection|message due to: java.lang.Exception: Failed to create "ejb/collaxa/system/DeliveryBean" bean; exception reported is: "javax.naming.NameNotFoundException: ejb/collaxa/system/DeliveryBean not found
at com.evermind.server.rmi.RMIServerContext.lookup(RMIServerContext.java:207)
at com.evermind.server.ApplicationContext.unprivileged_lookup(ApplicationContext.java:256)
at com.evermind.server.ApplicationContext.lookup(ApplicationContext.java:196)
at javax.naming.InitialContext.lookup(InitialContext.java:351)"
It was solved by adding in server.xml - <application-server ... global-jndi-lookup-enabled="true">. But now i am getting
"Error while trying to hand off bad message to Rejection handler bpel://default:welcome1|BPEL_Error_Handler|handleRejection|message due to: java.lang.LinkageError: duplicate class definition: com/oracle/bpel/client/ejb/interfaces/IDeliveryBeanHome. Please address the underlying issue or correct/redeploy the process."
*For wsif rejection handler*:
getting error: "Error while trying to hand off bad message to Rejection handler wsif://http//localhost8888/Error_webservices/RejectionHandlerPort?WSDL|handleRejection|message due to: exception on JaxRpc invoke: serialization error: java.lang.IllegalArgumentException: getSerializer requires a Java type and/or an XML type
Please address the underlying issue or correct/redeploy the process."
I followed: Link:[http://www.oracle.com/technology/products/integration/adapters/pdf/Adapter_TN_004_Adapter_ErrorManagement.pdf]
Same bpel/wsif handlers pointing to same BPEL/J2EE services, if configured for BPEL adapters, works absolutly fine and gives proble in ESB.
Am i missing something in ESB or is there any patch need to be applied? Please help me there.
Thanks in advance.
Inder

Hi
I even installed SOA Suite 10.1.3.4 MLR#5 Advanced installation with Oracle Express dehyderation store.
I was able to use WSIF rejection handler with this upgrade... but bpel rejection handler was still a failure.
So basically i re-visited ESB documentation. it says that ESB will not support bpel rejection handler.
At least not upto now.
So Summary:
For BPEL we can use - file, wsif, bpel & aq rejection and fatal message handler.
For ESB we can use file, WSIF (10.1.3.4 with MLR#5) & aq rejection and fatal message handler.
Thanks
Inder
Keep going...

How Handle ESB business Faults using Error Hospital

Hai Everyone
I am trying to configure Error Hospital for both BPEL & ESB faults. I`ve successfully configured it for BPEL and am trying to do that for ESB. I found that Fault Management can`t be done for ESB. Is that true ?
If thats true, then I was thinking of a solution:
1) Throw Fault from ESB to BPEL Service Invoker
2) BPEL Invoke activity fails
3) BPEL fault policy will be used.
Now I am struck in throwing fault using XSL transformation from ESB service wsdl to BPEL, but my BPEL invoke activity doesnt understand the fault from wsdl and just thinks that as the output and succeeds.
Is there anyway to get around this ?
cheers
Srini

Nagakiran-
As long as the fault is thrown by external service, you could handle the same ways as system fault.
Below URL could show some example:
http://www.it-eye.nl/weblog/2009/02/14/oracle-bpel-fault-policy-framework-handling-custom-business-faults/
-Sridhar

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

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

ESB Error Recovery

Hi All,
I currently have a service running on the ESB, which takes an input file of 12,000+ rows and processes them in batches of 1 (PublishSize="1"). I'm using rejectedMessageHandlers to output errors to a file. The flow is: file input adapter, translation, database output adapter (stored procedure call).
My issue is that once an error is found in any row of the file, the rest of the file is ignored. As an example, if row 243 is invalid for any reason, the service writes that information to the error file, and then the file is deleted, leaving 11,700+ rows unprocessed.
Is there a way to tell the service to continue to the next row when an error is written using just ESB? We are not using BPEL or any other part of SOA. We do not want to have to manually remove the first 243 rows and then place the remainder in the directory to be picked up again if we don't have to.
Thanks in advance.

Hi
http://download.oracle.com/docs/cd/B14099_19/integrate.1012/b25307/adptr_file.htm
uniqueMessageSeparator Property
""In the case of debatching (multiple messages in a single file), the typical behavior is to reject the messages from the first bad message to the end of the file. If each message has a unique separator and that separator is not part of any data, then rejection can be more fine-grained. In these cases, you can define a uniqueMessageSeparator in the schema element of the native schema to have the value of this unique message separator. This property controls how the adapter translator works when parsing through multiple records in one file (debatching). This property enables recovery even when detecting bad messages inside a large batch file; when a bad record is detected, the adapter translator skips to the next unique message separator boundary and continues from there. If you do not set this property, all records that follow the record that errored are also rejected."
That's what you need right ?

How does BPEL Fault Management Framework gel with ESB Error Handling ?

I see that BPEL 10.1.3.3 has pretty neat Fault Management Framework (although I have to admit it is not very well advertised).
The next logical question is: what about ESB ? Would that help in ESB error handling ? I understand that ESB has its own Error Hospital etc.; however, we have to constantly grapple with two distinct paths for any piece of integration functionality (1. ESB 2. BPEL). I guess, all of this will be moot in the 11g timeframe. Still wondering if anyone out there has somehow unified error handling for these two distinct offerings ?

It's not available in ESB, you have to implement/extend that by your self. Off course in the next release everthing will be better :-)
But, if you are able to use Oracle AIA (http://edelivery.oracle.com) You could use Oracle AIA Foundation, that has a fault 'hospital' implemented both for BPEL and ESB.
Marc
http://orasoa.blogspot.com

Duet has encountered an error during Approve , Reject Reassign the workflow

Hi,
We have implemented DUET with two scenario (LEMA & WOMA) in our organization. When try Approve , Reject or Reassign the Duet work flow Item Duet has encountered an error . The scenario was working fine earlier. Suddenly the error has start coming. The error is coming in a pop up window. I am attaching the error details from event log.
Event Type:     Error
Event Source:     Duet Diagnostics
Event Category:     None
Event ID:     0
Date:          1/04/2010
Time:          10:49:37 AM
User:          N/A
Computer:     xxxxxxxxxxx001
Description:
Error in Approve/Reject from Approver Mail.
Exception message: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Method: Close
StackTrace:   at Microsoft.Office.Interop.Outlook._MailItem.Close(OlInspectorClose SaveMode)
   at SAP.Office.Apps.Leave.Outlook.LeaveApproverMailInspectorCodeBehind.AfterOnSelectControl(String name, String param)
     =====Additional Information=====
oba://oba.microsoft.com/outlook?boundItemId=
Bound Item ID:
Bound Item Type:
Correlation ID:
Process Name: C:\PROGRA1\MICROS3\Office12\OUTLOOK.EXE
User Name: xx\99901
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Thanks in advance,
Monirul Islam

HI Monirul,
You can get better advice and help in another forum dedicated to Duet only.
Regards,
Sangvir

Best practice for Error logging and alert emails

I have SQL Server 2012 SSIS. I have Excel files that are imported with Exel Source and OLE DB Destination. Scheduled Jobs runs every night SSIS packages.
I'm looking for advice that what is best practice for production environment.Requirements are followings:
1) If error occurs with tasks, email is sent to admin
2) If error occurs with tasks, we have log in flat file or DB
Kenny_I

Are you asking about difference b/w using standard logging and event handlers? I prefer latter as using standard logging will not always data in the way in which we desire. So we've developed a framework to add necessary functionalities inside event handlers
and log required data in the required format to a set of tables that we maintain internally.
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

Is it possible to send a instance to error hospital for business errors?

I have a business cenario where if an error is returned from an external service the first time it will automatically retry. The second time it will need to be sent for manual resolution which I was thinking of doing in the error hospital (human intervention) does anyone know if it is possible to send an instance for human-intervention from within the process rather from the fault policies?

We have an instance where sometimes we are sending embedded tiff images to an external service and if the image is corrupt we need to allow the users to terminate the process. Unfrotunately there are no capabilities to send any notifications (email/sms/fax/voicemail) and need to notify the user of the corrupt image and to terminate the process. We could use a worklist task and but the business have defined this as a support team responsibility and want to use the same manual recovery console for all errors. (activities tab)

10.1.3.3 fault management to simplify our complex error hospital pattern

We have designed an error hospital pattern on 10.1.3.1, this consists of :
1. A loop around key components of each process which may fail and need retry (e.g. invokes, database operations)
2. Within each error loop a fault handler, this catches faults as they are thrown and passes them onto another BPEL error handling process (with a nested fault handler in case this invoke fails which spits error out to a file), the error handler can reply with retry (loop around again) or cancel (exit loop), if no response is received an automated retry occurs
3. An error service process which creates a human task for an error to be dealt with
4. A web app which allows users to process the tasks created by the error service, user can inspect data, see fault detail and mainly just select to cancel or retry the failed operation (including multi select if for example hundreds of processes had hit the same error)
This has been refined and is now operating nicely in production, but the development (items 1 and 2 above) and testing effort involved is high - frequently more than the actual business logic. In a 3GL this error handling would be simplified by having a nice reusable piece of code (proceudre or method call) that could go in the error handling loop, rather than putting a whole set of logic (invoke, pick, handling of faults in the error handling code, etc).
I'm aware of the fault management framework in 10.1.3.3 which does a subset of our functionality, we are now looking back at the error hospital we have created and wondering if we could simplify. The main stumbing block I see with the fault management framework is that we need to decide whether to do an automated retry after some interval or whether to await human action, we want to do both, await human activity but if they don't action it retry the operation. I'm thinking that we could achieve everything that we have got by a slight manipulation of the error management framework, as follows :
A. Define faults such that all faults cause human intervention.
B. Create a daemon process which scans for activities requiring human intervention and automatrically triggers a rety after a configurable period (so that things like database errors will get auto retried)
C. Adapt our web app to look for and operate on activities outstanding rather than workflow tasks.
Questions:
i) To support B/C above is there a java api this daemon can use or is it a question of updating the rdbms
ii) Am I underestimating what can be done with the java action fault policy ?
iii) To make our existing approach easier, is there a way of doing an invoke and pick operation actually within an embedded java routine to minimise the amount of code we have in each error handling block
Hope this makes sense, thanks in advance - there seem to be a lot of knowledgeable people out there in this forum.

Hi,
The next blogs might be interesting for you. It addresses your questions.
http://technology.amis.nl/blog/?p=2485
http://www.it-eye.nl/weblog/2007/09/10/oracle-bpel-10133-fault-policy-management/
Kind regards,
Harm

Error : Severity and Description Path Resource Location Creation Time Id

i have this error :
Severity and Description Path Resource Location Creation Time Id
invalid character or markup found in script block. Try surrounding your code with a CDATA block. essai/src essai.mxml Unknown 1236103965593 182
my source is attach code
Many thanks for your help ,
Lionceau,

look my source :
<![CDATA[
import mx.controls.Alert;
import com.adobe.rtc.events.SessionEvent; //utilisé
pour les trois blocs
import com.adobe.rtc.messaging.UserRoles; //utilisé
pour les trois blocs
import com.adobe.rtc.collaboration.AudioPublisher; //
AudioPublisher me sert pour la gestion du microphone
import com.adobe.rtc.collaboration.AudioSubscriber; // me
sert pour choisr l' aboné écouté
//import com.adobe.rtc.collaboration; // me sert pour la
gestion du microphone
//import com.adobe.rtc.clientManagers;// me sert pour la
gestion du microphone
import com.adobe.rtc.events.StreamEvent;// pour le son
(audio xml)
import mx.events.ItemClickEvent; //pour le son ( audio xml)
import mx.controls.Label;
import mx.core.UIComponent; // me sert pour la gestion du
microphone
import flash.events.EventDispatcher;// me sert pour la
gestion du microphone
// import com.adobe.rtc.components:ResizableCanvas; amettre?
//debut bloc share
import
com.adobe.rtc.sharedManagers.descriptors.FileDescriptor;
import mx.utils.UIDUtil;
import mx.collections.ArrayCollection;
import com.adobe.rtc.collaboration.FileSubscriber;
import com.adobe.rtc.sharedManagers.UserManager;
import com.adobe.rtc.messaging.NodeConfiguration;
import com.adobe.rtc.events.CollectionNodeEvent;
import com.adobe.rtc.collaboration.FilePublisher;
import com.adobe.rtc.sharedManagers.FileManager;
[Bindable]
private var applicationTitle:String = "File Publisher
Example";
// list of managers
private var _fileManager:FileManager;
private var _filePublisher:FilePublisher;
private var _fileSubscriber:FileSubscriber;
private var _userManager:UserManager;
// our datagrid dataprovider will use this collection
[Bindable]
private var _fileDescriptors:ArrayCollection = new
ArrayCollection();
// file sharing group id, it is similiar to that of folder
concept
private var _groupid:String = "_filePublisherExample";
//fin bloc share
//debut bloc camera
import com.adobe.rtc.events.UserEvent;
import com.adobe.rtc.events.SharedPropertyEvent;
import com.adobe.rtc.events.ConnectSessionEvent;
import mx.controls.Button;
import com.adobe.coreUI.controls.CameraUserBar;
import mx.core.UITextField;
import com.adobe.rtc.events.SharedPropertyEvent;
import com.adobe.rtc.sharedModel.SharedProperty;
import com.adobe.rtc.collaboration.WebcamSubscriber;
import mx.containers.VBox;
import com.adobe.rtc.events.UserEvent;
import com.adobe.rtc.sharedManagers.StreamManager ;
import
com.adobe.rtc.sharedManagers.descriptors.StreamDescriptor ;
private var currentSubscriber:WebcamSubscriber ;
private var sharedProperty:SharedProperty ;
* This example shows how the camera component can be used
with a publisher and a
* number of subscribers. The publisher has a big view while
subscribers have a small view.
* A shared property is used to pass the stream to the
publisher's user interface.
* Every user is provided with play and pause handlers.
private function onCreationComplete():void
sessionManager.roomManager.autoPromote = true ;
sessionManager.roomManager.guestsHaveToKnock = false ;
sharedProperty = new SharedProperty();
sharedProperty.isSessionDependent = true ;
sharedProperty.sharedID = "webcamShare2" ;
sharedProperty.connectSession = sessionManager ;
sharedProperty.subscribe();
sharedProperty.addEventListener(SharedPropertyEvent.CHANGE,onChange);
sessionManager.userManager.addEventListener(UserEvent.USER_REMOVE,onUserRemove)
* @private
protected function onUserRemove(p_event:UserEvent):void
if ( sharedProperty.value &&
p_event.userDescriptor.userID == sharedProperty.value[0]) {
sharedProperty.value = [] ;
* When the main big stream changes, all users can view it
via the sharedProperty.
private function onChange(p_evt:SharedPropertyEvent):void
if ( currentSubscriber != null ) {
clickedContainer.removeChild(currentSubscriber);
currentSubscriber.close();
currentSubscriber = null ;
if ( sharedProperty.value == null ||
sharedProperty.value.length == 0 ) {
return ;
currentSubscriber = new WebcamSubscriber();
currentSubscriber.connectSession = sessionManager ;
currentSubscriber.subscribe();
currentSubscriber.webcamPublisher = webCamPub ;
currentSubscriber.publisherIDs = sharedProperty.value ;
currentSubscriber.addEventListener(UserEvent.USER_BOOTED,onCleared);
currentSubscriber.addEventListener(UserEvent.STREAM_CHANGE,onCameraPause);
clickedContainer.addChild(currentSubscriber);
invalidateDisplayList();
* If the big image is stopped, clear it.
private function onCleared(p_evt:UserEvent):void
if ( sessionManager.userManager.myUserRole ==
UserRoles.OWNER ) {
sharedProperty.value = [] ;
* Clicking on the small image below makes it large.
private function onClick(p_evt:MouseEvent):void
if ( (p_evt.currentTarget is WebcamSubscriber) &&
!(p_evt.target.parent is CameraUserBar)) {
sharedProperty.value = (p_evt.currentTarget as
WebcamSubscriber).publisherIDs;
* Handler for a user pausing the camera.
protected function onCameraPause(p_evt:UserEvent):void
var userStreams:Array =
sessionManager.streamManager.getStreamsForPublisher(p_evt.userDescriptor.userID,StreamMan ager.CAMERA_STREAM);
if (userStreams.length == 0) {
trace("onCameraPause: no userStreams");
return;
for (var i:int = 0; i< userStreams.length ; i++ ) {
if (userStreams
.type == StreamManager.CAMERA_STREAM ) {
break;
var streamDescriptor:StreamDescriptor = userStreams;
if ( streamDescriptor.streamPublisherID ==
sessionManager.userManager.myUserID ) {
sessionManager.streamManager.pauseStream(StreamManager.CAMERA_STREAM,!streamDescriptor.pa use,streamDescriptor.streamPublisherID);
* Handler for a user stopping the camera.
private function onBooted(p_evt:UserEvent):void
if ( (p_evt.currentTarget is WebcamSubscriber) &&
(p_evt.userDescriptor.userID == sessionManager.userManager.myUserID
|| sessionManager.userManager.myUserRole == UserRoles.OWNER)) {
webCamPub.stop();
if ( (p_evt.currentTarget.parent as VBox).getChildAt(1) is
Button ){
((p_evt.currentTarget.parent as VBox).getChildAt(1) as
Button).label = "Start" ;
if ( sharedProperty.value && (sharedProperty.value
as Array)[0] == p_evt.userDescriptor.userID ) {
sharedProperty.value = [] ;
]]>
</mx:Script>

ESB Error Hospital and Rejection Handlers

Similar Messages

Maybe you are looking for