B2B not creating instance in SOA

Question

hello,
I am not able to create instance in my SOA composite. B2B console shows me the message as below:-
***Document Type     InvoiceUBL2***
***Document Definition     InvoiceUBL2_def***
***Document Protocol Name     InvoiceUBL2***
***Document Protocol Version     InvoiceUBL2***
***Refer To Application Message Id     Refer To Application Message Id***
***App Conversation Id     ***
***App Message property     {ACTION_NAME=null, Protocol Version=1.0, Recepient=b2buser, Endpoint=aq://IP_IN_QUEUE, Protocol=AQ}***
***Direction     INBOUND***
***State     MSG_COMPLETE***
The irony is, that all other interface which work on the same console and the same configuration are running successfully. Therefore, i dont understand where the problem lies exactly. I am the only one who is using that particular B2B defination. Please help me solve this issue.
Regards,
Shreya.

Answer 1

Hello Anuj/Venkatesh,
When i try to read the file using the Invoice UBL-2 standard Xsd, SOA cannot create an instance. So i tried reading it with the opaque schema and that create an instance in SOA. But the data comes in 64 bit binary. Is it possible that i can remove the BOM character before it reaches SOA i.e using callouts in the B2B console? because parsing 64bit binary into XML format is posing a problem now because the Invoice UBL-2 xsd comes with a lot of reference xsds. Kindly help.
Anuj- Yes, when I manually change the encoding of the file to ANSI or UTF-8 without BOM via Notepad++, an instance is created in SOA.
Regards,
Shreya.
Edited by: 918008 on Dec 29, 2012 8:37 AM
Edited by: 918008 on Dec 29, 2012 8:39 AM