EDIFACT Document Identification with Oracle B2B

When receive a "document protocol identification error" on an inbound native EDI transaction set, it is possible that extraneous characters e.g. CR/LF at the end of the EDI have been added to the file. For example:

The following property setting will have Oracle B2B checks and removes them.

b2b.edi.enablePreprocess= true

The properties will need to be set in the System Mbean Browser within Enterprise manager.
Below are the steps to navigate to the System Mbean Browser, and how to invoke the B2B config Mbean.

1. Login into Enterprise manager.
2. Expand SOA
3. Right click on soa-infra
4. Select Administration
5. Select System Mbean browser
6. Expand Application Defined Mbeans
7. Expand oracle.as.soainfra.config
8. Expand the soa server domain
9. Expand B2B config
10. Select Operations
11. Select addProperty
12. Enter the desired property for the key, such as b2b.edi.enablePreprocess.
13. Enter the value, true.
14. Add any comments if desired.
15. Invoke the mbean and check the b2b-config.xml that the property is reflected in the file.
16. Restart the managed server.