Protocol Identification
I´m tryng to use the automotive diagnostic library to create a diagnostic tool using the NI USB-8473. The problem is that i couldn´t identy de protocol that the car is usyng. So I used created a logging VI to see the bus traffic while another diagnostic tool is running:
ID: Data Frame:
04F0 00 A3 FF FF FF FF FF FF
04F1 00 E3 15 A4 01 FF FF FF
04F1 15 E4 01 FF FF FF FF FF
04F0 15 21 02 FF FF FF FF FF
04F1 15 61 02 09 46 47 3B 02
04F0 15 A1 FF FF FF FF FF FF
04F1 15 E1 07 05 08 41 00 FF
04F1 15 E1 06 03 08 42 00 FF
04F1 15 E1 05 02 04 43 00 FF
-I know that 4F0 is the transmiting adress of the tool and 4F1 is the receiving adress of the tool,
-I also know that 15 is the ECU adress when I use KWP2000 K-line diagnosys.
-Besides that 21 is a KWP2000 command and his answer should be 61.
Based on that I assumed the ISO-TP Mixed Mode, wich uses ISO-15765 document. But when I look at the ISO document the 3-4 byte doesn´t fit to the protocol, because they don´t obbey the Protocol control information (N_PCI). So my question is wich protocol this comunication use, is there another standard for this type of communication?
I´m usyng the OBD entrance of the vehicle in both cases and it is a Daimler truck.
Hello MarcusBianchi.
Well, from what I understand, you want to discover a protocol used by Daimler. If this is correct, unfortunally, it is a Daimler's confidential information and I suggest you to contact then.
If you still have doubts or questions, I'm available.
Let me know if this answers your question.
Regards.
Wesley Rocha
Application Engineer
National Instruments Brazil
Visite a nossa comunidade em PORTUGUÊS!!!
Similar Messages
-
Document protocol identification error
Hi While receving Shipment from our trading partner, it showing below error in b2b, Please help me in resolving this? We are suing Custom document over internet.
Machine Info: (essaps000-u008.emrsn.com)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
at java.lang.Thread.run(Thread.java:534)
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) MimePackaging:unpack:Exit
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Enter
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Number of Components = 1
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage compInfoList[k].getValue().toLowerCase()==>text/plain
2009.09.15 at 10:31:07:504: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Components List= [Loracle.tip.adapter.b2b.packaging.ComponentInfo;@4fa23a
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: null Type: AS2 Identifier Value: BENCHQA
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage File Name=>null
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: AS2 Identifier Value: EMRSNS
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: AS2 Identifier Value: BENCHQA
2009.09.15 at 10:31:07:505: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage:Payload <?xml version="1.0" encoding="utf-8"?><ShowShipment releaseID="9.0" systemEnvironmentCode="Production" languageCode="en-US" xmlns:ns6="http://www.openapplications.org/oagis/9/IANAMIMEMediaTypes:2003" xmlns:ns0="http://www.openapplications.org/oagis/9/unqualifieddatatypes/1.1" xmlns:ns1="http://www.openapplications.org/oagis/9/qualifieddatatypes/1.1" xmlns:ns5="http://www.openapplications.org/oagis/9/currencycode/54217:2001" xmlns:ns3="http://www.openapplications.org/oagis/9/languagecode/5639:1988" xmlns:ns2="http://www.openapplications.org/oagis/9/codelists" xmlns:ns4="http://www.openapplications.org/oagis/9/unitcode/66411:2001" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ApplicationArea>
<Sender>
<LogicalID>SCN024538</LogicalID>
<ComponentID>SHIPMENT</ComponentID>
<TaskID>SHOW</TaskID>
<ReferenceID>TSI20090914000000000000000000000002</ReferenceID>
<ConfirmationCode>Never</ConfirmationCode>
<AuthorizationID>160</AuthorizationID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</ApplicationArea>
<DataArea>
<Show>
<OriginalApplicationArea>
<Sender>
<LogicalID>EMR1601000</LogicalID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</OriginalApplicationArea>
</Show>
<Shipment>
<ShipmentHeader>
<DocumentID xsi:type="ItemIDType">
<ID>TSI543897</ID>
</DocumentID>
<DocumentDateTime>20090914</DocumentDateTime>
<DocumentReference type="WayBillAirBill">
<DocumentID>TTSA021720000001</DocumentID>
</DocumentReference>
<DocumentReference type="BillOfLading">
<DocumentID>BTSA02172000002</DocumentID>
</DocumentReference>
<DocumentReference type="PackingSlip">
<DocumentID>TSI543897</DocumentID>
</DocumentReference>
<Attachment inline="false">
</Attachment>
<ActualShipDateTime>20090914</ActualShipDateTime>
<ScheduledDeliveryDateTime>20091012</ScheduledDeliveryDateTime>
<ShipFromParty>
<PartyIDs>
<ID>501V00041757</ID>
</PartyIDs>
<Name>BENCHMARK ELECTRONICS THAILAND</Name>
<Location>
<ID>160234567</ID>
</Location>
</ShipFromParty>
</ShipmentHeader>
<ShipmentItem>
<ItemID>
<ID>166806G1</ID>
<RevisionID>
</RevisionID>
</ItemID>
<SupplierItemID>
<ID> EML166806G1</ID>
</SupplierItemID>
<Description>ASSY GROUND CURRENT DETECTOR</Description>
<ShippedQuantity unitCode="EA">20</ShippedQuantity>
<PurchaseOrderReference>
<DocumentID xsi:type="DocumentIDType">
<ID>501LBR295816</ID>
</DocumentID>
<ReleaseNumber>
</ReleaseNumber>
<LineNumber>001</LineNumber>
<ScheduleLineNumber>1 </ScheduleLineNumber>
</PurchaseOrderReference>
</ShipmentItem>
</Shipment>
</DataArea>
</ShowShipment>
2009.09.15 at 10:31:07:506: Thread-30: B2B - (DEBUG) calling setMode() changing from -1 to 2
2009.09.15 at 10:31:07:511: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:decodeIncomingMessage Exit
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP EMRSNS
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
2009.09.15 at 10:31:07:512: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
2009.09.15 at 10:31:07:513: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
2009.09.15 at 10:31:07:513: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
2009.09.15 at 10:31:07:515: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument Enter
2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = false
2009.09.15 at 10:31:07:519: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2009.09.15 at 10:31:07:520: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2009.09.15 at 10:31:07:520: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@23ce9f
2009.09.15 at 10:31:07:597: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument errcode = Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
2009.09.15 at 10:31:07:598: Thread-30: B2B - (ERROR) com.edifecs.shared.jni.JNIException: Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
at com.edifecs.shared.jni.xdata.INativeToXData.ExecuteNative(Native Method)
at com.edifecs.shared.jni.xdata.INativeToXData.Execute(Unknown Source)
at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.identifyIncomingDocument(EDIDocumentPlugin.java:370)
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3226)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
at java.lang.Thread.run(Thread.java:534)
2009.09.15 at 10:31:07:598: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Enter
2009.09.15 at 10:31:07:657: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2009.09.15 at 10:31:07:658: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:659: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2009.09.15 at 10:31:07:660: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2009.09.15 at 10:31:07:661: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Exit
2009.09.15 at 10:31:07:662: Thread-30: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
at java.lang.Thread.run(Thread.java:534)
2009.09.15 at 10:31:07:662: Thread-30: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
at java.lang.Thread.run(Thread.java:534)
2009.09.15 at 10:31:07:662: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2009.09.15 at 10:31:07:662: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2009.09.15 at 10:31:07:663: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50083: Document protocol identification error
2009.09.15 at 10:31:07:663: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {CONTENT-TRANSFER-ENCODING=binary, CONNECTION=Keep-Alive, AS2-FROM=BENCHQA, CONTENT-TYPE=application/pkcs7-mime; smime-type=enveloped-data; name="smime.p7m", MIME-VERSION=1.0, RECEIPT-DELIVERY-OPTION=http://b2b-qa.bench.com/BenchmarkAS2Receive_QA/BTSHTTPReceive.dll, AS2-VERSION=1.1, EXPECT=100-continue, USER-AGENT=Microsoft(R) BizTalk(R) Server 2006 R2 3.0.1.0, AS2-TO=EMRSNS, CONTENT-LENGTH=5137, ORACLE-ECID=1253032264:10.236.2.145:16396:0:3376,0, MESSAGE-ID=<ANG-QA-BT01_09D55C86-117A-4E5A-90C1-03C8B96EDB2E>, HOST=emersonb2b-s.emrsn.com, B2B_SERVLET_URI_PATTERN=/b2b/transportServlet, DISPOSITION-NOTIFICATION-TO=http://b2b-qa.bench.com/BenchmarkAS2Receive_QA/BTSHTTPReceive.dll}
2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2009.09.15 at 10:31:07:665: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50083: Document protocol identification error
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2009.09.15 at 10:31:07:666: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2009.09.15 at 10:31:07:667: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum0 not null
2009.09.15 at 10:31:07:667: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2009.09.15 at 10:31:07:671: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2009.09.15 at 10:31:07:684: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2009.09.15 at 10:31:07:694: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2009.09.15 at 10:31:07:694: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.09.15 at 10:31:07:734: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
2009.09.15 at 10:31:07:734: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value AS2 IdentifierEMRSNS
2009.09.15 at 10:31:07:769: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2009.09.15 at 10:31:07:815: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2009.09.15 at 10:31:07:827: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2009.09.15 at 10:31:07:828: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2009.09.15 at 10:31:07:828: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2009.09.15 at 10:31:07:830: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = <ANG-QA-BT01_09D55C86-117A-4E5A-90C1-03C8B96EDB2E>
2009.09.15 at 10:31:07:830: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2009.09.15 at 10:31:07:841: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2009.09.15 at 10:31:07:841: Thread-30: B2B - (DEBUG) Engine:notifyApp Enter
2009.09.15 at 10:31:07:848: Thread-30: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>0AEC0291123BE8B0DB800000B91B0200</b2bMessageId>
<errorCode>AIP-50083</errorCode>
<errorText>Document protocol identification error</errorText>
<errorDescription>
<![CDATA[Machine Info: (essaps000-u008.emrsn.com)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
at java.lang.Thread.run(Thread.java:534)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) Engine:notifyApp Exit
2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-50083: Document protocol identification error
2009.09.15 at 10:31:07:859: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Exit
2009.09.15 at 10:31:07:860: Thread-30: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Exit
2009.09.15 at 10:31:07:861: Thread-30: B2B - (DEBUG) DBContext commit: Enter
2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) DBContext commit: Leave
2009.09.15 at 10:31:07:865: Thread-30: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
Edited by: user8653471 on Sep 15, 2009 10:55 PMHi Anuj,
Please set oracle.tip.adapter.b2b.edi.enablePreprocess = true in the ip/config/tip.properties file and restart the server.
Do above statement is related to EDI? I am using Custom document over internet
I did not find any unreadable/non-xml characters in the xml file, here i am attaching the xml fille.
<?xml version="1.0" encoding="utf-8"?><ShowShipment releaseID="9.0" systemEnvironmentCode="Production" languageCode="en-US" xmlns:ns6="http://www.openapplications.org/oagis/9/IANAMIMEMediaTypes:2003" xmlns:ns0="http://www.openapplications.org/oagis/9/unqualifieddatatypes/1.1" xmlns:ns1="http://www.openapplications.org/oagis/9/qualifieddatatypes/1.1" xmlns:ns5="http://www.openapplications.org/oagis/9/currencycode/54217:2001" xmlns:ns3="http://www.openapplications.org/oagis/9/languagecode/5639:1988" xmlns:ns2="http://www.openapplications.org/oagis/9/codelists" xmlns:ns4="http://www.openapplications.org/oagis/9/unitcode/66411:2001" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ApplicationArea>
<Sender>
<LogicalID>SCN024538</LogicalID>
<ComponentID>SHIPMENT</ComponentID>
<TaskID>SHOW</TaskID>
<ReferenceID>TSI20090914000000000000000000000002</ReferenceID>
<ConfirmationCode>Never</ConfirmationCode>
<AuthorizationID>160</AuthorizationID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</ApplicationArea>
<DataArea>
<Show>
<OriginalApplicationArea>
<Sender>
<LogicalID>EMR1601000</LogicalID>
</Sender>
<CreationDateTime>2009-09-15T11:11:21</CreationDateTime>
</OriginalApplicationArea>
</Show>
<Shipment>
<ShipmentHeader>
<DocumentID xsi:type="ItemIDType">
<ID>TSI543897</ID>
</DocumentID>
<DocumentDateTime>20090914</DocumentDateTime>
<DocumentReference type="WayBillAirBill">
<DocumentID>TTSA021720000001</DocumentID>
</DocumentReference>
<DocumentReference type="BillOfLading">
<DocumentID>BTSA02172000002</DocumentID>
</DocumentReference>
<DocumentReference type="PackingSlip">
<DocumentID>TSI543897</DocumentID>
</DocumentReference>
<Attachment inline="false">
</Attachment>
<ActualShipDateTime>20090914</ActualShipDateTime>
<ScheduledDeliveryDateTime>20091012</ScheduledDeliveryDateTime>
<ShipFromParty>
<PartyIDs>
<ID>501V00041757</ID>
</PartyIDs>
<Name>BENCHMARK ELECTRONICS THAILAND</Name>
<Location>
<ID>160234567</ID>
</Location>
</ShipFromParty>
</ShipmentHeader>
<ShipmentItem>
<ItemID>
<ID>166806G1</ID>
<RevisionID>
</RevisionID>
</ItemID>
<SupplierItemID>
<ID> EML166806G1</ID>
</SupplierItemID>
<Description>ASSY GROUND CURRENT DETECTOR</Description>
<ShippedQuantity unitCode="EA">20</ShippedQuantity>
<PurchaseOrderReference>
<DocumentID xsi:type="DocumentIDType">
<ID>501LBR295816</ID>
</DocumentID>
<ReleaseNumber>
</ReleaseNumber>
<LineNumber>001</LineNumber>
<ScheduleLineNumber>1 </ScheduleLineNumber>
</PurchaseOrderReference>
</ShipmentItem>
</Shipment>
</DataArea>
</ShowShipment> -
Error Code: AIP: 50080: Exchange protocol identification error
Hi,
I have setup a business action to process EDI X12 850 (PO) document version 4010 over EDI X12 over Internet - HTTP. To simulate the Trading Partner sending the EDI data to us I have developed a test.html page to submit the EDI data. The test.html does a http post to the b2b/transportServlet. When I do this I get the following error:
AIP: 50080 Exchange protocol identification errorMy Business Action
setup look like this:
BUSINESS ACTION:
Create Business Action : Review for 850
Business Protocol : EDI X12 over Internet
Process Protocol : B2B
Process Protocol Revision : B2B Process - 1.0
General
Name :Process_850
Revision :1.0
Document Protocol Revision
Name :X12_4010
Revision :4010
Document Type
Document Type :850
Document Definition :850_Def
Create Business Action : Review
Business Protocol :EDI X12 over Internet
Process Protocol :B2B
Process Protocol Revision :B2B Process - 1.0
General
Name :Process_997
Revision :1.0
Document Protocol Revision
Name :X12_4010
Revision :4010
Document Type
Document Type :997
Document Definition :997_Def
Create Trading Partner : Review
General
Name :ACME
Operational Capability
Business Protocol :EDI X12 over Internet
Business Action :Process_850
Use Default Document Protocol Parameters :false
Use Default Document Definition :true
Communication Capability
Delivery Channel :ACME_X12_DC
Document Exchange :ACME_X12_DocEx
Exchange Protocol Revision :AS2 - 1.1
Transport :ACME_X12_Transport
Transport Protocol :HTTP
Transport Server :ACME_X12_Transport_Server
Trading Partner :ACME
Business Protocol :EDI X12 over Internet
Details
Business Action :Process_997 - Responder
Is Initiator :false
Functional acknowledgement required? :false
Is acknowledgement handled by Integration B2B? :true
Document Information
Document Protocol :EDI_X12
Document Protocol Revision :X12_4010
Document Type :997
Document Definition
Document Protocol Parameters
Name Value
Interchange Time #SystemTime(HHMM)#
Interchange ecs File
Security Information Qualifier 00
Security Information
Authorization Information
[ Application Receiver's Code ] ACME
Interchange Control Standard/Repetition Separator U
Segment Delimiter 0x27
Interchange Date #SystemDate(YYMMDD)#
Authorization Information Qualifier 00
[ Application Sender's Code ] ACME
ImplementationClass oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin
[ Interchange Sender ID Qualifier ] ZZ
Replacement Character 0x7c
Subelement Delimiter 0x2b
Interchange Control Version Number 00200
[ Interchange Sender ID ] ACME
[ Interchange Receiver ID Qualifier ] ZZ
Tag Delimiter 0x3d
Usage Indicator P
[ Interchange Receiver ID ] ACME
Version/Release/Industry Identifier Code
Component Element Separator 0x2b
Decimal Separator 0x2e
Functional Group Time #SystemTime(HHMM)#
Responsible Agency Code X
Functional Group Date #SystemDate(CCYYMMDD)#
Group ecs File
Element Delimiter 0x7e
Create Trading Partner : Review
General
Trading Partner :GLOBALCHIPS
Communication Capability
Delivery Channel :GLOBALCHIPS_X12_DOC
Document Exchange :GLOBALCHIPS_X12_DocEx
Exchange Protocol Revision :AS2 - 1.1
Transport :GLOBALCHIPS_X12_Transport
Transport Protocol :HTTP
Transport Server :GLOBALCHIPS_X12_Transport_Server
Confirmation
Trading partner participant successfully added.
Agreement Details: X12_Agreement
Details
Agreement Id X12_1001
Description
Effective From Date
Effective To Date
Invocation Limit
Concurrent Conversations
Trading Partner Participants
ACME - Process_850 - Initiator
GLOBALCHIPS - Process_850 - Responder
GLOBALCHIPS - Process_997 - Initiator
ACME - Process_997 - Responder
If I tried to use enq_850 I am getting the following error:
AIP-50547 : Trading partner agreement not found for the given input values: From party[NAME] "GLOBALCHIPS", To party[NAME] "GLOBALCHIPS", Business action name "Process_850"; also verify agreement effectiveToDateHi Ramesh,
I have created Internal Deliver Channel as File Inbound for the Host Trading Partner and at the time of creating the agreement between the partners I have selected this channel.
And I am keeping the EDI document in the end point folder. I am giving the file name as XXX_850_4010_1_12345.dat.
Now I am not getting General validation error. This time I am getting the below error.
Please Let me know If my approch is correct?
Error Brief :
5000: Parser error - Missing trailer.
5042: Parser error - No matching parser schema was found.
Error Brief :
5000: Parser error - Missing trailer.
5042: Parser error - No matching parser schema was found.
iAudit Report :
<?xml version="1.0" encoding="UTF-16"?><AnalyzerResults Guid="{BACD5C1A-90BE-4D6D-8F48-97E66EE909B6}" InterchangeReceived="1" InterchangeProcessed="1" InterchangeAccepted="0"> <ExecutionDate>Friday, January 12, 2007</ExecutionDate> <ExecutionTime>02:26:40 PM (India Standard Time)</ExecutionTime> <AnalyzerReturn>Failed</AnalyzerReturn> <NumberOfErrors>2</NumberOfErrors> <ErrorByCategory> <Category Name="Rejecting"> <Severity Name="Normal">2</Severity> </Category> </ErrorByCategory> <Status>Finished</Status> <DataFile> <FilePath>D:\OraASRel2\ip</FilePath> <FileName/> <LastModified/> <FileSize/> <DataURL>file:\\D:\OraASRel2\ip</DataURL> </DataFile> <Interchange Guid="{A87B69C1-43E3-423B-AA44-9F0C3BE37CF3}" InterchangeAckCode="R" FunctionalGroupReceived="1" FunctionalGroupProcessed="1" FunctionalGroupAccepted="0" RError="1" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>951</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="InterchangeSenderQual">ZZ</Link> <Link Name="InterchangeSenderID">BLUECHIPS </Link> <Link Name="InterchangeReceiverQual">12</Link> <Link Name="InterchangeReceiverID">colourchips </Link> <Link Name="InterchangeControlVersion">00300</Link> <Link Name="Standard">X12</Link> </Links> <Properties> <Property Name="InterchangeAuthorizationInfoQual">00</Property> <Property Name="InterchangeAuthorizationInfo"> </Property> <Property Name="InterchangeSecurityInfoQual">00</Property> <Property Name="InterchangeSecurityInfo"> </Property> <Property Name="InterchangeSenderQual">ZZ</Property> <Property Name="InterchangeSenderID">BLUECHIPS </Property> <Property Name="InterchangeReceiverQual">12</Property> <Property Name="InterchangeReceiverID">colourchips </Property> <Property Name="InterchangeDate">061207</Property> <Property Name="InterchangeTime">1601</Property> <Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property> <Property Name="InterchangeControlVersion">00300</Property> <Property Name="InterchangeControlNumber">000050524</Property> <Property Name="InterchangeAckRequested">1</Property> <Property Name="InterchangeUsageIndicator">P</Property> <Property Name="InterchangeComponentElementSep">0x2a</Property> <Property Name="DecimalSeparator"/> <Property Name="ElementDelimiter">0x7e</Property> <Property Name="ReleaseCharacter"/> <Property Name="RepeatingSeparator"/> <Property Name="SegmentDelimiter">0x2b0xd0xa</Property> <Property Name="SubelementDelimiter">0x2a</Property> </Properties> </NodeInfo> <FunctionalGroup Guid="{BF922FB1-9661-462C-B5A6-D868869A8C79}" FunctionalGroupAckCode="R" TransactionSetsIncluded="1" TransactionSetsReceived="1" TransactionSetsProcessed="1" TransactionSetsAccepted="0" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>108</StartPos> <Size>843</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="GroupSenderID">BLUECHIPS</Link> <Link Name="GroupReceiverID">colourchips</Link> <Link Name="GroupVersionNumber">004010</Link> </Links> <Properties> <Property Name="GroupID">PO</Property> <Property Name="GroupSenderID">BLUECHIPS</Property> <Property Name="GroupReceiverID">colourchips</Property> <Property Name="GroupDate">20061207</Property> <Property Name="GroupTime">1601</Property> <Property Name="GroupControlNumber">150524</Property> <Property Name="GroupAgencyCode">X</Property> <Property Name="GroupVersionNumber">004010</Property> <Property Name="GroupChildCount">1</Property> <Property Name="GroupTrailerControlNumber">150524</Property> </Properties> </NodeInfo> <Transaction Guid="{367C24CC-9747-4E49-9F02-AFC4295CF850}" TransactionAckCode="R" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>171</StartPos> <Size>766</Size> </DataXPointer> <NodeInfo> <Links> <Link Name="TransactionID">850</Link> </Links> <Properties> <Property Name="TransactionID">850</Property> <Property Name="TransactionControlNumber">158192</Property> <Property Name="TransactionImplementationReference"/> <Property Name="TransactionChildCount">26</Property> <Property Name="TransactionTrailerControlNumber">158192</Property> </Properties> </NodeInfo> </Transaction> </FunctionalGroup> <InterchangeErrors> <Error ErrorCode="{03942C04-7909-4DFB-8F7D-6E5B3D8BDF48}" Severity="Normal" Category="Rejecting" Index="1" ID="50000200"> <ErrorBrief>5000: Parser error - Missing trailer.</ErrorBrief> <ErrorMsg>The Interchange Trailer is missing. The segment itself may be missing or the Segment Delimiter may be missing.{br}{br}Trailer was expected after:{br}{tab}Character: 952 </ErrorMsg> <ErrorObjectInfo> <Parameter Name="ErrorLevel">1</Parameter> <Parameter Name="Name">Parser</Parameter> <Parameter Name="_ec_CaseID">02</Parameter> <Parameter Name="_ec_dn_guid_">{A87B69C1-43E3-423B-AA44-9F0C3BE37CF3}</Parameter> <Parameter Name="_ec_start_pos_">952</Parameter> <Parameter Name="ec_error_scope">File</Parameter> </ErrorObjectInfo> <ErrorDataInfo> <Part1/> <Part3/> <DataXPointer> <StartPos>952</StartPos> <Size>0</Size> </DataXPointer> </ErrorDataInfo> </Error> </InterchangeErrors> </Interchange> <AnalyzerErrors> <Error ErrorCode="{9EE55FDF-8668-4499-9F2E-D9247519A850}" Severity="Normal" Category="Rejecting" Index="2" ID="50420000"> <ErrorBrief>5042: Parser error - No matching parser schema was found.</ErrorBrief> <ErrorMsg>The data starting at position 951 is not a valid EDI interchange. The remainder of the data file was ignored.</ErrorMsg> <ErrorObjectInfo> <Parameter Name="ErrorLevel">0</Parameter> <Parameter Name="Name">Parser</Parameter> <Parameter Name="_ec_start_pos_">951</Parameter> <Parameter Name="ec_error_scope">File</Parameter> </ErrorObjectInfo> <ErrorDataInfo> <Part1/> <ErrData/> <Part3/> <DataXPointer> <StartPos>951</StartPos> <Size>0</Size> </DataXPointer> </ErrorDataInfo> </Error> </AnalyzerErrors></AnalyzerResults>
2007.01.12 at 14:26:40:779: Thread-12: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:2403)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1263)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:1845)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1777)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1735)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:455)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:327)
at java.lang.Thread.run(Thread.java:534)
Thanks
Raghu -
Rosettanet--document protocol identification error
Hi guys,
i am trying inbound operation using oracle Rosettanet standard(3a4) i have taken PO request XSD and Input XML from Oracle sample Rosettanet-004 i am getting document protocol identification error i have changed the GlobalBusinessIdentifier value for buyer and seller according to my duns values. Still any values i have to change?
can any one help on this?
thanks in advance...Hi,
Here is my wire message payload..
*<?xml version="1.0" encoding="UTF-8"?>*
*<Pip3A4PurchaseOrderRequest xmlns="http://www.edifecs.com/RosettaNet/100PO">*
*<fromRole>*
*<PartnerRoleDescription>*
*<ContactInformation>*
*<contactName>*
*<FreeFormText>Kerri Makela</FreeFormText>*
*</contactName>*
*<EmailAddress>Not Available</EmailAddress>*
*<telephoneNumber>*
*<CommunicationsNumber>4805521413</CommunicationsNumber>*
*</telephoneNumber>*
*</ContactInformation>*
*<GlobalPartnerRoleClassificationCode>Buyer</GlobalPartnerRoleClassificationCode>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>927775478</GlobalBusinessIdentifier>*
*<GlobalSupplyChainCode>Electronic Components</GlobalSupplyChainCode>*
*</BusinessDescription>*
*<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>*
*</PartnerDescription>*
*</PartnerRoleDescription>*
*</fromRole>*
*<GlobalDocumentFunctionCode>Request</GlobalDocumentFunctionCode>*
*<PurchaseOrder>*
*<AccountDescription>*
*<accountName>*
*<FreeFormText>INTEL CORP</FreeFormText>*
*</accountName>*
*<AccountNumber>035219007</AccountNumber>*
*<billTo>*
*<PartnerRoleDescription>*
*<ContactInformation>*
*<PhysicalAddress>*
*<addressLine1>*
*<FreeFormText>ACCOUNTS PAYABLE</FreeFormText>*
*</addressLine1>*
*<addressLine2>*
*<FreeFormText>P.O. Box 1000</FreeFormText>*
*</addressLine2>*
*<cityName>*
*<FreeFormText>Hillsboro</FreeFormText>*
*</cityName>*
*<GlobalCountryCode>US</GlobalCountryCode>*
*<GlobalLocationIdentifier>0478978550001</GlobalLocationIdentifier>*
*<NationalPostalCode>97123-100</NationalPostalCode>*
*<regionName>*
*<FreeFormText>OR</FreeFormText>*
*</regionName>*
*</PhysicalAddress>*
*</ContactInformation>*
*<GlobalPartnerRoleClassificationCode>Payer</GlobalPartnerRoleClassificationCode>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>*
*<businessName>*
*<FreeFormText>INTEL CORP</FreeFormText>*
*</businessName>*
*</BusinessDescription>*
*</PartnerDescription>*
*</PartnerRoleDescription>*
*</billTo>*
*</AccountDescription>*
*<comments>*
*<FreeFormText>THIS PURCHASE ORDER CONFORMS TO THE TERMS AND__CONDITIONS SET FORTH IN CONTRACT. THE PARTIES HEREBY AGREE__TO AMEND SAID CONTRACT, FOR THIS ORDER ONLY, BY INCORPORATING THE NON__CONFLICTING TERM BELOW:__PARTIAL SHIPMENTS WILL NOT BE ACCEPTED. SHIP COMPLETE__PLEASE CONFIRM THIS ORDER BY SIGNING ON THE SIGNATURE__LINE BELOW AND RETURNING A COPY TO BUYER.__SIGNATURE DATE__THE TOOL ID, PURCHASE ORDER NUMBER, LINE ITEM AND__RELEASE, CRATE/BOX OF WILL BE ON THE PACKING SLIP__ATTACHED TO THE BILL OF LADING AND WRITTEN OR STAMPED__ON EACH CRATE/BOX OR CRATES/BOXES. THE TOOL ID,__PURCHASE ORDER, LINE ITEM AND RELEASE, WILL BE ON EACH__INVOICE TO ENSURE PROMPT AND CORRECT PAYMENT__SHIP VIA:__UVL REPRESENTATIVE AT 800-716-6625 OR__FAX: 602-470-0345__Danzas-AEI REPRESENTATIVE: GREGG TEUNISSEN:(31)(20)316-9754 OR FAX:__(31)(20)316-9898__KWE REPRESENTATIVE ICHIRO FURUSAWA:(81)(3)5443-4510 OR__FAX: (81)(3)5443-4515__SELLER WILL PROVIDE THE CARRIER WITH THE FOLLOWING INFORMATION:__PURCHASE ORDER NUMBER, LINE ITEM NUMBER AND RELEASE__NUMBER, TOOL IDENTIFIER FOR EACH PART NUMBER, TOOL__IDENTIFIER FOR EACH SYSTEM TO BE SHIPPED, DATE AND TIME__THE SYSTEM(S) WILL BE AVAILABLE FOR PICKUP; AND__CONFIRMATION OF THE PIECES, DIMENSIONS AND WEIGHTS TO__BE INCLUDED.__.</FreeFormText>*
*</comments>*
*<FinancingTerms>*
*<GlobalFinanceTermsCode>Bank transfer</GlobalFinanceTermsCode>*
*<PaymentTerms>*
*<GlobalPaymentConditionCode>Acceptance</GlobalPaymentConditionCode>*
*<netTermsDays>*
*<CountableAmount>0</CountableAmount>*
*</netTermsDays>*
*<percentDue>*
*<PercentAmount>20</PercentAmount>*
*</percentDue>*
*</PaymentTerms>*
*</FinancingTerms>*
*<GlobalPurchaseOrderTypeCode>Standard</GlobalPurchaseOrderTypeCode>*
*<isDropShip>*
*<AffirmationIndicator>No</AffirmationIndicator>*
*</isDropShip>*
*<ProductLineItem>*
*<comments>*
*<FreeFormText>.</FreeFormText>*
*</comments>*
*<GlobalProductUnitOfMeasureCode>Each</GlobalProductUnitOfMeasureCode>*
*<isDropShip>*
*<AffirmationIndicator>No</AffirmationIndicator>*
*</isDropShip>*
*<LineNumber>0010</LineNumber>*
*<OrderQuantity>*
*<requestedQuantity>*
*<ProductQuantity>1</ProductQuantity>*
*</requestedQuantity>*
*</OrderQuantity>*
*<OrderShippingInformation>*
*<CarrierInformation>*
*<GlobalCarrierCode>UVLN</GlobalCarrierCode>*
*</CarrierInformation>*
*<GlobalFreeOnBoardCode>Origin</GlobalFreeOnBoardCode>*
*<GlobalShipmentTermsCode>Collect</GlobalShipmentTermsCode>*
*<GlobalShippingServiceLevelCode>Premium Surface</GlobalShippingServiceLevelCode>*
*<SpecialHandlingInstruction>*
*<specialHandlingText>*
*<FreeFormText>Carrier Name : UVL Capital - Fob Text: EXW Amatpos;s Dock</FreeFormText>*
*</specialHandlingText>*
*</SpecialHandlingInstruction>*
*</OrderShippingInformation>*
*<ProductIdentification>*
*<PartnerProductIdentification>*
*<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>*
*<ProprietaryProductIdentifier>DESCRIPTION:PreFac Kit</ProprietaryProductIdentifier>*
*</PartnerProductIdentification>*
*</ProductIdentification>*
*<ProductSubLineItem>*
*<GlobalProductUnitOfMeasureCode>Each</GlobalProductUnitOfMeasureCode>*
*<isDropShip>*
*<AffirmationIndicator>No</AffirmationIndicator>*
*</isDropShip>*
*<OrderQuantity>*
*<requestedQuantity>*
*<ProductQuantity>1</ProductQuantity>*
*</requestedQuantity>*
*</OrderQuantity>*
*<OrderShippingInformation>*
*<CarrierInformation>*
*<GlobalCarrierCode>UVLN</GlobalCarrierCode>*
*</CarrierInformation>*
*<GlobalFreeOnBoardCode>Origin</GlobalFreeOnBoardCode>*
*<GlobalShipmentTermsCode>Collect</GlobalShipmentTermsCode>*
*<GlobalShippingServiceLevelCode>Premium Surface</GlobalShippingServiceLevelCode>*
*<SpecialHandlingInstruction>*
*<specialHandlingText>*
*<FreeFormText>Carrier Name : UVL Capital - Fob Text: EXW Amaapos;s Dock</FreeFormText>*
*</specialHandlingText>*
*</SpecialHandlingInstruction>*
*</OrderShippingInformation>*
*<requestedEvent>*
*<TransportationEvent>*
*<DateStamp>20020311Z</DateStamp>*
*<GlobalTransportEventCode>Dock</GlobalTransportEventCode>*
*</TransportationEvent>*
*</requestedEvent>*
*<shipTo>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>*
*<businessName>*
*<FreeFormText>Intel Corporation</FreeFormText>*
*</businessName>*
*</BusinessDescription>*
*<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>*
*<PhysicalAddress>*
*<addressLine1>*
*<FreeFormText>2501 N.W. 229th</FreeFormText>*
*</addressLine1>*
*<addressLine2>*
*<FreeFormText>Attn: D1C</FreeFormText>*
*</addressLine2>*
*<cityName>*
*<FreeFormText>HILLSBORO</FreeFormText>*
*</cityName>*
*<GlobalCountryCode>US</GlobalCountryCode>*
*<GlobalLocationIdentifier>0478978550D1C</GlobalLocationIdentifier>*
*<regionName>*
*<FreeFormText>OR</FreeFormText>*
*</regionName>*
*</PhysicalAddress>*
*</PartnerDescription>*
*</shipTo>*
*<subLineItem>*
*<LineNumber>1</LineNumber>*
*</subLineItem>*
*</ProductSubLineItem>*
*<requestedEvent>*
*<TransportationEvent>*
*<DateStamp>20020311Z</DateStamp>*
*<GlobalTransportEventCode>Dock</GlobalTransportEventCode>*
*</TransportationEvent>*
*</requestedEvent>*
*<requestedUnitPrice>*
*<FinancialAmount>*
*<GlobalCurrencyCode>USD</GlobalCurrencyCode>*
*<MonetaryAmount>0</MonetaryAmount>*
*</FinancialAmount>*
*</requestedUnitPrice>*
*<shipTo>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>*
*<businessName>*
*<FreeFormText>Intel Corporation</FreeFormText>*
*</businessName>*
*</BusinessDescription>*
*<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>*
*<PhysicalAddress>*
*<addressLine1>*
*<FreeFormText>2501 N.W. 229th</FreeFormText>*
*</addressLine1>*
*<addressLine2>*
*<FreeFormText>Attn: D1C</FreeFormText>*
*</addressLine2>*
*<cityName>*
*<FreeFormText>HILLSBORO</FreeFormText>*
*</cityName>*
*<GlobalCountryCode>US</GlobalCountryCode>*
*<GlobalLocationIdentifier>0478978550D1C</GlobalLocationIdentifier>*
*<regionName>*
*<FreeFormText>OR</FreeFormText>*
*</regionName>*
*</PhysicalAddress>*
*</PartnerDescription>*
*</shipTo>*
*<TaxExemptStatus>*
*<isTaxExempt>*
*<AffirmationIndicator>Yes</AffirmationIndicator>*
*</isTaxExempt>*
*<TaxExemption>*
*<GlobalTaxExemptionCode>Exempt - per State law</GlobalTaxExemptionCode>*
*<taxExemptionCertificationIdentifier>*
*<ProprietaryReferenceIdentifier>Not Available</ProprietaryReferenceIdentifier>*
*</taxExemptionCertificationIdentifier>*
*</TaxExemption>*
*</TaxExemptStatus>*
*</ProductLineItem>*
*<shipTo>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>047897855</GlobalBusinessIdentifier>*
*<businessName>*
*<FreeFormText>Intel Corporation</FreeFormText>*
*</businessName>*
*</BusinessDescription>*
*<GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>*
*</PartnerDescription>*
*</shipTo>*
*</PurchaseOrder>*
*<thisDocumentGenerationDateTime>*
*<DateTimeStamp>20020307T002254.760Z</DateTimeStamp>*
*</thisDocumentGenerationDateTime>*
*<thisDocumentIdentifier>*
*<ProprietaryDocumentIdentifier>pip3a4_po_id1</ProprietaryDocumentIdentifier>*
*</thisDocumentIdentifier>*
*<toRole>*
*<PartnerRoleDescription>*
*<GlobalPartnerRoleClassificationCode>Seller</GlobalPartnerRoleClassificationCode>*
*<PartnerDescription>*
*<BusinessDescription>*
*<GlobalBusinessIdentifier>123456789</GlobalBusinessIdentifier>*
*<GlobalSupplyChainCode>Electronic Components</GlobalSupplyChainCode>*
*</BusinessDescription>*
*<GlobalPartnerClassificationCode>Manufacturer</GlobalPartnerClassificationCode>*
*</PartnerDescription>*
*</PartnerRoleDescription>*
*</toRole>*
*</Pip3A4PurchaseOrderRequest>*
I cant see any junk characters or BOM in my Payload.. -
Document protocol identification error for custom protocol
Hi,
Working for B2B inbound transaction. By using B2B need to transfer file from remote TP location to Host TP location. The file type is non EDI file (FLAT file of type fixed length) .
I am doing given below steps but B2B giving document identification protocol error after file picked for processing.
Document Defination at administration level:
Protocol : Custom
Version : 1.0
DocType : CustomerDoc
DocDef : CustomerDocDef( In these mentioned values as
Identification Type = "Flat"
Identification Start Position = 1,
Identification End Position = 1 ,
Identification Value = 1)
Host Tp set up:
TP Name : Client
EDI INTERCHANGE ID : ClientID
EDI GroupID : ClientID
EDI Interchange ID Qualifier : 01
Listening channel : Client_Deliverychannel
Remote TP setup :
TP Name : Customer
EDI INTERCHANGE ID : CustomerID
EDI GroupID : CustomerID
EDI Interchange ID Qualifier : 02
Document IMPORTED : Custom --> 1.0 --> CustomerDoc --> CustomerDocDef
Listening channel : Customer_Listeningchannel
Agrement for the Remote TP 'customer:'
Document using : Custom --> 1.0 --> CustomerDoc --> CustomerDocDef
TP names using : Customer , Client
Listening channels using : Customer_Listeningchannel, Client_Deliverychannel
Sample Flat File Using:
1 00123451107200600123456780021000021001500049870USD 0000000000
Thanks&Regards,
Sridhar.Rachumallu.
Edited by: user1133742 on Jun 29, 2010 11:54 PM
Edited by: user1133742 on Jun 30, 2010 12:00 AMConfiguration is looking fine. however error says B2B is not able to identify incoming document.
Please paste/send the log in trace:32 mode for further analysis.
Rgds,
Nitesh Jain
[email protected] -
Unable to identify the exchange protocol of the message (sync AS2 MDN)
Hi,
We got the following error:
Description: Unable to identify the exchange protocol of the message
StackTrace:
Error -: AIP-50080: Exchange protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1367)
at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2370)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1813)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1152)
at oracle.tip.adapter.b2b.xmlgwIntg.XMLGWIntegration.raiseOutboundMessage(XMLGWIntegration.java:168)
at oracle.tip.adapter.b2b.xmlgwIntg.Outbound.onMessage(Outbound.java:297)
at oracle.jms.AQjmsListenerWorker.dispatchOneMsg(AQjmsListenerWorker.java:316)
at oracle.jms.AQjmsListenerWorker.run(AQjmsListenerWorker.java:129)
at java.lang.Thread.run(Thread.java:534)
Here is the Wire message (sync MDN)
=======================
Message-ID=<23033756.391232032071968.JavaMail.SYSTEM@INUBITTEST>
Subject=Your ORDERS AS2
[email protected]
Content-Length=1347
MIME-Version=1.0
Server=Apache
Date=Thu, 15 Jan 2009 15:07:52 GMT
Content-Type=multipart/mixed; boundary="----=_Part_53998_23619909.1232032071968"
[email protected]
------=_Part_53998_23619909.1232032071968
Content-Type: text/plain; charset=UTF-8; name=test.txt
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=test.txt
Message-ID: <17080722.371232032071906.JavaMail.SYSTEM@INUBITTEST>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=disposition-notification;
boundary="----=_Part_53997_14786767.1232032071906"
AS2-Version: 1.1
AS2-From: test_AS2
AS2-To: as2me
------=_Part_53997_14786767.1232032071906
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
MDN for Message ID: <33156:4:0:137@as2me>
From: as2me
To: test_AS2
Received on: Thu, 15 Jan 2009 16:07:51 +0100
Status: processed
Comment: This is not a guarantee that the message has
been completely processed or unterstood.
------=_Part_53997_14786767.1232032071906
Content-Type: message/disposition-notification
Content-Transfer-Encoding: 7bit
Reporting-UA: inubit Integration Server
Original-Recipient: rfc822; test_AS2
Final-Recipient: rfc822; test_AS2
Original-Message-ID: <33156:4:0:137@as2me>
Disposition: automatic-action/MDN-sent-automatically; processed
Received-Content-MIC: 5kFOLMXOUurpm6DUTA8IMRj5gcs=, sha1
------=_Part_53997_14786767.1232032071906--
------=_Part_53998_23619909.1232032071968--
============================
The communication with our TP is going well, we are able to send, receive messages over AS2 and send back MDN, but we are not able
to receive their MDN.
Edit:
It seems that after the latest MLR patch, the error changed to [IPT_HttpSendError] HTTP encounters send error :. Premature EOF encounter but the roots seem to lead to the problem with MDN as B2B is sending the message a couple of times now and gives the mentioned EOF error.
Please advise,
Thank you
Edited by: Kamil Zadora on Jan 30, 2009 3:44 AMHi Ramesh,
Yes, agreement uses AS2 IDentifiers. Incoming messages are recognized correctly, and we send back sync MDN that is correctly received by our TP. They also recieve our messages correctly although Oracle B2B does not recognize the MDN from them. I think that this causes that, now after applying the latest MLR patch, B2B tries to send it around 6 times and gives the Unexpected EOF error.
Thank you for your help in advance,
Kind regards, -
Error when using File protocol
Hi,
I have set up ACME (Host) and Vision (TP) to send an xml file using "Custom Document over Generic Exchange". I post a file to the inbound queue using the tutorial shell script. The file shows up in the /tmp/b2b directory that I set up. However, it gets deleted in about a minute.
The transactions shows as completed under "Business Message Status Report" The error report shows: "Document protocol identification error."
The debug log shows the following:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>0A0428AA10EA56E70720000017C970F0</b2bMessageId>
<errorCode>AIP-50083</errorCode>
<errorText>Document protocol identification error</errorText>
<errorDescription>
<![CDATA[Unable to identify the document protocol of the message ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
The ack mode is set to none. Why is the iB2B trying to read the message after writing to the output directory?
Thanks in advance.Hi
This could be due to the fact that you have used the same endpoint for Vision and Acme.
The flow seems to be as follows
- Enqueue message into Queue
- Acme B2B picks up the message, finds the message is for Vision and drops it into the endpoint defined for Vision (endpoint taken from the Delivery Channel created for TP Vision). Till this it seems as expected.
- Acme B2B polls on the endpoint for it to receive the message ( this is endpoint taken from the Delivery Channel created for Host Acme).
- If there is a file in the endpoint directory, it will be picked by Acme B2B.
I feel you have the same endpoint given for both Acme and Vision. Please try the following
- Change the Vision endpoint to /tmp/vision
- If the endpoint had been used as "use exsiting" then even the Acme endpoint would have changed to "/tmp/vision", so please create a new Delivery Channel for Acme and set this endpoint to "/tmp/Acme".
Hope this helps.
Cheers
-Arun -
Getting error using the EMail Transport Protocol
Hi Gurus,
I am using the EMail Transport Protocol (Custom Document over Generic Exchange).
I am able to send the document using this protocol to a exchange server successfully. but when tried to receive the document from exchange server to Oracle B2B. I am getting the below error.
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
at java.lang.Thread.run(Thread.java:534)
As per my knowledge all necessary properties are reaching Oracle B2B. Please go through the b2b.log content below.
2009.05.14 at 13:16:56:994: Thread-20: B2B - (DEBUG)
Protocol = Email
Version = null
Transport Header
SUBJECT:Test Message from SP
ACTION_NAME:CSVProcess
DATE:Thu, 14 May 2009 12:16:46 GMT
CONNECTION:close
TO:[email protected]
CONTENT-TYPE:multipart/mixed; boundary="----=_Part_3_11019994.1242303406228"
MIME-VERSION:1.0
X-MAILER:IPTransport
FROM_PARTY:EmailTP_GI
DOCTYPE_NAME:CSVProcess_DT
DOCTYPE_REVISION:1.0
FROM:EmailTP_GI
MESSAGE-ID:AC18E52A1213F0D9FB9000001629E7B0
RECEIVED:from INBAAMPC00933 ([172.24.229.42]) by vitz.techm.com (IceWarp 9.1.1) with ESMTP id VRE73645 for <[email protected]>; Thu, 14 May 2009 13:16:45 +0100
TO_PARTY:EmailSP_GI
Content-Type:application/b2b; name="Test Message from SP"
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
Sample Email Test1
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) InterfaceListener:onMessage - Invoke inbound callout - null - null
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) InterfaceListenersyncAckEBMSchecking header names
2009.05.14 at 13:16:57:057: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Enter
2009.05.14 at 13:16:57:088: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Exit
2009.05.14 at 13:16:57:088: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:onMessage sendEventtrue
2009.05.14 at 13:16:57:088: Thread-20: B2B - (DEBUG) DBContext commit: Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.05.14 at 13:16:57:104: Thread-19: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processEvents begin transaction
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) DBContext beginTransaction: Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) DBContext beginTransaction: Leave
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Identify Business Protocol
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Do Unpack using the BP specific package class
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:unpack:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:doUnpack:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMessageContent:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processInputStreamOrStringMessage:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processInputStreamOrStringMessage:Content Type = application/b2b; name="Test Message from SP"
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:newMimeBodyPart.getAllHeaders()
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:getting content info
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:setContentTypeInfo:Enter
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:setContentTypeInfo:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:newMimeBodyPart.getContent()
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:check content type(InputStream/String)
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:contentObj instanceof InputStream
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:addMimeBodyPartToMessageInfoString()
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMimeBodyPart:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processInputStreamOrStringMessage:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:processMessageContent:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:doUnpack:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) MimePackaging:unpack:Exit
2009.05.14 at 13:16:57:104: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Number of Components = 1
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {Email}
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromTPoveride = null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromParty = EmailTP_GI tmpFromParty :EmailTP_GI
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromTPName ..GOT FROM CACHE= null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Remote TP Name = null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: Generic Identifier Value: EmailTP_GI
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage toTPoveride = null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Host TP Name = null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromParty = EmailTP_GI
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: null Type: Generic Identifier Value: EmailTP_GI
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: Generic Identifier Value: [email protected]
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage security info NULL
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Exit
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP [email protected]
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Exit
2009.05.14 at 13:16:57:119: Thread-19: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
at java.lang.Thread.run(Thread.java:534)
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50083: Document protocol identification error
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {SUBJECT=Test Message from SP, ACTION_NAME=CSVProcess, DATE=Thu, 14 May 2009 12:16:46 GMT, CONNECTION=close, [email protected], CONTENT-TYPE=multipart/mixed; boundary="----=_Part_3_11019994.1242303406228", MIME-VERSION=1.0, X-MAILER=IPTransport, FROM_PARTY=EmailTP_GI, DOCTYPE_NAME=CSVProcess_DT, DOCTYPE_REVISION=1.0, FROM=EmailTP_GI, MESSAGE-ID=AC18E52A1213F0D9FB9000001629E7B0, RECEIVED=from INBAAMPC00933 ([172.24.229.42]) by vitz.techm.com (IceWarp 9.1.1) with ESMTP id VRE73645 for <[email protected]>; Thu, 14 May 2009 13:16:45 +0100, TO_PARTY=EmailSP_GI, Content-Type=application/b2b; name="Test Message from SP"}
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50083: Document protocol identification error
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum0 not null
2009.05.14 at 13:16:57:119: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2009.05.14 at 13:16:57:135: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2009.05.14 at 13:16:57:151: Thread-20: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.05.14 at 13:16:57:151: Thread-20: B2B - (DEBUG) DBContext commit: Leave
2009.05.14 at 13:16:57:370: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2009.05.14 at 13:16:57:386: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2009.05.14 at 13:16:57:386: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.05.14 at 13:16:57:386: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
2009.05.14 at 13:16:57:386: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value Generic [email protected]
2009.05.14 at 13:16:57:386: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = AC18E52A1213F0D9FB9000001629E7B0
2009.05.14 at 13:16:57:401: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2009.05.14 at 13:16:57:433: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2009.05.14 at 13:16:57:433: Thread-19: B2B - (DEBUG) Engine:notifyApp Enter
2009.05.14 at 13:16:57:433: Thread-19: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>AC18E5411213F0DCB100000013829EB0</b2bMessageId>
<errorCode>AIP-50083</errorCode>
<errorText>Document protocol identification error</errorText>
<errorDescription>
<![CDATA[Machine Info: (INBAAMPC00883)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
at java.lang.Thread.run(Thread.java:534)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) Engine:notifyApp Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-50083: Document protocol identification error
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Exit
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) DBContext commit: Enter
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) DBContext commit: Leave
2009.05.14 at 13:16:57:448: Thread-19: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit
Kindly look into this.
Regards,
VithalHi Nandagopal,
I have configured email idc to send the payload as an attachment. & the attachment I am trying is send is a simple text file. So I am stuck here, how can I check against xPath for the mail :(.
I have copied the sample message below which is there in the SMTP server & ready to be fetched by Oracle B2B. This is how message looks like in the exchange server, before it gets consumed by Oracle B2B.
============================================================
Message-ID: AC18E52A121544A46D4000001629E840
DATE: Mon, 18 May 2009 15:15:02 GMT
From: [email protected]
FROM: EmailTP_GI
To: [email protected]
Subject: Test Message from SP
Mime-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_6_17282414.1242659702625"
X-Mailer: IPTransport
ACTION_NAME: CSVProcess
DOCTYPE_NAME: CSVProcess_DT
FROM_PARTY: EmailTP_GI
DOCTYPE_REVISION: 1.0
TO_PARTY: EmailSP_GI
Connection: close
------=_Part_6_17282414.1242659702625
Content-Type: application/b2b; name="Test Message from SP"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Test Message from SP"
PGRvY3VtZW50IHhzaTpzY2hlbWFMb2NhdGlvbj0iaHR0cDovL0JUZUJvbmQuaHAuY29tIGZpbGU6
L0Q6L3RyYW5zZm9ybWF0aW9uLWVuZ2luZS9yaWNoYXJkL3NjaGVtYTAueHNkIiB4bWxuczp4c2k9
Imh0dHA6Ly93d3cudzMub3JnLzIwMDEvWE1MU2NoZW1hLWluc3RhbmNlIiB4bWxucz0iaHR0cDov
L0JUZUJvbmQuaHAuY29tIj4KCgogICAgPHRyYW5zX2lkPnRyYW5zX2lkMDwvdHJhbnNfaWQ+Cgog
ICAgPGUyZV9pZD5lMmVfaWQwPC9lMmVfaWQ+CgogICAgPG1zZ190c3RhbXA+MjAwNi0wNS0wNFQx
ODoxMzo1MS4wWjwvbXNnX3RzdGFtcD4KCiAgICA8dHJhbnNfdHlwZT5JTkNJREVOVDwvdHJhbnNf
dHlwZT4KCiAgICA8dHJhbnNfc3ViX3R5cGU+Q1JFQVRFPC90cmFuc19zdWJfdHlwZT4KCiAgICA8
c2NfdHlwZT5JTjwvc2NfdHlwZT4KICAgIDxzZW5kZXJfaWQ+c2VuZGVyX2lkMDwvc2VuZGVyX2lk
PgoKICAgIDxzZW5kZXJfdGlja2V0X2lkPnNlbmRlcl90aWNrZXRfaWQwPC9zZW5kZXJfdGlja2V0
X2lkPgogICAgPGRlc3RfaWQ+ZGVzdF9pZDA8L2Rlc3RfaWQ+CiAgICA8ZGVzdF90aWNrZXRfaWQ+
ZGVzdF90aWNrZXRfaWQwPC9kZXN0X3RpY2tldF9pZD4KCiA8YWNrX3N0YXR1cz5hY2s8L2Fja19z
dGF0dXM+CiAgICA8YWNrX21zZz5hY2ttc2c8L2Fja19tc2c+CiAgICA8Y2FsbGVyPgogICAgICAg
IDxzZWFyY2hjb2RlPnNlYXJjaDwvc2VhcmNoY29kZT4KICAgICAgICA8ZW1haWw+YnRzZW50cnlA
YnQuY29tPC9lbWFpbD4KICAgICAgICA8Zmlyc3RfbmFtZT5Tb3VyYXY8L2ZpcnN0X25hbWU+CiAg
ICAgICAgPGxhc3RfbmFtZT5HYW5ndWx5PC9sYXN0X25hbWU+CiAgICAgICAgPHRlbGVwaG9uZT4x
MjM0NTY8L3RlbGVwaG9uZT4KICAgICAgICA8c3RyZWV0MT5TYWx0IExha2UgQ2l0eTwvc3RyZWV0
MT4KICAgICAgICA8c3RyZWV0Mj5Lb2w8L3N0cmVldDI+CiAgICAgICAgPGNpdHk+S29sa2F0YTwv
Y2l0eT4KICAgICAgICA8c3RhdGVfcHJvdmluY2U+V2VzdCBCZW5nYWw8L3N0YXRlX3Byb3ZpbmNl
PgogICAgICAgIDxjb3VudHJ5PkluZGlhPC9jb3VudHJ5PgogICAgICAgIDx6aXBfY29kZT41NjAw
MTY8L3ppcF9jb2RlPgogICAgPC9jYWxsZXI+CgogICAgPHByaW9yaXR5PkhpZ2g8L3ByaW9yaXR5
PgogICAgPGltcGFjdD5EaWFzdHJvdXM8L2ltcGFjdD4KICAgIDxzdGF0dXM+QWN0aXZlPC9zdGF0
dXM+CiAgICA8c3RhdHVzX2NoYW5nZV90c3RhbXA+CiAgICAgICAgMjAwMi0xMC0xMFQxMjowMDow
MC0wNTowMAogICAgPC9zdGF0dXNfY2hhbmdlX3RzdGFtcD4KCgoKCgogICAgPGhwX2lkPmhwX2lk
MDwvaHBfaWQ+CiAgICA8Y2VfaWQ+Y2VfaWQwPC9jZV9pZD4KCgo8ZGVzY3JpcHRpb24+Tm8gY29v
bDwvZGVzY3JpcHRpb24+CiAgICA8aW5mbz5UaGlzIGlzIGNvb2w8L2luZm8+CiAgICA8d29ya2xv
Zz5sb2dnaW5mPC93b3JrbG9nPgogICAgPHdvcmtncm91cD5JbmRlZWQ8L3dvcmtncm91cD4KICAg
IDxjbGFzc2lmaWNhdGlvbj5jbGFzczwvY2xhc3NpZmljYXRpb24+CiAgICA8Y2xvc3VyZV9jb2Rl
PjExMjwvY2xvc3VyZV9jb2RlPgogICAgPGNsb3N1cmVfY29kZV9kZXNjPjEwMDwvY2xvc3VyZV9j
b2RlX2Rlc2M+CiAgICA8c29sdXRpb24+UmVxdWlyZXM8L3NvbHV0aW9uPgoKCjxjb21wbGV0aW9u
X2RhdGU+MjAwMi0xMC0xMFQxMjowMDowMC0wNTowMDwvY29tcGxldGlvbl9kYXRlPgogICAgPGNj
ZD4yMDAyLTEwLTEwVDEyOjAwOjAwLTA1OjAwPC9jY2Q+CiAgICA8Y2NkX2RldGFpbHM+VGVjaE08
L2NjZF9kZXRhaWxzPgoKCgo8Y2k+CiAgICAgICAgPHNlYXJjaGNvZGU+NTYwMDE2PC9zZWFyY2hj
b2RlPgogICAgICAgIDxzdHJlZXQxPjJuZCBDcm9zcyA0dGggTWFpbjwvc3RyZWV0MT4KICAgICAg
ICA8c3RyZWV0Mj5TYWRhbmFuZCBOYWdhcjwvc3RyZWV0Mj4KICAgICAgICA8Y2l0eT5CYW5nYWxv
cmU8L2NpdHk+CiAgICAgICAgPHN0YXRlPkthcm5hdGFrYTwvc3RhdGU+CiAgICAgICAgPHppcGNv
ZGU+NTYwMDE2PC96aXBjb2RlPgogICAgICAgIDxjb3VudHJ5PkluZGlhPC9jb3VudHJ5PgogICAg
ICAgIDxtYWtlPkluZGlhPC9tYWtlPgogICAgICAgIDxtb2RlbD4xOTk2PC9tb2RlbD4KICAgICAg
ICA8c2VyaWFsX25vPjEyMzQ1Njc4OTwvc2VyaWFsX25vPgogICAgICAgIDxhc3NldF9ubz4xMjM0
NTY3ODk8L2Fzc2V0X25vPgogICAgICAgIDxuYW1lMT5Sb2NrPC9uYW1lMT4KICAgICAgICA8bmFt
ZTI+T248L25hbWUyPgogICAgICAgIAogICAgPC9jaT4KCgo8c2VydmljZT5NTEM8L3NlcnZpY2U+
CiAgICA8c2VydmljZV9pbXBhY3RlZD5ZZXM8L3NlcnZpY2VfaW1wYWN0ZWQ+CiAgIDwhLS0gPGNs
b3N1cmVfZGF0ZT4yMDAyLTEwLTEwVDEyOjAwOjAwLTA1OjAwPC9jbG9zdXJlX2RhdGU+IC0tPgog
ICAgPHJlZ19jcmVhdGVkPjIwMDItMTAtMTBUMTI6MDA6MDAtMDU6MDA8L3JlZ19jcmVhdGVkPgog
ICAgPHRhcmdldF9kYXRlPjIwMDItMTAtMTBUMTI6MDA6MDAtMDU6MDA8L3RhcmdldF9kYXRlPgoK
ICAgIDxyZXFfc3RhcnRfdHN0YW1wPjIwMDItMTAtMTBUMTI6MDA6MDAtMDU6MDA8L3JlcV9zdGFy
dF90c3RhbXA+CjxlY2hvPnNpbXBsZTwvZWNobz4KCgoKPC9kb2N1bWVudD4=
------=_Part_6_17282414.1242659702625--
======================================================
Regards,
Vithal -
Hi,
I'm using 11.1.1.5 and been using the ebXML protocol using a custom XML document and I can get it to work without any issue.
I am playing with using the same custom XML document using AS2 as the channel and can communicate with the Trading Partner environment as I am getting a this error:
B2B-50032 B2B exchange protol negative acknowledge received.
On the Trading Partner environment, I am getting this error:
Document protocol identification error.
I checked other threads and they are saying that it might be an invalid document. I know it is valid because it did work in the ebXML channel. Can anybody point me to any sample of setting up AS2 messaging. I followed the same procedure as setting up ebXML but there might be other configurations I missed.
Regards,
RobertDocument protocol identification error.Have you defined identification xpath in the document definition at receiving side? If no then please do so and redeploy the agreement and then retest.
To understand the xpath expression which is used in B2B, please refer section "8.1.1 How to Configure the XPath Expression for a Custom XML Document" at -
http://docs.oracle.com/cd/E28280_01/user.1111/e10229/b2b_documents.htm#CHDEFFEH
Regards,
Anuj -
AS2 Custom DocumentDefinition with Xpath Identification Error
Currently I'm busy with a B2B11g with a AS2 implementation. It's planned to go live tomorrow, but suddenly today incoming messages on the acceptance environment won't be recognized. I've defined several XML based document definitions, with identification expressions like: /*[local-name()="MINFONotificationEnvelope"].
Now when I receive a message, then in the logs I see:
[2012-11-26T17:57:59.750+01:00] [AdminServer] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 9c326e12b49334d0:-57e9224c:13b3d5cace3:-8000-000000000000212c,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: identifyIncomingDocument: Not EDI or HL7
[2012-11-26T17:57:59.750+01:00] [AdminServer] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 9c326e12b49334d0:-57e9224c:13b3d5cace3:-8000-000000000000212c,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] EDIDocumentPlugin: identifyIncomingDocument: Not EDI or HL7. Return
[2012-11-26T17:57:59.750+01:00] [AdminServer] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 9c326e12b49334d0:-57e9224c:13b3d5cace3:-8000-000000000000212c,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] OagDocumentPlugin: identifyIncomingDocument: Enter
[2012-11-26T17:57:59.769+01:00] [AdminServer] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 9c326e12b49334d0:-57e9224c:13b3d5cace3:-8000-000000000000212c,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] OagDocumentPlugin: identifyIncomingDocument: Identification Based on Document
[2012-11-26T17:57:59.772+01:00] [AdminServer] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 9c326e12b49334d0:-57e9224c:13b3d5cace3:-8000-000000000000212c,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] OagDocumentPlugin: identifyIncomingDocument: Exit
[2012-11-26T17:57:59.773+01:00] [AdminServer] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 9c326e12b49334d0:-57e9224c:13b3d5cace3:-8000-000000000000212c,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] UccnetDocumentPlugin: identifyIncomingDocument: Enter
[2012-11-26T17:57:59.773+01:00] [AdminServer] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 9c326e12b49334d0:-57e9224c:13b3d5cace3:-8000-000000000000212c,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] UccnetDocumentPlugin: identifyIncomingDocument: Exiting, failed to id document
[2012-11-26T17:57:59.774+01:00] [AdminServer] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 9c326e12b49334d0:-57e9224c:13b3d5cace3:-8000-000000000000212c,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] CustomDocumentPlugin: identifyIncomingDocument: Enter
[2012-11-26T17:57:59.774+01:00] [AdminServer] [TRACE] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 9c326e12b49334d0:-57e9224c:13b3d5cace3:-8000-000000000000212c,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [SRC_METHOD: synchedLog_J] CustomDocumentPlugin: identifyIncomingDocument: Exiting, failed to identify the document as there is no xpath comfigured for any of the document
[2012-11-26T17:57:59.775+01:00] [AdminServer] [ERROR] [] [oracle.soa.b2b.engine] [tid: [ACTIVE].ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 9c326e12b49334d0:-57e9224c:13b3d5cace3:-8000-000000000000212c,0] [APP: soa-infra] Error -: B2B-50083: Document protocol identification error.[[
Error -: B2B-50083: Document protocol identification error.
at oracle.tip.b2b.engine.Engine.identifyDocument(Engine.java:5062)
at oracle.tip.b2b.engine.Engine.processIncomingMessageImpl(Engine.java:2180)
at oracle.tip.b2b.engine.Engine.processIncomingMessage(Engine.java:1660)
at oracle.tip.b2b.transport.InterfaceListener.onMessage(InterfaceListener.java:328)
at oracle.tip.b2b.transport.basic.TransportServlet.doPost(TransportServlet.java:709)
What draws my attention is the message "Exiting, failed to identify the document as there is no xpath comfigured for any of the document"
Now, we work with PS4 (11.1.1.5). On my local (VirtualBox Image) 11.1.1.5 installation, when I create a new document defnition, I got a poplist to toggle between XML or Flatfile. This changes the tabs below for the identification expression and values.
But on our 11.1.1.5 installations of Cogas I got two different tabs for "XML" and "Flat" without the poplist. It turns out that on my local PS5 (11.1.1.6) VirtualBox image it is the same.
So it looks to me that B2B11g does not see that I have XML-based documentTypes.
Do you have an idea what goes wrong?
Thanks in advance.
MartienMartien,
Can you cross-check if the corresponding agreement(s) is deployed? If no then please deploy the agreements. If yes, then probably your repository has got corrupted and you may try below steps -
1. Export the entire B2B repository
2. Purge the design time metadata
3. Restart the SOA servers
4. Import the repository back
5. Deploy the agreements and run the test again
If it does not work then send your B2B repository export to my id (in my profile)
Regards,
Anuj -
Identify the exchange protocol of the message
Hi,
I have created a business action, a Trading partner and deployed a Agreement for a partner. On the other side, i have a jsp which post message through HTTP protocol.
Whenever i try to post a Message to the B2B through the jsp, the Error status reports page shows me the error as,
"Unable to identify the exchange protocol of the message".
Has anyone faced a similar problem?Hi Nandagopal,
I tried to find the b2b.log, but it was not available in the path, oracle_home\ip\logs\b2b. But there were some error in the log.xml, which i have mentioned below,
AIP-50080: Exchange protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:972)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:1851)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1783)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1741)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:454)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:326)
at java.lang.Thread.run(Thread.java:534)
java.lang.NullPointerException
at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:436)
at oracle.tip.adapter.b2b.msgproc.DbAccess.updateWireBusinessToErrorState(DbAccess.java:4442)
at oracle.tip.adapter.b2b.engine.Engine.handleInboundException(Engine.java:3092)
at oracle.tip.adapter.b2b.engine.Engine.handleExceptionBeforeIncomingTPA(Engine.java:2983)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:973)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:1851)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1783)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1741)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:454)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:326)
at java.lang.Thread.run(Thread.java:534)
AIP-50031: B2B adapter general error: java.lang.NullPointerException
at oracle.tip.adapter.b2b.msgproc.DbAccess.updateWireBusinessToErrorState(DbAccess.java:4495)
at oracle.tip.adapter.b2b.engine.Engine.handleInboundException(Engine.java:3092)
at oracle.tip.adapter.b2b.engine.Engine.handleExceptionBeforeIncomingTPA(Engine.java:2983)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:973)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:1851)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1783)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1741)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:454)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:326)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NullPointerException
at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:436)
at oracle.tip.adapter.b2b.msgproc.DbAccess.updateWireBusinessToErrorState(DbAccess.java:4442)
... 9 more
Wat do i need to do for getting the b2b.log. I cud not find the ui.log also. Can u pls explain? -
I am trading a custom flat file via generic exchange (based on the newest version iDoc. I have a ecs and xsd file created with no issues. I can test etc... using doc editor.
When enabling the trading partner set up I am refering to the correct doc types and xsd.
I have defined the identification values by position (0 to being the first position) and ensured thge value is matching.
Still getting the below exception
Machine Info: (nalinoap01.na.acco.com)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:2619)
Document header is below and I am defingin 0 to 6 as "E1EDK01" =
E1EDK01 PO1000000009158788800000100000001 USD 1.00000 0008 NBthanks for te quick reply. I did restart the app with the deployment active. Still throwing the protocol exception though. Here is the b2b.log
Protocol = FTP
Version = 1.0
Transport Header
filename:Custom_CustomDocType_CustomDocTypeRev.txt
filesize:6152
file_ext:txt
fullpath://wmdev/WEBMETHODS65/EDIfiles/b2bData/Inbound/Dev/Custom_CustomDocType_CustomDocTypeRev.txt
timestamp:1969-12-31T18:00:00.000-06:00
2008.08.08 at 12:38:19:771: Thread-11: BusinessLogicLayer - (DEBUG) New ExecutionContext has been created
2008.08.08 at 12:38:19:771: Thread-11: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2008.08.08 at 12:38:19:771: Thread-11: BusinessLogicLayer - (DEBUG) Recieve a new PersistencyService
2008.08.08 at 12:38:19:829: Thread-11: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Design
2008.08.08 at 12:38:19:829: Thread-11: BusinessLogicLayer - (DEBUG) Push Stack: queryConfiguration
2008.08.08 at 12:38:19:829: Thread-11: BusinessLogicLayer - (DEBUG) Pop Stack: queryConfiguration
2008.08.08 at 12:38:19:830: Thread-11: BusinessLogicLayer - (DEBUG) A new PersistencyService is created
2008.08.08 at 12:38:19:902: Thread-11: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2008.08.08 at 12:38:19:903: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Enter
2008.08.08 at 12:38:19:904: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2008.08.08 at 12:38:19:904: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Leave
2008.08.08 at 12:38:19:905: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS enter
2008.08.08 at 12:38:19:905: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS checking header names
2008.08.08 at 12:38:19:905: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =filename
2008.08.08 at 12:38:19:905: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =filesize
2008.08.08 at 12:38:19:905: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =file_ext
2008.08.08 at 12:38:19:906: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =fullpath
2008.08.08 at 12:38:19:906: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS name =timestamp
2008.08.08 at 12:38:19:906: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:syncAckEBMS exit
2008.08.08 at 12:38:19:925: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Enter
2008.08.08 at 12:38:19:976: Thread-11: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:19:976: Thread-11: BusinessLogicLayer - (DEBUG) Push Stack: createDataStorage
2008.08.08 at 12:38:20:062: Thread-11: BusinessLogicLayer - (DEBUG) Pop Stack: createDataStorage
2008.08.08 at 12:38:20:068: Thread-11: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:20:068: Thread-11: BusinessLogicLayer - (DEBUG) Push Stack: createWireMessage
2008.08.08 at 12:38:20:084: Thread-11: BusinessLogicLayer - (DEBUG) Pop Stack: createWireMessage
2008.08.08 at 12:38:20:084: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Exit
2008.08.08 at 12:38:20:127: Thread-11: B2B - (DEBUG) DBContext commit: Enter
2008.08.08 at 12:38:20:128: Thread-11: B2B - (DEBUG) DBContext commit: Transaction.commit()
2008.08.08 at 12:38:20:129: Thread-11: B2B - (DEBUG) DBContext commit: Leave
2008.08.08 at 12:38:20:140: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
2008.08.08 at 12:38:20:140: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Enter
2008.08.08 at 12:38:20:140: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2008.08.08 at 12:38:20:141: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Leave
2008.08.08 at 12:38:20:141: Thread-10: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2008.08.08 at 12:38:20:141: Thread-10: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Enter
2008.08.08 at 12:38:20:142: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processEvents begin transaction
2008.08.08 at 12:38:20:142: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Enter
2008.08.08 at 12:38:20:142: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Leave
2008.08.08 at 12:38:20:142: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Enter
2008.08.08 at 12:38:20:142: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Enter
2008.08.08 at 12:38:20:142: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Enter
2008.08.08 at 12:38:20:147: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:20:147: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryWireMessage
2008.08.08 at 12:38:20:167: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryWireMessage
2008.08.08 at 12:38:20:167: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Exit
2008.08.08 at 12:38:20:167: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Enter
2008.08.08 at 12:38:20:178: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Exit
2008.08.08 at 12:38:20:178: Thread-10: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Enter
2008.08.08 at 12:38:20:236: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Identify Business Protocol
2008.08.08 at 12:38:20:237: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Do Unpack using the BP specific package class
2008.08.08 at 12:38:20:238: Thread-10: B2B - (DEBUG) MimePackaging:unpack:Enter
2008.08.08 at 12:38:20:240: Thread-10: B2B - (DEBUG) MimePackaging:doUnpack:Enter
2008.08.08 at 12:38:20:243: Thread-10: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Enter
2008.08.08 at 12:38:20:248: Thread-10: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:oracle.tip.adapter.b2b.packaging.Component@76db09
2008.08.08 at 12:38:20:248: Thread-10: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Exit
2008.08.08 at 12:38:20:248: Thread-10: B2B - (DEBUG) MimePackaging:unpack:Exit
2008.08.08 at 12:38:20:248: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
2008.08.08 at 12:38:20:249: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Enter
2008.08.08 at 12:38:20:249: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Number of Components = 1
2008.08.08 at 12:38:20:258: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {FTP}
2008.08.08 at 12:38:20:260: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage filename = Custom_CustomDocType_CustomDocTypeRev.txt
2008.08.08 at 12:38:20:260: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage File TP Host name = Custom
2008.08.08 at 12:38:20:260: Thread-10: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: Custom Type: null Value: null
2008.08.08 at 12:38:20:261: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromParty = Custom
2008.08.08 at 12:38:20:261: Thread-10: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: Custom Type: null Value: null
2008.08.08 at 12:38:20:261: Thread-10: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: null Value: null
2008.08.08 at 12:38:20:261: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage security info NULL
2008.08.08 at 12:38:20:265: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Exit
2008.08.08 at 12:38:20:265: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
2008.08.08 at 12:38:20:265: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP null
2008.08.08 at 12:38:20:266: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
2008.08.08 at 12:38:20:266: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
2008.08.08 at 12:38:20:266: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
2008.08.08 at 12:38:20:266: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
2008.08.08 at 12:38:20:266: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
2008.08.08 at 12:38:20:267: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
2008.08.08 at 12:38:20:268: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:20:268: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryWireMessage
2008.08.08 at 12:38:20:273: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryWireMessage
2008.08.08 at 12:38:20:273: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
2008.08.08 at 12:38:20:285: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
2008.08.08 at 12:38:20:285: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument Enter
2008.08.08 at 12:38:20:394: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
2008.08.08 at 12:38:20:396: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = false
2008.08.08 at 12:38:20:397: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
2008.08.08 at 12:38:20:397: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
2008.08.08 at 12:38:20:397: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@9b688e
2008.08.08 at 12:38:21:432: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument errcode = Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
2008.08.08 at 12:38:21:433: Thread-10: B2B - (ERROR) com.edifecs.shared.jni.JNIException: Execute failed - CECToolsException thrown - HRESULT[650007], description[The data in the file could not be parsed. Please check the file to verify that it is valid and formatted correctly. This error can occur for one of the following reasons: A) The data file may be a Word document or have some other binary format. B) The envelope data may not be formatted properly. If this is an X12 data file, please verify that the ISA segment is the correct size (exactly 106 characters). If this is an EDIFACT data file, it must have either a UNA or begin with UNB. For other standards, verify that the envelope segments conform to the specified rules. C) The segment/record delimiters in the file are incorrect.]
at com.edifecs.shared.jni.xdata.INativeToXData.ExecuteNative(Native Method)
at com.edifecs.shared.jni.xdata.INativeToXData.Execute(Unknown Source)
at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.identifyIncomingDocument(EDIDocumentPlugin.java:344)
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:2600)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1365)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
at java.lang.Thread.run(Thread.java:534)
2008.08.08 at 12:38:21:433: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Enter
2008.08.08 at 12:38:21:711: Thread-10: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:2619)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1365)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
at java.lang.Thread.run(Thread.java:534)
2008.08.08 at 12:38:21:711: Thread-10: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:2619)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1365)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
at java.lang.Thread.run(Thread.java:534)
2008.08.08 at 12:38:21:712: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2008.08.08 at 12:38:21:712: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2008.08.08 at 12:38:21:712: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50083: Document protocol identification error
2008.08.08 at 12:38:21:712: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2008.08.08 at 12:38:21:712: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {filename=Custom_CustomDocType_CustomDocTypeRev.txt, filesize=6152, file_ext=txt, fullpath=//wmdev/WEBMETHODS65/EDIfiles/b2bData/Inbound/Dev/Custom_CustomDocType_CustomDocTypeRev.txt, timestamp=1969-12-31T18:00:00.000-06:00}
2008.08.08 at 12:38:21:712: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2008.08.08 at 12:38:21:713: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2008.08.08 at 12:38:21:713: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50083: Document protocol identification error
2008.08.08 at 12:38:21:713: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2008.08.08 at 12:38:21:713: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2008.08.08 at 12:38:21:713: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2008.08.08 at 12:38:21:714: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum not null
2008.08.08 at 12:38:21:714: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2008.08.08 at 12:38:21:716: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2008.08.08 at 12:38:21:720: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:21:721: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: createDataStorage
2008.08.08 at 12:38:21:767: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: createDataStorage
2008.08.08 at 12:38:21:770: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2008.08.08 at 12:38:21:774: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:21:775: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: updateWireMessage
2008.08.08 at 12:38:21:795: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: updateWireMessage
2008.08.08 at 12:38:21:795: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:21:795: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryBusinessMessage
2008.08.08 at 12:38:21:800: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryBusinessMessage
2008.08.08 at 12:38:21:800: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2008.08.08 at 12:38:21:800: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2008.08.08 at 12:38:21:809: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:21:809: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
2008.08.08 at 12:38:21:812: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
2008.08.08 at 12:38:21:812: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:21:813: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
2008.08.08 at 12:38:21:815: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
2008.08.08 at 12:38:21:826: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
2008.08.08 at 12:38:21:826: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value nullnull
2008.08.08 at 12:38:21:826: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:21:827: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryTradingPartner
2008.08.08 at 12:38:21:829: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryTradingPartner
2008.08.08 at 12:38:21:829: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:21:829: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryTradingPartner
2008.08.08 at 12:38:21:832: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryTradingPartner
2008.08.08 at 12:38:21:832: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:21:832: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryBusinessAction
2008.08.08 at 12:38:21:834: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryBusinessAction
2008.08.08 at 12:38:21:834: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2008.08.08 at 12:38:21:839: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:21:839: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: createBusinessMessage
2008.08.08 at 12:38:22:001: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: createBusinessMessage
2008.08.08 at 12:38:22:002: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2008.08.08 at 12:38:22:004: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:22:004: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2008.08.08 at 12:38:22:010: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2008.08.08 at 12:38:22:010: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2008.08.08 at 12:38:22:010: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2008.08.08 at 12:38:22:010: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2008.08.08 at 12:38:22:018: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = [email protected]01F78B740
2008.08.08 at 12:38:22:018: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2008.08.08 at 12:38:22:018: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2008.08.08 at 12:38:22:018: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: updateWireMessage
2008.08.08 at 12:38:22:021: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: updateWireMessage
2008.08.08 at 12:38:22:022: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2008.08.08 at 12:38:22:022: Thread-10: B2B - (DEBUG) Engine:notifyApp Enter
2008.08.08 at 12:38:22:025: Thread-10: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>AC19115011BA365C399000001F78B730</b2bMessageId>
<errorCode>AIP-50083</errorCode>
<errorText>Document protocol identification error</errorText>
<errorDescription>
<![CDATA[Machine Info: (nalinoap01.na.acco.com)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:2619)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1365)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2030)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1962)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1920)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
at java.lang.Thread.run(Thread.java:534)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception> -
Getting error while testing a outbound file in oracle B2B11g
Hi,
I am trying to configuare a outbound scenario in oracle B2B 11g.
I have created .ecs file and .xsd file and created a document type also and i am using generic file 1.0 as a lintening channel protocol and trying to read the input xml document from a perticular path.
I had setup partner and agreement also. everything is working fine and also file is succesfully polling from the source folder but i am getting error in B2B as :
B2B-50083
Error Description Machine Info: (infva0325) Description: Document protocol identification error.
Error Level ERROR_LEVEL_COLLABORATION
Error Severity ERROR
Error Text Document protocol identification error.
Can anyone guide me how to resolve this error?
I had tried everything but of no use.
Please do reply me with your suggestions.Hi Anuj,
Please find below xml data which will be saved as .txt file for outbound processing. Let me know if there are any changes i have to do. Please let me know if you need any further information. Listening channel is reading the file but in agreement level it is failing.
<?xml version="1.0" encoding="UTF-8"?><Transaction-DESADV XDataVersion="1.0" Standard="EDIFACT" Version="D93A" CreatedBy="ECXEngine_837" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" CreatedDate="2011-12-14T12:59:40" GUID="{2d323135-3336-3630-3232-313938393033}" xmlns="urn:oracle:integration:b2b:099C29D4C4ED419194917C20ADF8ABC3">
<Internal-Properties>
<Data-Structure Name="Interchange">
<Property Name="InterchangeSenderID">senderID</Property>
<Property Name="InterchangeSenderQual">senderQuali</Property>
<Property Name="InterchangeReceiverID">RecieverID</Property>
<Property Name="InterchangeReceiverQual">RecieverQuali</Property>
<Property Name="RepeatingSeparator"/>
<Property Name="InterchangeApplicationRef">DESADV</Property>
<Data-Structure Name="Transaction">
<Property Name="TransactionID">DESADV</Property>
<Property Name="TransactionControllingAgency"/>
<Property Name="TransactionMessageVersionNumber">D</Property>
<Property Name="TransactionMessageReleaseNumber">93A</Property>
<Property Name="TransactionAssociationAssignedCode"/>
</Data-Structure>
</Data-Structure>
</Internal-Properties>
<Segment-UNH>
<Element-0062>#ControlNumber#</Element-0062>
<Composite-S009>
<Element-0065>DESADV</Element-0065>
<Element-0052>D</Element-0052>
<Element-0054>93A</Element-0054>
<Element-0051>UN</Element-0051>
<Element-0057>EDIT30</Element-0057>
</Composite-S009>
</Segment-UNH>
<Segment-BGM>
<Composite-C002>
<Element-1001>351</Element-1001>
</Composite-C002>
<Element-1004>3364382</Element-1004>
</Segment-BGM>
<Segment-DTM>
<Composite-C507>
<Element-2005>137</Element-2005>
<Element-2380>20111214</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
<Loop-Group_2>
<Segment-NAD>
<Element-3035>SH</Element-3035>
<Composite-C082>
<Element-3039>7393142020009</Element-3039>
<Element-1131 xsi:nil="true"/>
<Element-3055>9</Element-3055>
</Composite-C082>
</Segment-NAD>
</Loop-Group_2>
<Loop-Group_2>
<Segment-NAD>
<Element-3035>CN</Element-3035>
<Composite-C082>
<Element-3039>7350056030012</Element-3039>
<Element-1131 xsi:nil="true"/>
<Element-3055>9</Element-3055>
</Composite-C082>
</Segment-NAD>
</Loop-Group_2>
<Loop-Group_10>
<Segment-CPS>
<Element-7164>1</Element-7164>
</Segment-CPS>
<Loop-Group_15>
<Segment-LIN>
<Element-1082>1</Element-1082>
<Element-1229 xsi:nil="true"/>
</Segment-LIN>
<Segment-PIA>
<Element-4347>5</Element-4347>
<Composite-C212_1>
<Element-7140>210587</Element-7140>
<Element-7143>BP</Element-7143>
</Composite-C212_1>
</Segment-PIA>
<Segment-QTY>
<Composite-C186>
<Element-6063>12</Element-6063>
<Element-6060>3</Element-6060>
</Composite-C186>
</Segment-QTY>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>PK</Element-1153>
<Element-1154>1</Element-1154>
</Composite-C506>
</Segment-RFF>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>VN</Element-1153>
<Element-1154>6152310</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>171</Element-2005>
<Element-2380>20111214</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_23>
<Segment-QVA>
<Composite-C279>
<Element-6064>0</Element-6064>
<Element-6063_1>83</Element-6063_1>
</Composite-C279>
<Element-4221>CP</Element-4221>
</Segment-QVA>
</Loop-Group_23>
</Loop-Group_15>
<Loop-Group_15>
<Segment-LIN>
<Element-1082>2</Element-1082>
<Element-1229 xsi:nil="true"/>
</Segment-LIN>
<Segment-PIA>
<Element-4347>5</Element-4347>
<Composite-C212_1>
<Element-7140>210510</Element-7140>
<Element-7143>BP</Element-7143>
</Composite-C212_1>
</Segment-PIA>
<Segment-QTY>
<Composite-C186>
<Element-6063>12</Element-6063>
<Element-6060>3</Element-6060>
</Composite-C186>
</Segment-QTY>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>PK</Element-1153>
<Element-1154>1</Element-1154>
</Composite-C506>
</Segment-RFF>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>VN</Element-1153>
<Element-1154>6152310</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>171</Element-2005>
<Element-2380>20111214</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_23>
<Segment-QVA>
<Composite-C279>
<Element-6064>0</Element-6064>
<Element-6063_1>83</Element-6063_1>
</Composite-C279>
<Element-4221>CP</Element-4221>
</Segment-QVA>
</Loop-Group_23>
</Loop-Group_15>
<Loop-Group_15>
<Segment-LIN>
<Element-1082>3</Element-1082>
<Element-1229 xsi:nil="true"/>
</Segment-LIN>
<Segment-PIA>
<Element-4347>5</Element-4347>
<Composite-C212_1>
<Element-7140>081349</Element-7140>
<Element-7143>BP</Element-7143>
</Composite-C212_1>
</Segment-PIA>
<Segment-QTY>
<Composite-C186>
<Element-6063>12</Element-6063>
<Element-6060>1</Element-6060>
</Composite-C186>
</Segment-QTY>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>PK</Element-1153>
<Element-1154>2</Element-1154>
</Composite-C506>
</Segment-RFF>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>VN</Element-1153>
<Element-1154>6152310</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>171</Element-2005>
<Element-2380>20111214</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>NB</Element-1153>
<Element-1154>JF074</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>21E</Element-2005>
<Element-2380>20160905</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_23>
<Segment-QVA>
<Composite-C279>
<Element-6064>0</Element-6064>
<Element-6063_1>83</Element-6063_1>
</Composite-C279>
<Element-4221>CP</Element-4221>
</Segment-QVA>
</Loop-Group_23>
</Loop-Group_15>
<Loop-Group_15>
<Segment-LIN>
<Element-1082>4</Element-1082>
<Element-1229 xsi:nil="true"/>
</Segment-LIN>
<Segment-PIA>
<Element-4347>5</Element-4347>
<Composite-C212_1>
<Element-7140>051596</Element-7140>
<Element-7143>BP</Element-7143>
</Composite-C212_1>
</Segment-PIA>
<Segment-QTY>
<Composite-C186>
<Element-6063>12</Element-6063>
<Element-6060>1</Element-6060>
</Composite-C186>
</Segment-QTY>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>PK</Element-1153>
<Element-1154>2</Element-1154>
</Composite-C506>
</Segment-RFF>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>VN</Element-1153>
<Element-1154>6152310</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>171</Element-2005>
<Element-2380>20111214</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_16>
<Segment-RFF>
<Composite-C506>
<Element-1153>NB</Element-1153>
<Element-1154>116812505</Element-1154>
</Composite-C506>
</Segment-RFF>
<Segment-DTM>
<Composite-C507>
<Element-2005>21E</Element-2005>
<Element-2380>20150131</Element-2380>
<Element-2379>102</Element-2379>
</Composite-C507>
</Segment-DTM>
</Loop-Group_16>
<Loop-Group_23>
<Segment-QVA>
<Composite-C279>
<Element-6064>0</Element-6064>
<Element-6063_1>83</Element-6063_1>
</Composite-C279>
<Element-4221>CP</Element-4221>
</Segment-QVA>
</Loop-Group_23>
</Loop-Group_15>
</Loop-Group_10>
<Segment-CNT>
<Composite-C270>
<Element-6069>2</Element-6069>
<Element-6066>4</Element-6066>
</Composite-C270>
</Segment-CNT>
<Segment-UNT>
<Element-0074>#SegmentCount#</Element-0074>
<Element-0062>#ControlNumber#</Element-0062>
</Segment-UNT>
</Transaction-DESADV> -
Issue with receiving response from web application
Hi,
I have configured B2B with business protocol as 'Custom document document over Internet', document exchange protocol as AS2-1.1 and transport protocol HTTPS1.1 to invoke a web application deployed in Oracle Application server. B2B is able to invoke the web application with HTTPS request which contains an xml.
I have set the acknowledgment mode as 'Sync' and 'Is acknowledgement handled by B2B' as true. But while receiving the response from web application which is an xml, B2B is showing the error as
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3244)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1665)
at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2382)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1825)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:974)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1166)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
at java.lang.Thread.run(Thread.java:534)
I have added headers as present in the wire message of the request. In B2B, it is showing the wire message for response as follows.
TO_PARTY=XXX
AS2-To=XXX
DOCTYPE_NAME=TestAS2DT
DOCTYPE_REVISION=1.0
Date=Tue, 03 Nov 2009 06:09:22 GMT
AS2-Version=1.1
AS2-From=YYY
Content-Transfer-Encoding=binary
[email protected]
ACTION_NAME=TestAS2_BA
Content-Type=application/xml
Server=Oracle-Application-Server-10g/10.1.3.4.0 Oracle-HTTP-Server
MIME-version=1.0
User-Agent=AS2 Server
FROM_PARTY=YYY
Content-Disposition=attachment; filename=1.0
Connection=Keep-Alive
From=YYY
Keep-Alive=timeout=15, max=100
<?xml version="1.0" encoding="UTF-8"?>
<Books>
<Book>
<BookTitle>Ajax Hacks</BookTitle>
<Author>Bruce W. Perry</Author>
<PubDate>March 2006</PubDate>
</Book>
</Books>
I am able to see the xml sent as response from web application in Payload as follows.
<?xml version="1.0" encoding="UTF-8"?>
<Books>
<Book>
<BookTitle>Ajax Hacks</BookTitle>
<Author>Bruce W. Perry</Author>
<PubDate>March 2006</PubDate>
</Book>
</Books>
I am able to see the HTTP response in b2b_dc_transport.log. In transport log it is not showing any error. Please help me to fix this issue.Hi,
Request and Response should be part of same agreement. I hope you are not confused between Acknowledgement and Response. Acknowledgement can be received in the same session (sync mode) but Response will always come in a different session and will be treated as a different document. If, for request, party A is initiator and B is responder then for response party B will be initiator and party A will be responder (as Requset and Response are two docs in case of Custom Document)
For configuring X-Path, please refer section 8.3.11 Configuring the XPath Expression for a Custom XML Document at below link -
http://download.oracle.com/docs/cd/B14099_19/integrate.1012/b19370/busact_coll.htm#sthref784
Please let us know whether you are trying to receive a response or Ack?
Regards,
Anuj -
Error while sending transaction
Hi All,
We are facing below error while sending transactions,
We are able to send successfully OAGIS file to supplier using custom documnet over internet, but in the reports after couple of sceond it showing one blank error.
EX:
Machine Info: (usstlz-pinfwi11)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2384)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1827)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:976)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1167)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
at java.lang.Thread.run(Thread.java:534)
If I check the payload it showing empty and wire message is below
Date=Tue, 23 Feb 2010 11:59:38 GMT
Server=Microsoft-IIS/6.0
X-Powered-By=ASP.NET
Content-Length=0
We are ableto receiving a MDN back from them.
Could you please tell what we need to set in below for both inbound and outbound transactions
Functional acknowledgement required?
Is acknowledgement handled by Integration B2B?
for custom document over internet...
p[lease help me to resolve this
Regards
cnu
Edited by: B2B_GoToGuY on Feb 23, 2010 4:36 AMAnuj ,
here is the log and i send it ur ID also
Parameters
-- listing properties --
http.sender.timeout=0
2010.02.22 at 10:03:53:844: Thread-20: B2B - (DEBUG) scheme null userName null realm null
2010.02.22 at 10:03:57:590: Thread-20: B2B - (DEBUG)
Protocol = HTTP
Version = HTTP/1.1
Transport Header
Date:Mon, 22 Feb 2010 16:03:57 GMT
X-Powered-By:ASP.NET
Server:Microsoft-IIS/6.0
Content-Length:0
2010.02.22 at 10:03:57:594: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.TransportInterface:send Message Successfully Transmitted
2010.02.22 at 10:03:57:597: Thread-20: B2B - (INFORMATION) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Send Successful!, Request Message sucessfully Transmitted
2010.02.22 at 10:03:57:600: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Calling postTransmit to do post transmit processing of request message
2010.02.22 at 10:03:57:602: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Enter
2010.02.22 at 10:03:57:605: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2010.02.22 at 10:03:57:607: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Leave
2010.02.22 at 10:03:57:610: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:postTransmit Enter
2010.02.22 at 10:03:57:613: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:postTransmit AckMode is SYNC
2010.02.22 at 10:03:57:615: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Enter
2010.02.22 at 10:03:57:657: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Exit
2010.02.22 at 10:03:57:660: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:postTransmit Update the Message Table Row with message state Wait for Incoming Acknowledgment
2010.02.22 at 10:03:57:679: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:postTransmit Commit
2010.02.22 at 10:03:57:683: Thread-20: B2B - (DEBUG) DBContext commit: Enter
2010.02.22 at 10:03:57:690: Thread-20: B2B - (DEBUG) DBContext commit: Transaction.commit()
2010.02.22 at 10:03:57:693: Thread-20: B2B - (DEBUG) DBContext commit: Leave
2010.02.22 at 10:03:57:695: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Enter
2010.02.22 at 10:03:57:697: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2010.02.22 at 10:03:57:699: Thread-20: B2B - (DEBUG) DBContext beginTransaction: Leave
2010.02.22 at 10:03:57:702: Thread-20: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Enter
2010.02.22 at 10:03:57:711: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Identify Business Protocol
2010.02.22 at 10:03:57:713: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:identifyExchange Enter
2010.02.22 at 10:03:57:715: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:identifyExchange Exit
2010.02.22 at 10:03:57:718: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Do Unpack using the BP specific package class
2010.02.22 at 10:03:57:721: Thread-20: B2B - (DEBUG) MimePackaging:unpack:Enter
2010.02.22 at 10:03:57:723: Thread-20: B2B - (DEBUG) MimePackaging:doUnpack:Enter
2010.02.22 at 10:03:57:726: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Enter
2010.02.22 at 10:03:57:728: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:encoding = UTF-8
2010.02.22 at 10:03:57:731: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:oracle.tip.adapter.b2b.packaging.Component@7cb44d
2010.02.22 at 10:03:57:733: Thread-20: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Exit
2010.02.22 at 10:03:57:735: Thread-20: B2B - (DEBUG) MimePackaging:unpack:Exit
2010.02.22 at 10:03:57:738: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
2010.02.22 at 10:03:57:740: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Enter
2010.02.22 at 10:03:57:743: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Number of Components = 1
2010.02.22 at 10:03:57:746: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {HTTP}
2010.02.22 at 10:03:57:749: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage remote host name = null
2010.02.22 at 10:03:57:752: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage host name = null
2010.02.22 at 10:03:57:754: Thread-20: B2B - (DEBUG) calling setInitiatingPartyId() changing from null to TPName: null Type: Generic Identifier Value: 127.0.0.1
2010.02.22 at 10:03:57:757: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage fromParty = 127.0.0.1
2010.02.22 at 10:03:57:760: Thread-20: B2B - (DEBUG) calling setFromPartyId() changing from null to TPName: null Type: Generic Identifier Value: 127.0.0.1
2010.02.22 at 10:03:57:762: Thread-20: B2B - (DEBUG) calling setToPartyId() changing from null to TPName: null Type: Generic Identifier Value: 127.0.0.1
2010.02.22 at 10:03:57:764: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage security info NULL
2010.02.22 at 10:03:57:767: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Exit
2010.02.22 at 10:03:57:770: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Enter
2010.02.22 at 10:03:57:772: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage toTP 127.0.0.1
2010.02.22 at 10:03:57:775: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage hubUrl null
2010.02.22 at 10:03:57:777: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processHubMessage Exit
2010.02.22 at 10:03:57:779: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage ProtocolCollabId = null
2010.02.22 at 10:03:57:781: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage CollaborationName null
2010.02.22 at 10:03:57:784: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Enter
2010.02.22 at 10:03:57:786: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate check non-RosettaNet Message
2010.02.22 at 10:03:57:800: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:checkDuplicate Exit
2010.02.22 at 10:03:57:803: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Protocol Collaboration Id : null
2010.02.22 at 10:03:57:805: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument Enter
2010.02.22 at 10:03:57:893: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:identifyIncomingDocument errcode = SetData failed - CECToolsException thrown - HRESULT[30005], description[The size of blob is wrong: must be greater then zero]
2010.02.22 at 10:03:57:897: Thread-20: B2B - (ERROR) com.edifecs.shared.jni.JNIException: SetData failed - CECToolsException thrown - HRESULT[30005], description[The size of blob is wrong: must be greater then zero]
at com.edifecs.shared.jni.xdata.INativeToXData.SetDataNative(Native Method)
at com.edifecs.shared.jni.xdata.INativeToXData.SetData(Unknown Source)
at com.edifecs.shared.jni.xdata.INativeToXData.SetData(Unknown Source)
at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.identifyIncomingDocument(EDIDocumentPlugin.java:367)
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3226)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2384)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1827)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:976)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1167)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
at java.lang.Thread.run(Thread.java:534)
2010.02.22 at 10:03:57:900: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Enter
2010.02.22 at 10:03:57:956: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2010.02.22 at 10:03:57:958: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2010.02.22 at 10:03:57:961: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
2010.02.22 at 10:03:57:964: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2010.02.22 at 10:03:57:967: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2010.02.22 at 10:03:57:970: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2010.02.22 at 10:03:57:972: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2010.02.22 at 10:03:57:975: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2010.02.22 at 10:03:57:978: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2010.02.22 at 10:03:57:981: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument continuing
2010.02.22 at 10:03:57:983: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument non-XML Payload
2010.02.22 at 10:03:57:986: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument iDoc ECS = null
2010.02.22 at 10:03:57:988: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get start pos
2010.02.22 at 10:03:57:990: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument could not get end pos
2010.02.22 at 10:03:57:993: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:identifyIncomingDocument Exit
2010.02.22 at 10:03:58:000: Thread-20: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2384)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1827)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:976)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1167)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
at java.lang.Thread.run(Thread.java:534)
2010.02.22 at 10:03:58:004: Thread-20: B2B - (ERROR) Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2384)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1827)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:976)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1167)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
at java.lang.Thread.run(Thread.java:534)
2010.02.22 at 10:03:58:006: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2010.02.22 at 10:03:58:009: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2010.02.22 at 10:03:58:011: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-50083: Document protocol identification error
2010.02.22 at 10:03:58:013: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2010.02.22 at 10:03:58:016: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {Date=Mon, 22 Feb 2010 16:03:57 GMT, X-Powered-By=ASP.NET, Server=Microsoft-IIS/6.0, Content-Length=0}
2010.02.22 at 10:03:58:018: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2010.02.22 at 10:03:58:021: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2010.02.22 at 10:03:58:024: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-50083: Document protocol identification error
2010.02.22 at 10:03:58:027: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2010.02.22 at 10:03:58:030: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2010.02.22 at 10:03:58:032: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2010.02.22 at 10:03:58:036: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum0 not null
2010.02.22 at 10:03:58:040: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error information
2010.02.22 at 10:03:58:054: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message protocol message id
2010.02.22 at 10:03:58:061: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message payload storage
2010.02.22 at 10:03:58:087: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new business message
2010.02.22 at 10:03:58:089: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2010.02.22 at 10:03:58:129: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name null
2010.02.22 at 10:03:58:132: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value Generic Identifier127.0.0.1
2010.02.22 at 10:03:58:187: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow BusinessAction for the given name null null
2010.02.22 at 10:03:58:242: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2010.02.22 at 10:03:58:277: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
2010.02.22 at 10:03:58:280: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Native Event Tbl Row
2010.02.22 at 10:03:58:282: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2010.02.22 at 10:03:58:295: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = 0A10482B126F66BB0BC000001BE47920
2010.02.22 at 10:03:58:298: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2010.02.22 at 10:03:58:307: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException notifying App
2010.02.22 at 10:03:58:311: Thread-20: B2B - (DEBUG) Engine:notifyApp Enter
2010.02.22 at 10:03:58:324: Thread-20: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>0A10482B126F66BB08B000001BE47910</b2bMessageId>
<errorCode>AIP-50083</errorCode>
<errorText>Document protocol identification error</errorText>
<errorDescription>
<![CDATA[Machine Info: (usstlz-pinfwi25.dev.emrsn.org)
Description: Unable to identify the document protocol of the message
StackTrace:
Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3245)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1666)
at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2384)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1827)
at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:976)
at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1167)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
at java.lang.Thread.run(Thread.java:534)
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
2010.02.22 at 10:03:58:344: Thread-20: B2B - (DEBUG) Engine:notifyApp Exit
2010.02.22 at 10:03:58:347: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updated the Error Message Successfully: Error -: AIP-50083: Document protocol identification error
2010.02.22 at 10:03:58:350: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Exit
2010.02.22 at 10:03:58:352: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Exit
2010.02.22 at 10:03:58:355: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:postTransmit Exit
2010.02.22 at 10:03:58:358: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequestPostColab Exit
2010.02.22 at 10:03:58:360: Thread-20: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:outgoingRequest Exit
2010.02.22 at 10:03:58:363: Thread-20: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage:
Edited by: B2B_GoToGuY on Feb 23, 2010 4:57 AM
Maybe you are looking for
-
how to add data in xml file from textbox in c# without overwriting???
-
I recently purchased a PC with Windows 7. (I have several other PCs with varying OS' on this home network; mainly Wireless; see below). When adding this to my network I experienced intermittent connectivity issues with ALL PCs; sometimes the Network
-
Hi All, I tried to post goods receipt against a Purchase Order. When i complete all the details as per messages and check the document it says document is OK. When I go to save the document it hives error as " Field text is required for "CoCode" "G/L
-
Update custom field in VA01/VA02 after message V1152
Hi experts, The consultant wants the following issue: Whenever a sales order is saved, if the error V1152 raises, I new field in additional Tab B must be filled. I knwo where this error raises but not how to check this error in user exit SAVE_DOCUMEN
-
Congrats Anji!!!
Congratulations Anji for crossing 10K milestone within no time!! You motivated many of us and set the new trend by contributing around 3500 points for the last 30 days periods!! Keep going!!!