Unable To Indentify Document Using File Name Format For Customidocumentplugin (Doc ID 736199.1)

Last updated on NOVEMBER 19, 2016

Applies to:

Oracle Application Server Integration B2B - Version: 10.1.2.3
This problem can occur on any platform.

Symptoms

On 10.1.2.3 in Production:
When attempting to identify an inbound message by filename with

* Document Protocol Parameter ImplementationClass set to
oracle.tip.adapter.b2b.document.custom.CustomIDocumentPlugin

* Start position of Identification for non-XML Document not set

* End position of Identification for non-XML Document not set

the following error occurs.


ERROR
oracle.tip.adapter.b2b.document.custom.CustomIDocumentPlugin:identifyIncomingDocument
could not get start pos

oracle.tip.adapter.b2b.document.custom.CustomIDocumentPlugin:identifyIncomingDocument
could not get end pos

oracle.tip.adapter.b2b.document.custom.CustomIDocumentPlugin:identifyIncomingDocument
Exit

Error -: AIP-50083: Document protocol identification error
at oracle.tip.adapter.b2b.engine.Engine.identifyDocument(Engine.java:3043)
at
oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1552)
at
oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2404)
.
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2303)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2258)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:500)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:348)
at java.lang.Thread.run(Thread.java:534)


EXPECTED BEHAVIOR
When using Generic Exchange (File, FTP, sFTP) to process inbound custom documents, if the start
and end position parameters are not set, the transport parameters Directory name Format or
Filename Format are used to identify the partner.


STEPS
1) Assuming you are configured to process messages for a custom document, navigate to Partners
-> Trading Partners -> <trading partner> -> Capabilities.

2) Click Custom link for Document Protocol.

3) Click Document Protocol Revision Details icon.

4) Change ImplementationClass setting to
oracle.tip.adapter.b2b.document.custom.CustomIDocumentPlugin and apply.

5) Navigate back to the Document Protocol Revision Details page.

6) Click the custom document type.

7) Click Update icon for the custom document type definition.

8) Verify these document parameters are not set:

Start position of Identification for non-XML Document
End position of Identification for non-XML Document

9) Revalidate the agreement and deploy a new configuration.

10) Restart B2B.

11) Send a message through and observe the error in $ORACLE_HOME/ip/log/b2b/b2b.log.



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms