Physical Filename Issue ( got past this ) and New Invalid Guideline Issue

Question

I had a problem ( from before ) getting a file called --> test_oracle.edi into the system. I am using a set up of EDI X12 over Generic Exchange together with FILE 1.0 protocol.
The file has a sender of ACME and a receiver of GLOBALCHIPS, which to be parsed correctly from the b2b.log file; however, the system had problems finding the TPA, since at this point, its FROM PARTY was set to "test".
I renamed the file from above to --> ACME_oracle.edi, and I now got past this issue, but now have a new --> invalid guideline problem, as seen in the b2b.log file.
Note that a filename of --> ACME.edi also fails.
Can someone tell me if there is a restriction on filenames and secondly can someone help me out on this --> "invalid guideline" issue.
I have emailed SANKAR my EDI file together with the b2b.log file.
I need to get past this stage, and into SOA.
Thanks as always.
Arthur (203-921-5925)

Answer 1

Arthur,
Some findings that I can share with you on this-
When using Generic Protocols like File and FTP you may want to set the following property in tip.properties file
oracle.tip.adapter.b2b.allTPInOneDirectory - If set to true, it identifies trading partner based on File Name, if false, then identifies trading partners based on FolderName.
The logic behind it explained well by Ramesh in an old post, probably you could dig-it up on the Forum.
But its surprising that you are getting an invalid guideline error, ideally it should throw
"trading partner agreement not found" error. You might also want to look at the this thread - Re: EDI over FTP
To confirm the issue - please rename your sample file with this naming convention <TPNAME>_<DOCTYPE>_<DOCREVISION>.dat, ideally if this error is because of file naming issue, it should get resolved by using this file naming convention.
and a technote from Oracle ( B2B_TN_010_Transport_File_FTP_Internal.pdf) is available on OTN, which details out the File naming conventions.
hope this helps,
Shailesh