Positional Flat File Handling in B2B

Question

Problem:
There is a big problem with handling positional flat files in Oracle B2B. We are trying to handle Positional Flat File, in UTF-8 with BOM encoding, after creating document definition and setting the agreement, we received:
B2B-51507 Error: The data starting at position 0 is not recognized as a valid data transmission.
What’s more, we remembered to locate Parser file into Config/schema location, which usually fixes problem.
Full description:
We have a sample flat file, with UNIX (LF) endline character, encoded in UTF-8 with BOM:
11B6Kamil Mazur     Lazurowa       8 12 CityABCD       PL
Junior Consultant        MyCompanyX
StreetAAAAAA       00-000 CityABCD      
First of all, we have created a guideline *.ecs and schema XSD, like that:
imgur: the simple image sharer
During XSD creation we have remembered to confirm, that our endline character is in UNIX standard (LF).
After that, we have created Parser Schema File, and paste it in the schema location in our server:
/oracle/Middleware/MyDomain/soa/thirdparty/edifecs/XEngine/config/schema,
after that we paste the schema location in XRegistry file:
imgur: the simple image sharer
After that action, we restarted SOA Server (which was running during these changes).
When SOA Server was in alive again, we’ve created a document definition :
imgur: the simple image sharer
Starting and Ending positions are from 2-5, because of BOM character existence. Then, we created Trading Partner and Inbound Agreement, based on this Document Definition:
imgur: the simple image sharer
Then we posted out test file via Generic File Listening Channel, with no Java Callout and other properties. Unfortunately, we receive error like this:
Business Message :
Id
AC18017B146145ADDCD00000178AA4F9
Message Id
AC18017B146145ADDCB00000178AA4F8-1
Refer To Message
Refer To Message
Sender Type
Name
Sender Value
Szkolenie
Receiver Type
Name
Receiver Value
MyCompany
Sender
Szkolenie
Receiver
MyCompany
Agreement Id
PersonIn
Agreement
PersonIn
Document Type
Person
Document Protocol
PositionalFlatFile
Document Version
Logistics2013
Message Type
REQ
Direction
INBOUND
State
MSG_ERROR
Acknowledgement Mode
NONE
Response Mode
ASYNC
Send Time Stamp
2014-05-19 14:00
Receive Time Stamp
2014-05-19 14:00
Document Retry Interval(Channel)
0
Document Remaining Retry(Channel)
0
Document Retry Interval(Agreement)
Document Remaining Retry(Agreement)
Native Message Size
141
Translated Message Size
Business Action Name
Business Transaction Name
Xpath Name1
Xpath Value1
Xpath Expression1
Xpath Name2
Xpath Value2
Xpath Expression2
Xpath Name3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
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 May 15 15:04:40 CEST 2014 - 1
Collaboration Id
AC18017B146145ADD9200000178AA4F7
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: (soatest.corp.prv) The data starting at position 0 is not recognized as a valid data transmission.
Error Level
ERROR_LEVEL_COLLABORATION
Error Severity
ERROR
Error Text
Payload validation error.
Wire Message:
Id
AC18017B146145ADAB400000178AA4F1
Message Id
AC18017B146145ADAB400000178AA4F1
Business Message
AC18017B146145ADDCD00000178AA4F9
Packed Message
Packed Message
Payload
Payload
Protocol Message Id
test_4value.txt@AC18017B146145ADAE500000178AA4F5
Refer To Protocol Message Id
Protocol Collaboration Id
Protocol Transport Binding
filename=test_4value.txt filesize=143 ChannelName=SzkolenieChannel file_ext=txt fullpath=/home/oracle/POC/positional/Krzysiek/test_4value.txt timestamp=2014-05-07T10:23:30.000+01:00 tp_profile_name=Szkolenie MSG_RECEIVED_TIME=Mon May 19 14:00:37 CEST 2014
Message Digest
Message Digest
Digest Algorithm
Transport Protocol
File
Transport Protocol Version
1.0
Url
file://localhost//home/oracle/POC/positional/Krzysiek
security
Transport Headers
filename=test_4value.txt filesize=143 ChannelName=SzkolenieChannel file_ext=txt fullpath=/home/oracle/POC/positional/Krzysiek/test_4value.txt timestamp=2014-05-07T10:23:30.000+01:00 tp_profile_name=Szkolenie MSG_RECEIVED_TIME=Mon May 19 14:00:37 CEST 2014
certificates
certificates
State
ERROR
Reattempt Count
Error Code
B2B-51507
Error Description
Machine Info: (soatest.corp.prv) The data starting at position 0 is not recognized as a valid data transmission.
Error Text
Payload validation error.
exchange Retry Interval
exchange Remaining Retry
Message Size
141
Payload seems to be unchanged. Problem appears, when our B2B works in Cluster (but both configuration parameters b2b.HAInstance  b2b.HAInstanceName are set properly for both soa-servers):
imgur: the simple image sharer
There are no additional info in logs :
[2014-05-19T14:07:47.994+02:00] [soa_server1] [NOTIFICATION] [] [oracle.soa.b2b.engine] [tid: DaemonWorkThread: '20' of WorkManager: 'wm/SOAWorkManager'] [userId: <anonymous>] [ecid: a8bc74c6eb84aa5b:452af1da:146046c88de:-8000-00000000000598a0,0] [APP: soa-infra] Engine: processIncomingMessageImpl: Message id = AC18017B14614616E1A00000178AA510-1 FromParty = Szkolenie Doctype = Person version = Logistics2013
That’s unfortunately all. Is there any configuration that we missed? How to fix this problem?

Answer 1

Hi Anuj,
I have added a transformation in the mediator component and I'm now able to transfer the opaque data from Oracle B2B to composite and then write the contents of flat file to another specified file thorugh file adapter.
However I still have few more issues in different scenarios:
I have tried the excercise that was mentioned in your blog:
http://www.anuj-dwivedi.blogspot.com/2011/10/handling-positionaldelimited-flat-files.html
I tried to create a flat file with two records or lines as mentioned in the blog. First line contains header information whose length is 57 characters with 5 Fileds in it. Second line contains the actual data with 57 characters and 5 fields in it. In the agreement that was created to handle this flat file, I have checked the Validate & Translate check box.
During validation, B2B is failing to treat the second line as a new record and it considering it in one record and the validation is failing as nothing is specified from 58th character in the ECS & XSD files.
Following is the error:
Error -: B2B-51507: Payload validation error.: Machine Info: (corpdevsoa10) Extra Field was found in the data file as part of Record HEADER. Record HEADER is defined in the guideline at position 1.{br}{br}This error was detected at:{br}{tab}Record Count: 1{br}{tab}Field Count: 6{br}{tab}Characters: 57 through 116
Please advice me in resolving this issue.
Thanks,
Krishna.