This content has been marked as final. Show 3 replies
The first issue is that the system couldn't find the trading partner agreements. When I set logging on I found that it was not identifying the "to_party" correctly.Was it identifying to_party as one of the remote TP? Have you checked whether "internal" checkbox (under Channel Attributes) was enabled or not in the listening channel?
Just to force this I added the "to_party" to the file name making it %TO_PARTY%_%FROM_PARTY%_%DOCTYPE_REVISION%_%DOCTYPE_NAME% and re-named the files as appropriate. It is now able to identify the trading partner agreement.This is forced identification which should have not been required. Better try to figure out the reason why it was not able to identify to_party.
I can run the same file into the development environment and it works.It gives the clue. Can you cross-check -
1. Whether parser schema files are copied under $ORACLE_HOME/soa/thirdparty/edifecs/XEngine/config/schema and XERegistry.xml has correct entry for them (validate the path in XERegistry.xml and also cross-check the file and directory access). Make sure that servers were restarted after copying these files and it is a shared storage accessible by all the servers of the domain.
2. Download the Wire Message payload from B2B report and make sure that B2B is receiving the complete and correct file and there are no junk characters visible in the start/end of the payload.
Yes, development provided the parsers and the new XERegistry.xml. They are installed as is in development. I compared all the files using using XMLSpy to make sure they were all the same.
I will do this: "Have you checked whether "internal" checkbox (under Channel Attributes) was enabled or not in the listening channel?" and make sure it matches what is in the development environment.
I did download the wire message and looked at it in Notepad++ it looks exactly like the one I dropped in. I have however seen the issue you described in another scenerio. I also have since it map only the header information into the XML and none of the data, but this is not getting that far.
What about this -
cross-check the file and directory access). Make sure that servers were restarted after copying these files and it is a shared storage accessible by all the servers of the domain.If setup is REALLY same as development then I don't see any reason why it won't work.