Payload validation Error - Outbound flow
Hi,
I am trying to create an outbound flow to send a X12,4010,810 document to a trading partner.
Got the error - Payload Validation error.
Payload is as below
<?xml version = '1.0' encoding = 'UTF-8'?><Transaction-810 xmlns="http://www.edifecs.com/xdata/200" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="X12" Version="V4010" CreatedDate="2007-04-10T17:16:24" CreatedBy="ECXEngine_837" GUID="{12345678-1234-1234-1234-123456789012}"><Internal-Properties><Data-Structure Name="Interchange"><Lookup Name="InterchangeControlVersion">00401</Lookup><Lookup Name="InterchangeReceiverID">MarketInc</Lookup><Lookup Name="InterchangeReceiverQual">ZZ</Lookup><Lookup Name="InterchangeSenderID">OracleServices</Lookup><Lookup Name="InterchangeSenderQual">ZZ</Lookup><Lookup Name="InterchangeUsageIndicator">I</Lookup><Lookup Name="Standard">X12</Lookup><Property Name="ElementDelimiter">0x7e</Property><Property Name="InterchangeAckRequested">0</Property><Property Name="InterchangeAuthorizationInfo">Authorizat</Property><Property Name="InterchangeAuthorizationInfoQual">00</Property><Property Name="InterchangeChildCount">1</Property><Property Name="InterchangeComponentElementSep">0x5c</Property><Property Name="InterchangeControlNumber">000000001</Property><Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property><Property Name="InterchangeControlVersion">00401</Property><Property Name="InterchangeDate">140313</Property><Property Name="InterchangeReceiverID">MarketInc</Property><Property Name="InterchangeReceiverQual">ZZ</Property><Property Name="InterchangeSecurityInfo">Security I</Property><Property Name="InterchangeSecurityInfoQual">00</Property><Property Name="InterchangeSenderID">OracleServices</Property><Property Name="InterchangeSenderQual">ZZ</Property><Property Name="InterchangeTime">1727</Property><Property Name="InterchangeTrailerControlNumber">000000001</Property><Property Name="InterchangeUsageIndicator">I</Property><Property Name="SegmentDelimiter">0x0d0x0a</Property><Property Name="Standard">X12</Property><Property Name="SubelementDelimiter">0x5c</Property></Data-Structure></Internal-Properties><Segment-ST><Element-143>IN</Element-143><Element-329>0001</Element-329></Segment-ST><Segment-BIG><Element-373>20140313</Element-373><Element-76>I</Element-76></Segment-BIG><Segment-TDS><Element-610>2</Element-610></Segment-TDS><Segment-SE><Element-96>4</Element-96><Element-329>0001</Element-329></Segment-SE></Transaction-810>
Can someone suggest what is the problem with this payload.
More detail --
Below is the message that is displayed in Oracle B2B Reports -> Business Message
Id
7F000001144BE0AB3A100000231A6860
Message Id
11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc
Refer To Message
Refer To Message
Sender Type
Name
Sender Value
OracleServices
Receiver Type
Name
Receiver Value
MarketInc
Sender
OracleServices
Receiver
MarketInc
Agreement Id
OS_MI_X12_4010_810_OutboundInvoiceAgr
Agreement
OS_MI_X12_4010_810_OutboundInvoiceAgr
Document Type
IN
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
OUTBOUND
State
MSG_ERROR
Acknowledgement Mode
NONE
Response Mode
NONE
Send Time Stamp
Mar 13, 2014 7:42 PM
Receive Time Stamp
Mar 13, 2014 7:42 PM
Document Retry Interval(Channel)
0
Document Remaining Retry(Channel)
0
Document Retry Interval(Agreement)
0
Document Remaining Retry(Agreement)
0
Native Message Size
Translated Message Size
2344
Business Action Name
Business Transaction Name
Xpath Name1
XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2
XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3
XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message
Wire Message
Application Message
Application Message
Payload Storage
Payload Storage
Attachment
Attachment
Label
soa_b2b_ - Thu Mar 17 08:30:33 CDT 2014 - 8
Collaboration Id
7F000001144BE0AB37E00000231A6850
Collaboration Name
Collaboration Version
Business Action Name
Exchange Protocol Name
Generic File
Exchange Protocol Version
1.0
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code
B2B-51507
Error Description
Machine Info: (XXXX) Description: Payload validation error.
Error Level
ERROR_LEVEL_COLLABORATION
Error Severity
ERROR
Error Text
Error Brief : XEngine error.
Application Message :
Id7F000001144BE0AB22400000231A6820Sender Id TypeSender ValueOracleServicesReceiver Id TypeReceiver ValueMarketIncDocument TypeINDocument Definition810_DefDocument Protocol NameEDI_X12Document Protocol Version4010Refer To Application Message IdRefer To Application Message IdApp Conversation IdApp Message property{fabric.enterpriseId=-1, b2b.documentProtocolVersion=4010, b2b.documentDefinitionName=810_Def, b2b.messageId=11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc, MESH_METRICS=null, b2b.messageType=1, tracking.parentReferenceId=mediator:954F1AF0AB1111E3BF8A5F99BC4D6B4E:954F6910AB1111E3BF8A5F99BC4D6B4E:oneway, tracking.compositeInstanceId=20012, tracking.ecid=11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfc, b2b.toTradingPartnerId=MarketInc, b2b.fromTradingPartnerId=OracleServices, tracking.compositeInstanceCreatedTime=Thu Mar 13 19:42:55 CDT 2014, tracking.conversationId=snbwNIP3idSWrxOB_9mfQZizjgj_IKJyb-EozcpIyP4., tracking.parentComponentInstanceId=mediator:954F1AF0AB1111E3BF8A5F99BC4D6B4E, b2b.documentTypeName=IN}DirectionOUTBOUNDStateMSG_COMPLETEError CodeError TextError DescriptionCreatedMar 13, 2014 7:42 PMModifiedMar 13, 2014 7:42 PMMessage Size2344PayloadPayloadBusiness MessageBusiness MessageRetry Interval0Reattempt CountRemaining Retry0ECID11d1def534ea1be0:-7e1384fb:144bd539c55:-8000-0000000000007dfcComposite Instance Id20012Parent Composite Instance Idmediator:954F1AF0AB1111E3BF8A5F99BC4D6B4EConversation IdsnbwNIP3idSWrxOB_9mfQZizjgj_IKJyb-EozcpIyP4.Domain NamedefaultComposite NameOSToMIOutboundInvoiceProjectComposite Version1.0Reference NameB2BOSToMarketIncOutboundUrl
Payload Storage :
<?xml version = '1.0' encoding = 'UTF-8'?><Transaction-810 xmlns="http://www.edifecs.com/xdata/200" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="X12" Version="V4010" CreatedDate="2007-04-10T17:16:24" CreatedBy="ECXEngine_837" GUID="{12345678-1234-1234-1234-123456789012}"><Internal-Properties><Data-Structure Name="Interchange"><Lookup Name="InterchangeControlVersion">00401</Lookup><Lookup Name="InterchangeReceiverID">MarketInc</Lookup><Lookup Name="InterchangeReceiverQual">ZZ</Lookup><Lookup Name="InterchangeSenderID">OracleServices</Lookup><Lookup Name="InterchangeSenderQual">ZZ</Lookup><Lookup Name="InterchangeUsageIndicator">I</Lookup><Lookup Name="Standard">X12</Lookup><Property Name="ElementDelimiter">0x7e</Property><Property Name="InterchangeAckRequested">0</Property><Property Name="InterchangeAuthorizationInfo">Authorizat</Property><Property Name="InterchangeAuthorizationInfoQual">00</Property><Property Name="InterchangeChildCount">1</Property><Property Name="InterchangeComponentElementSep">0x5c</Property><Property Name="InterchangeControlNumber">000000001</Property><Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property><Property Name="InterchangeControlVersion">00401</Property><Property Name="InterchangeDate">140313</Property><Property Name="InterchangeReceiverID">MarketInc</Property><Property Name="InterchangeReceiverQual">ZZ</Property><Property Name="InterchangeSecurityInfo">Security I</Property><Property Name="InterchangeSecurityInfoQual">00</Property><Property Name="InterchangeSenderID">OracleServices</Property><Property Name="InterchangeSenderQual">ZZ</Property><Property Name="InterchangeTime">1727</Property><Property Name="InterchangeTrailerControlNumber">000000001</Property><Property Name="InterchangeUsageIndicator">I</Property><Property Name="SegmentDelimiter">0x0d0x0a</Property><Property Name="Standard">X12</Property><Property Name="SubelementDelimiter">0x5c</Property></Data-Structure></Internal-Properties><Segment-ST><Element-143>IN</Element-143><Element-329>0001</Element-329></Segment-ST><Segment-BIG><Element-373>20140313</Element-373><Element-76>I</Element-76></Segment-BIG><Segment-TDS><Element-610>2</Element-610></Segment-TDS><Segment-SE><Element-96>4</Element-96><Element-329>0001</Element-329></Segment-SE></Transaction-810>
I have set the following b2b headers in SOA before sending it to B2B outbound
Constant: 4010_810_Def Property: b2b.documentDefinitionName
Constant: 4010 Property: b2b.documentProtocolVersion
Constant: OracleServices Property: b2b.fromTradingPartnerId
Constant: MarketInc Property: b2b.toTradingPartnerId
Constant: 1 Property: b2b.messageType
Constant: IN Property: b2b.documentTypeName ( I defined my docuemnt with name 'IN')
Property: tracking.ecid Property: b2b.messageId
Similar Messages
-
B2B-51507- Payload validation error - 11.1.1.7 Latest Version
Anuj/Nitesh (B2B Gurus)
I am facing a problem when Posting the message from SOA to B2b (XML->EDI) using the B2b Adapter.
Flow is : Ebusiness->PLSQL->AQ->BPEL->B2B. Once the message is posted to B2b It is throwing the following Error.
But I am passing all the mandatory and Optional Parameters.
Tried the Following Threads, But No luck. I am passing all the Mandatory Parameters.
How to map Internal-Properties in XSLT.
Oracle B2B Payload Validation exception
Scenario - 1 (Success No Errors , Output Does not Contain PO Details)
Disabled the Validate flag in the Partner Agreement for the B2B Document.
Verified the B2b Wired Message, Output got generated but without the PO information I am passing from BPEL.
Scenario - 2 (Error )
Enabled the Validate flag in the Partner Agreement for the B2B Document. The system is generating an error and throwing list of errors.
Error
Id
C064016C14103689486000005559CD14
Message Id
C064016C14103688C7F000005559CD0F
Refer To Message
Refer To Message
Sender Type
Name
Sender Value
ABC
Receiver Type
Name
Receiver Value
TEST123
Sender
ABC
Receiver
TEST123
Agreement Id
EDI_850_tpa_Lt7763342564515893374
Agreement
XXX_EDI_X12_4010_850_Outbound
Document Type
850
Document Protocol
EDI_X12
Document Version
4010
Message Type
REQ
Direction
OUTBOUND
State
MSG_ERROR
Acknowledgement Mode
NONE
Response Mode
NONE
Send Time Stamp
9/9/2013 10:48
Receive Time Stamp
9/9/2013 10:48
Document Retry Interval(Channel)
0
Document Remaining Retry(Channel)
0
Document Retry Interval(Agreement)
0
Document Remaining Retry(Agreement)
0
Native Message Size
Translated Message Size
5471
Business Action Name
Business Transaction Name
Xpath Name1
XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2
XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3
XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message
Wire Message
Application Message
Application Message
Payload Storage
Payload Storage
Attachment
Attachment
Label
soa_b2b_ - Thu Sep 05 11:51:44 CDT 2013 - 4
Collaboration Id
C064016C14103688E1A000005559CD13
Collaboration Name
Collaboration Version
Business Action Name
Exchange Protocol Name
Generic File
Exchange Protocol Version
1
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code
B2B-51507
Error Description
Description: Payload validation error.
Error Level
ERROR_LEVEL_COLLABORATION
Error Severity
ERROR
Error Text
Error Brief : Error reporting limit exceeded. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A functional group code mismatch was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A transaction ID mismatch was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. An X12 syntax error occurred. An X12 syntax error occurred. Validator error - Extra data was encountered. Validator error - Extra data was encountered. A data element with 'Mandatory' status is missing. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered. Validator error - Extra data was encountered.
Error Brief :^M
Error reporting limit exceeded.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
A data element with 'Mandatory' status is missing.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Validator error - Extra data was encountered.^M
Description: Payload validation error., null, null, null, null, C064016C140EF31BFCA000005559CC
A4, null, null, 1258, B2B-51507, null, null, null, null, null, 2013-09-05 12:35:49.092, null, ^M
Error :^M
Analysis halted after 101 error(s) (Limit for Transaction is 100). Large numbers of errors usually indicate that the same error is repeatedly encountered in multiple segments or transactions. Fix the repeating error and resubmit the test to obtain further results.^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 1{br}{tab}Characters: 210 through 212^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 2{br}{tab}Characters: 247 through 257^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 3{br}{tab}Characters: 292 through 294^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 4{br}{tab}Characters: 329 through 339^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 5{br}{tab}Characters: 374 through 376^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 6{br}{tab}Characters: 411 through 426^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 7{br}{tab}Characters: 463 through 465^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 8{br}{tab}Characters: 502 through 517^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 9{br}{tab}Characters: 552 through 558^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 10{br}{tab}Characters: 593 through 597^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 11{br}{tab}Characters: 632 through 633^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 12{br}{tab}Characters: 668 through 673^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 13{br}{tab}Characters: 708 through 717^M
Extra Element was found in the data file as part of Segment ISA. Segment ISA is defined in the guideline at position N/A.{br}{br}This error was detected at:{br}{tab}Segment Count: 1{br}{tab}Element Count: 14{br}{tab}Characters: 752 through 753^M
Thanks
Rao.Issue is resolved by doing the Following Steps.
1. Open the ECS file in the Document Editor, Exclude the ISA, GS segments in the ECS file. Save the File and Upload the Document and Redeploy the Agreement.
2. Export the XSD and refer it in the BPEL process and do the transformation.
Thanks
Nethi. -
B2B-51507 - Payload Validation Error - while creating VDA -4913V3
I created a document definition under Positional Flat file for VDA-> 4913V4. I created ecs file using the Document editor and created the xsd. I used both these files in creating the Document definition. In the document definition, under identification tab, I have these values.
Identification Value -> empty
Identification Start Position -> 0
Identification End Position -> 128
And I created a Partner Agreement using this Document Definition. I created a channel to send the document to GXS Mailbox.
In the agreement if I have both Validate and Translate checked on, I am getting an error which is show in the reports->Business Message.
Error Code B2B-51507
Error Description Machine Info: (RRDV2SOA) Description: Payload validation error.
Error Level ERROR_LEVEL_COLLABORATION
Error Severity ERROR
Error Text Payload validation error.
If I have only Translate checked on, I am not getting any error, but the message that is sent to GXS is zero bytes.
If I leave both Validate and translate unchecked, the xml is sent to GXS but not the native Format.
I took the payload from the business message and validated and it looks correct.
I am using the sample data that is already validated in the B2B Document Editor using Data Analyzer.
Can you help me on this. I am not sure what I am doing wrong. If needed I can send you the ecs, xsd, and B2B partner definition export zip file to your email address.
Here is the logfile for this error.
[2011-04-06T21:00:41.652-07:00] [soa_server1] [TRACE] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@1a33f088] [userId: <anonymous>] [ecid: 0000Iwi7c0MCcpiF_7I7S61DVcAD0051W4,0] [SRC_CLASS: oracle.tip.b2b.system.DiagnosticService] [APP: soa-infra] [dcid: 4e45f5dff566a29f:-335a9823:12eb62ea520:-7ffd-000000000000008c] [SRC_METHOD: synchedLog_J] oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Exit
[2011-04-06T21:00:41.653-07:00] [soa_server1] [ERROR] [] [oracle.soa.b2b.engine] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@1a33f088] [userId: <anonymous>] [ecid: 0000Iwi7c0MCcpiF_7I7S61DVcAD0051W4,0] [APP: soa-infra] [dcid: 4e45f5dff566a29f:-335a9823:12eb62ea520:-7ffd-000000000000008c] Error -: B2B-51507: Payload validation error.: Error -: B2B-51507: Payload validation error.[[
at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:835)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1326)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:837)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1411)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:781)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3319)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2948)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:575)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:798)
... 11 more
Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:798)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1326)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:837)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1411)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:781)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3319)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2948)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:575)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Error -: B2B-51507: Payload validation error.: Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:835)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1326)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:837)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1411)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:781)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3319)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2948)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:575)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:214)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:105)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Caused by: Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.pff.PFFDocumentPlugin.processOutgoingDocument(PFFDocumentPlugin.java:798)
... 11 more
Thank you
Krishna.I selected the option "Save guideline before exporting". I am guessing it is failing on the main element of the xml message because of some namespace issue. I am generating the XML using xsl transformationin BPEL and sending the XML payload to B2B Service.
Is there a way to know what part of the XML is erroring duing the validation on the server. The error message is not helpful even I turned on Trace 32 level.
Any ideas?
Thank you
Krishna -
B2B-51507 Payload validation error
Can someone tell me a what point in the b2b inbound process MDN errors are sent.
I assumed (I know shouldn't assume anything in this game) that with translate and validate on an agreement that an MDN would be sent if translate or validation fails, but this does not seem to be the case. I am using 11G.
JohnI selected the option "Save guideline before exporting". I am guessing it is failing on the main element of the xml message because of some namespace issue. I am generating the XML using xsl transformationin BPEL and sending the XML payload to B2B Service.
Is there a way to know what part of the XML is erroring duing the validation on the server. The error message is not helpful even I turned on Trace 32 level.
Any ideas?
Thank you
Krishna -
Getting Validation Error at B2B Console for 856 Outbound B2B-51507
Hi,
We are getting this error while sending the EDI 856 in an outgoing Process. We are getting the data from Oracle Apps and sending it to B2B via B2b adapter using mediator.
we are using X856 ecx file and X856 xsd.
Can Anyone help in this. If Anyone is having any idea please help us on this.
Do we need to set the Deployment Validation Property to False? If yes then is it in EM we need to Set?
Appreciate quick response.
Below is the error details:
Id 0AF6038D12BE3AE21CF0000011881680
Message Id 0AF6038D12BE3AE1C5E0000011881630
Refer To Message Refer To Message
Sender Type Specialties
Receiver Type Name
Receiver Value XXXX_4010
Sender Sybron Dental Specialties
Receiver :XXXX_4010
Agreement Id:XXXXXXX
Agreement HEN_KRR_AGR
Document Type 856
Document Protocol EDI_X12
Document Version 4010
Message Type REQ
Direction OUTBOUND
State MSG_ERROR
Acknowledgement Mode NONE
Response Mode NONE
Send Time Stamp Monday, October 25, 2010 6:57:41 AM GMT-07:00
Receive Time Stamp Monday, October 25, 2010 6:57:41 AM GMT-07:00
Document Retry Interval 0
Document Remaining Retry 0
Native Message Size
Translated Message Size 3811
Business Action Name
Business Transaction Name
Xpath Name1 XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2 XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3 XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message Wire Message
Application Message Application Message
Payload Storage Payload Storage
Attachment Attachment
Label soa_b2b_ - Fri Oct 22 04:32:37 PDT 2010
Collaboration Id 0AF6038D12BE3AE205B0000011881670
Collabration Name
Collabration Version
Business Action Name
Exchange Protocol Name Generic File
Exchange Protocol Version 1.0
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code B2B-51507
Error Description Machine Info: (org-vmsosoa.sds.sybrondental.com) Description: Payload validation error.
Error Level ERROR_LEVEL_COLLABORATION
Error Severity ERROR
Error Text Error Brief : XEngine error.
This is the Application Message we are getting in Error Details:
Document Type 856
Document Definition 856_DocDefHENK
Document Protocol Name EDI_X12
Document Protocol Version 4010
Refer To Application Message Id Refer To Application Message Id
App Conversation Id
App Message property {tracking.compositeInstanceId=11, b2b.documentProtocolVersion=4010, b2b.toTradingPartnerId=HEN_KRR_4010, tracking.ecid=0000IjZLVsfDCgS5IFc9yf1ChDOY0034Rz, b2b.fromTradingPartnerId=Sybron Dental Specialties, tracking.conversationId=BPEL, tracking.compositeInstanceCreatedTime=Mon Oct 25 06:57:39 PDT 2010, tracking.parentComponentInstanceId=mediator:D4A7EA60E03F11DFBFC66D8172AE9492, MESH_METRICS=null, b2b.documentTypeName=856, tracking.parentReferenceId=mediator:D4A7EA60E03F11DFBFC66D8172AE9492:D4AC5730E03F11DFBFC66D8172AE9492:oneway}
Direction OUTBOUND
State MSG_ERROR
Error Code B2B-51507
Error Text Error Brief : XEngine error.
Error Description Error : Mandatory attribute missing: Standard.
Created Date Monday, October 25, 2010 6:57:40 AM GMT-07:00
Modified Date Monday, October 25, 2010 6:57:41 AM GMT-07:00
Message Size 3811
Payload Payload
Business Message Business Message
Retry Interval 0
Reattempt Count 0
Remaining Retry 0
ECID 0000IjZLVsfDCgS5IFc9yf1ChDOY0034Rz
Composite Instance Id 11
Parent Composite Instance Id mediator:D4A7EA60E03F11DFBFC66D8172AE9492
Conversation Id BPEL
Domain Name default
Composite Name Generate856ASNOutbound
Composite Version 2.0
Reference Name B2B_GetDataHi,
It looks like , Payload is not valid as per the ecs/xsd so B2B is giving Payload validation Error.
If Validation is must then validate the payload against ecs/xsd offline and correct.
or you can turn off validation in Agreement (Validation = false) and redeploy the agreement.
Rgds,
Nitesh Jain -
Oracle B2B Payload Validation exception
Hi,
I'm trying to input EDI and get XML as output, the EDI file gets picked up, a note, these files are all generated in the Document Editor, it's the X12 4010, 850 example. It picks up my EDI and if Translate is turned off, it validates against the ECS file and dumps the EDI file into the output partner's folder. If I turn translate on though, I get a validation error, I did tick save before generating the XSD, no validation errors in document editor. Please advise.... also note that I am doing this on the SOA VM as supplied on the Oracle website.
Id 7F00000113F80756FB800000A2DAF570
Message Id 1
Refer To Message Refer To Message
Sender Type Name
Sender Value MyCompany
Receiver Type Name
Receiver Value TheirCompany
Sender MyCompany
Receiver TheirCompany
Agreement Id New Agreement_0624_0749
Agreement New Agreement_0624_0749
Document Type 850
Document Protocol EDI_X12
Document Version 4010
Message Type REQ
Direction OUTBOUND
State MSG_ERROR
Acknowledgement Mode NONE
Response Mode NONE
Send Time Stamp 06/26/2013 05:29:06 AM
Receive Time Stamp 06/26/2013 05:29:06 AM
Document Retry Interval(Channel) 0
Document Remaining Retry(Channel) 0
Document Retry Interval(Agreement) 0
Document Remaining Retry(Agreement) 0
Native Message Size
Translated Message Size 4260
Business Action Name
Business Transaction Name
Xpath Name1 XPathName1
Xpath Value1
Xpath Expression1
Xpath Name2 XPathName2
Xpath Value2
Xpath Expression2
Xpath Name3 XPathName3
Xpath Value3
Xpath Expression3
Correlation From XPath Name CorrelationFromXPathName
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name CorrelationToXPathName
Correlation To XPath Value
Correlation To XPath Expression
Wire Message Wire Message
Application Message Application Message
Payload Storage Payload Storage
Attachment Attachment
Label soa_b2b_ - Wed Jun 26 01:15:31 PDT 2013 - 2
Collaboration Id 7F00000113F80756AE600000A2DAF560
Collabration Name
Collabration Version
Business Action Name
Exchange Protocol Name Generic File
Exchange Protocol Version 1.0
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code B2B-51507
Error Description Machine Info: (soabpm-vm) Description: Payload validation error.
Error Level ERROR_LEVEL_COLLABORATION
Error Severity ERROR
Error Text Error Brief : XML Parser error.
<Jun 26, 2013 4:09:26 AM PDT> <Error> <oracle.soa.b2b.engine> <BEA-000000> <Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2754)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1622)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1090)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1539)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:801)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3788)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3205)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:677)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:211)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2754)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1622)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1090)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1539)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:801)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3788)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3205)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:677)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:211)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
>
<Jun 26, 2013 5:29:07 AM PDT> <Error> <oracle.soa.b2b.engine> <BEA-000000> <Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2754)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1622)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1090)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1539)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:801)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3788)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3205)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:677)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:211)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
Error -: B2B-51507: Payload validation error.
at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2754)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1622)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:1090)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1539)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:801)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:3788)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:3205)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:677)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:211)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)
at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
>Issue is resolved by doing the Following Steps.
1. Open the ECS file in the Document Editor, Exclude the ISA, GS segments in the ECS file. Save the File and Upload the Document and Redeploy the Agreement.
2. Export the XSD and refer it in the BPEL process and do the transformation.
Thanks
Nethi. -
Payload Validation failing for EBM
Hi,
I have a composite which takes input based on a simple XSD.
Inside the composite the input is mapped to Sales Order EBM and this EBM is sent as input to other composite.
For data validation purpose, I switched on Payload Validation for this composite in Weblogic EM.
The input data validation works fine but it's throwing follwing error while invoking composite which accepts EBM as input.
<fault>
<bpelFault>
<faultType>0</faultType>
<remoteFault>
<part name="summary">
<summary>oracle.fabric.common.FabricInvocationException: Schema validation failed for message part payload. Please ensure at the message sender level that the data sent is schema compliant.</summary>
</part>
<part name="detail">
<detail>Element 'ProcessSalesOrderFulfillment' not expected.</detail>
</part>
<part name="code">
<code>null</code>
</part>
</remoteFault>
</bpelFault>
</fault>
The payload validation error is occuring for all composites which accepts EBM as input. It picks the attribute name just after the header and says element not expected.
Any help is greatly appreciated.
Thanks,
RaviPlease ensure that you have created EBS properly, verify all the datatypes of the elements in input XSD & EBO schema. And also verify whether EBM header is reflecting properly.
One more thing you should able to navigate from EBS to EBM, EBM to EBO then only you can assume you have done all things correctly. If not reconstruct EBS, EBM & EBO with valid request & response messages. -
ORAMED-01304:[Payload schematron validation error]
Hi
I'm trying to do a simple Schematron validation with Oracle Mediator and am receiving the following error: ORAMED-01304:[Payload schematron validation error]
Any tips on how to debug?$
UPDATE: I should add that if I test my composite with xml data that doesn't validate against the xml schema, I get an xsd validation error. only when I pass valid data (valid for the xml schema) does it actually return the schematron validation error.
Edited by: SwC on Apr 10, 2012 9:23 AMI found the reason.
I was missing the namespace declaration
<sch:ns uri="{your namespace}" prefix="{your prefix}" />
and the prefix for the context and test attribute elements. -
Hi All,
I need some clarification on receiving the 997/FA for the Validation error that happens at the remote trading partner.
Will the 997 payload contain the details of the error in it??
How will B2B interpret the FA as positive FA or negative FA?
In my case the payload which I am sending is getting validation error at receiving side, they are sending me the FA. But in my side, both the initial transaction and the ack transaction goes to MSG_Completed state. Is it a normal behavior?
Thanks in advance.
Regards,
MonicaHi,
1. The 997 has fields which will tell if the EDI transactions has SNIP errors. In your case, the outbound EDI should goto MSG_ERROR.
2. In a 999 transaction, the fields such as AK9, IK4, IK5 will tell the problem in the EDI, I am sure 997 should also have something like that. -
Validator error - Extra data was encountered.
Hi All,
I am working on Outbound EDI870, getting below Error:
2010.06.03 at 04:33:34:988: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (ERROR) Error -: B2B-51505: General validation error.
at oracle.tip.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2539)
at oracle.tip.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1279)
at oracle.tip.b2b.msgproc.Request.outgoingRequest(Request.java:790)
at oracle.tip.b2b.engine.Engine.processOutgoingMessageImpl(Engine.java:1201)
at oracle.tip.b2b.engine.Engine.processOutgoingMessage(Engine.java:713)
at oracle.tip.b2b.engine.Engine.handleMessageEvent(Engine.java:2754)
at oracle.tip.b2b.engine.Engine.processEvents(Engine.java:2444)
at oracle.tip.b2b.engine.ThreadWorkExecutor.processEvent(ThreadWorkExecutor.java:464)
at oracle.tip.b2b.engine.ThreadWorkExecutor.run(ThreadWorkExecutor.java:180)
at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:77)
at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:171)
at java.lang.Thread.run(Thread.java:619)
2010.06.03 at 04:33:34:988: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) Engine: processOutgoingMessageImpl: B2BDomainException
2010.06.03 at 04:33:34:988: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.engine.Engine:handleOutboundException Updating Error Message: Error -: B2B-51505: General validation error.
2010.06.03 at 04:33:34:988: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) DbAccess:updateWireBusinessToErrorState
2010.06.03 at 04:33:34:988: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2010.06.03 at 04:33:34:989: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Enter
2010.06.03 at 04:33:34:989: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Got RTP Context
2010.06.03 at 04:33:35:006: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Got 1messages for field messageId with value 1410017
2010.06.03 at 04:33:35:007: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Exit
2010.06.03 at 04:33:35:007: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: findWireMessageByB2BMessageId: querying for id = 1410017
2010.06.03 at 04:33:35:007: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: findWireMessageByB2BMessageId: Returning null
2010.06.03 at 04:33:35:007: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message not found.
2010.06.03 at 04:33:35:008: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
2010.06.03 at 04:33:35:008: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Enter:
2010.06.03 at 04:33:35:008: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Got RTP Context
2010.06.03 at 04:33:35:008: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Exit
2010.06.03 at 04:33:35:009: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateAppMessageState Enter
2010.06.03 at 04:33:35:009: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: getAppMessageById: Enter appMsg id = 7F000001128FCF1A4C600000EA6A8D00
2010.06.03 at 04:33:35:009: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: getAppMessageById: Got RTP Context
2010.06.03 at 04:33:35:012: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: getAppMessageById: Got [1] messages for AppMessage ID 7F000001128FCF1A4C600000EA6A8D00
2010.06.03 at 04:33:35:012: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: getAppMessageById: Exit
2010.06.03 at 04:33:35:013: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:setAppMsgErrorInfo Enter
2010.06.03 at 04:33:35:013: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:setAppMsgErrorInfo Setting AppMessage to ERROR
2010.06.03 at 04:33:35:013: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:setAppMsgErrorInfo Exitr
2010.06.03 at 04:33:35:013: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Enter:
2010.06.03 at 04:33:35:013: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Got RTP Context
2010.06.03 at 04:33:35:014: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Exit
2010.06.03 at 04:33:35:014: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateAppMessageState Exit
2010.06.03 at 04:33:35:014: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Enter
2010.06.03 at 04:33:35:015: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Enter:
2010.06.03 at 04:33:35:015: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Got RTP Context
2010.06.03 at 04:33:35:016: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: updateObject: Exit
2010.06.03 at 04:33:35:016: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
2010.06.03 at 04:33:35:016: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.engine.Engine:handleOutboundException Updating Native Event Tbl Row
2010.06.03 at 04:33:35:016: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:updateNativeEvtTblRow Enter
2010.06.03 at 04:33:35:017: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Enter
2010.06.03 at 04:33:35:017: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Got RTP Context
2010.06.03 at 04:33:35:019: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Got 1messages for field messageId with value 1410017
2010.06.03 at 04:33:35:019: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: queryById: Exit
2010.06.03 at 04:33:35:019: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: findWireMessageByB2BMessageId: querying for id = 1410017
2010.06.03 at 04:33:35:019: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.ToplinkHelper: findWireMessageByB2BMessageId: Returning null
2010.06.03 at 04:33:35:019: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) DbAccess:updateNativeEvtTblRowGot WireMessage with B2BMessage ID 1410017
2010.06.03 at 04:33:35:020: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg wiremsg not found
2010.06.03 at 04:33:35:020: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) oracle.tip.b2b.engine.Engine:handleOutboundException notifying App
2010.06.03 at 04:33:35:020: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) Notification: notifyApp: Enter
2010.06.03 at 04:33:35:020: oracle.integration.platform.blocks.executor.WorkManagerExecutor$1@8f1195: B2B - (DEBUG) Notification: notifyApp: payload = <Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>7F000001128FCF1A4C600000EA6A8D00</correlationId>
<b2bMessageId>1410017</b2bMessageId>
<errorCode>B2B-51505</errorCode>
<errorText>
Error Brief :
Validator error - Extra data was encountered.
An X12 syntax error occurred.
An X12 syntax error occurred.
Validator error - Extra data was encountered.
Validator error - Extra data was encountered.
A data element with 'Mandatory' status is missing.
</errorText>
<errorDescription>
<![CDATA[
Error :
Extra Element was found in the data file as part of Segment REF. Segment REF is defined in the guideline at position 046.{br}{br}This error was detected at:{br}{tab}Segment Count: 3{br}{tab}Element Count: 2{br}{tab}Characters: 567 through 575
At least one of REF02, REF03 must be present. The syntax rule R0203 of Segment REF is violated. Segment REF is defined in the guideline at position 046.{br}{br}This error was detected at:{br}{tab}Segment Count: 3{br}{tab}Element Count: 2{br}{tab}Characters: 593 through 593
At least one of REF02, REF03 must be present. The syntax rule R0203 of Segment REF is violated. Segment REF is defined in the guideline at position 046.{br}{br}This error was detected at:{br}{tab}Segment Count: 3{br}{tab}Element Count: 3{br}{tab}Characters: 593 through 593
Extra Element was found in the data file as part of Segment ISR. Segment ISR is defined in the guideline at position 030.{br}{br}This error was detected at:{br}{tab}Segment Count: 6{br}{tab}Element Count: 1{br}{tab}Characters: 870 through 872
Extra Element was found in the data file as part of Segment ISR. Segment ISR is defined in the guideline at position 030.{br}{br}This error was detected at:{br}{tab}Segment Count: 6{br}{tab}Element Count: 2{br}{tab}Characters: 907 through 915
Element ISR01 (Shipment/Order Status Code) is missing. This Element's standard option is 'Mandatory'. Segment ISR is defined in the guideline at position 030.{br}{br}This Element was expected in:{br}{tab}Segment Count: 6{br}{tab}Element Count: 1{br}{tab}Character: 933
]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
Even though I am providing REF01 and ISR01 values, I am getting this Error.
Below is my XML payload.
<?xml version="1.0" encoding="UTF-8" ?>
- <Transaction-870 xmlns:ns0="http://www.edifecs.com/xdata/200" Standard="X12" xmlns="http://www.edifecs.com/xdata/200">
- <ns0:Segment-ST>
<ns0:Element-143>870</ns0:Element-143>
<ns0:Element-329>000000043</ns0:Element-329>
</ns0:Segment-ST>
- <ns0:Segment-BSR>
<ns0:Element-850>3</ns0:Element-850>
<ns0:Element-847>PA</ns0:Element-847>
<ns0:Element-127>3110000031OTM_TestPR</ns0:Element-127>
<ns0:Element-373>20100603</ns0:Element-373>
</ns0:Segment-BSR>
- <ns0:Loop-REF>
- <ns0:Segment-REF>
<ns0:Element-128>VR</ns0:Element-128>
<ns0:Element-127>RHEEM002</ns0:Element-127>
</ns0:Segment-REF>
</ns0:Loop-REF>
- <ns0:Loop-HL>
- <ns0:Segment-HL>
<ns0:Element-628>1</ns0:Element-628>
<ns0:Element-735>O</ns0:Element-735>
</ns0:Segment-HL>
- <ns0:Segment-PRF>
<ns0:Element-324>OTM_Test</ns0:Element-324>
</ns0:Segment-PRF>
- <ns0:Loop-ISR>
- <ns0:Segment-ISR>
<ns0:Element-368>PR</ns0:Element-368>
<ns0:Element-373>20100531</ns0:Element-373>
</ns0:Segment-ISR>
</ns0:Loop-ISR>
</ns0:Loop-HL>
- <ns0:Loop-HL>
- <ns0:Segment-HL>
<ns0:Element-628>2</ns0:Element-628>
<ns0:Element-735>I</ns0:Element-735>
</ns0:Segment-HL>
- <ns0:Loop-PO1>
- <ns0:Segment-PO1>
<ns0:Element-350>1</ns0:Element-350>
<ns0:Element-330>2</ns0:Element-330>
<ns0:Element-355>EA</ns0:Element-355>
<ns0:Element-235>SK</ns0:Element-235>
<ns0:Element-234>6836003</ns0:Element-234>
<ns0:Element-235_1>VP</ns0:Element-235_1>
<ns0:Element-234_1>TAHM ITEM</ns0:Element-234_1>
</ns0:Segment-PO1>
- <ns0:Segment-PID>
<ns0:Element-349>F</ns0:Element-349>
<ns0:Element-352>TAHM ITEM</ns0:Element-352>
</ns0:Segment-PID>
</ns0:Loop-PO1>
</ns0:Loop-HL>
- <ns0:Segment-CTT>
<ns0:Element-354>2</ns0:Element-354>
</ns0:Segment-CTT>
- <ns0:Segment-SE>
<ns0:Element-96>11</ns0:Element-96>
<ns0:Element-329>000000043</ns0:Element-329>
</ns0:Segment-SE>
</Transaction-870>
Thanks in Advance
RavdeepHi Ravdeep,
Have you validated the payload against the ecs using document editor? If no, please do so.
Also refer -
5084: XEngine error - Invalid data (outbound with validation disabled)
Please paste the complete B2B log here/mail it to my id (in my profile)
Regards,
Anuj -
Weblogic app server wsdl web service call with SSL Validation error = 16
Weblogic app server wsdl web service call with SSL Validation error = 16
I need to make wsdl web service call in my weblogic app server. The web service is provided by a 3rd party vendor. I keep getting error
Cannot complete the certificate chain: No trusted cert found
Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure
Validation error = 16
From the SSL debug log, I can see 3 verisign hierarchy certs are correctly loaded (see 3 lines in the log message starting with “adding as trusted cert”). But somehow after first handshake, I got error “Cannot complete the certificate chain: No trusted cert found”.
Here is how I load trustStore and keyStore in my java program:
System.setProperty("javax.net.ssl.trustStore",”cacerts”);
System.setProperty("javax.net.ssl.trustStorePassword", trustKeyPasswd);
System.setProperty("javax.net.ssl.trustStoreType","JKS");
System.setProperty("javax.net.ssl.keyStoreType","JKS");
System.setProperty("javax.net.ssl.keyStore", keyStoreName);
System.setProperty("javax.net.ssl.keyStorePassword",clientCertPwd); System.setProperty("com.sun.xml.ws.transport.http.client.HttpTransportPipe.dump","true");
Here is how I create cacerts using verisign hierarchy certs (in this order)
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignClass3G5PCA3Root.txt -alias "Verisign Class3 G5P CA3 Root"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediatePrimary.txt -alias "Verisign C3 G5 Intermediate Primary"
1.6.0_29/jre/bin/keytool -import -trustcacerts -keystore cacerts -storepass changeit -file VerisignC3G5IntermediateSecondary.txt -alias "Verisign C3 G5 Intermediate Secondary"
Because my program is a weblogic app server, when I start the program, I have java command line options set as:
-Dweblogic.security.SSL.trustedCAKeyStore=SSLTrust.jks
-Dweblogic.security.SSL.ignoreHostnameVerification=true
-Dweblogic.security.SSL.enforceConstraints=strong
That SSLTrust.jks is the trust certificate from our web server which sits on a different box. In our config.xml file, we also refer to the SSLTrust.jks file when we bring up the weblogic app server.
In addition, we have working logic to use some other wsdl web services from the same vendor on the same SOAP server. In the working web service call flows, we use clientgen to create client stub, and use SSLContext and WLSSLAdapter to load trustStore and keyStore, and then bind the SSLContext and WLSSLAdapter objects to the webSerive client object and make the webservie call. For the new wsdl file, I am told to use wsimport to create client stub. In the client code created, I don’t see any way that I can bind SSLContext and WLSSLAdapter objects to the client object, so I have to load certs by settting system pramaters. Here I attached the the wsdl file.
I have read many articles. It seems as long as I can install the verisign certs correctly to web logic server, I should have fixed the problem. Now the questions are:
1. Do I create “cacerts” the correct order with right keeltool options?
2. Since command line option “-Dweblogic.security.SSL.trustedCAKeyStore” is used for web server jks certificate, will that cause any problem for me?
3. Is it possible to use wsimport to generate client stub that I can bind SSLContext and WLSSLAdapter objects to it?
4. Do I need to put the “cacerts” to some specific weblogic directory?
---------------------------------wsdl file
<wsdl:definitions name="TokenServices" targetNamespace="http://tempuri.org/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:tns="http://tempuri.org/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/08/addressing/policy" xmlns:wsaw="http://www.w3.org/2006/05/addressing/wsdl" xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract" xmlns:wsa10="http://www.w3.org/2005/08/addressing" xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex" xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata">
<wsp:Policy wsu:Id="TokenServices_policy">
<wsp:ExactlyOne>
<wsp:All>
<sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:TransportToken>
<wsp:Policy>
<sp:HttpsToken RequireClientCertificate="true"/>
</wsp:Policy>
</sp:TransportToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic256/>
</wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp:Policy>
<sp:Strict/>
</wsp:Policy>
</sp:Layout>
</wsp:Policy>
</sp:TransportBinding>
<wsaw:UsingAddressing/>
</wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>
<wsdl:types>
<xsd:schema targetNamespace="http://tempuri.org/Imports">
<xsd:import schemaLocation="xsd0.xsd" namespace="http://tempuri.org/"/>
<xsd:import schemaLocation="xsd1.xsd" namespace="http://schemas.microsoft.com/2003/10/Serialization/"/>
</xsd:schema>
</wsdl:types>
<wsdl:message name="ITokenServices_GetUserToken_InputMessage">
<wsdl:part name="parameters" element="tns:GetUserToken"/>
</wsdl:message>
<wsdl:message name="ITokenServices_GetUserToken_OutputMessage">
<wsdl:part name="parameters" element="tns:GetUserTokenResponse"/>
</wsdl:message>
<wsdl:message name="ITokenServices_GetSSOUserToken_InputMessage">
<wsdl:part name="parameters" element="tns:GetSSOUserToken"/>
</wsdl:message>
<wsdl:message name="ITokenServices_GetSSOUserToken_OutputMessage">
<wsdl:part name="parameters" element="tns:GetSSOUserTokenResponse"/>
</wsdl:message>
<wsdl:portType name="ITokenServices">
<wsdl:operation name="GetUserToken">
<wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetUserToken" message="tns:ITokenServices_GetUserToken_InputMessage"/>
<wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetUserTokenResponse" message="tns:ITokenServices_GetUserToken_OutputMessage"/>
</wsdl:operation>
<wsdl:operation name="GetSSOUserToken">
<wsdl:input wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserToken" message="tns:ITokenServices_GetSSOUserToken_InputMessage"/>
<wsdl:output wsaw:Action="http://tempuri.org/ITokenServices/GetSSOUserTokenResponse" message="tns:ITokenServices_GetSSOUserToken_OutputMessage"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="TokenServices" type="tns:ITokenServices">
<wsp:PolicyReference URI="#TokenServices_policy"/>
<soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="GetUserToken">
<soap12:operation soapAction="http://tempuri.org/ITokenServices/GetUserToken" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="GetSSOUserToken">
<soap12:operation soapAction="http://tempuri.org/ITokenServices/GetSSOUserToken" style="document"/>
<wsdl:input>
<soap12:body use="literal"/>
</wsdl:input>
<wsdl:output>
<soap12:body use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="TokenServices">
<wsdl:port name="TokenServices" binding="tns:TokenServices">
<soap12:address location="https://ws-eq.demo.i-deal.com/PhxEquity/TokenServices.svc"/>
<wsa10:EndpointReference>
<wsa10:Address>https://ws-eq.demo.xxx.com/PhxEquity/TokenServices.svc</wsa10:Address>
</wsa10:EndpointReference>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
----------------------------------application log
adding as trusted cert:
Subject: CN=VeriSign Class 3 International Server CA - G3, OU=Terms of use at https://www.verisign.com/rpa (c)10, OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x641be820ce020813f32d4d2d95d67e67
Valid from Sun Feb 07 19:00:00 EST 2010 until Fri Feb 07 18:59:59 EST 2020
adding as trusted cert:
Subject: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x3c9131cb1ff6d01b0e9ab8d044bf12be
Valid from Sun Jan 28 19:00:00 EST 1996 until Wed Aug 02 19:59:59 EDT 2028
adding as trusted cert:
Subject: CN=VeriSign Class 3 Public Primary Certification Authority - G5, OU="(c) 2006 VeriSign, Inc. - For authorized use only", OU=VeriSign Trust Network, O="VeriSign, Inc.", C=US
Issuer: OU=Class 3 Public Primary Certification Authority, O="VeriSign, Inc.", C=US
Algorithm: RSA; Serial number: 0x250ce8e030612e9f2b89f7054d7cf8fd
Valid from Tue Nov 07 19:00:00 EST 2006 until Sun Nov 07 18:59:59 EST 2021
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Cipher: SunPKCS11-Solaris version 1.6 for algorithm DESede/CBC/NoPadding>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Will use default Cipher for algorithm DESede>
<Mar 7, 2013 6:59:21 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RSA/ECB/NoPadding>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSetup: loading trusted CA certificates>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 28395435>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <25779276 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - xx.xxx.xxx.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
at javax.xml.ws.Service.<init>(Service.java:56)
at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 6457753>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.removeContext(ctx): 22803607>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Filtering JSSE SSLSocket>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLIOContextTable.addContext(ctx): 14640403>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLSocket will be Muxing>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 115>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 SSL3/TLS MAC>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <23376797 received HANDSHAKE>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHello>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Cannot complete the certificate chain: No trusted cert found>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 0 in the chain: Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validating certificate 1 in the chain: Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[0] = Serial number: 2400410601231772600606506698552332774
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Subject:C=US, ST=New York, L=New York, O=xxx LLC, OU=GTIG, CN=ws-eq.demo.xxx.com
Not Valid Before:Tue Dec 18 19:00:00 EST 2012
Not Valid After:Wed Jan 07 18:59:59 EST 2015
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> < cert[1] = Serial number: 133067699711757643302127248541276864103
Issuer:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=(c) 2006 VeriSign, Inc. - For authorized use only, CN=VeriSign Class 3 Public Primary Certification Authority - G5
Subject:C=US, O=VeriSign, Inc., OU=VeriSign Trust Network, OU=Terms of use at https://www.verisign.com/rpa (c)10, CN=VeriSign Class 3 International Server CA - G3
Not Valid Before:Sun Feb 07 19:00:00 EST 2010
Not Valid After:Fri Feb 07 18:59:59 EST 2020
Signature Algorithm:SHA1withRSA
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 16>
<Mar 7, 2013 6:59:22 PM EST> <Warning> <Security> <BEA-090477> <Certificate chain received from ws-eq.demo.xxx.com - 12.29.210.156 was not trusted causing SSL handshake failure.>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is untrusted>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 16>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <Trust status (16): CERT_CHAIN_UNTRUSTED>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 42
java.lang.Exception: New alert stack
at com.certicom.tls.record.alert.Alert.<init>(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.handshake.ClientStateReceivedServerHello.handle(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessage(Unknown Source)
at com.certicom.tls.record.handshake.HandshakeHandler.handleHandshakeMessages(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.interpretContent(Unknown Source)
at com.certicom.tls.record.MessageInterpreter.decryptMessage(Unknown Source)
at com.certicom.tls.record.ReadHandler.processRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.WriteHandler.write(Unknown Source)
at com.certicom.io.OutputSSLIOStreamWrapper.write(Unknown Source)
at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123)
at java.io.FilterOutputStream.flush(FilterOutputStream.java:123)
at weblogic.net.http.HttpURLConnection.writeRequests(HttpURLConnection.java:154)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:358)
at weblogic.net.http.SOAPHttpsURLConnection.getInputStream(SOAPHttpsURLConnection.java:37)
at weblogic.wsee.util.is.InputSourceUtil.loadURL(InputSourceUtil.java:100)
at weblogic.wsee.util.dom.DOMParser.getWebLogicDocumentImpl(DOMParser.java:118)
at weblogic.wsee.util.dom.DOMParser.getDocument(DOMParser.java:65)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:311)
at weblogic.wsee.wsdl.WsdlReader.getDocument(WsdlReader.java:305)
at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:296)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:77)
at weblogic.wsee.jaxws.spi.WLSProvider.createServiceDelegate(WLSProvider.java:62)
at javax.xml.ws.Service.<init>(Service.java:56)
at ideal.ws2j.eqtoken.TokenServices.<init>(TokenServices.java:64)
at com.citi.ilrouter.util.IpreoEQSSOClient.invokeRpcPortalToken(IpreoEQSSOClient.java:165)
at com.citi.ilrouter.servlets.T3LinkServlet.doPost(T3LinkServlet.java:168)
at com.citi.ilrouter.servlets.T3LinkServlet.doGet(T3LinkServlet.java:206)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(Unknown Source)
at weblogic.servlet.internal.WebAppServletContext.execute(Unknown Source)
at weblogic.servlet.internal.ServletRequestImpl.run(Unknown Source)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <write ALERT, offset = 0, length = 2>
<Mar 7, 2013 6:59:22 PM EST> <Debug> <SecuritySSL> <BEA-000000> <close(): 16189141>I received a workaround by an internal message.
The how to guide is :
-Download the wsdl file (with bindings, not the one from ESR)
-Correct it in order that the schema corresponds to the answer (remove minOccurs or other things like this)
-Deploy the wsdl file on you a server (java web project for exemple). you can deploy on your local
-Create a new logicial destination that point to the wsdl file modified
-Change the metadata destination in your web dynpro project for the corresponding model and keep the execution desitnation as before.
Then the received data is check by the metadata logical destination but the data is retrieved from the correct server. -
AIP-51505: General Validation Error - SFTP transport - validation disabled
Configuration :
internal DC with SFTP
external DC with SFTP (via proxy)
Business Protocol Custom Document over Generic Exchange
MLR 12? (patch 8703404)
3 environments have the same tip.properties
2 environments pick up and send all files successfully.
I cannot see a difference between the deployments that is causing the validation error.
[also in all three B2B's are an ebXML and AS2 trading partner configuration]
The 3rd generates validation errors for all files (14) in the b2b.log and sends some (1-7).
Note that the sent ones change, if a failed one is retried in the source directory, sometimes it is sent successfully.
In the failing/validating deployment there is no validation for (cut and pasted from UI screens) :
Document Protocol Revision Details = Translation Enabled False Validation Enabled False
Document Types (Document Definition Details for each document def) = Is Translation Enabled False Is Validation Enabled False
tip.properties (environment where error occurs) :
#valid valudes for DiagnosticLevel:
#DEBUG, INFORMATION, WARNING, ERROR, FATAL.
#default logging level
oracle.tip.DiagnosticLevel = ERROR
#default component log level for B2B Engine
b2b.oracle.tip.DiagnosticLevel = ERROR
# following logging properties to be set back to false after resolving Sequence 98
# oracle.tip.adapter.b2b.logPayload = true
# oracle.tip.adapter.b2b.packaging.logDecryptMessage = true
b2b.oracle.tip.DiagnosticLevel.Repository = ERROR
b2b.oracle.tip.DiagnosticLevel.BusinessLogicLayer
b2b.oracle.tip.DiagnosticLevel.B2B
b2b.oracle.tip.DiagnosticLevel.ModelValidation
b2b.oracle.tip.DiagnosticLevel.ValidationRule
b2b.oracle.tip.DiagnosticLevel.TechStack
b2b.oracle.tip.DiagnosticLevel.Deployment
b2b.oracle.tip.DiagnosticLevel.Reports
b2b.oracle.tip.DiagnosticLevel.UI
#default component level logging for UI
ui.oracle.tip.DiagnosticLevel = ERROR
#specify component log leel to override default;
ui.oracle.tip.DiagnosticLevel.Repository = ERROR
ui.oracle.tip.DiagnosticLevel.BusinessLogicLayer
ui.oracle.tip.DiagnosticLevel.B2B
ui.oracle.tip.DiagnosticLevel.ModelValidation
ui.oracle.tip.DiagnosticLevel.ValidationRule
ui.oracle.tip.DiagnosticLevel.TechStack
ui.oracle.tip.DiagnosticLevel.Deployment
ui.oracle.tip.DiagnosticLevel.Reports
ui.oracle.tip.DiagnosticLevel.UI
oracle.tip.adapter.b2b.encoding=UTF-8
# Diagnostic Service defaults
oracle.core.ojdl.OrganizationId = oracle.com
oracle.core.ojdl.ComponentId = tip
oracle.core.ojdl.HostingClientId = beta
oracle.core.ojdl.BufferSize = 100000
oracle.core.ojdl.FlushInterval = 5000
# Specific diagnostic settings
oracle.tip.LogDirectory = /space/sw/oracle/products/ias/b2b/ip/log
oracle.tip.LogMaxSegmentSize = 10000000
oracle.tip.LogType = text
# option to save old log when rebounding the service
oracle.tip.LogSave = true
# B2B Info
oracle.tip.adapter.b2b.NumOfWFListeners = 1
oracle.tip.adapter.b2b.NumOfIPListeners = 1
oracle.tip.adapter.b2b.WFAgentName = OUTAGENT
oracle.tip.adapter.b2b.RMIPort = 5111
oracle.tip.adapter.b2b.RMIInstance = IP
#oracle.tip.adapter.b2b.WalletLocation = file:/etc/ORACLE/WALLETS/oracle/ora_wallet.txt
oracle.tip.adapter.b2b.ContinueValidationOnError = true
oracle.tip.adapter.b2b.MultipleIdentifications=false
oracle.tip.adapter.b2b.allTPInOneDirectory=true
oracle.tip.adapter.b2b.DocumentRouting=false
#oracle.tip.adapter.b2b.edi.identifyFromTP = Interchange | Group | Exchange
#oracle.tip.adapter.b2b.transportTrace = /space/sw/oracle/products/ias/b2b/ip/log/transport.trc
#oracle.tip.adapter.b2b.edi.ignoreValidation=InterchangeReceiverID,InterchangeSenderID,GroupReceiverID,GroupSenderID,GroupSenderQual,GroupReceiverQual,InterchangeSenderQual,InterchangeReceiverQual
#report Certificate validation as ERROR or WARNING; default value is ERROR
#oracle.tip.adapter.b2b.tpa.validateCertificate= ERROR | WARNING
#oracle.tip.adapter.b2b.document.NoValidation = inbound | outbound
# HTTP Proxy Host and Proxy Port
oracle.tip.adapter.b2b.ProxyHost =
oracle.tip.adapter.b2b.ProxyPort =
# MaxCachedSessions is set to 0 means no ExecutionContext
# is stored in HTTP session (IP cache is empty).Line below overwrites default
# value equals to 5 when 5 concurrent users could store context in their sessions
# By commenting that line you might turn IP cache on.
oracle.tip.ui.MaxCachedSessions = 0
# Suppression of Validation Warnings
oracle.tip.buslogic.validation.SuppressWarnings=false
# Callout directory
oracle.tip.callout.directory=%s_calloutDirectory%
# persistence directory
oracle.tip.runtime.persistence.dirName=%s_persistenceDir%
# enable ONS reverse ping
enableONS=true
# Optional property which user can set to specify saved report encoding e.g. UTF-8, UTF-16LE etc
# By default this property is not set, in this case the saved report csv file
# will be generated by using the native encoding
# Users can set this parameter to change the encoding of the generated saved report csv file
#savedReportEncoding=UTF-8
# Please don't modify the following properties
# Connection Info
username=%s_intgDBUser%
password=%s_intgDBPasswd%
#connect=jdbc:oracle:thin:@%s_intgDBHost%:%s_intgDBPort%:%s_intgDBSid%
drivertype = thin
tnsentry = inst1
host = %s_intgDBHost%
port = %s_intgDBPort%
sid = %s_intgDBSid%
oracle.tip.connection.useRepositoryAPI=on
oracle.tip.connection.oraclehome=/space/sw/oracle/products/ias/b2b
# property specific to Deployment
oracle.tip.deploy.workflow_username=%s_wfUsername%
oracle.tip.deploy.workflow_passwd=%s_wfPasswd%
oracle.tip.deploy.workflow_tnsname=%s_wfTnsname%
# UI user authorization
authorization = true
# encryption key used for securing secrets in the schema.
oracle.tip.security.key=Be8ejb7yOX3rSefEr5pxBl49WLc0Iej9VeI8jykdjRfv
##oracle.tip.adapter.b2b.WalletLocation = /sw/oracle/products/ias/b2b/Apache/Apache/conf/ssl.wlt/default/b2bwallet
#oracle.tip.adapter.b2b.WalletLocation = /sw/oracle/products/ias/101202/ib/Apache/Apache/conf/ssl.wlt/default/b2bwallet
oracle.tip.adapter.b2b.WalletLocation =file:/sw/oracle/products/ias/b2b/Apache/Apache/conf/ssl.wlt/default/b2bwallet/ewallet.txt
# performance best practices
oracle.tip.adapter.b2b.sleepTimeout=1
oracle.tip.repos.RowSize=100
oracle.tip.adapter.b2b.receiveTimeout=1
oracle.tip.adapter.b2b.TPACache=true
The b2b.log from the failing environment has some lines not seen in the other two environments (the lines referring to MimePackaging:unpack) :
2010.04.29 at 19:07:14:295: Thread-11: B2B - (DEBUG)
Protocol = SFTP
Version = 2.0
Transport Header
filename:SA_ENVSTATUSES.txt
filesize:1
file_ext:.txt
filename_format:%TO_PARTY%_%DOCTYPE_NAME%_%TIMESTAMP%.txt
fullpath:/mnt/maximage_prd/sa_transfer/SA_ENVSTATUSES.txt
timestamp:Thu Jan 15 09:29:53 PST 1970
2010.04.29 at 19:07:14:295: Thread-11: BusinessLogicLayer - (DEBUG) New ExecutionContext has been created
2010.04.29 at 19:07:14:296: Thread-11: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2010.04.29 at 19:07:14:296: Thread-11: BusinessLogicLayer - (DEBUG) Recieve a new PersistencyService
2010.04.29 at 19:07:14:299: Thread-11: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Design
2010.04.29 at 19:07:14:300: Thread-11: BusinessLogicLayer - (DEBUG) Push Stack: queryConfiguration
2010.04.29 at 19:07:14:300: Thread-11: BusinessLogicLayer - (DEBUG) Pop Stack: queryConfiguration
2010.04.29 at 19:07:14:300: Thread-11: BusinessLogicLayer - (DEBUG) A new PersistencyService is created
2010.04.29 at 19:07:14:340: Thread-11: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Enter
2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) DBContext beginTransaction: Leave
2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) InterfaceListener:onMessage - Invoke inbound callout - null - null
2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) InterfaceListenersyncAckEBMSchecking header names
2010.04.29 at 19:07:14:341: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Enter
2010.04.29 at 19:07:14:342: Thread-11: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2010.04.29 at 19:07:14:343: Thread-11: BusinessLogicLayer - (DEBUG) Push Stack: createDataStorage
2010.04.29 at 19:07:14:345: Thread-11: BusinessLogicLayer - (DEBUG) Pop Stack: createDataStorage
2010.04.29 at 19:07:14:346: Thread-11: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2010.04.29 at 19:07:14:346: Thread-11: BusinessLogicLayer - (DEBUG) Push Stack: createWireMessage
2010.04.29 at 19:07:14:348: Thread-11: BusinessLogicLayer - (DEBUG) Pop Stack: createWireMessage
2010.04.29 at 19:07:14:348: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertNativeEvtTblRow(2 params) Exit
2010.04.29 at 19:07:14:348: Thread-11: B2B - (DEBUG) oracle.tip.adapter.b2b.transport.InterfaceListener:onMessage sendEventtrue
2010.04.29 at 19:07:14:359: Thread-11: B2B - (DEBUG) DBContext commit: Enter
2010.04.29 at 19:07:14:362: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Enter
2010.04.29 at 19:07:14:362: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Enter
2010.04.29 at 19:07:14:362: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Transaction.begin()
2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Leave
2010.04.29 at 19:07:14:363: Thread-10: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2010.04.29 at 19:07:14:363: Thread-10: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processEvents Enter
2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processEvents begin transaction
2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Enter
2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) DBContext beginTransaction: Leave
2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleMessageEvent Enter
2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:incomingContinueProcess Enter
2010.04.29 at 19:07:14:363: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Enter
2010.04.29 at 19:07:14:364: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2010.04.29 at 19:07:14:364: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryWireMessage
2010.04.29 at 19:07:14:364: Thread-11: B2B - (DEBUG) DBContext commit: Transaction.commit()
2010.04.29 at 19:07:14:364: Thread-11: B2B - (DEBUG) DBContext commit: Leave
2010.04.29 at 19:07:14:365: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryWireMessage
2010.04.29 at 19:07:14:365: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:getWireMessage Exit
2010.04.29 at 19:07:14:366: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Enter
2010.04.29 at 19:07:14:367: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:formTransportMessage Exit
2010.04.29 at 19:07:14:367: Thread-10: B2B - (INFORMATION) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Enter
2010.04.29 at 19:07:14:369: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Identify Business Protocol
2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:identifyExchange Enter
2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.as2.AS2ExchangePlugin:AS2ExchangePlugin:identifyExchange Exit
2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:identifyExchange Enter
2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.ebms.EBMSExchangePlugin:identifyExchange SOAPAction is [null]
2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Do Unpack using the BP specific package class
2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) MimePackaging:unpack:Enter
2010.04.29 at 19:07:14:370: Thread-10: B2B - (DEBUG) MimePackaging:doUnpack:Enter
2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Enter
2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:encoding = UTF-8
2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:oracle.tip.adapter.b2b.packaging.Component@391da0
2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) MimePackaging:unpackNonMimeMessage:Exit
2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) MimePackaging:unpack:Exit
2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Decode the Incoming Message into B2B Message
2010.04.29 at 19:07:14:371: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Enter
2010.04.29 at 19:07:14:372: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:GenericExchangePlugin:decodeIncomingMessage Number of Components = 1
2010.04.29 at 19:07:14:372: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {SFTP}
2010.04.29 at 19:07:14:372: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage filename = SA_ENVSTATUSES.txt
2010.04.29 at 19:07:14:372: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = TO_PARTY - SA
2010.04.29 at 19:07:14:372: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = DOCTYPE_NAME - ENVSTATUSES
2010.04.29 at 19:07:14:373: Thread-10: B2B - (ERROR) Error -: AIP-51505: General Validation Error
at oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin.decodeIncomingMessage(GenericExchangePlugin.java:408)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1477)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2576)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2446)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2401)
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)
2010.04.29 at 19:07:14:373: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleExceptionBeforeIncomingTPA Enter
2010.04.29 at 19:07:14:373: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Enter
2010.04.29 at 19:07:14:373: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException Error message is Error -: AIP-51505: General Validation Error
2010.04.29 at 19:07:14:373: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired Enter
2010.04.29 at 19:07:14:373: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired {filename=SA_ENVSTATUSES.txt, filesize=1, file_ext=.txt, filename_format=%TO_PARTY%_%DOCTYPE_NAME%_%TIMESTAMP%.txt, fullpath=/mnt/maximage_prd/sa_transfer/SA_ENVSTATUSES.txt, timestamp=Thu Jan 15 09:29:53 PST 1970}
2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: isFARequired returning false
2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: handleInboundException FA not required
2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleInboundException Updating Error Message: Error -: AIP-51505: General Validation Error
2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message found
2010.04.29 at 19:07:14:374: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Creating new b2berror object
2010.04.29 at 19:07:14:375: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState enum0 not null
2010.04.29 at 19:07:14:375: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating wire message error informationThank you for the suggestion, unfortunately, I cannot get it to work.
I've updated the IDC transport server to 3 different filename_formats, and tried the corresponding files, with correct names to match the filename_format.
After updating the IDC I validated the trading partner (host).
I then updated the agreement using the updated IDC, and validated the agreement.
I then validated the host again.
Then I created a new deployment.
And still received the error.
I then deleted the old IDC and created a new IDC and new agreement and new deployment, trying 3 different "Internal delivery channel filename format" values (updating and validating the agreement and host trading partner each time).
And still received the error.
No matter what I set EITHER the IDC "filename format" OR "Internal delivery channel filename format", the b2b.log always reports :
filename_format = %TO_PARTY%_%DOCTYPE_NAME%_%TIMESTAMP%.txt
e.g.
2010.05.16 at 18:05:02:758: Thread-15: B2B - (DEBUG)
Protocol = SFTP
Version = 2.0
Transport Header
filename:SA_DRUGS_10.txt
filesize:1
file_ext:.txt
filename_format:%TO_PARTY%_%DOCTYPE_NAME%_%TIMESTAMP%.txt
fullpath:/mnt/maximage_prd/sa_transfer/SA_DRUGS_10.txt
timestamp:Thu Jan 15 09:54:18 PST 1970
When I try a file with a revision number, e.g. SA_DRUGS_10.txt the log shows :
2010.05.16 at 18:05:03:602: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = TO_PARTY - SA
2010.05.16 at 18:05:03:603: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = DOCTYPE_NAME - DRUGS
2010.05.16 at 18:05:03:603: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = TIMESTAMP - 10
2010.05.16 at 18:05:03:895: Thread-14: B2B - (ERROR) Error -: AIP-51505: General Validation Error
which makes sense as "10" is not a timestamp.
If I exclude the revision, using SA_DRUGS.txt the log shows :
2010.05.16 at 18:27:03:543: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage Transport Protocol = {SFTP}
2010.05.16 at 18:27:03:544: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage filename = SA_DRUGS.txt
2010.05.16 at 18:27:03:544: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = TO_PARTY - SA
2010.05.16 at 18:27:03:544: Thread-14: B2B - (DEBUG) oracle.tip.adapter.b2b.exchange.generic.GenericExchangePlugin:decodeIncomingMessage FILE_FORMAT = DOCTYPE_NAME - DRUGS
2010.05.16 at 18:27:03:545: Thread-14: B2B - (ERROR) Error -: AIP-51505: General Validation Error
So, the timestamp gets ignored (as there is no "_" delimiter), but it still fails, probably because there is no timestamp in the filename.
So, why won't the UI correctly set the IDC filename_format or Internal filename_format ? -
Bdoc validation error- BP replication CRM to R/3
Hi,
We are trying to replicate BP from CRM to R/3 after creating the BP with all required fields excluding sales area with classification Customer the BP flows to R/3 but on checking in Smw01 a bdoc is found in error state with the following errors:
1)No central data for partner DEA725E5C30D4CF1A1C8005056B92270/4000000079 in the required database activity U
2)Business Partner 4000000079 is Currently Being Processed
3)Validation error occurred: Module CRM_BUPA_MAIN_VAL, BDoc type BUPA_MAIN.
on reprocessing the same bdoc it shows confirmed (fully processed)
Please let me know why this error occurs an dhow it can be resolved.
Regards
PrathibaHi Prathiba,
I assume your BP is replicated to R/3 here, when its trying to send the confirmation from ECC to CRM, this BDOC is failing. This fail is due to one small GUI setting in BP transaction.
Check and Maintain Below setting.
1. In CRM, go to transaction BP.
2. From the main screen, go to the menu bar at the top of the screen and select Extras u2013 Setting.
3. When the window below displays under the heading u201CType of Processing for Business Partneru201D select "Display". I assume your user had "Change" or "Setting Last Selected."
Regards,
PBP. -
BPM Problem: Schema validation error notification
Hello all,
When a schema validation error takes place upon receiving XML messages via HTTP, is there something that can be set up in BPM to notify data owners? (either alert or email)
Regards,
SteveBhavesh,
<i>When you mean source schema validation, does it imply that you want to validate your Source XML before graphical mapping to make sure it meets the Source XML Schema?</i>
validate my Source XML
<i>As you pointed out you are usinga BPM, you can wrap the Transfromation step with a Exception handling block, so when there is a mismatch of Source schema and ite actual message the exception handler will be invoked and in the exception handler you can trigger alerts using the control step.</i>
I'm using an outbound interface (outside BPM) to call the abstract interface (very first step in BPM), and there's a tranformation step after that.
-If the Source schema is wrong, will the error take place at the outbound interface or at the transformation step? If outside at the outbound interface, i wouldn't be able to wrap anything around it.
-Exception handling block means the BLOCK step?
Regards,
Steve -
Can SOA 11g fault policy handle XSD Validation errors from the Mediator?
I would like all errors in my SOA process to go through the fault-policies.xml. But I don't seem to be able to catch any mediator error caused by an XSD validation failure. A sample of the sort of error I am trying to 'catch' is:
Nonrecoverable System Fault oracle.tip.mediator.infra.exception.MediatorException: ORAMED-01303:[Payload default schema validation error]XSD schema validation fails with error Invalid text 'A' in element: 'TermCode'Possible Fix:Fix payload and resubmit.
My fault-policies.xml file is as follows:
<?xml version="1.0" encoding="UTF-8" ?>
<faultPolicies xmlns="http://schemas.oracle.com/bpel/faultpolicy">
<faultPolicy version="2.0.1"
id="NewStudentRegistrationFaults"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:1303">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:rjm="http://schemas.oracle.com/sca/rejectedmessages" name="rjm:GetNewStudentRegistrationFile">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:TYPE_ALL">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:mediatorException">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:bindingFault">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
<faultName xmlns:bpelx="http://schemas.oracle.com/bpel/extension" name="bpelx:remoteFault">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="java-fault-handler">
<javaAction className="edu.villanova.soa.handlers.FaultNotificationHandler"
defaultAction="ora-human-intervention" propertySet="faultNotificationProps">
<returnValue value="OK" ref="ora-human-intervention"/>
</javaAction>
</Action>
<!-- Human Intervention -->
<Action id="ora-human-intervention">
<humanIntervention/>
</Action>
<!-- Terminate -->
<Action id="ora-terminate">
<abort/>
</Action>
</Actions>
<!-- Property sets used by custom Java actions -->
<Properties>
<!-- Property set for FaultNotificationHandler customer java action -->
<propertySet name="faultNotificationProps">
<property name="from">[email protected]</property>
<property name="to">[email protected]</property>
<property name="subject">Reporting a SOA fault</property>
</propertySet>
</Properties>
</faultPolicy>
<faultPolicy version="2.0.1"
id="MediatorFaults"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Conditions>
<faultName xmlns:medns="http://schemas.oracle.com/mediator/faults" name="medns:1303">
<condition>
<action ref="java-fault-handler"/>
</condition>
</faultName>
</Conditions>
<Actions>
<Action id="java-fault-handler">
<javaAction className="edu.villanova.soa.handlers.FaultNotificationHandler"
defaultAction="ora-human-intervention" propertySet="faultNotificationProps">
<returnValue value="OK" ref="ora-human-intervention"/>
</javaAction>
</Action>
<!-- Human Intervention -->
<Action id="ora-human-intervention">
<humanIntervention/>
</Action>
<!-- Terminate -->
<Action id="ora-terminate">
<abort/>
</Action>
</Actions>
<!-- Property sets used by custom Java actions -->
<Properties>
<!-- Property set for FaultNotificationHandler customer java action -->
<propertySet name="faultNotificationProps">
<property name="from">[email protected]</property>
<property name="to">[email protected]</property>
<property name="subject">Reporting a SOA rejected msg. fault</property>
</propertySet>
</Properties>
</faultPolicy>
</faultPolicies>
My fault-bindings.xml file is as follows:
<?xml version="1.0" encoding="UTF-8" ?>
<faultPolicyBindings version="2.0.1"
xmlns="http://schemas.oracle.com/bpel/faultpolicy"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<composite faultPolicy="NewStudentRegistrationFaults"/>
<component faultPolicy="MediatorFaults">
<name>NewStudentRegistrationMediator</name>
</component>
<service faultPolicy="NewStudentRegistrationFaults">
<name>GetNewStudentRegistrationFile</name>
</service>
</faultPolicyBindings>
You'll notice that I've tried a number of ways (and various other combinations) to try to steer the error above into my Java fault handler but nothing has meet with success. The mplan is as follows:
<?xml version = '1.0' encoding = 'UTF-8'?>
<!--Generated by Oracle SOA Modeler version 1.0 at [2/3/10 1:21 PM].-->
<Mediator name="NewStudentRegistationMediator" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.oracle.com/sca/1.0/mediator"
wsdlTargetNamespace="http://xmlns.oracle.com/pcbpel/adapter/ftp/Experiments/NewStudentRegistration/GetNewStudentRegistrationFile%2F">
<operation name="Get" deliveryPolicy="AllOrNothing" priority="4"
validateSchema="true">
<switch>
<case executionType="queued" name="RegToBanner.insert_2">
<action>
<transform>
<part name="$out.NewstudentregistrationCollection"
function="xslt(xsl/NewStudentRegistration_To_NewstudentregistrationCollection.xsl, $in.body)"/>
</transform>
<invoke reference="RegToBanner" operation="insert"/>
</action>
</case>
</switch>
</operation>
</Mediator>
I'm a newbie to Oracle SOA. So perhaps I am missing the obvious. But I haven't read much in the documentation specifically about using the XSD validation option on the mediator and have seen nothing specifically about catching this sort of exception in the fault policy (apart from the faults I already have in my policy). Can anyone suggest what I am doing incorrectly here or perhaps whether what I am attempting to do is not possible? Thanks.
- CrisHas anyone got it working yet?
In my case, I have the following sequence:
FileAdapter -> Mediator1 -> Mediator2->DB Adapter
I am deliberately introducing validation error in File. Isn't it correct to assume Fault framework would get triggered at Mediator1 level since we are invoking FileAdapter service?
I am getting a strange behaviour. If I enable XSD validation at Mediator1 level, process is Faulted with no re-try option. However, if I enable XSD validation ONLY at Mediator2 level, I get Recoverable fault. There seems to be some disconnect between documentation and reality. I am using JDeveloper 11.1.1.3.0 version and SOA Suite 11g.
Thanks,
Amjad.
Maybe you are looking for
-
Process audio from mic and play it back. (What is wrong with my code?)
Hi, I am trying to take the audio from the mic (at javasound://0), process it (add the JMF API sample plug in GainEffect.java) and then play the processed data source. The code I have so far is below. I am getting no errors - compiles fine - but noth
-
Bpm workspace xhtml/jsf customisation
Hi, Can anyone help me with customising component.xhtml/layout.xhtml?? I would like to know how workspace differentiates default layout and customised layout. I need to include my own custom page in the new layout created using iframe but am unable t
-
Flv video format converter code in c#?
I have different types of video formats like(mp4,wmv,etc). I want to convert this video formats into .flv. Please help me by using c#,jquery .. Nothing is impossible...
-
Canon EOS Rebel T3. Need editing program that came with this camera.
I have Canon Rebel T3. Recently I had computer problems and my programs were wiped out. It is not the driver for the camera, but the editing program that came with the camera, where files were placed, cropped, sorted, etc. I have searched everywhere
-
Hi, Has anybody information on the replacing the DCjack, or is there a way of wiring up without the removing, the jack , eg; wiring to the battery charger. thanking you in anticipation. skippytu.